Appendix D - Polycom PathNavigator™ Configuration Summary

Download as PDFDownload as PDF

This example assumes installation has been successfully completed and an Administrator password has been set. Where a configuration option is not mentioned, it can be ignored or left unchecked. Always select Submit (or OK) before leaving a page or pop-up configuration window, to confirm and save any changes.

Configuration>General>Gatekeeper Identifier: Suitable name
Configuration>General>Gatekeeper Description: Suitable description
Configuration>Registration Policy: Predefined Endpoints Only
Configuration>Registration Policy> Registration timeout: 999
Configuration>Registration Policy> Offline timeout: 300
(Submit)

Configuration>Call Policy>Routing Mode: Direct
Configuration>Call Policy>Show messages on Polycom: Checked
Configuration>Call Policy>Neighbour gatekeeper hop count: 9
(Submit)

Configuration>Routing and Policies>Network Topology>Networks>Add

Network name: Suitable name
Endpoints within this network…zone: Checked
Country Code: 044
Area Code: Local telephone code
# of digits: 6
Did Assignment: both zero
IP Config:
Default Group Policy: Everyone
Default LCR table: None

(OK)

Configuration>Routing and Policies>Network Topology>WAN Links>Internet/VPN>Add

WAN Link Name: Link to JANET (or similar)
First network in path: name of the network created in the last step
Other networks reached…: None
Max bandwidth: Suitable value
Max Bit Rate: 768 (or other suitable value)

(OK)

Configuration>Routing and Policies>Network Topology>Network Addresses>Add

IP address: single machine or Class C address (latter ends in .0)
Subnet mask: single machine: 255.255.255.255; Class C: 255.255.255.0
Max Video bandwidth: suitable value (2,000 suggested)
Max bit rate: suitable value (768 suggested)

(OK)

Repeat the above step until all networks (with endpoints) administered by this PathNavigator have been added.

Configuration>Neighbor Gatekeeper>Neighbors>Add

Description: JVCS Directory Gatekeeper
IP: aaa.bbb.ccc.ddd (IP address supplied by JVCS)
Prefix: Leave blank
# of digits to strip: 0
Prepending String: leave blank
Port: 1719

(OK)

Repeat the above step for the second JVCS directory gatekeeper, substituting its numeric IP address.

Configuration>Neighbor Gatekeeper>Local Zone Prefixes>Add:

Description: Gatekeeper name (this gatekeeper – as in ‘gatekeeper identifier’ above)
Prefix: 0044xxxxx (xxxxx = 5-digit zone number supplied by JVCS-MC)

(OK)

Note: an alternative approach: If the Configuration>Registration Policy is originally set to ‘Everyone’, then each legitimate endpoint registers, and is visible on the Monitor>Endpoints page. The Configuration>Registration Policy can then be re-set to ‘Predefined Endpoints’ and the next step can be omitted, as the endpoints registered at the time of making the change will be retained in the endpoint list.

Monitor>Endpoints>Add:

Type: Terminal
IP Address: complete for Static/DHCP; enter IP address of terminal
Call Signalling Port: 1720
Expiration: Never
Use default from network
Group Policy: Everyone
Alias type(1): E.164
Alias value(1): terminal extension number (the terminal’s local ‘extension’ number)
Alias type(2): H.323 ID
Alias Value(2): terminal-jvcs-reg-name@domain (substitute your correct values)

(OK)
Repeat the above step until all terminals are known to the gatekeeper.

End of Configuration