Hi, Takeshi!
Is the UAS sending a 100 Trying? 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.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 12/21/2013 03:24 AM, mayamatakeshi wrote:
Hello,
I have a requirement to delay the relay of '180 Ringing' for 3 seconds.
So what I did was to intercept the '180 Ringing' at the onreply_route
and drop it.
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.
This works fine.
However, if after the delayed '180 Ringing' is sent the caller cancels
the request, opensips doesn't send CANCEL to the callee.
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.
However, if the delayed '180 Ringing' is sent, the call cannot be
cancelled anymore.
So, am I doing something wrong?
Regards,
Takeshi
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
