10 Feb
2017
10 Feb
'17
8:25 p.m.
So the ingress is actually TLS -> our VIP address and I see that as the
second record.
The first record shows the physical interface of the system with no
transport value so it's always defaulting to UDP. I need to set this
particular header to use transport=tcp so subsequent UPDATE messages from
the server will use TCP throughout the call.
On Fri, Feb 10, 2017 at 9:05 AM, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
What is the actual goal? If one of the RRs is
generated by an ingress
out of a TCP listener, it should already have ;transport=TCP in it.
On Fri, Feb 10, 2017 at 08:53:56AM -0800, Andy Chen wrote:
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen(a)thinkingphones.com
Hi all,
I need some advise on how to use the record_route() function. So I make
that call when the first method comes in and there are two Record-Route
headers created. However, one of of the headers I want to add
transport=tcp. What is the best way to do this?
I've tried adding that string per documentation within the () and added
it
to both.
Thanks.
--
Andy Chen
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
