Specifications

Spectralink 84-Series with AudioCodes Gateway and Avaya Communication Manager: Interoperability Guide
1725-86914-000_C.docx
September 2013 58
5 Submit and Burn.
Note: Ensure correspondence between PBX and Mediant Gateway
Configure a destination index for every unique set of numbers that you define in the
AAR routing table (see Chapter 6 section 7). Using this method you will have a one to
one correspondence between patterns entered into the AAR table destined for this
Mediant Gateway and pattern indices you create here.
Detecting a routing loop
Routing loops are detected by the appearance of certain patters in the syslog. By way of
explanation, consider the following example.
Using our example number ranges we will define extensions 7xxx to reside on the Mediant
Gateway, and tell the PBX to send all calls destined for extensions in the 7xxx range out the PRI
circuit to the Mediant Gateway. Imagine if extension 7001 was not currently registered on the
Gateway. Without providing an alternate number to route such calls to, the Mediant Gateway
would just send the request back to the PBX. The PBX would look at the invite and route the call
back to the Mediant Gateway. This is a loop. Here we have the D-channel attempting to set up
this call, but since no one is around to accept it, the call would never get set up. It would be
rather difficult to tell this was occurring without looking at syslog output from the Mediant
Gateway. In our testing our syslogs showed many repeated attempts to set up calls to the same
number going back and forth between the Mediant Gateway and the PBX. The above
configuration would resolve this.