|
|
|
| Configuring site settings |
|
|
|
|
|
|
|
|
| Field | Field description | Usage tips |
|
|
|
| address. Changes to this page are not | conferences page and the conference |
|
|
|
| saved if a connection cannot be made to | URL displayed on the Edit conference |
|
|
|
| the specified address or it is not that of this | page. Otherwise links to conferences |
|
|
|
| Content Server. | use the address that you typed in the |
|
|
|
|
| browser URL to log in to the Content |
|
|
|
|
| Server. |
|
|
|
|
|
|
|
|
| Gatekeeper |
|
|
|
|
| settings |
|
|
|
|
|
|
|
|
|
|
| Registration | Displays the status of Content Server | Click View all gatekeeper |
|
|
| status | registration with the gatekeeper (registered | registrations to display a page showing |
|
|
|
| or not registered). | all the system and Recording alias |
|
|
|
|
| registration details. See Displaying |
|
|
|
|
| gatekeeper registrations. |
|
|
|
|
|
|
|
|
| Gatekeeper | Select to register with the gatekeeper. | Enter the Gatekeeper address, an |
|
|
| enabled |
| H.323 ID and/or an E.164 alias and |
|
|
|
|
| choose the Registration mode. |
|
|
|
|
| The gatekeeper must be enabled for a |
|
|
|
|
| cluster – it is not possible to disable the |
|
|
|
|
| gatekeeper functionality. |
|
|
|
|
|
|
|
|
| Gatekeeper | Always Manual. | Manual gatekeeper discovery means |
|
|
| discovery |
| that the Content Server registers with |
|
|
|
|
| one specific gatekeeper, identified by its |
|
|
|
|
| IP address or fully qualified domain |
|
|
|
|
| name. |
|
|
|
|
|
|
|
|
| Gatekeeper | The IP address or DNS name of the |
|
|
|
| address | gatekeeper. |
|
|
|
| H.323 ID | Other systems can call the Content Server | If the Content Server is in a cluster, its |
|
|
|
| using the H.323 ID if the Content Server is | H.323 ID is not set here but in the |
|
|
|
| registered to the gatekeeper. The | server overview page. |
|
|
|
| Recording alias specified in the Default |
|
|
|
|
| Recording aliases below is used for the |
|
|
|
|
| call. |
|
|
|
|
|
|
|
|
|
| E.164 alias | Other systems can call the Content Server | If the Content Server is in a cluster, its |
|
|
|
| using the E.164 alias if the Content Server | E.164 alias is not set here but in the |
|
|
|
| is registered to the gatekeeper. The | server overview page. |
|
|
|
| Recording alias specified in the Default |
|
|
|
|
| Recording aliases below is used for the |
|
|
|
|
| call. |
|
|
|
| Registration | Choose to register the Content Server as a | If you select Gateway enter the H.323 |
|
|
|
| Terminal or as a Gateway. | gateway prefix and the E.164 gateway |
|
|
|
|
| prefix. The registration mode for a |
|
|
|
|
| cluster must be Gateway. |
|
|
|
|
|
|
|
|
| H.323 gateway | If registered as a gateway, this prefix must | For a cluster, enter |
|
|
| prefix | be entered before the H.323 ID of a | H.323 and E.164 gateway prefixes. The |
|
|
|
| Recording alias when calling the Content | prefixes you enter cannot be subsets of |
|
|
|
| Server. | each other; make sure they are unique |
|
|
|
|
| and that they follow the dialing plan set |
|
|
| E.164 gateway | If registered as a gateway, this prefix must |
| |
|
| up on your VCS. The |
| ||
|
| prefix | be entered before the E.164 alias of a | prefix will be used for Recording aliases |
|
|
|
| Recording alias when calling the Content |
| |
|
|
| with no live streaming outputs; the live |
| |
|
|
| Server. |
| |
|
|
| gateway prefix will be used for |
| |
|
|
|
|
| |
|
|
|
| Recording aliases with live streaming |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Cisco TelePresence Content Server 4.1 printable online | Page 86 of 121 |
| |
Page 86
Image 86
