reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Why resip create a new connection from another port to connect Server?

I'm sorry, please ignore mu previous email, I have got this: https://www.resiprocate.org/DUM_Client_Outbound_Support



On Tue, Jul 29, 2014 at 7:50 PM, Herbert Karajan <boost.regex@xxxxxxxxx> wrote:
Hi, I'm tried use the my UA(base on resip 1.7) connect to sip2sip.info server over TLS, when add addTransport I set the local port is 5046, but in the wireshark log, the resip use the 23439 port to connect SIP server, why? This is cause the call can't be received because in the SIP messages the "Via" and "Contact" header still using the 5046 port.

I'm watch the log found this:

DEBUG | 20140729-192914.888 | Gala Dialer | RESIP:TRANSPORT | 5852 | TcpBaseTransport.cxx:283 | Processing write for [ V4 81.23.228.129:443 TLS target domain=sip2sip.info mFlowKey=0 ]
DEBUG | 20140729-192914.888 | Gala Dialer | RESIP:TRANSPORT | 5852 | ConnectionManager.cxx:93 | Could not find a connection for [ V4 81.23.228.129:443 TLS target domain=sip2sip.info mFlowKey=0 ]
DEBUG | 20140729-192914.888 | Gala Dialer | RESIP:TRANSPORT | 5852 | InternalTransport.cxx:115 | Creating fd=1416 V4/TCP
DEBUG | 20140729-192914.888 | Gala Dialer | RESIP:TRANSPORT | 5852 | TcpBaseTransport.cxx:223 | Opening new connection to [ V4 81.23.228.129:443 TLS target domain=sip2sip.info mFlowKey=0 ]
DEBUG | 20140729-192914.889 | Gala Dialer | RESIP:TRANSPORT | 5852 | ConnectionBase.cxx:71 | ConnectionBase::ConnectionBase, who: [ V4 81.23.228.129:443 TLS target domain=sip2sip.info mFlowKey=0 ] 000000001B40B760

Why the resip can't find the connection so has to create a new connection ?


How could I let the resip using the 5046 port ?

Best regards,