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
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
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
Hello all,
Problem
I just added to OpenSIPS a new feature that makes possible to deal with
ghost calls in proper and complete way (detection, reporting and
termination).
Ghost calls are calls where (due network or hardware issue), one of
the end-points simply died without
Quick question about this -- does the timeout happen in the case where two
joined sessions are in sendonly (ie, listening to hold music)? If so, is
there an easy way around this and can this feature be enabled on a per
force/unforce rtpproxy function call?
On Thu, Dec 16, 2010 at 1:14 PM, Razvan
