<div dir="ltr">Hi Răzvan.<div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 24, 2013 at 6:23 PM, Răzvan Crainea <span dir="ltr"><<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi, Takeshi!<br>
<br>
Is the UAS sending a 100 Trying?</blockquote><div><br></div><div>Yes. I just confirmed now: '100 Trying' is sent by the UAS.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
If it's not and you are also dropping all the replies (the 180 messages), then OpenSIPS considers that no reply was received from the UAS, therefore it cannot be reached. A CANCEL would not make sense, because there is no indication that the UAS received the INVITE request.<br>
</blockquote><br></div><div class="gmail_quote">Yes, I eventually realized this would be the case and my approach was wrong.<br><br></div><div class="gmail_quote">However, this doesn't explain the result of my other test:<br>
</div><div class="gmail_quote">if instead of dropping it I convert 180 to 181, then the transaction is cancellable.<br></div><div class="gmail_quote">But if after relaying this modified message I send '180 Ringing', the transaction cannot be cancelled anymore.<br>
</div><div>So it looks like using MI t_reply messes with transactions.<br></div><div></div><div><br></div><div>Regards,<br>Takeshi<br></div><div></div><div> </div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Best regards,<br>
<br>
Răzvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><div><div class="h5"><br>
<br>
On 12/21/2013 03:24 AM, mayamatakeshi wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="h5">
Hello,<br>
I have a requirement to delay the relay of '180 Ringing' for 3 seconds.<br>
So what I did was to intercept the '180 Ringing' at the onreply_route<br>
and drop it.<br>
I send the transaction_id and to-tag to an external app that starts a 3<br>
seconds timer and uses t_reply via MI to send a '180 Ringing' on the<br>
transaction.<br>
This works fine.<br>
<br>
However, if after the delayed '180 Ringing' is sent the caller cancels<br>
the request, opensips doesn't send CANCEL to the callee.<br>
<br>
I have also tried to convert '180 Ringing' to '181 Call is Being<br>
Forwarded' instead of dropping it, and this works fine too and the call<br>
can be cancelled.<br>
However, if the delayed '180 Ringing' is sent, the call cannot be<br>
cancelled anymore.<br>
So, am I doing something wrong?<br>
<br>
Regards,<br>
Takeshi<br>
<br>
<br>
<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div></div></div>