Cisco Cisco Meeting Server 2000 开发者指南
Cisco Meeting Server 2.0 : Customization Guidelines
8
2 WebRTC Client Customization
The recommended procedure for customization of the WebRTC client is via the API, which
requires a branding license (see
requires a branding license (see
).
Using the API allows customization of these elements of the WebRTC client:
n
sign in background image,
n
sign in dialog box – icon displayed,
n
sign in dialog box – colours used.
The branding files are held within an archive (zip) file stored on the web server. The location of
this resourceArchive is set via the API (a POST method to the "/webBridges" node or a PUT to a
"/webBridges/<web bridge id>").
this resourceArchive is set via the API (a POST method to the "/webBridges" node or a PUT to a
"/webBridges/<web bridge id>").
The Call Bridge retrieves the archive file from the web server and pushes it to the Web Bridge to
be served. In the event of a failure (for example, if the configured URI can't be reached) an alarm
is displayed in the Web Admin Interface and on the API "/system/alarms" node, but users can
still log in using the WebRTC Client.
be served. In the event of a failure (for example, if the configured URI can't be reached) an alarm
is displayed in the Web Admin Interface and on the API "/system/alarms" node, but users can
still log in using the WebRTC Client.
Note: Without a branding license you can only control the background image and logo on the
WebRTC landing page of a single Web Bridge, and this must be done via the Web Admin
Interface Configuration > General page.
WebRTC landing page of a single Web Bridge, and this must be done via the Web Admin
Interface Configuration > General page.
2.1 File Properties and Names
The branding files must be placed together in an archive file such as a zip file. The total file size of
the zipped file must be less than 1MB. The zip file is retrieved by the Call Bridge and then used by
the Web Bridge to brand WebRTC client pages.
the zipped file must be less than 1MB. The zip file is retrieved by the Call Bridge and then used by
the Web Bridge to brand WebRTC client pages.
When you zip the files, do not zip the folder containing the branded files. If this is done, this will
create an extra layer of folder (zipped file -> folder -> branded files). Instead, highlight the
branded files and right-click to zip them (or open a zip application and zip the files together).
This will create a zipped file with the branded files without creating an extra layer of folder (e.g.
zipped file -> branded files).
create an extra layer of folder (zipped file -> folder -> branded files). Instead, highlight the
branded files and right-click to zip them (or open a zip application and zip the files together).
This will create a zipped file with the branded files without creating an extra layer of folder (e.g.
zipped file -> branded files).
For example, in Figure 2, WebRTC_client.zip folder contains the branded files so when
configuring for Web Bridge customization (either via the Web Admin or API), you can use the
path http://<webserver address>/Branding/webRTC_client.zip.
configuring for Web Bridge customization (either via the Web Admin or API), you can use the
path http://<webserver address>/Branding/webRTC_client.zip.
2 WebRTC Client Customization