[Blink] no audio if multiple ip-addresses are active
kenny.macdermid at gmail.com
Fri Aug 13 15:00:01 CEST 2010
On 11 August 2010 04:29, Saúl Ibarra Corretgé <saul at ag-projects.com> wrote:
>> Here's the differences I see between a working SIP/SDP connection with
>> another client, and Blink:
>> My vlan IP is 10.1.15.10, other IPs on interfaces are 172.27.0.148 and
>> X: Via: SIP/2.0/UDP
>> B: Via: SIP/2.0/UDP
>> -- this is the first case of the wrong IP address. 192.168.53.1 is
>> actually the IP of a vmware interface that's not used for any normal
> This is not right. Can you reproduce it always? If so, can you give me more
> details on your network setup so I can reproduce it?
I can, it happens with every call I make. My network setup is as follows:
en0: ethernet cable unplugged
en1: wifi IP of 172.27.0.148
vmnet1: vmware fusion virtual iface, IP 192.168.53.1
vmnet8: vmware fusion virtual iface, IP 192.168.25.1
jnc0: vpn interface, IP 10.1.15.10
My SIP server is at 10.1.20.7
Routing info (related to the call):
Destination Gateway Flags Netif
default 172.27.0.1 UGSc en1
10.1/16 10.1.15.10 UGSc jnc0
192.168.53 link#8 UC vmnet1
The VPN is setup using Juniper Network Connect.
>> X: Contact:<sip:432 at 10.1.15.10:35060;transport=udp>
>> B: Contact:<sip:tjrkpxia at 172.27.0.148:50200>
>> -- this is the second incorrect address. 172.27.0.148 is the IP of the
>> default route interface. Also 432 is the extension of the client. I'm
>> not sure what tjrkpxia is.
> Blink currently sends all traffic through the default route, so this is
> expected. If your default route gos through that IP address, it will be the
> one chosen. There is no support for selecting other interfaces.
You say this is expected. Do you mean it's expected currently, but a
bug? The SIP traffic is not being sent out the default route, it's
being sent out the 10.1.15.10 interface (as I would expect). If it's
using an IP for a route it's not using I'd consider that a bug.
>> Now in SDP:
>> X: o=- 8 2 IN IP4 10.1.15.10
>> B: o=- 3490461286 3490461286 IN IP4 172.27.0.148
>> X: c=IN IP4 10.1.15.10
>> B: c=IN IP4 172.27.0.148
>> the a= lines also differ, but I doubt they'd matter.
> Even if o and a lines are wrong audio would flow if c line is correct. It
> looks like here we have the same case as in the Contact header: the IP for
> the default route is being used, as expected.
Again, not quite sure what you mean by expected.
If I can provide any more assistance on tracking this down let me
know. I'd much rather use Blink than X-Lite.
More information about the Blink