[SR-Users] Kamailio/RTPProxy incorrect port 0

Daniel-Constantin Mierla miconda at gmail.com
Mon Nov 23 09:33:26 CET 2015


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:
> 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 at 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 at gmail.com]
>> *Envoyé :* vendredi 20 novembre 2015 19:09
>> *À :* sr-users at 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 at 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 at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
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




More information about the sr-users mailing list