<div dir="ltr"><div><div><div><div><div><div><div style="color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<span class="">Hello,<br></span><span class=""><span class="">I have a requirement to delay the relay of '180 Ringing' for 3 seconds.</span></span></div><div style="color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<span class="">So what I did was to intercept the '180 Ringing' at the onreply_route and drop it</span>. <br>I send the transaction_id and to-tag to an external app that starts a 3 seconds timer and uses t_reply via MI to send a '180 Ringing' on the transaction.</div>
This works fine. <br><br>However, if after the delayed '180 Ringing' is sent the caller cancels the request, opensips doesn't send CANCEL to the callee.<br></div><br></div>I have also tried to convert '180 Ringing' to '181 Call is Being Forwarded' instead of dropping it, and this works fine too and the call can be cancelled.<br>
However, if the delayed '180 Ringing' is sent, the call cannot be cancelled anymore.<br></div>So, am I doing something wrong?<br><br></div>Regards,<br></div>Takeshi<br><br></div><br><div><div><div><div><br><div><div>
<div><br></div></div></div></div></div></div></div></div>