Igor Potjevlesch [mailto:igor.potjevle...@gmail.com]
Envoyé : mercredi 25 novembre 2015 12:00
À : 'Kamailio (SER) - Users Mailing List'
Objet : RE: [SR-Users] Kamailio/RTPProxy incorrect port 0
Nice, thank you Gholamreza. Not sure the RTPPRoxy is loaded. I mean from a CPU
point of view, t
.conf or ulimit settings?
Regards,
Igor.
De : sr-users [mailto:sr-users-boun...@lists.sip-router.org] De la part de
Gholamreza Sabery
Envoyé : mardi 24 novembre 2015 19:22
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Kamailio/RTPProxy incorrect port 0
If your syst
ind the -L option into the manual. I'm not sure to understand
>> what the option is used for?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Igor.
>>
>>
>>
>> *De :* sr-users [mailto:sr-users-boun...@lists.sip-router.org] *De la
t;
>
>
> *De :* sr-users [mailto:sr-users-boun...@lists.sip-router.org] *De la
> part de* Maxim Sobolev
> *Envoyé :* mardi 24 novembre 2015 06:26
>
> *À :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] Kamailio/RTPProxy incorrect port 0
>
>
>
> Try
router.org] De la part de
Maxim Sobolev
Envoyé : mardi 24 novembre 2015 06:26
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Kamailio/RTPProxy incorrect port 0
Try setting some more reasonable FD limit, i.e. say 10,000. Bumping from 1,000
to 500,000 seems somewhat excessive.
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-boun...@lists.sip-router.org] De la part de
> Daniel-Constantin Mierla
> Envoyé : l
e 2015 09:33
À : Kamailio (SER) - Users Mailing List
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
r
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 rtp
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 y
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/
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 cal
11 matches
Mail list logo
