3 Mar
2016
3 Mar
'16
6:09 p.m.
Hi Alex,
Yes, you are correct. It simply wraps the standard t_replicate() function,
replicating the original request to every other node (first appending a new
branch for each). Use case is essentially the same as the original but
having the benefit of not having to define destination(s) statically in
config, since that part is handled by DMQ.
Cheers,
Charles
On 3 March 2016 at 15:37, Alex Balashov <abalashov(a)evaristesys.com> wrote:
Hi,
If I understand the DMQ documentation correctly, when a SIP request is
distributed to other Kamailio instances via dmq_t_replicate(), it is not
merely sent as a payload in a novel way, but actually "rehydrated" by the
receiver into a mock request on the other end and processed as through it
were a "real" message that came into the request_route[] in the natural way.
Is this an accurate assumption?
-- Alex
--
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/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered
office: Faraday Wharf, Innovation Birmingham Campus, Holt Street,
Birmingham Science Park, Birmingham B7 4BB.