[SR-Users] REGISTER request and save() from onreply_route

Hi all! Seems to be an old topic but still unclean is it possible or not, please correct me if I'm wrong. There are some old threads like http://lists.sip-router.org/pipermail/users/2007-May/011278.html I use Kamailio 4.2.1 trying to create intercepting registrar proxy, which handles NAT (rewrite

Re: [SR-Users] REGISTER request and save() from onreply_route

BTW, is there any way to alias contacts on Kamailio side and then on INVITE use rewritten contact as base for real (original untouched) contact lookup, like using 'received' field as lookup source? And thanks for your detailed reply, I'll dig into the docs about 'received' handling. 2015-01-19 22

Re: [SR-Users] REGISTER request and save() from onreply_route

Yes, you're right about contact matching and ATAs, this is a part of our case too. I actually use Path module to forward REGISTERs to backend servers. But there is a problem that not all backends support Path, like Asterisk 11. If I get the point right, I should forward them as is and when I recei

Re: [SR-Users] REGISTER request and save() from onreply_route

On 01/19/2015 12:56 PM, Dmitry Sytchev wrote: Is there a way to make save() use original request fields like T_req($ct), or some way to call save() with full set of custom params? Yes; in fact, there are many standards-based reasons why it's desirable to store the original Contact binding pro

[SR-Users] REGISTER request and save() from onreply_route

Hi all! Seems to be an old topic but still unclean is it possible or not, please correct me if I'm wrong. There are some old threads like http://lists.sip-router.org/pipermail/users/2007-May/011278.html I use Kamailio 4.2.1 trying to create intercepting registrar proxy, which handles NAT (rewrite