[OpenSIPS-Users] TCP connection relay issue
devang.dhandhalya at ecosmob.com
Wed May 4 08:58:27 UTC 2022
Issue is whenever i am sending Register or INVITE request with TCP in
opensips using tcp connection to relay request to Freeswitch server while i
want to use UDP socket to send Request from OpenSIPs to Freeswitch , using
mid registrar for registering users.
OpenSIPS version : 3.2.2
flow :end user -> OpenSIPS -> Freeswitch -> OpenSIPS -> enduser
OpenSIPS configuration :
tcp_connection_lifetime = 3615
socket=udp:192.168.0.1:5060 as 22.214.171.124:5060
socket=tcp:192.168.0.1:5060 as 126.96.36.199:5060
modparam("proto_tcp", "tcp_async", 1)
modparam("proto_tcp", "tcp_send_timeout", 3000)
modparam("proto_tcp", "tcp_async_local_connect_timeout", 3000)
modparam("proto_tcp", "tcp_async_local_write_timeout", 3000)
modparam("proto_tcp", "tcp_max_msg_chunks", 8)
I used force_send_socket , $fs function to use UDP socket but still
OpenSIPS using tcp connection for relay packet to Freeswitch any other
functionality which overwrites this core function .
In another setup the same configuration but opensips sends requests using a
UDP socket. That's strange for me because of the same setup .
There is a particular configuration that we use tcp connection / UDP socket
to relay packets.
Kindly inform me how we send requests using UDP socket instead of tcp
In addition to generic Disclaimer which you have agreed on our
website, any views or opinions presented in this email are solely those of
the originator and do not necessarily represent those of the Company or its
sister concerns. Any liability (in negligence, contract or otherwise)
arising from any third party taking any action, or refraining from taking
any action on the basis of any of the information contained in this email
is hereby excluded.
This communication (including any
attachment/s) is intended only for the use of the addressee(s) and contains
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading,
dissemination, distribution, or copying of this communication is
prohibited. Please inform originator if you have received it in error.
*Caution for viruses, malware etc.*
This communication, including any
attachments, may not be free of viruses, trojans, similar or new
contaminants/malware, interceptions or interference, and may not be
compatible with your systems. You shall carry out virus/malware scanning on
your own before opening any attachment to this e-mail. The sender of this
e-mail and Company including its sister concerns shall not be liable for
any damage that may incur to you as a result of viruses, incompleteness of
this message, a delay in receipt of this message or any other computer
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users