Re: [SR-Users] SIP contact header question

2017-03-14 Thread Jack Davis
Thanks Alex. And objection duly noted, =) I'll just have to test it out and make sure it doesn't break any of my other clients. Thank you, Jack Davis On Tue, Mar 14, 2017 at 5:46 PM, Alex Balashov <abalas...@evaristesys.com> wrote: > append_to_reply("Record-Route: \r\n"

Re: [SR-Users] SIP contact header question

2017-03-14 Thread Jack Davis
by kamailio to a re-invite. Thank you, Jack Davis On Tue, Mar 7, 2017 at 3:49 PM, Alex Balashov <abalas...@evaristesys.com> wrote: > On Tue, Mar 07, 2017 at 03:44:31PM -0600, Jack Davis wrote: > > > What kind of problems can arise from inserting said header? > > Theore

Re: [SR-Users] SIP contact header question

2017-03-07 Thread Jack Davis
What kind of problems can arise from inserting said header? I'm trying to find a way to get a pesky setup to start behaving, of course, without requiring them to make any changes. Thank you, Jack Davis On Fri, Mar 3, 2017 at 2:39 PM, Alex Balashov <abalas...@evaristesys.com> wrote: &g

Re: [SR-Users] SIP contact header question

2017-03-03 Thread Jack Davis
Thank you all for the replies. I'm already utilizing a record-route header in the initial Invite before any re-invites occur. Is the preferred method to also include a record-route header in the 200 OK that is given in response to the re-invite? Thank you, Jack Davis On Fri, Mar 3, 2017 at 2

[SR-Users] SIP contact header question

2017-03-02 Thread Jack Davis
dialog ONLY when a record-route is not used. I would appreciate any clarification on the RFC or best practices in this scenario. Thank you, Jack Davis ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-rout