Thank you. So I was correct other than mixing up the Route and Via headers. Some day I'll get them right...
On Mon, 11 Feb 2019 at 14:10, Alex Balashov <abalas...@evaristesys.com> wrote: > On Mon, Feb 11, 2019 at 02:08:18PM +1300, David Cunningham wrote: > > > OK, so the Contact is the address on the envelope, but the postal service > > should actually send it through the chain of Route headers? > > Yes, but once the request exits the last proxy, that last proxy should > set the domain part of the request URI (the remote Contact) as its next > hop. > > > Our issue is that the device is sending the ACK directly to the Contact > > address, but the Contact address doesn't support TLS, which is why we > need > > it to go through the proxy listed in the route set. > > Yes, that's wrong. The e2e ACK should follow the route set. > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782 _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
