What happens in a scenario where no second call is made i.e.:
Ua1 makes call, places call on hold, waits for TIMEOUT=60 and comes back to the call?! On Feb 26, 2016 6:11 PM, "GG" notifications@github.com wrote:
Hi !
With this patch applied, I got a problem, let me explain this:
- ua1 makes a first call
- ua1 holds the first call to make a second call
- ua1 hangups the second call and keep the first call on hold
- when the TIMEOUT=60 will be reached, rptengine will removed the
second call from memory, that's ok
- now ua1 comes back to first call and rtpengine closes the call
saying "Closing call due to timeout". But it's not the same call as the one previously destroyed, the callid/from/to tags are different.
in kamailio, for SIP request I'm using rtpengine_manage("replace-origin replace-session-connection RTP/AVP"); and for REPLY I'm using rtpengine_manage("replace-origin replace-session-connection RTP/SAVP");
Before this patch, all is fine for me.
Thanks.
— Reply to this email directly or view it on GitHub https://github.com/kamailio/kamailio/pull/505#issuecomment-189346870.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev