Module: sip-router
Branch: tmp/tm_async_reply_support
Commit: 7eabeb5ecd12d647e927cd08d5e7e887f18ab9ca
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7eabeb5…
Author: Richard Good <richard.good(a)smilecoms.com>
Committer: Richard Good <richard.good(a)smilecoms.com>
Date: Tue Jun 25 14:16:02 2013 +0200
Merge branch 'master' into tmp/tm_async_reply_support
---
Module: sip-router
Branch: richard.good/diameter_rx_media
Commit: 969377018a770af6032109514205f3aa8e9bcfc9
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9693770…
Author: Richard Good <richard.good(a)smilecoms.com>
Committer: Richard Good <richard.good(a)smilecoms.com>
Date: Tue Jun 25 14:15:02 2013 +0200
Merge branch 'master' into richard.good/diameter_rx_media
---
Hi,
Re. TM suspend/continue, in the continue function we create a faked_env
(similar to that used in failure route handling). The problem here is that
any async route block we execute will be classified as a FAILURE ROUTE
block regardless of where we are in message processing process. This will
cause problems for many cfg commands that are restricted to REQUEST_ROUTE
only. Was this the intention and if so, why?
Cheers
Jason