On 21/08/2010, at 12:14 AM, M. Ranganathan wrote: > 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.
Do you mean that bandwidth.com sends one invite with two routes, or two invites with separate routes in each? Is the route in the Via header? In the first invite there's just one Via line. There are no Route headers from the ITSP initially, but sipXproxy adds this one: Record-Route: <sip:172.30.0.68:5060;lr> Route: <sip:scooby.adelaide.carbonplanet.com:5070;transport=tcp;lr> Interesting. Well the two ITSP accounts aren't related to each other technically I don't think, and I only see one INVITE coming from the ITSP when I make a call. But even the registration is screwed up without making any calls. Here's the headers from the initial INVITE from the itsp (with phone numbers altered) INVITE sip:[email protected]:5080;transport=udp SIP/2.0 Via: SIP/2.0/UDP 203.2.134.10:5060;branch=z9hG4bK2n5r9p00e0i0kk4827o1.1 From: "Rxxxxxxx" <sip:[email protected];user=phone>;tag=1796322398-1282275612638- To: "Node Phone" <sip:[email protected]> Call-ID: [email protected] CSeq: 113937392 INVITE Contact: <sip:[email protected]:5060;transport=udp> Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY Accept: multipart/mixed,application/media_control+xml,application/sdp Supported: Max-Forwards: 9 Content-Type: application/sdp Content-Length: 361 > > 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. Yes it looks that way. They ack some of them but mostly not. > > If you are convinced it is a bug, send along a snapshot. Should I send the snapshot to the list? Or to a jira issue? Is there a way to obfuscate all the phone numbers in the logs? Is a log excerpt created for sipxviewer also useful? I'm looking at one that is quite strange to me, but I'm still finding my way with sip and sipxecs. Thanks Jesse > > Ranga > > > -- > M. Ranganathan Jesse Reynolds Virtual Artists Pty Ltd - http://www.va.com.au/ Phone: 08 7120 7134 (Adelaide) or 02 9043 2288 (Sydney) Mobile: 0414 669 790
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
