Office SIP Dialing Loop Detected.

[f0netech]

Our company has 2 Operation's Centers offices, one in the Eastern portion of the U.S. and one on the Western portion with branch offices located throughout the US, Canada and PR. The Primary servers are S8720 located at the Eastern Operations centers and the majority of the voice traffic is routed using SIP trunks at both centers.

The branch offices are primarily G350 and G450 gateways that register to the S8720's.

Within the branch offices, the route patterns dial calls out the SIP trunks but was recently discovered that the route patterns in our Puerto Rico branch were only using local trunks. As we tried to correct this, we saw the following occur when tracing the station of the individual testing locally with us. Note the active trunk group is a SIP trunk and all route patterns are setup similar to other branch offices that work fine.

active station XXXXXX cid 0x1c3a
dial 91787529XXXX routeREFIX:HNPA:ARS
term trunk group 120 cid 0x1c3a
dial 91787529XXXX routeREFIX:HNPA:ARS
route-pattern 734 preference 1 cid 0x1c3a
seize trunk-group 120 member 161 cid 0x1c3a
Calling Number $ Name NO-CPNumber NO-CPName
SIP>INVITE sip: 787529XXXX@XX.XX.XX.XX SIP/2.0
setup digigits 787529XXXX
Calling Number and Name 787758XXXX Calling Name
SIP<SIP/2.0 100 Trying
Proceed trunk-group 120 member 161 cid 0x1c3a
SIP<INVITE sip:787529XXXX@company.com SIP/2.0
SIP>SIP/2.0 302 Loop detected by CM
SIP<SIP/2.0 302 Loop detected by CM
SIP>ACK sip:787529XXXX@XX.XX.XX SIP/2.0
dial 78
denial station XXXXXX cid 0x1c3a

I have found enough of the subject online to understand that the Loop indicates multiple SIP requests of the same nature were sent prior to the SIP acknowledgement, however 302 does not appear to be the correct error code and because this pattern is setup just as all the others within our infrastructure, where are the multiple requests coming from.

If anyone has suggestions on this, would be greatly appreciated.

 

[montyzummer]

do the same trace on the station with a /s after the station number

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[montyzummer]

is this ses or session manager ??

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[f0netech]

We are using SES.

 

[montyzummer]

Have a look at this link pretty sure its your issue

https://support.avaya.com/ext/index?page=content&id=SOLN121014&group=UG_ENTITLED_CUSTOMER

Session Initiation Protocol (SIP)/2.0 302 Loop is detected by Communication Manager (CM). SIP Enablement Services (SES) does not terminate calls.
Nov 12 11:57:49 2007 matching filter label <8111>: sipix.mrpg.net: [Recv Response]

{connection: Unavailable}

Cause
Incorrect route to destination. Connection is not available.




Solution
SES has wrong map to destination of call. User needs to delete the wrong map.

Remove the wrong map. After removing of wrong map, SES will start to communicate without "SIP/2.0 302 Loop detected by CM".
Maps must be unique.Maps for hosts mapping must have no similar maps for media server maps.
Example: Host map388[0-9]{9} will not work simultaneously with Media Server map 388005068800.
The good 'pointer' that user creates non-unique maps is "SIP/2.0 302 Loopdetected by CM".

APSS (SME)
ACSS (SME)
ACIS (UC)