So how do I define what is used?  Again when I did call "record_route" I need one of the records to have "transport=tcp" param and not the default UDP.

On Wed, Feb 15, 2017 at 12:09 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

Hello,


On 13/02/2017 19:43, Andy Chen wrote:
So the INVITE coming in (TLS) don't have Record-Route.  When Kamailoi received the INVITE, I call record_route() and adds the two entry.  However, one of the entry I need to have transport=tcp.  When I added it as this:

record_route(";transport=tcp")
you don't need to force a transport protocol via the parameter of record_route(), it is added by kamailio rr module by default in this case, each of the two record-route header having the appropriate transport depending what was used (udp, tcp, tls or sctp).


It adds it to both Record-Route therefore messes up the call.

Just remove the parameter with the transport, use record_route().

Kamailio forwards to endpoint device via tcp using the following function:

t_replay_to_tcp();

I guess you meant t_relay_to_tcp(). The 'replay' doesn't exit in tm function names, there are functions with 'reply', but those send sip responses back, not forwarding requests.

Cheers,
Daniel

 

On Mon, Feb 13, 2017 at 10:16 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

Hello,

hmm, some confusion there. So the request is sent over tcp, but the record route doesn't have transport=tcp? What function do you use to send the request out?

Cheers,
Daniel


On 13/02/2017 17:39, Andy Chen wrote:
Hi Daniel,

To answer your earlier question, Kamailio receive the request via TLS, but need to forward the method to endpoint device via TCP with those Record-Route entries.  I used record_route_preset() but that broke my call so I ended up using appened_hf to get around this problem.

On Mon, Feb 13, 2017 at 3:18 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:

No, you should use either record_route() or record_route_preset(), not both of them for the same request.

Cheers,
Daniel


On 10/02/2017 20:44, Andy Chen wrote:
One other question.  Do I need to run record_route() after I run record_route_preset(string1, string2)?  I tried this and the Record-Route doesn't show presets I defined.

On Fri, Feb 10, 2017 at 9:25 AM, Andy Chen <achen@fuze.com> wrote:
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@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:

> 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@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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)



--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)


_______________________________________________
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
-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.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
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com



--
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@thinkingphones.com