User manual POLYCOM READIMANAGERLX100

[. . . ] Polycom ReadiManager LX 100 Scheduling Administrator's Guide September 2004 Polycom ReadiManager LX100 Scheduling Administrator's Guide Copyright © 2003-2004 Polycom, Inc. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. retains title to and ownership of all proprietary rights with respect to the software contained within its products. [. . . ] An H. 320 Service must also be defined for this MCU, using the name that you specify here. Make sure that the name entered here matches the H. 320 Service name. Setting Up H. 323 Services (IP) H. 323 Services define how MCUs and Video Codecs can be reached through an IP address. The H. 323 fields required vary, depending on whether you are defining the service for an MCU or for a video codec, and depending on the specific equipment you are defining. To set up H. 323 (IP) service for an MCU or a video codec 1. (For details, see Viewing Equipment Associated with a Resource on page 63. ) Scroll down to the Equipment Parameter Information section of the Equipment form. If you want to see details of an existing H. 323 Service, click the Parameter Set link to open the H. 323 Service page. The particular fields required vary, depending on whether you are defining an MCU or a video codec. Examples of H. 323 fields for two different MCUs and a Video codec are described below, under: Fields in the H. 323 Services (IP) Form for an MGC-100. Fields in the H. 323 Services (IP) Form for a Radvision MCU-30 Fields in the H. 323 Services (IP) Form for a Codec 5. © Polycom, Inc. 79 Polycom ReadiManager LX100 Scheduling Administrator's Guide 6. For video codecs, Direct will now appear in the Default Service list. 8. Repeat steps 4 through 8 until all H. 323 services are defined. Fields in the H. 323 Services (IP) Form for an MGC-100 For an example of where to find these settings in the MGC Manager software, see Where Services are Set in MGC Manager on page 84. Field Name Service Name* IP Address* Alias* Description The name of the H. 323 service as defined in the MCU configuration. IP address connected to the service, as defined in the MCU configuration. Alias corresponding to the service, as defined in the MCU configuration. The alias for the MGC can be found in the Span tab of the H323 Service (see Figure 5-3). The Prefix for the MGC can be found in the H. 323 Service properties dialog (see Figure 5-2). Indicates whether the MCU is registered with a gatekeeper (Yes or No), and that the MCU alias will be used for calls. Ports* Prefix* Use Gatekeeper?* Fields in the H. 323 Services (IP) Form for a Radvision MCU-30 For an example of where to locate these settings in the Radvision MCU software, see Where Settings You Need Are Defined in Radvision MCU-30 Software on page 89. Field Name Service Name* Channels* Prefix* Mode** Description The name of the H. 323 service as defined in the MCU configuration. (Shown as "Description" in the Radvision software. ) Number of 64K channels. Figure Figure 5-8 shows where the prefix can be found in the MCU-30 software. Indicates whether CP--Continuous Presence (All see one)--or SW--switching (See you, see me)--will be used. (Shown as "Voice Activate Method" in the Radvision software. ) 80 Setting Up Services Chapter 5 - Setting Up and Working with Resources Fields in the H. 323 Services (IP) Form for a Codec Field Name Service Name* Alias Description The name of the H. 323 service. This is number that will be dialed if the endpoints are registered with the same gatekeeper. (If the endpoints are not registered with the same gatekeeper, they will use their regular IP address to connect. ) If endpoints are not registered with a gatekeeper, you still need to define an H. 323 service, however you should leave this field blank. Setting Up H. 320 Services (ISDN) H. 320 Services define how MCUs and Codecs can be reached through ISDN. The information required to define the ISDN service (H. 320) in Polycom ReadiManager LX100 varies for MCUs and Codecs. [. . . ] In the Administrator Console, click the Edit link for Least Cost Routing. On the page that lists the Least Cost Routing Tables, locate the table you want to edit and click the LCR Table link. In the Modify Least Cost Routing Table form, make the desired changes. · To add another LCR file, complete the details at the top of the screen and click the Add button (Figure 9-4). © Polycom, Inc. 207 Polycom ReadiManager LX100 Scheduling Administrator's Guide Figure 9-4. [. . . ]