Strange Linphone Failure

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Strange Linphone Failure

Robert Dixon
I have 2 PCs connected by  switch, and then to a router.
Using IP address calling  <a href="sip:ip" class="">sip:ip address.
If I call from A to B, then A says B cannot respond to the call.
If I call from B to A, it connects for 2 seconds, then disconnects.

What is going on?

Bob

_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Stuart D. Gathman
On Sat, 8 Jun 2019, Robert Dixon wrote:

> I have 2 PCs connected by  switch, and then to a router.Using IP address
> calling  sip:ip address.
> If I call from A to B, then A says B cannot respond to the call.
> If I call from B to A, it connects for 2 seconds, then disconnects.

You need some actual information for a diagnosis.  If you don't want to
share the actual IPs, some general traits are very relevant:

IPv4?  IPv6?

Private IPs?  (192.168.*.*,172.168.*.*.*,10.*.*.*,fc00::/7, etc)

NAT?

--
       Stuart D. Gathman <[hidden email]>
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Stuart D. Gathman
In reply to this post by Robert Dixon
On Sat, 8 Jun 2019, Robert Dixon wrote:

> I have 2 PCs connected by  switch, and then to a router.Using IP address
> calling  sip:ip address.
> If I call from A to B, then A says B cannot respond to the call.
> If I call from B to A, it connects for 2 seconds, then disconnects.
>
> What is going on?

You also need to report what ports are allowed through firewall on
both sides, and what ports linphone is configured to use for SIP,
audio RTP, and video RTP.  The version of linphone is critical.

If the ips in question are private IPv6, you might find this bug
relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1713947

--
       Stuart D. Gathman <[hidden email]>
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Robert Dixon
In reply to this post by Stuart D. Gathman
IPv4
Private IPs.   192.168.*.*

Bob

PS this has worked in the past, but now it does not.  
I uninstalled Linphone on both PCs, including those files that the uninstall did not get.
Then reinstalled on both PCs.  
No change.


> On Jun 8, 2019, at 1:18 PM, Stuart D. Gathman <[hidden email]> wrote:
>
> On Sat, 8 Jun 2019, Robert Dixon wrote:
>
>> I have 2 PCs connected by  switch, and then to a router.Using IP address
>> calling  sip:ip address.
>> If I call from A to B, then A says B cannot respond to the call.
>> If I call from B to A, it connects for 2 seconds, then disconnects.
>
> You need some actual information for a diagnosis.  If you don't want to
> share the actual IPs, some general traits are very relevant:
>
> IPv4?  IPv6?
>
> Private IPs?  (192.168.*.*,172.168.*.*.*,10.*.*.*,fc00::/7, etc)
>
> NAT?
>
> --
>      Stuart D. Gathman <[hidden email]>
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial._______________________________________________
> Linphone-users mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Stuart D. Gathman
On Sat, 8 Jun 2019, Robert Dixon wrote:

> IPv4
> Private IPs.   192.168.*.*

I've only verified this for private IPv6, but one of the underlying
libraries changed early this year to become rather prejudiced against
private IPs.  If any routable public IPs are available, it will try
to use those for SIP responses - ignoring the private IP you told it
to use.  If the public IP is actually routed to your destination (not
likely for your private IP4s, more likely for private IPv6), and
is allowed through firewalls, well and good (except if you
were counting on a VPN to encrypt things).  Otherwise, the call
setup fails, or works briefly before failing.

I haven't tested with IP4 (it's been obsolete for 15 years), but I
suspect the same thing happens with private IP4.

The work-around for me is to disable IP6 on the public (non-vpn)
interfaces during the call.  That is likely more difficult for you,
as your VPN probably doesn't support layer 2 connections, and relies
on public IP4s to send/recv VPN packets.

If your private IP4s are assigned by a router, and you have no public
IPs on the PCs - then your problem is likely with router or firewalls
instead.

--
       Stuart D. Gathman <[hidden email]>
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Robert Dixon
In reply to this post by Stuart D. Gathman
I disabled both firewalls. No change.
ports:
sip udp 5060 enabled
      tcp -1  random
audio 7078
video 9078
all same on both PCs.

Bob

