Filter
Top Products
Configuring the V2IU 4350
3 - 45
Proxy provides an access point into this network and is responsible for the
E.164 dial plan using NANP (North American Numbering Plans or NAP’s).
The NAP’s in this case are 831 and 408.
Dial plan integrity is required to insure proper routing of prefix's. This means
that if users are to dial into your network, they could be required to enter a
“Prefix” on their V
2
IU with a corresponding destination IP. If the user was to
dial another user NOT destined to your network with the same beginning
prefix, the prefix configured on this V
2
IU would create a prefix match and the
call would route incorrectly. The call routes to the destination defined in the
prefix and not to the intended endpoint. The example shows “Private Video
Network A's Peering Proxy” with an inbound prefix defined as 8315…… Any
inbound call that matches 8315 with any 6 digits creates a prefix match and
sends the call to 10.10.11.1. Refer to “Regular Expressions” in the Info button
on the GUI interface for information on all the methods for defining prefixes.
Private Video Network A is one example of a V
2
IU configured in “LAN Side
Gatekeeper” mode with an ANNEX O dial method to dial “Off Net.” Internal
“On Net” endpoints registered to the LAN Side Gatekeeper will dial E.164
only. This allows any location to place calls to any location with an ANNEX O
dial plan, that is, E.164@WAN_IP or other V
2
IU's deployed on the network. In
this example a Peering Proxy has been deployed to allow dialing ingress and
egress to the Public Internet. At each V
2
IU location required to egress, the
Public Internet requires a “Prefix” to be configured. This allows that location's
endpoint to dial “Off Net” to the Public Internet. This prefix can be configured
to any digit and may be part of the externally dialed E.164 in the
E.164@WAN_IP, that is, to reach site A by dialing 4155551000@66.20.20.4
where the prefix is defined as 415* or 415……. In this example, a “9” was
chosen. The prefix is then mapped to the LAN interface of the Peering Proxy
10.10.11.1. The dial string is now 94155551000@66.20.20.4 and a strip rule for
the prefix is applied. This is needed to route the call at the destination
correctly. If the Site C V
2
IU does not strip the “9”, the destination V
2
IU fails the
call with a “No Registered Client” message (call failures can be viewed under
the “H323 Activity” page in the GUI), since the “9” becomes part of the E.164.
If you choose a prefix that matches the destination E.164, set Site A’s V
2
IU to
NOT strip matching prefixes.
NOTE: In this illustration E.164@WAN_IP was used as an example. Peering
Proxy and all V
2
IU's support user@host ANNEX O dialing methods, for
example 123@1.1.1.1 or abc@1.1.1.1 or abc@abc.com with a DNS SRV record
configured to point to an A record for the WAN IP of the V
2
IU.
The following sections demonstrate the Dial Plan for ingress and egress calls
to Private Video Network A as shown in the illustration.
Outbound from Site C to Site A
Site C dials an endpoint located at Site A: 94155551000@66.20.20.4. The
PathNavigator receives the call and generates a Q.931setup to the V
2
IU for that
subnet. The V
2
IU processes the Q.931 setup from the calling endpoint. The
V
2
IU looks for a prefix match. In this case, the “9” creates a match. The “Strip
Matching Prefix” rule is applied, the “9” is stripped, and the call is routed to