23 Nov
2015
23 Nov
'15
3:37 p.m.
Hello Daniel, Dirk,
I'm also seeing that these errors seems to be related to the load. Because
the errors are present during peak of traffic.
Many of the cases are not updates but new calls.
Regarding to the file descriptors : I set the limit to 500000:
Max open files 500000 500000 files
And if I had a look to the opened files with, globally, "lsof | grep rtppro
| wc -l", there is still less than 1000.
RTPProxy is already running with -d DBUG. I can see that there are update
which fail because the log is associated to a call handled into On Reply
Route.
How can be explained that the RTPProxy can't find the call? And what is the
impact on the call?
Regards,
Igor.
-----Message d'origine-----
De : sr-users [mailto:sr-users-bounces@lists.sip-router.org] De la part de
Daniel-Constantin Mierla
Envoyé : lundi 23 novembre 2015 09:33
À : Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Objet : Re: [SR-Users] Kamailio/RTPProxy incorrect port 0
Hello,
typical reasons for this error are:
- the session is not found by rtpproxy (if it was an update command)
- rtpproxy run out of file descriptors (check the limits of your system
regarding opened files per process)
- some internal error of rtpproxy (see if there are errors in syslog from
rtpproxy, you can also run it in debug mode with -D DBUG command line
parameters)
Cheers,
Daniel
On 23/11/15 09:09, Dirk Teurlings - SIGNET B.V. wrote:
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced
Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
I'm seeing the exact same message sometimes as
well.
For me it seems to be tied to volume, as soon as a lot of calls are
coming from an interconnect this could occur. Also, as soon as this
happens both incoming and outgoing calls have audio problems.
My RTP instance isn't as much patched as your version, and I'm also
not seeing the other INFO packages, just the 0 port error message.
Any insight would be appreciated.
Dirk
On 20-11-15 19:25, Igor Potjevlesch wrote:
> To complete my message, each "incorrect port 0
" is preceded with the
> following logs:
>
> rtpproxy[3289]:
>
INFO:rtpp_command_ul_handle:ebf8863557e5c8709e46ba48c1f8f780@10.5.129.117:
RTP packets from caller will be resized to 20 milliseconds
rtpproxy[3289]: ERR:rtpp_command_pre_parse:GLOBAL: update/create
command syntax error: invalid number of arguments (1)
I use the following version:
rtpproxy -v
Basic version: 20040107
Extension 20050322: Support for multiple RTP streams and MOH
Extension 20060704: Support for extra parameter in the V command
Extension 20071116: Support for RTP re-packetization
Extension 20071218: Support for forking (copying) RTP stream
Extension 20080403: Support for RTP statistics querying
Extension 20081102: Support for setting codecs in the update/lookup
command
Extension 20081224: Support for session timeout notifications
Extension 20090810: Support for automatic bridging
Extension 20140323: Support for tracking/reporting load
Extension 20140617: Support for anchoring session connect time
Extension 20141004: Support for extendable performance counters
Extension 20150330: Support for allocating a new port ("Un"/"Ln"
commands)
Extension 20150420: Support for SEQ tracking and new rtpa_ counters;
Q command extended
Regards,
Igor.
*De :*Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com]
*Envoyé :* vendredi 20 novembre 2015 19:09 *À :*
sr-users(a)lists.sip-router.org *Objet :* Kamailio/RTPProxy incorrect
port 0
Hello,
I can't figure out why Kamailio reports hundreds of calls with the
following error:
"/usr/local/sbin/kamailio[2997]: ERROR: rtpproxy [rtpproxy.c:2727]:
force_rtp_proxy(): incorrect port 0 in reply from rtp proxy"
It seems that each time this error occurs, we got a one-way audio call.
I already check and increase the limit for opening files that the
process can open with ulimit -n 500000. But, anyway, if I look to
/proc/$PID/fd, I never see more than 1000 files open.
I also check the socket with netstat: same; I can see the error while
there's only less than 800 sockets open.
Is someone know what can be the trigger of this?
Regards,
Igor.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users