Hi All, I am trying to replay a request to the destination via Kamailio, and I am using t_relay_to_tcp for that , but in that case Kamailio is adding its own address as the top VIA header. Is there a way I can instruct Kamailio not to add local via header ?
Hello Panda,
You may consider this approach instead:
https://kamailio.org/docs/modules/5.8.x/modules/corex.html#corex.f.send_tcp
Cheers,
-- Alex
On Aug 28, 2024, at 8:59 AM, panda.paresh--- via sr-users sr-users@lists.kamailio.org wrote:
Hi All, I am trying to replay a request to the destination via Kamailio, and I am using t_relay_to_tcp for that , but in that case Kamailio is adding its own address as the top VIA header. Is there a way I can instruct Kamailio not to add local via header ? __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi, I was trying this out , but somehow Kamailio is not liking it. I am getting below error
Aug 27 14:04:27 kamailio01 /usr/sbin/kamailio[1135093]: DEBUG: <core> [core/tcp_main.c:2879]: tcpconn_do_send(): buf=#012SIP/2.0 500 I'm terribly sorry, server error occurred (1/TM)#015#012Via: SIP/2.0/TCP 192.168.136.153:5061;branch=z9hG4bK-29059-1-0;rport=5061#015#012From: +14164568558 sip:+14164568558@192.168.136.153:5062#015#012Call-ID: 1-29059@192.168.136.153#015#012 .....
What I observe is that previous to send_tcp function I am using some transaction related functions like t_suspend/t_continue. and becuse of the tm module I am getting this error.
My query is : do Kamailio can work in both modes ?, some parts transaction way(for internal interfaces like rabbit MQ(kazoo) and some parts(final relay part, send tcp way (stateless)?
Thank you so much for the quick reply to my previous query!
Regards Paresh Panda
I
Hello,
On 28.08.24 15:46, panda.paresh--- via sr-users wrote:
Hi, I was trying this out , but somehow Kamailio is not liking it. I am getting below error
Aug 27 14:04:27 kamailio01 /usr/sbin/kamailio[1135093]: DEBUG: <core> [core/tcp_main.c:2879]: tcpconn_do_send(): buf=#012SIP/2.0 500 I'm terribly sorry, server error occurred (1/TM)#015#012Via: SIP/2.0/TCP 192.168.136.153:5061;branch=z9hG4bK-29059-1-0;rport=5061#015#012From: +14164568558 sip:+14164568558@192.168.136.153:5062#015#012Call-ID: 1-29059@192.168.136.153#015#012 .....
What I observe is that previous to send_tcp function I am using some transaction related functions like t_suspend/t_continue. and becuse of the tm module I am getting this error.
My query is : do Kamailio can work in both modes ?, some parts transaction way(for internal interfaces like rabbit MQ(kazoo) and some parts(final relay part, send tcp way (stateless)?
Thank you so much for the quick reply to my previous query!
the debug message is from tm module, so the send_tcp() is not the reason for that log.
But t_suspend()/t_continue() are designed to work only with the other tm functions (e.g., t_relay()) and using send_tcp() is not updating the transaction state, which at some point is going to time out and send some response back.
Otherwise, Kamailio should work fine with mixing send_tcp() and transactions, but be sure you also reply (or the next hop replies) when using send*() functions, because they are just like writing to the socket/connection, is not even doing stateless sip forwarding as no Via header is added, therefore retransmissions are expected. Also, the next hop might no be able to send the sip reply properly, if the initial sender is behind nat. I do not know your scenarios/needs. but it can be tricky to get it working properly if UAs are behind nat/firewall.
Cheers, Daniel
Hi Daniel,
Thank you for the details !
Now I understand that It is belter to play around with VIA header rather than send_tcp , my requirement is to tell the upstream to send next set of requests to the original sender where my Kamailio will be out of the path as the upstream is looking at the via header to send next course of packets.
I am trying now below as per the documentation from corex module
... xavp_via_fields="mvia" ... request_route { ... $xavp(mvia=>address) = "10.10.10.10"; $xavp(mvia[0]=>port) = "5060"; via_use_xavp_fields("1"); ... }
Thank you again !
Regards Paresh
-
Alex Balashov -
Daniel-Constantin Mierla -
panda.paresh＠gmail.com