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. 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. Linux systems when they are operating normally have very little "free" space, because they keep copies of various disk files in memory. If the programs need space, the kernel will dispose of the file copies. What is very important is that the rate of swap operations is very low, preferably zero. "vmstat" and "xosview" will display the rate of swaps. 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
