linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] REGISTER headers Request-URI having port numbe


From: mcyep
Subject: Re: [Linphone-developers] REGISTER headers Request-URI having port number
Date: Mon, 21 Apr 2014 21:57:05 -0700 (PDT)

Hi, to get rid of the strange port number, try disable the sip_random_port

Open linphonerc-factory, under [sip] category, set sip_random_port=0

regards
mcyep


Adil Soomro wrote
> Hi,
> 
> I'm playing around with Linphone for iOS, having bellesip v 1.2.4. The
> problem I'm facing is, the REGISTER header is having a strange port number
> in the Request-URI. This is my REGISTER message:
> 
> REGISTER sip:xx.xx.xxx.xx:24219 SIP/2.0.
> Via: SIP/2.0/TCP xx.xxx.x.xx:60693;alias;branch=z9hG4bK.Q1xyX~5e4;rport.
> From: <sip:

> address@hidden

> >;tag=8gX2f3uVV.
> To: sip:

> address@hidden

> .
> CSeq: 22 REGISTER.
> Call-ID: csJaH0uBtx.
> Max-Forwards: 70.
> Supported: replaces, outbound.
> Contact: <sip:

> address@hidden

> :60693;transport=tcp>;+sip.instance="
> <urn:uuid:e0a17856-fc0c-45a6-b050-3fc7b49d7c1f>
> ".
> Expires: 600.
> User-Agent: LinphoneIPhone/1 (belle-sip/1.2.4).
> Content-Length: 0
> 
> 
> Where as the same app with bellesip on android is having correct URI in
> REGISTER message as:
> 
> REGISTER sip:192.237.178.40 SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.159:5060;branch=z9hG4bK.khToOrxLL;rport.
> ...
> 
> The Linphone for iOS from app store doesn't have this port number in its
> REGISTER message.
> 
> Any idea, how do I get rid of this port number?
> 
> Regards
> 
> -- 
> Adil Soomro
> 
> _______________________________________________
> Linphone-developers mailing list

> Linphone-developers@

> https://lists.nongnu.org/mailman/listinfo/linphone-developers





--
View this message in context: 
http://nongnu.13855.n7.nabble.com/REGISTER-headers-Request-URI-having-port-number-tp182424p182436.html
Sent from the linphone-developers mailing list archive at Nabble.com.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]