Andres,
Did you have to patch Asterisk to fix this? If so, would you share your patch?
Regards, Paul
On Fri, 04 Mar 2005 12:12:18 -0500, Andres andres@telesip.net wrote:
Bogdan-Andrei IANCU wrote:
Andres,
The problem is not in ser, but in Asterisk... As your net captures shows, * does not generate any INVITE final reply when receiving CANCEL. It should sent a "487 Request Terminated". The lack of this final reply keeps the transaction open on ser; when FR timer hits, internally "408 Timeout" is generated (after 120 secs) and failure_route called.
So the problem is *.
bogdan
Crystal clear Bogdan. Problem solved now in Asterisk. Now we can start testing 0.9.0.
Thanks!
-- Andres Network Admin http://www.telesip.net
Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
Java Rockx wrote:
Andres,
Did you have to patch Asterisk to fix this? If so, would you share your patch?
No patch. We were just testing things out with an older version of Asterisk in our lab. We upgraded to stable 1.0.3 and it worked as expected now
-
Andres -
Java Rockx