[OpenSIPS-Users] rtpproxy timeout notifications

[Flavio Goncalves]

Razavn,

I'm using OpenSIPS 1.8.2 from svn and rtpproxy from the opensips
repository.

Flavio E. Goncalves




2013/1/7 Răzvan Crainea <razvan at opensips.org>

>  Hi, Flavio!
>
> Can you tell me what versions of OpenSIPS and RTPProxy are you using?
>
> Best regards,
>
> Razvan Crainea
> OpenSIPS Core Developerhttp://www.opensips-solutions.com
>
> On 01/03/2013 12:31 PM, Flavio Goncalves wrote:
>
> Hi Razvan,
>
>  I'm checking if the problem is not related to re-invites and calling
> rtpproxy set with an invalid value. Anyway, the logs are below.
>
> Dec 20 14:59:28 /sbin/opensips[6978]:
> ERROR:rtpproxy:timeout_listener_process: Wrong formated message received
> from rtpproxy [1]
>
> Dec 20 14:59:28 /sbin/opensips[6978]:
> INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255]
> <3066.74196691#0121744.870880408#0121968.1268777973#012949.
> 1984340712#01274
> .448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.1176777710#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121>
>
>  Flavio E. Goncalves
> CEO - V.Office
>
>
>
> 2012/12/18 Răzvan Crainea <razvan at opensips.org>
>
>>  Hi, Flavio!
>>
>> I've attached a patch for the rtpproxy module, that for every error, it
>> prints the buffer received from the Rtpproxy server. What I want to see is
>> if the message is totally broken, or only some parts of it are malformed.
>> Could you please apply this patch, and paste us the output when the error
>> occurs again?
>>
>> Best regards,
>>
>> Razvan Crainea
>> OpenSIPS Core Developerhttp://www.opensips-solutions.com
>>
>>  On 12/13/2012 07:01 PM, Flavio Goncalves wrote:
>>
>>  I'm having an issue with timeout notification of rtpproxy.
>>
>>  Usually sessions are disconnected properly with rtpproxy timeout
>> notification:
>>
>>  INFO:do_timeout_notification: notification timeout sent 1715.2112525045
>> : Success (The dialog hash is presented correctly with period .)
>>
>>  However, In some cases (3 to 7 per day in 25000 calls) we got the
>> following message from rtpproxy module. RTP Proxy in this case send the
>> dialog id with a # in the middle. I can't reproduce the problem in the lab.
>>
>>  Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated
>> message received from rtpproxy - invalid dialog entry [1727216578#0123634
>> ]
>>
>>  In this case there is a hash in the middle of the dialog identifier (a
>> str2int function generates this error in the rtpproxy module denying the
>> request and throwing the error message.
>>
>>  No errors in OpenSIPS log
>> No errors in rtpproxy log (debug enabled)
>>
>>  Any ideas?
>>
>>  Flavio E. Goncalves
>>
>>
>>
>>  _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130107/d8a4d80c/attachment.htm>