|
| Chapter 3 - MGC+ Software Installation and Configuration |
|
|
|
| Table | |
|
|
|
| Field | Description |
|
|
|
| Prefix | Enter a number to be used by H.323 participants to dial |
|
| to the MCU as part of the |
|
| Enter 789 to use the default Entry Queues and Meeting |
|
| Rooms shipped with the MGC+ unit without modifying |
|
| their properties. |
|
| When PathNavigator is used, this prefix automatically |
|
| registers with the gatekeeper. When another |
|
| gatekeeper is used, this prefix must also be defined in |
|
| the gatekeeper. |
|
|
|
| SIP | Select this check box to indicate that SIP participants |
|
| can connect to the MCU using this service. Then select: |
|
| • Specify - to manually define the SIP server. |
|
| • Auto - to automatically detect the SIP server’s IP |
|
| address if a DHCP or if a DNS Server is defined. |
|
|
|
| SIP Server IP | If |
| Address or | enter either the IP address of the preferred SIP server |
| Name | or its host name (if a DNS server is used). |
|
|
|
| Domain Name | Conferences and Entry Queues can be registered in the |
| or IP Address | proxy in the format user@host. for example, |
|
| EQ1@polycom.com, where EQ1is the user part and |
|
| polycom.com is the host part. |
|
| When dialing to a conference or Entry Queue, the SIP |
|
| server expects to receive the host either as domain |
|
| name or as an IP address. |
|
| The domain name is used for identifying the SIP server |
|
| in the appropriate domain according to the host part in |
|
| the dialed string. For example, when the call to |
|
| EQ1@polycom.com reaches the outbound proxy, this |
|
| proxy looks for the SIP server in the polycom.com |
|
| domain to which it will forward the call. |
|
| When this call arrives at the SIP server in polycom.com, |
|
| the server looks for the registered user (EQ1) and |
|
| forwards the call to this Entry Queue or conference. |
|
|
|