Trunk-To-Trunk Routing Example - AudioCodes Mediant 1000 User Manual

SIP User's Manual
Below is an example of RADIUS Accounting, where the non-standard parameters are
preceded with brackets.
Accounting-Request (361)
user-name = 111
acct-session-id = 1
nas-ip-address = 212.179.22.213
nas-port-type = 0
acct-status-type = 2
acct-input-octets = 4841
acct-output-octets = 8800
acct-session-time = 1
acct-input-packets = 122
acct-output-packets = 220
called-station-id = 201
calling-station-id = 202
// Accounting non-standard parameters:
(4923 33) h323-gw-id =
(4923 23) h323-remote-address = 212.179.22.214
(4923 1) h323-ivr-out = h323-incoming-conf-id:02102944 600a1899
3fd61009 0e2f3cc5
(4923 30) h323-disconnect-cause = 22 (0x16)
(4923 27) h323-call-type = VOIP
(4923 26) h323-call-origin = Originate
(4923 24) h323-conf-id = 02102944 600a1899 3fd61009 0e2f3cc5
7.11

Trunk-to-Trunk Routing Example

This example describes two devices, each interfacing with the PSTN through four E1
spans. Device A is configured to route all incoming Tel-to-IP calls to Device B. Device B
generates calls to the PSTN on the same E1 trunk on which the call was originally received
(in Device A).
Device A IP address: 192.168.3.50
Device B IP address: 192.168.3.51
The ini file parameters configuration for devices A and B include the following:
1. At both devices, define four trunk groups, each with 30 B-channels:
•
TrunkGroup_1 = 0/1-31,1000
•
TrunkGroup_2 = 1/1-31,2000
•
TrunkGroup_3 = 2/1-31,3000
•
TrunkGroup_4 = 3/1-31,4000
2. At Device A, add the originating Trunk Group ID as a prefix to the destination number
for Tel-to-IP calls:
AddTrunkGroupAsPrefix = 1
3. At Device A, route all incoming PSTN calls starting with prefixes 1, 2, 3, and 4, to the
IP address of Device B:
•
Prefix = 1, 192.168.3.51
•
Prefix = 2, 192.168.3.51
•
Prefix = 3, 192.168.3.51
•
Prefix = 4, 192.168.3.51
Note: You can also define Prefix = *,192.168.3.51, instead of the four lines above.
Version 5.4 421
7. IP Telephony Capabilities
May 2008