[Blink] no audio if multiple ip-addresses are active

Saúl Ibarra Corretgé saul at ag-projects.com
Wed Aug 11 09:29:52 CEST 2010


Hi,

> 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
> 192.168.53.1.
>
> For the initial invite, X is the other client, B is Blink:
>
> X: INVITE sip:918007475150 at 10.1.20.7;transport=udp SIP/2.0
> B: INVITE sip:918007475150 at 10.1.20.7 SIP/2.0
>

The request line is fine.

> X: Via: SIP/2.0/UDP
> 10.1.15.10:35060;branch=z9hG4bK-d8754z-cd13430b3700605d-1---d8754z-;rport
> B: Via: SIP/2.0/UDP
> 192.168.53.1:50200;rport;branch=z9hG4bKPjgI0zX.MMVgnKbuS4io19Qse-bpMpctyh
>
> -- 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
> traffic.
>

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?

> 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.

The contact username is correct, we use a random string so it doesn't 
collide if multiple SIP clients are used at the same time in the same 
machine. The AoR is specified in the REGISTER requests To header.

> 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.

> These both result in a TRYING, and then OK. The only difference in the
> OK is that the VIA sent to blink contains the 192.168.53.1 address
> again:
>
> X: Via: SIP/2.0/UDP
> 10.1.15.10:35060;branch=z9hG4bK-d8754z-389e4b0db963dd1d-1---d8754z-;rport
> B: Via: SIP/2.0/UDP
> 192.168.53.1:50200;received=10.1.15.10;rport;branch=z9hG4bKPjCyOAaVPtvcVTmDG8JlClpVAyWlWlCyAb
>
> I'm not sure how this mailing list is with attachments, but I'll
> include a .txt of the working and non-working SIP connections from
> Wireshark. I deleted the Authorization: headers.
>

Thanks for sending the traces. Looks like the IP address in Via and 
a=rtcp lines is wrongly calculated. If you are able to reproduce this 
I'd be interested in knowing the details so this can be fixed.


Regards,

-- 
Saúl Ibarra Corretgé
AG Projects



More information about the Blink mailing list