Problem with TLS and record-route

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start call on device A
2. Accept call on device B
3. Terminate call on device B

What is the expected output? What do you see instead?
Call should end on the device A but the event BYE does not come to device A.

What version of the product are you using? On what operating system?
Latest Doubango used for iOS. Device A used TCP or TLS, device B used TLS. 

Please provide any additional information below.
Our sip server sends route field with no port(Record-Route: 
<sip:184.69.143.252;nat=yes;lr=on>) and doubango tries connect to peer with 
port 5060 by default. If server sends record-route with port(Record-Route: 
<sip:184.69.143.252:5061;nat=yes;lr=on>) it works fine with TLS<->TLS but not 
works with TLS<->TCP and TCP<->TLS. I tried use microSIP client with our 
server(record-route with no port) and it works fine.

Original issue reported on code.google.com by denis.tr...@gmail.com on 20 Sep 2013 at 4:14

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 4 Oct 2013 at 7:33

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Should be fixed by r1006
If not, do debug the code: the default port is set at:
https://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinySIP/s
rc/transports/tsip_transport_layer.c?spec=svn1006&r=1006#814
and
https://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinySIP/s
rc/transports/tsip_transport_layer.c?spec=svn1006&r=1006#824

Original comment by boss...@yahoo.fr on 8 Oct 2013 at 5:57

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****