[OpenSIPS-Users] [NEW] Media timeout detection and call termination
Dave Singer
dave.singer at wideideas.com
Sat Dec 18 00:40:36 CET 2010
It seems VAD would also be a potential problem with NAT and state
full packet inspection on firewalls. It would see a better practice for the
UA to send keep alive RTP packets. That would solve both dead call detection
and potential NAT issues. That would be nice RFC change.
In my situation I have never seen VAD in use. I would like to have the
option to set what determines a call is dead, 1 leg no RTP, both legs no
RTP, or don't kill a call no matter if there is no rtp.
Looking forward to the solution you are talking about.
Dave
On Fri, Dec 17, 2010 at 9:48 AM, Razvan Crainea
<razvancrainea at opensips.org>wrote:
> Hi Saul,
>
> Unfortunately this solution doesn't deal with the UA using VAD in case
> there are no RTP packages sent when voice is suppressed. Anyway, we are
> working on a solution that will solve this problem.
>
> Regards,
>
>
>
> On 12/17/2010 05:02 PM, Saúl Ibarra Corretgé wrote:
>
>>
>> As OpenSIPS is a proxy and at signaling level there is no continues
>>> traffic to help in detecting the ghost calls, such detection must be
>>> done at media level.
>>>
>>>
>> Hi,
>>
>> If this detection is done based only in the lack of RTP, then you could
>> say that a UA that uses VAD (it doesn't transmit RTP when there is silence)
>> timed out, but what really happened is that it was silent for a long time.
>> How is the timeout condition detected?
>>
>> Did this new addition deal with this situation?
>>
>>
>> Thanks and regards,
>>
>>
> --
> Razvan Crainea
> www.voice-system.ro
>
>
> _______________________________________________
> 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/20101217/9e4bd7f0/attachment.htm>
More information about the Users
mailing list