That's ok.
The issue on this thread was about suspending a transaction for which a final response was sent out back to initial originator of the request (e.g., invite was forwarded, 200ok comes in and it is sent out, then the transaction is suspended).
Daniel
On 06/10/15 00:23, Alex Balashov wrote:
Daniel,
Does this mean it's generally bad practice to suspend+resume when handling initial INVITE requests while handling all other requests in the main SIP worker children/main config body? In my case I suspend INVITEs and resume them in rtimer processes consuming an mqueue, but CANCELs for example, and everything else, is handled without async.
-- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Sent from my BlackBerry.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev