On Fri, Aug 20, 2010 at 10:38 AM, Worley, Dale R (Dale) <[email protected]> wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Jesse Reynolds > [[email protected]] > > Looking at the logs, something appears to be looping as there's a lot of "482 > Loop detected" messages. Even after hanging up both ends there is still this > 'loop detected' message being written to the sipxbridge.log file over and > over. > ________________________________________ > > Do you have a snapshot of a failure? > > Dale > _______________________________________________
Loop Detected is returned to the ITSP when sipxbridge detects two routes for an inbound INVITE. Some ITSPs (bandwidth.com in particular), send the INVITE to sipx following two routes as a redundancy and load balancing strategy. SIpxbridge will reject one of these with a LOOP DETECTED. The "Over and Over" part is because the ITSP is not ACKing the LOOP Detected (at least that is my guess). Please look at the logs using sipviewer and check if that is the case. If you are convinced it is a bug, send along a snapshot. Ranga -- M. Ranganathan _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
