Hi,

I have the same problem (but I don't have two physical interfaces but one
physical and two interfaces created by VMware).
But since I only use a SIP server within my network I was able to get rid of
this problem by installing a STUN server (which I have had to install anyway
bevause I use that SIP server through a VPN connection too).

I think it would be a nice to have if it was possible to select the
interface which Linphone is using. Which, by the way, would be a nice
feature in the Android client too.

Kind regards,
Marc


2011/4/20 Сергей Пачков <[email protected]>

> On my Windows XP PC I have two ethernet cards with IPs: 192.168.1.10 and
> 192.168.7.70
>
> I (A-side) call to [email protected] (B-side). Route table has rule
> to send packets through 192.168.7.70.
>
> SIP  INVITE sends from 192.168.7.70 and SIP negotiation looks FINE but in
> INVITE/SDP connection field
> contains 192.168.1.10
>
> and side B of call will send RTP to 192.168.1.10 which isn't accessable
> from B-side.
> in this case B-side will listen A-side but A-side wouldn't listen B-side.
>
> It will be nice when SDP part will contain proper connection line with IP
> which LinPhone uses to communicate with B-side.
>
> In this case LinPhone sends everything from 192.168.7.70 but in SDP it
> points RTP to 192.168.1.10 (this is wrong)
>
> in attachment I placed network dump gathered by WireShark
>
> /Sergey Pachkov
>
> _______________________________________________
> Linphone-users mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/linphone-users
>
>


-- 
Grüße,
Marc Rasmussen
_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users

Reply via email to