[Spce-user] RTP Time out question
john.nash778 at gmail.com
Sat Jan 3 09:20:54 EST 2015
OK --timeout parameter makes complete sense now. But just out of curiosity
in my test I gave value of --silent-timeout=10 and when I disabled wifi of
caller, the stream Caller ------>Rtpengine is actually not receiving any
kind of packet, so what should be the expected behavior? shouldn't it
destroy the session? (Unless I misunderstood the purpose of
Also I am little unclear on what should I put in b2b-url parameter (I am
using --b2b-url=http://127.0.0.1:8090/) In sems (I am using iptel
downloaded version not from sipwise trunk), I have defined to listen on
localhost and 8090 (xmlrpc2di). Please let me know if you have any quick
comment on this.
On Sat, Jan 3, 2015 at 7:37 PM, Richard Fuchs <rfuchs at sipwise.com> wrote:
> On 01/03/15 07:01, John Nash wrote:
> > I did some more detailed tests and found that --silent-timeout does not
> > seem to be working (It is not even deleting session in the specified
> > I made a test call and after session established I disabled wifi of the
> > caller. For test I set silent-timeout value as 10 but it did not delete
> > session. After that I hung up call but did not send rtpengine_delete()
> > (From proxy) so that rtpengine has no knowledge. I waited and after 60
> > seconds rtpengine cleared the session (Which i guess is default
> > --timeout value)
> > am I missing something?
> Yes, the silent timeout is supposed to be larger than the regular
> timeout; it's applied to silenced streams, i.e. streams which aren't
> transmitting any packets other than keepalives.
> Also, both timeouts only apply when neither side is sending packets. If
> only one side goes offline, it's the responsibility of the other party
> to terminate the call due to lost connectivity.
> Spce-user mailing list
> Spce-user at lists.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Spce-user