182 Radvision Gatekeeper
P0606298 02
General Gateway Setup for Radvision ECS Gatekeeper
Interoperability
To enable the VoIP Gateway to work with the Radvision ECS gatekeeper:
•
Protocol Management / Protocol Definition / Working with Gatekeeper = Yes
•
Protocol Management / Protocol Definition / Gatekeeper IP Address = IP address of the
Radvision ECS Gatekeeper
•
Protocol Management / Protocol Definition / Gatekeeper Redundancy = No
•
Protocol Management / Protocol Definition / Register as Terminal = No
•
Protocol Management / Protocol Definition / Gatekeeper Timers should be left at their default
values.
•
Protocol Management / Protocol Definition / H.323-ID = Unique H.323-ID name for this
gateway (optional)
Setting up the Numbering Plan
The Radvision ECS 3.2 gatekeeper uses the concept of a “service” to setup a supported gateway
endpoint’s numbering plan. The service records the number prefix supported by the gateway along
with the NPI / TON classification for that prefix. Destination digits in Address Resolution
Requests (ARQs) that come to the gatekeeper are examined against the recorded services and if
there is a match, an Address Confirmation (ACF) is returned to the calling gateway, allowing the
call to be set up.
Services can be created manually within the Gatekeeper and assigned to endpoints. The VoIP
Gateway has the ability to automatically setup the necessary services via its gatekeeper registration
function.
Registration type will depend on the numbering plan being used in the network. If all numbers are
coded using only the e.164 numbering plan, the Registration Type may be set to E.164. An
H.323-ID may also be added to the registration. The only value for adding H.323-ID is that it
provides a descriptive name for the gateway in the Gatekeeper’s endpoints table. If other
numbering plans are used, the NPI / TON values must be set in the Registration Prefixes table as
follows:
•
Protocol Management / Protocol Definition /Gateway Registration Type = “NPI / TON from
Table” or “NPI/TON & H.323-ID” if an H.323-ID is also provided.
•
The number prefixes supported by the gateway are entered into Protocol Management /
Registration Prefixes table. In the prefix column, enter in the leading digits of the supported
range of telephone numbers supported by the gateway. Range values within square brackets
are also supported. For each entry, define the NPI / TON in the Type of Number columns. This
type of number must be the same type of number that a calling gateway will use when calling
a number within this range. Destination type of number is programmed in Protocol
Management / Tel -> IP Destination Numbers manipulation table.
Summary of Contents for VoIP Gateway
Page 1: ...Part No P0606298 02 August 11 2003 Norstar VoIP Gateway Configuration Guide...
Page 12: ...12 Tables P0606298 02...
Page 26: ...26 Network assessment P0606298 02...
Page 84: ...84 Configuring the VoIP Gateway time and date P0606298 02...
Page 110: ...110 Using VoIP Gateway features P0606298 02...
Page 132: ...132 Example configurations P0606298 02...
Page 186: ...186 Setting up Remote Routers for IP Telephony Prioritization P0606298 02...
Page 196: ...196 VoIP Gateway supported MIBs P0606298 02...
Page 200: ...200 Call Hold and Retrieve features P0606298 02...
Page 202: ...202 P0606298 02...