Problem minisip and tcp with an openser proxy

[Philippe Torrelli]

Hello, 

This is with latest auto build found on the server ( 2952 )
Scenario:

810 at sbcsipsophia.dynds.org is a minisip client 
transport = TCP, IP = 192.168.92.23

850 at sbcsipsophia.dynds.org is a minisip client 
transport = TCP, IP = 192.168.92.54

sbcsipsophia.dyndns.org is their openser proxy , 
IP = 192.168.92.1

Scenario: 
810 calls 850

In the attached trace we see : 
Line 30:  the ack is sent in udp.
Line 35: the bye is sent in udp.

It is worse in tls. I can't send a trace because I don't have a means to
change the tls cipher list to nul for the 2952 client, but in TLS the same
packets ( ack of the 200 of a successful invite and bye), when they 'cross'
the proxy are sent in udp but on port 5061.  As a consequence, hangup are
not handled by the other side when the communication .

According to OpenSer developper, this behavior is because the ACK sent line
29 810 at ... (line 23) should feature all the fields of the contact header
from the corresponding OK in the request URI .
Ie 
Openser does that because the ACK line 29  is 
ACK sip:850 at 192.168.92.54:5060 SIP/2.0 

And should be
ACK sip:850 at 192.168.92.54:5060;transport=TCP SIP/2.0

It is the same for the bye sent line 34.


Hope it helps.

Philippe Torrelli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: udpintcp.pcap
Type: application/octet-stream
Size: 25718 bytes
Desc: not available
Url : http://lists.minisip.org/pipermail/minisip-devel/attachments/20061124/98e3702c/udpintcp-0001.obj