Re: [Linphone-users] not listening on port 5060 on Android

[Simon Morlat]

I would like to see the logs from Linphone itself, not a tcpdump capture
at the server level.
I suspect that there is nat router in between linphone and the asterisk
that is doing bad things with rports inside the message SIP.

It is unfortunately more and more common to see that, and we think that
we 'll have to switch to SIPS to avoid all these stupid nats to break
SIP messages.

Simon


Le vendredi 15 avril 2011 à 07:24 -0400, Brian J. Murrell a écrit :
> On 11-04-15 05:46 AM, Simon Morlat wrote:
> > In order to avoid port conflicts with other SIP application,
> > linphone-android does not use port 5060, but instead a random port
> > choosed at startup.
> 
> Ahh.  OK.  Fair enough.
> 
> > I have no idea why your asterisk thinks linphone is listening in port
> > 5060.
> 
> I wonder if it's because linphone is telling it that.  I'm certainly no
> SIP protocol expert but if you look at the detailed packet trace at
> http://brian.interlinx.bc.ca/linphone_dump.txt, you can see that
> throughout the SIP registration process linphone is using port 3270 and
> Asterisk is happy to respond to it on that port.
> 
> You can also see in packets 3, 6, 8, and 10, linphone sends along in
> it's SIP packets:
> 
>         Contact: <sip:address@hidden:3270>;expires=3600
> 
> and when it does so, Asterisk is happy to sent it's requests to port
> 3270, as can be seen in packet 9.  But then all of a sudden in packets
> 12, 14 and 16 linphone switches and sends:
> 
>         Contact: <sip:address@hidden:5060>
> 
> And we can see in packet 15, that this is where Asterisk tries to
> contact linphone on port 5060 and starts getting ICMP Port unreachable
> messages from Android.
> 
> I suspect that Asterisk is using that Contact: as it's means of
> determining how to reach that SIP client and it's when the client starts
> telling Asterisk that it's on port 5060 that Asterisk cannot
> communication with it anymore and determines it "unreachable" and the of
> course, will not route calls to it any more.  Or maybe I'm all wrong.  :-)
> 
> > Obviously it should not.
> 
> If the client is being honest about where it is, yes, I agree.
> 
> b.
> 
> _______________________________________________
> Linphone-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/linphone-users