[SIP Beyond VoIP] sip-session register contact tcp port does match source tcp port

Saúl Ibarra Corretgé saul at ag-projects.com
Mon Apr 8 09:43:08 CEST 2013


On Apr 8, 2013, at 9:31 AM, Juha Heinanen wrote:

> i noticed that sip-session register contact tcp port does not match
> source (via) tcp port:
> 
> $ sip-session -s
> using set_wakeup_fd
> Using account jh at test.fi
> ...
> 2013-04-08 10:20:37.109121: SENDING: Packet 1, +0:00:00
> 192.98.102.10:45015 -(SIP over tcp)-> 192.98.102.20:5060
> REGISTER sip:test.fi SIP/2.0
> Via: SIP/2.0/tcp 192.98.102.10:45015;rport;branch=z9hG4bKPj65abfeaf-497b-4479-80ee-4d80a549307e
> Max-Forwards: 70
> From: <sip:jh at test.fi>;tag=bd53a6ca-1603-4514-9511-95b57b4ddb0c
> To: <sip:jh at test.fi>
> Contact: <sip:76942853 at 192.98.102.10:54431;transport=tcp>;+sip.instance="<urn:uuid:2e4eae00-c2c7-4136-a74e-2336177a0ae0>"
> Call-ID: 0c05c04e-84b8-4f9d-88e8-df1db9d47fdd
> CSeq: 1 REGISTER
> Expires: 180
> Supported: gruu
> User-Agent: sipsimple 0.34.0
> Content-Length:  0
> 
> is this is a bug of feature?
> 

IIRC it's a feature. We create a single TCP transport for all accounts to receive incoming calls, but new TCP connections are created when sending requests out.

--
Saúl Ibarra Corretgé
AG Projects





More information about the SIPBeyondVoIP mailing list