6 Oct
2015
6 Oct
'15
1:51 a.m.
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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat