Hello
I have a problem when two clients (one using UDP and one using TCP) connect to SER (version 0.8.13-dev-23). My scenario is more or less like this:
TCP Client <----> SER <----> UDP Client
There are no NATs or Firewalls in scene.
I want to reuse the TCP connection of the TCP Client for the whole SIP signalling, so I have added the command force_tcp_alias(); to ser.cfg and changed tcp_conn.h as advised in http://lists.iptel.org/pipermail/serusers/2004-May/008262.html.
The TCP Client starts the call with an INVITE and everything works correctly. However, when the UDP Client tries to send a MESSAGE, SER doesn't route the MESSAGE through the TCP connection (it sends it over UDP with the TCP port included in TCP Clients Contact!).
Can anyone tell me what is misconfigured?
Lots of thanks to everyone.
DANIEL
On Jun 21, 2004 at 21:18, Daniel Mach?n Vazquez-Ill? dmachin@telefonica.net wrote:
Hello
I have a problem when two clients (one using UDP and one using TCP) connect to SER (version 0.8.13-dev-23). My scenario is more or less like this:
TCP Client <----> SER <----> UDP Client
There are no NATs or Firewalls in scene.
I want to reuse the TCP connection of the TCP Client for the whole SIP signalling, so I have added the command force_tcp_alias(); to ser.cfg and changed tcp_conn.h as advised in http://lists.iptel.org/pipermail/serusers/2004-May/008262.html.
The TCP Client starts the call with an INVITE and everything works correctly. However, when the UDP Client tries to send a MESSAGE, SER doesn't route the MESSAGE through the TCP connection (it sends it over UDP with the TCP port included in TCP Clients Contact!).
Can anyone tell me what is misconfigured?
A quick guess: the UDP client doesn't copy the proto parameter from the TCP client Contact: into the request uri.
If this is not the case, please send some packet dumps (tcpdump -w file or ngrep).
Andrei
Hello.
You where true, the problem was in the Request URI of the UDP client.
Lots of thanks
----- Original Message ----- From: "Andrei Pelinescu-Onciul" pelinescu-onciul@fokus.fraunhofer.de To: "Daniel Mach?n Vazquez-Ill?" dmachin@telefonica.net Cc: serusers@lists.iptel.org Sent: Monday, June 21, 2004 9:45 PM Subject: Re: [Serusers] Problem with TCP/UDP translation
On Jun 21, 2004 at 21:18, Daniel Mach?n Vazquez-Ill?
dmachin@telefonica.net wrote:
Hello
I have a problem when two clients (one using UDP and one using TCP)
connect
to SER (version 0.8.13-dev-23). My scenario is more or less like this:
TCP Client <----> SER <----> UDP Client
There are no NATs or Firewalls in scene.
I want to reuse the TCP connection of the TCP Client for the whole SIP signalling, so I have added the command force_tcp_alias(); to ser.cfg
and
changed tcp_conn.h as advised in http://lists.iptel.org/pipermail/serusers/2004-May/008262.html.
The TCP Client starts the call with an INVITE and everything works correctly. However, when the UDP Client tries to send a MESSAGE, SER
doesn't
route the MESSAGE through the TCP connection (it sends it over UDP with
the
TCP port included in TCP Clients Contact!).
Can anyone tell me what is misconfigured?
A quick guess: the UDP client doesn't copy the proto parameter from the TCP client Contact: into the request uri.
If this is not the case, please send some packet dumps (tcpdump -w file or ngrep).
Andrei
-
Andrei Pelinescu-Onciul -
Daniel Machín Vazquez-Illá