Nortel Networks TP-1610 SIP user manual PRI to SIP Calls, IP to Trunk Group Routing Table

Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description

For the SIP2PRI gateway to be able to apply the routing rules on the combined string, the prefix (domain name and trunk group) must previously be defined in the IP to Trunk Group Routing table either using the Embedded Web Server (refer to screen below) or via the ini file:

Figure 8-4: IP to Trunk Group Routing Table

Via the ini file:

PSTNPrefix = nortelnetworks.com/TrkGrp3,2

Thus, in the above example, any number starting with the prefix ‘nortelnetworks.com/TrkGrp3’ is routed to trunk group number 2.

Using the routing table, any combination of domain name and trunk group name can be routed to any trunk group.

Note: To route calls to the trunk group before modifying the called number, add the parameter ‘RouteModeIP2Tel = 0’ to the ini file.

After applying the routing rule (the trunk to which the call is to be routed is already determined), it is possible to modify the combined called number (before it is sent to the PRI ISDN) to its initial state by removing the created prefix:

•Using the ini file parameter ‘RemovePrefix = 1’; the called number is automatically modified (by removal of the prefix) to the original called number ‘2145551234’.

•Setting ‘RemovePrefix = 0’ and using the number manipulation rules (either via the Embedded Web Server or the ini file as described below):

NumberMapIP2Tel = nortelnetworks.com/TrkGrp3,26

8.13.1.2 PRI to SIP Calls

Trunk group ID and domain name are added to the generated INVITE messages for ISDN IP calls.

For example:

INVITE sip:8795551212@nortelnetworks.com:5060;norteltrkgrp=5;user=phone SIP/2.0

The PRI2SIP gateway sends SIP INVITE message with a trunk group number (marked in blue), preceded by ‘norteltrkgrp’ (hard-coded string) and domain name (marked in red).

The trunk group number is automatically determined as the trunk group from which the call was received (for detailed information on trunk groups, refer to Section 5.8.4.2 on page 51).

Version 4.4 159 July 2005