Not sure if you fought through this yet... but the BYE comes from sipXbridge before the loop detected... Maybe the provider's timeout is shorter than sipXbridge's?
On Thu, May 19, 2011 at 2:31 PM, Matthew Kitchin (public/usenet) < [email protected]> wrote: > We just had our first dropped call for the day (problem 1 way below). > The user's exact descriptions is "Pam tried to answer, phone stopped > ringing, the caller ID continued to show on the phone but they weren’t > there. > Then, they tried to call back – exact same situation." > I have the source and destination numbers. > 260.420.2666 == called ==> 260.478.2659 > As outlined here: > > http://wiki.sipfoundry.org/display/sipXecs/Display+SIP+message+flow+using+Sipviewer > The logging level was set to info yesterday. I have copied all the logfiles > to another directory. > > I located the call using sipx-dialog-count and created the merged file with > sipx-trace > > The merged file is attached. I have to think the part that indicates 'Loop > Detected' (text below for anyone who might want to see without opening up > the trace file) is something significant. I just don't know how to interpret > what that means. These calls hit a phantom extension that forwards the call > do different users based on time of day. The originating caller in this case > was on the Verizon VoIP network as well if that is relevant. They are not on > sipx though. > > Can someone help me interpret this? I would love nothing more than to find > out it is something we have done that we can fix on our end! > > Thanks, > Matthew > > Time: 2011-05-19T17:32:47.901657Z > Frame: 45 /tmp/trace.Rmb15765/_.sipXproxy.trace.xml:232531 > /tmp/trace.Rmb15765/_.sipXproxy.trace.xml:232534 > /tmp/trace.Rmb15765/_.sipXproxy.trace.xml:232537 > /tmp/trace.Rmb15765/_.sipXproxy.trace.xml:232540 > Source: 10.81.8.233:5060 > Dest: pbx.in223.sipx.voip-SipXProxy > > SIP/2.0 482 Loop Detected > Via: SIP/2.0/TCP 10.81.8.5;branch=z9hG4bK-XX-db4eE63FH77mKA`nUsPZYNe01A > Via: SIP/2.0/UDP > 10.81.8.5;branch=z9hG4bK-XX-db4bR0_OkOpBsbtEKi7WVG3`RQ~n5ni8iV8mQWKdPxvn`UoeQ;id=5483-943 > Via: SIP/2.0/UDP > 10.81.8.5;branch=z9hG4bK-XX-db46dGyBGfB1_SR9Qo39ii6xPA~WKrtGuMJnAIM3aRYX0ds9Q > Via: SIP/2.0/UDP > 10.81.8.5;branch=z9hG4bK-XX-db3fywBaksft1JTClnd87As4JQ~WiTApnBOZUpykbQ5B_qdZw > Via: SIP/2.0/UDP 10.81.8.5:5090 > ;branch=z9hG4bKf8b2ca2d953617c847bc38aaf6e9d3f8333234;sipxecs-id=3fb19a34 > From: "DSI Holdings Lake Ave" > <sip:[email protected];user=phone><sip:[email protected];user=phone> > ;tag=436139476 > To: "12604782659 DSI Fort Wayne IN" > <sip:[email protected]><sip:[email protected]> > ;tag=3A9145DC-3BE72AC5 > CSeq: 78150433 INVITE > Call-ID: [email protected] > Record-Route: <sip:10.81.8.5:5060 > ;lr;sipXecs-CallDest=AL%2CAL%2CINT;sipXecs-rs=%2Aauth%7E.%2Afrom%7ENDM2MTM5NDc2.900_ntap%2Aid%7ENTQ4My05NDM%60%21dc29093e32cc8879a1b935177fd6db89> > User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.2.5.0508 > Accept-Language: en > Content-Length: 0 > > > > On 5/19/2011 8:35 AM, Matthew Kitchin (public/usenet) wrote: > > At this site, the largest hunt group is 8 users. > I do have some updates from yesterday. Yesterday morning, I replaced the > 550 where most of the calls are answered and I dropped the paging group from > 17 users to 15. I dropped it to 14 users late yesterday after they were done > for the day. > > This reportedly did not happen a single time yesterday. > --Problem 1, straight from the Polycom 550 user "About 7-8 times a day when > the main line rings, I go to answer it and no one is there, but on the LED > screen the first button says “answer”. You cannot pick up the call at all > and the caller hangs up and calls back." > > This reportedly only happened a single time yesterday as opposed to 50% of > the time. > --Problem 2, also from the 550 user "about 50% of the time the overhead > can’t be heard, then when you try to use the overhead a second time it rings > busy" > She is referring to the the paging group. Nobody hears anything. The paging > call then sits in the active calls list within sipx indefinitely. Usually, I > will have to restart the paging service to get everything going again. > > So, I will monitor them today and see what they say. > > On 5/19/2011 4:33 AM, Michael Picher wrote: > > Do you have a large number of phones in a hunt group to ring at the same > time? > > On Wed, May 18, 2011 at 7:37 AM, Matthew Kitchin (usenet/public) < > [email protected]> wrote: > >> No. It was a new phone. I have upgraded the firmware if that makes a >> difference. I'm replacing it today, so that will take care of that. >> -----Original Message----- >> From: "Todd Hodgen" <[email protected]> >> Sender: [email protected] >> Date: Tue, 17 May 2011 21:55:50 >> To: 'Discussion list for users of sipXecs software'< >> [email protected]> >> Reply-To: Discussion list for users of sipXecs software >> <[email protected]> >> Subject: Re: [sipx-users] Need some help, dropping calls, paging locking >> up >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > There are 10 kinds of people in this world, those who understand binary and > those who don't. > > [email protected] > blog: http://www.sipxecs.info > call: sip:[email protected] > > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected]
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