> On Jun 8, 2019, at 1:27 PM, Stuart D. Gathman <[hidden email]> wrote:
>
> On Sat, 8 Jun 2019, Robert Dixon wrote:
>
>> I have 2 PCs connected by  switch, and then to a router.Using IP address
>> calling  sip:ip address.
>> If I call from A to B, then A says B cannot respond to the call.
>> If I call from B to A, it connects for 2 seconds, then disconnects.
>> What is going on?
>
> You also need to report what ports are allowed through firewall on
> both sides, and what ports linphone is configured to use for SIP,
> audio RTP, and video RTP.  The version of linphone is critical.
>
> If the ips in question are private IPv6, you might find this bug
> relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1713947
>
> --
>      Stuart D. Gathman <[hidden email]>
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial._______________________________________________
> Linphone-users mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Robert Dixon
In reply to this post by Stuart D. Gathman
I changed both PCs to a different switch and router. No internet connection.
addresses are now 10.176.*.*
No change in behavior.
I could disable IPv6, but I doubt that is in play here.

Thanks for your help!

Bob

> On Jun 8, 2019, at 1:41 PM, Stuart D. Gathman <[hidden email]> wrote:
>
> On Sat, 8 Jun 2019, Robert Dixon wrote:
>
>> IPv4
>> Private IPs.   192.168.*.*
>
> I've only verified this for private IPv6, but one of the underlying libraries changed early this year to become rather prejudiced against
> private IPs.  If any routable public IPs are available, it will try
> to use those for SIP responses - ignoring the private IP you told it
> to use.  If the public IP is actually routed to your destination (not
> likely for your private IP4s, more likely for private IPv6), and
> is allowed through firewalls, well and good (except if you
> were counting on a VPN to encrypt things).  Otherwise, the call
> setup fails, or works briefly before failing.
>
> I haven't tested with IP4 (it's been obsolete for 15 years), but I
> suspect the same thing happens with private IP4.
>
> The work-around for me is to disable IP6 on the public (non-vpn) interfaces during the call.  That is likely more difficult for you,
> as your VPN probably doesn't support layer 2 connections, and relies
> on public IP4s to send/recv VPN packets.
>
> If your private IP4s are assigned by a router, and you have no public
> IPs on the PCs - then your problem is likely with router or firewalls
> instead.
>
> --
>      Stuart D. Gathman <[hidden email]>
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
>
> _______________________________________________
> Linphone-users mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Robert Dixon
In reply to this post by Stuart D. Gathman
I turned off IPv6 in both PCs. No change.

Bob

> On Jun 8, 2019, at 1:41 PM, Stuart D. Gathman <[hidden email]> wrote:
>
> On Sat, 8 Jun 2019, Robert Dixon wrote:
>
>> IPv4
>> Private IPs.   192.168.*.*
>
> I've only verified this for private IPv6, but one of the underlying libraries changed early this year to become rather prejudiced against
> private IPs.  If any routable public IPs are available, it will try
> to use those for SIP responses - ignoring the private IP you told it
> to use.  If the public IP is actually routed to your destination (not
> likely for your private IP4s, more likely for private IPv6), and
> is allowed through firewalls, well and good (except if you
> were counting on a VPN to encrypt things).  Otherwise, the call
> setup fails, or works briefly before failing.
>
> I haven't tested with IP4 (it's been obsolete for 15 years), but I
> suspect the same thing happens with private IP4.
>
> The work-around for me is to disable IP6 on the public (non-vpn) interfaces during the call.  That is likely more difficult for you,
> as your VPN probably doesn't support layer 2 connections, and relies
> on public IP4s to send/recv VPN packets.
>
> If your private IP4s are assigned by a router, and you have no public
> IPs on the PCs - then your problem is likely with router or firewalls
> instead.
>
> --
>      Stuart D. Gathman <[hidden email]>
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
>
> _______________________________________________
> Linphone-users mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/linphone-users


_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users
Reply | Threaded
Open this post in threaded view
|

Re: Strange Linphone Failure

Stuart D. Gathman
On Sat, 8 Jun 2019, Robert Dixon wrote:

> I turned off IPv6 in both PCs. No change.

You said you were using IP4 - so that possibility didn't apply.


--
       Stuart D. Gathman <[hidden email]>
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

_______________________________________________
Linphone-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/linphone-users