Unfortunately i don't understand those logs. Is there something wrong with my configuration? Or any ideas what to try next? I am doing yum update now so will do another try then and see if anything changed.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joegen Baclor Sent: Thursday, October 04, 2012 1:06 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.6 Cluster Here's what happened to the bad call. Unforutenately, there is not enough information in the proxy what happened to the call prior to hitting IVR. On 10/04/2012 04:53 PM, George Niculae wrote: > On Thu, Oct 4, 2012 at 11:47 AM, darthzejdr <[email protected]> wrote: >> "201"<sip:[email protected]> >> <sip:[email protected]:56053;transport=TCP;rinstance=fbf9694cbf1534fc; >> x-sipX- >> nonat> 2472 >> "200"<sip:[email protected]> >> <sip:[email protected]:36150;rinstance=25d8170036270c5a;x-sipX-nonat> 3407 >> >> This are the current registrations, but i'm not 100% sure it was the >> same since we're constantly testing and changing. >> > Could you please yum update, there are some changes we done lately in > this area. If still see the issue, try to register 201 as UDP too so > we could isolate the problem > > 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/
