On Tue, 2009-02-17 at 09:20 +0100, Matus wrote: > Hello, > > On Monday 16 of February 2009 17:49:52 Dale Worley wrote: > > On Mon, 2009-02-16 at 09:17 +0100, Matus wrote: > > > thanks for answer. :-) Strange is that is acting like that only for 5 - > > > 10% of all calls from same provider and same number. And when i was > > > comparing packet traffic only difference is on sipx end, it start with > > > "SIP/sipfrag Request: NOTIFY sip:[email protected]:5060, with > > > Sipfrag(SIP/2.0 503 Service Unavailable)." > > > > If a SIP message contains a sipfrag, then the message is reporting that > > the network element received the contained message (in this case, "503") > > from some other element. You want to determine where the 503 message > > came from, as it indicates a serious error. > > > > 503 is produced by sipx server. This is why i was looking at the memory ... > Machine is not overloaded ... there is in or outgoing call ( except mine ), > there is plenty of memory, no swap and load is under 1. > What else can trigger this error ?
I don't believe that -- I don't think that there is any situation where sipX can generate a 503. What I think you are seeing is a 503 sipfrag *inside* a different message, which different message was generated by sipX. What you need to determine is where the original 503 came from. Can you cut the message in question into a file and attach it to an e-mail? (Do *not* cut-and-paste it directly into the e-mail, which will likely damage its formatting badly.) > > In your case, I suspect your ITSP is producing the 503, and that it is > > doing so incorrectly -- 503 is supposed to be used only to indicate an > > overload condition (see RFC 3261 section 21.5.4). > > > > > Today i found out that in this moment there is only 8MB of memory free on > > > my sipx machine, can this be a problem ? There is plenty of not used > > > swap. > > > > No swap is used, right now machine is using around 25 - 50MB free ... > I was just guessing if there is no build in mechanism preventing using > swap ... > but it isn't :) It doesn't matter if swap space is *used*, what you care about is the *rate* at which paging/swapping is done. Linux systems often have a considerable amount of information parked in swap space, but it is programs and things that aren't accessed (or rather, very rarely), so it doesn't affect performance. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
