Hi Giovanni, thanks for testing and reporting. I will prepare a PR for this. About your solution I do agree with it, simple and effective :)
Regards, Federico On Fri, Jul 8, 2016 at 8:20 AM, gmele <giovanni.m...@nagra.com> wrote: > Hello Federico, > > your patch seems to work for us. Thx. > > For the 2 registrars needing the transaction information, we have found > another way to solve it: in our previous config, the dispatcher > ds_select_dst was using algo 1 (from URI) for INVITE and REGISTER, meaning > that the INVITE may be done on first registrar and the callee REGISTER > (after push notif) on the second one, causing the INVITE to be never sent. > Now, we will use algo 2 instead, meaning that both INVITE and callee > REGISTER will be done on the same registrar. > > What do you think about this solution? > > Thx again > > Giovanni > > > > -- > View this message in context: > http://sip-router.1086192.n5.nabble.com/tsilo-ts-append-problem-tp150184p150267.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
