Hi Andy. I just looked at the snapshot. There are many TCP connections to proxy. Do you use TCP transport for the phones ? Your dns zone file shows TCP and UDP have same weight.
If you want to see the error faster, you can prioritize TCP maybe. _lvnd_ (^_^) On Thu, Jun 7, 2012 at 1:07 AM, <[email protected]> wrote: > George, > > I provided another snapshot for a server that did the same thing on 6/3. > Unfortunately, we weren't taking tcpdumps on either of these servers when > the loss of registrations happened, but going forward I will provide any of > these that I can. Some of our systems are capturing this information > continuously, but unfortunately not on those two at the time. > > > Thanks! > Andy > > ________________________________ > From: "George Niculae" <[email protected]> > To: "Discussion list for users of sipXecs software" > <[email protected]> > Sent: Wednesday, June 6, 2012 5:04:58 AM > > Subject: Re: [sipx-users] Regarding JIRA XX-10177. > > Thanks Andy, > > I took a look on the snapshot and noticed some problems in proxy logs, > discussing this with Joegen it looks like a proxy parsing issue. Not > sure if doable but it would really help if you could provide us a > capture containing sip packets from when the problem occurs > > Thanks > George > > On Fri, Jun 1, 2012 at 2:01 AM, <[email protected]> wrote: >> George, >> >> I've uploaded a snapshot of an affected system to the JIRA. This should >> have all the logs from the time the registrations were lost (restart was >> 2012-05-24 at 21:49 GMT). >> >> Let me know if you need anything else. >> >> Thanks! >> Andy >> >> ________________________________ >> From: "George Niculae" <[email protected]> >> >> To: "Discussion list for users of sipXecs software" >> <[email protected]> >> Sent: Wednesday, May 30, 2012 6:00:28 PM >> >> Subject: Re: [sipx-users] Regarding JIRA XX-10177. >> >> On Wed, May 30, 2012 at 10:26 PM, andrewpitman <[email protected]> >> wrote: >>> >>> >>> Has anyone else come across this running a recent version of >>> 4.4.0? When I say recent, I'm referring to update #15, as >>> that's the latest we're running in production. I didn't see >>> anything in the release notes for update #16 that would >>> indicate that this was something that was fixed, though. >>> >>> Basically, the server seems to simply stop responding to >>> registration requests. AFAICT, sipXproxy loses its >>> connection to sipregistrar on tcp port 5070 and needs to be >>> restarted in order to re-establish this. >>> >>> This has happened to us on multiple servers running 4.4.0 >>> update #15 with Polycom phones running 3.2.6/4.3.1 as remote >>> workers. >>> -- >> >> Didn't hear of such issue from any client running this version, can >> you get a snapshot and attach to JIRA when this happens? >> >> Thanks >> George >> _______________________________________________ >> 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/ > _______________________________________________ > 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/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
