They're all Polycom phones. Mostly 450s, with a couple of 550s, a 670 and a SoundStation 6000 in the mix. Firmware 3.2.6 with bootrom 4.3.1.
-Andy ----- Original Message ----- From: "Tony Graziano" <[email protected]> To: "Discussion list for users of sipXecs software" <[email protected]> Sent: Tuesday, August 21, 2012 1:01:03 PM Subject: Re: [sipx-users] new patch for XX-10177 can you elaborate what the UA's are that are involved in that transaction? On Tue, Aug 21, 2012 at 5:59 AM, andrewpitman < [email protected] > wrote: Joegen, George, I noticed some messages in my sipXproxy log from a hang on a customer system just today, which may or may not be pertinent. Besides the parsing errors, I also see messages such as this immediately before the hang: "2012-08-21T15:40:56.031862Z" :269589:NAT:WARNING:pbx1.sipdomain.com:SipUserAgent-2:B5EBAB 90:SipXProxy: "'83226727-F4CE51E8': Received unexpected event InviteRequest while in state 'WaitingForMediaOffer'" "2012-08-21T15:40:56.233883Z" :269590:SIP:WARNING:pbx1.sipdomain.com:SipRouter-15:B5DB9B90 :SipXProxy: "SipUserAgent::send INVITE request matches existing transaction" "2012-08-21T15:40:56.323512Z" :269591:SIP:ERR:pbx1.sipdomain.com:SipUserAgent-2:B5EBAB90:S ipXProxy: "SipUserAgent::handleMessage SIP message timeout expired with no matching transaction" "2012-08-21T15:40:56.414306Z" :269592:NAT:WARNING:pbx1.sipdomain.com:SipRouter-15:B5DB9B90 :SipXProxy: "'5FHSHt9cQ2XBS':Received unexpected event UpdateRequest while in state 'WaitingForInvite'" "2012-08-21T15:40:56.516706Z" :269593:NAT:WARNING:pbx1.sipdomain.com:SipUserAgent-2:B5EBAB 90:SipXProxy: "'5FHSHt9cQ2XBS': Received unexpected event UpdateRequest while in state 'WaitingForInvite'" "2012-08-21T15:40:56.523583Z" :269594:NAT:WARNING:pbx1.sipdomain.com:SipClientTcp-4212:B19 FAB90:SipXProxy: "'5FHSHt9cQ2XBS': Received unexpected event SuccessfulResponse while in state 'WaitingForInvite'" Since this has been happening to some of our customers more than once within a 24 hour period, in order to keep them from cancelling with us we've had to resort to a watchdog script which sends OPTIONS messages to the servers periodically and restarts sipXproxy if it fails to respond. Obviously this is just a band-aid workaround until we can resolve this issue, since this means they incur approximately 3-4 minutes of service interruption every time this happens. Joegen Baclor wrote on Mon, 20 August 2012 13:45 > I'll discuss this with GEroge later. Thanks for pointing > it out. -- _______________________________________________ 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.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ 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/
