I'd also suggest looking at top if it happens again and see if the cpu is being busied out by anything. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431
Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: Scott Lawrence <[email protected]> Cc: [email protected] <[email protected]> Sent: Mon Mar 01 07:34:23 2010 Subject: Re: [sipx-users] Registration looks ok. in/out does not work 2010-03-01 13:23, Scott Lawrence skrev: > On Mon, 2010-03-01 at 11:55 +0100, Ola Samuelson wrote: > >> Hi all. >> I think i have a failing call traced. >> What happened: >> >> >> I am no expert but to me the trace of my call shows >> that sipxbridge is sending a cancel to sipxproxy on the invite >> generated by my call. >> > The CANCEL is sent 3 minutes after the INVITE - it's just the call > timing out. > > The trace you attached shows only traffic between the proxy and the > bridge. It doesn't show anything from the proxy to any other system > component, so there's no way to see what happened. > > I see the ITSP in the enclosed trace. It sends invite and waits 3 minutes then cancels. The question is why it does not get any response in 3 mins. I could at that point surf into the itsp management gui and see that sip account registrations looked fine. Newly re-registered. Where do i find more info about why the invite fails? >> I have an 158m snapshot on loglevel info to work with. >> > Create a temporary directory on your sipXecs system where you can unpack > the snapshot, then cd to that directory and execute: > > tar xzf<snapshot-file-name> > sipx-trace -o full.xml -P . > [email protected] > > are you sure that the logging on the registrar was at INFO level? > > Proxy, registrar, trunking, supervisor has log-level info. So i guess so. >> Closed for all outside access now. These options were sent >> a couple of hours before sipx malfunction. >> >> Could these access attempts have led to errors in sipx? >> > It's impossible to rule it out entirely, but especially given the > separation in time it seems very unlikely that they are related. > > ok. > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
