(if you remember most of Mike's postings, they usually have to deal with a particular ITSP, sounds like he's made some headway though!)
On Wed, Dec 8, 2010 at 10:19 AM, Nikolay Kondratyev <[email protected]> wrote: > LOL! > > Rgds, > Nikolay. > > ------------------------------ > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Burden, Mike > *Sent:* Wednesday, December 08, 2010 6:09 PM > > *To:* 'Discussion list for users of sipXecs software' > *Subject:* Re: [sipx-users] Disconenct at exactly the two hour mark > > Just in case anyone is following this and wondering what the answer > turned out to be…. > > > > The ITSP’s switch was configured to force a disconnect at the two hour mark > (presumably to prevent “run away” calls where the phone didn’t get properly > hung up or something.) > > > > The INFO thing looks like it was a red herring. > > > > > > [image: Description: cid:[email protected]] > > * **Mike Burden* > > [image: Description: Lynk.gif]* > Lynk Systems, Inc* > > * e-mail:* [email protected] > > * Phone:* 616-532-4985 > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Nikolay Kondratyev > *Sent:* Wednesday, December 08, 2010 3:34 AM > *To:* 'Discussion list for users of sipXecs software' > *Subject:* Re: [sipx-users] Disconenct at exactly the two hour mark > > > > Interesting questions... > > > > Afaik, sipx does not implement INFO method. So 405 is quite legitimate > answer. > > > > > By the way, you show the call going from itsp to sipx. I wonder if the > situation is the same when the call goes from sipx to itsp? > > The thing is that sipxbridge includes Allow header in the invite messages, > and this Allow header does not contain Info. This, as far as i know, should > prevent the other side form sending INFO. > > > > But sipxbridge does not include Allow header in 200Ok for incoming call. > > Sipxbridge should do it, doesn't it? > > Should an issue be raised? > > > > Regarding the second question: > > I tried to find "normative reference" if there is any rules how INFO > requests are processed (namely if UAC must/must not/may terminate a call > when getting 405 in reply to INFO), but alas... > > May be others are more knowledgeable... > > May be that it's up to UAC, what to do with this situation... > > > > Rgds, > > Nikolay. > > > > ------------------------------ > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Burden, Mike > *Sent:* Wednesday, December 08, 2010 12:01 AM > *To:* Discussion list for users of sipXecs software( > [email protected]) > *Subject:* [sipx-users] Disconenct at exactly the two hour mark > > We’ve had a number of calls disconnect at exactly the two hour mark. > > > > Running a trace, I found that the ITSP sent us an INFO, we returned a NOT > ALLOWED, and the ITSP responded with a BYE. > > > > If I parse this right, it looks like the INFO was just informational to let > us know the call duration and signal quality so far. > > > > 1. Was NOT ALLOWED the correct/desired response from sipXecs? > > > > 2. Was terminating the call a valid response from the ITSP after > receiving the NOT ALLOWED reply? > > > > > > > > Here is are the three packets in question. There were no SIP packets > between these packets. Identifying info has been redacted. > > > > > > At 15:19:44.946, the ITSP sent me an INFO: > > > > Time: 2010-11-30T20:19:44.946000Z > > Frame: 134 /tmp/trace.yFcp6069/_.sipxbridge.trace.xml:302802 > > Source: ITSPIPAddr:5060 > > Dest: ls-sip1.lynk.com-sipXbridge > > > > INFO sip:myphonenum...@sipxecsipaddr:5080;transport=udp SIP/2.0 > > Via: SIP/2.0/UDP > SipProxyIPAddr:5060;branch=z9hG4bK-d8754z-d145746366dfbc12-1---d8754z-;rport=5060;received=ITSPIPAddr > > Via: SIP/2.0/UDP ITSPIPAddr:5061;branch=z9hG4bK-vqmzrjdsx3ziootw;rport=5061 > > Record-Route: <sip:myphonenum...@sipproxyipaddr;lr> > > From: <sip:numberical...@itspipaddr;user=phone>;tag=b6ozx43ypndfo4qp.i > > To: "sipxbridge" <sip:myphonenum...@sipxecsipaddr>;tag=4094594954750048626 > > Call-ID: CallID > > CSeq: 928 INFO > > Contact: "Anonymous" <sip:SipProxyIPAddr:5060> > > Max-Forwards: 69 > > User-Agent: Sippy > > Cisco-guid: H323ConfID > > H323-conf-id: H323ConfID > > Content-Type: application/dtmf-relay > > Content-Length: 25 > > > > Signal=3 > > Duration=1640 > > > > > > Which my system apparently rejected as NOT ALLOWED at 15:19:44.953: > > > > Time: 2010-11-30T20:19:44.953000Z > > Frame: 135 /tmp/trace.yFcp6069/_.sipxbridge.trace.xml:302833 > > Source: ls-sip1.lynk.com-sipXbridge > > Dest: ITSPIPAddr:5060 > > > > SIP/2.0 405 Method not allowed > > Via: SIP/2.0/UDP > SipProxyIPAddr:5060;branch=z9hG4bK-d8754z-d145746366dfbc12-1---d8754z-;rport=5060;received=ITSPIPAddr > > Via: SIP/2.0/UDP ITSPIPAddr:5061;branch=z9hG4bK-vqmzrjdsx3ziootw;rport=5061 > > From: <sip:numberical...@itspipaddr;user=phone>;tag=b6ozx43ypndfo4qp.i > > To: "sipxbridge" <sip:myphonenum...@sipxecsipaddr>;tag=4094594954750048626 > > Call-ID: CallID > > CSeq: 928 INFO > > Server: sipXecs/4.2.0 sipXecs/sipxbridge (Linux) > > Content-Length: 0 > > > > > > The ITSP hung up on me at 15:19:54.954: > > > > Time: 2010-11-30T20:19:54.954000Z > > Frame: 136 /tmp/trace.yFcp6069/_.sipxbridge.trace.xml:302839 > > Source: ITSPIPAddr:5060 > > Dest: ls-sip1.lynk.com-sipXbridge > > > > BYE sip:myphonenum...@sipxecsipaddr:5080;transport=udp SIP/2.0 > > Via: SIP/2.0/UDP > SipProxyIPAddr:5060;branch=z9hG4bK-d8754z-b5e7f1354b9cf838-1---d8754z-;rport=5060;received=ITSPIPAddr > > Via: SIP/2.0/UDP ITSPIPAddr:5061;branch=z9hG4bK-cqtg4sgjt7pwslve;rport=5061 > > Record-Route: <sip:myphonenum...@sipproxyipaddr;lr> > > From: <sip:numberical...@itspipaddr;user=phone>;tag=b6ozx43ypndfo4qp.i > > To: "sipxbridge" <sip:myphonenum...@sipxecsipaddr>;tag=4094594954750048626 > > Call-ID: CallID > > CSeq: 929 BYE > > Contact: "Anonymous" <sip:SipProxyIPAddr:5060> > > Max-Forwards: 69 > > User-Agent: Sippy > > Cisco-guid: H323ConfID > > H323-conf-id: H323ConfID > > Content-Length: 0 > > > > > > > > > > > > > > > > [image: Description: cid:[email protected]] > > * **Mike Burden* > > [image: Description: Lynk.gif]* > Lynk Systems, Inc* > > * e-mail:* [email protected] > > * Phone:* 616-532-4985 > > > > > > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
