Thanks, i'll do that. It shouldn't be busy. It does not run anything really and there are fewer than 100 calls per day.
Can i safely ignore messages in logs regarding: - "2010-02-26T07:09:22.090660Z":212878:KERNEL:ERR:sip.flyglinjen.se:SipServerBroker-8:FFFFFFFF:SipRegistrar:"OsServerSocket: accept(-1) error: 22=Invalid argument" - 2010-02-26 08:10:05 [CRIT] switch_loadable_module.c:839 switch_loadable_module_load_file() Error Loading module /usr/local/freeswitch/mod/mod_spidermonkey.so ..and more... - "2010-02-18T10:31:56.351371 ":ERR:, ERROR: null value in column "from_tag" violates not-null constraint - "2010-02-18T11:23:43.015957 ":ERR:, ERROR: duplicate key violates unique constraint "cdrs_call_id_unique - "2010-02-26T03:13:27.141908Z":1625050:KERNEL:INFO:sip.flyglinjen.se:SipClientTcp-14002:89EE7B90:SipXProxy:"OsConnectionSocket::read[4] error or EOF on fd 286, errno = 0 Success" - "2010-02-26T03:12:37.849853Z":1624874:INCOMING:INFO:sip.flyglinjen.se:SipClientUdp-8:B7A4BB90:SipXProxy:"Read SIP message:\n----Remote Host:192.168.1.25---- Port: 5090----\nSIP/2.0 482 Loop detected\ - "2010-02-26T00:36:18.382660Z":1547587:KERNEL:WARNING:sip.flyglinjen.se:OsTimer-9:B794AB90:SipXProxy:"OsTimerTask::run firing took 21108 usecs, queue length = 2676" If not...what do i do about these things? I think there should never be loops. How does one find the reason for loops? 2010-03-01 13:40, Tony Graziano skrev: > 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: tgrazi...@myitdepartment.net > > 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: sipx-users-boun...@list.sipfoundry.org > <sipx-users-boun...@list.sipfoundry.org> > To: Scott Lawrence<scottlawr...@avaya.com> > Cc: sipx-users@list.sipfoundry.org<sipx-users@list.sipfoundry.org> > 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 . >> 152920547f74d2d024b35f777c313...@111.83.208.29 >> >> 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 sipx-users@list.sipfoundry.org >> 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 sipx-users@list.sipfoundry.org 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/
