rt of
information is useful to provide for something like this? I’m on 5.1.3.
> On 4/05/2018, at 1:51 PM, Nathan Ward wrote:
>
> Hi,
>
> About a year ago I posted this, but haven’t had much chance to follow up on
> it:
> https://lists.kamailio.org/pipermail/sr-users/2017
p:a@domain');
append_branch('sip:b@domain');
xlog("L_DBG", "1 ds: [$ds]\n");
lookup_branches('location');
xlog("L_DBG", "2 ds: [$ds]\n");
t_load_contacts();
xlog("L_DBG", "3 ds: [$ds]\n");
t_next_contacts();
xlog("L_DBG", "4 ds:
the SIP server to achieve
this (i.e. force $du = 127.0.0.1 in my branch_route), or, can I avoid that
complexity?
--
Nathan Ward
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr
=en=kamailio+replace+caller+id=UTF-8=UTF-8_rd=cr=c4Y6WYH5DcbN8gfGjo6IBg>
First result is great.
--
Nathan Ward
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi,
Developing such a solution is going to be quite complicated any way you look at
it, and will require deep understanding of a number of things in order to
operate it, and there are a number of tradeoffs you’ll need to make based on
your exact use case. I don’t think a mailing list
