[Blink] RTP issue in Bonjour mode

John Dyer jdyer at tropo.com
Mon Aug 12 17:00:20 CEST 2013


Hello,

  In Blink 3.0.1 on OSX I am no longer able to call hosts on my network “direct” due to an RTP issue.  I noticed in the SDP there is two media IP addresses which is causing issues for us.   I tried this in Bonjour mode and it doesn’t work.  I also tried creating a dummy connection w/o proxy registration in hopes that this maybe was some sort of Bonjour bug, but that didn’t work either.  Both invites are below:


Bonjour Connection
——

SENDING: Packet 302, +1:53:53.749916
2013-08-12 10:57:14.672035: 192.168.1.36:61805 -(SIP over UDP)-> 10.6.xxxx.xxxx:5060
INVITE sip:999xxxxx at tropo104.xxxx.xxxxx SIP/2.0
Via: SIP/2.0/UDP 192.168.1.36:61805;rport;branch=z9hG4bKPjUMqCKNLxWZ62KIOLjA9rSzjyWmZnWh.i
Max-Forwards: 70
From: "John Dyer" <sip:91835470 at 192.168.1.36>;tag=G-7nC82x41PT7DCgVmIhtDbRBY1D8zAY
To: <sip:9991x at tropo104.xxxx.xxx.xxxxxx>
Contact: <sip:91835470 at 10.6.96.92:61805>
Call-ID: LQh-lMA5AG.TTgNHZLLrMW1D24kTlbBv
CSeq: 6709 INVITE
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER
Supported: 100rel, replaces, norefersub, gruu
User-Agent: Blink Pro 3.1.0 (MacOSX)
Content-Type: application/sdp
Content-Length:   556

v=0
o=- 3585308234 3585308234 IN IP4 10.6.96.92
s=Blink Pro 3.1.0 (MacOSX)
c=IN IP4 10.6.96.92
t=0 0
m=audio 50030 RTP/AVP 108 99 98 9 0 8 96
c=IN IP4 192.168.1.36
a=rtcp:50031
a=rtpmap:108 opus/48000
a=rtpmap:99 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:DmZqsgsiaCkJjolhkPdd7OFS2aPoYOlJageL9unP
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:LpkpmzbtBeXmKL533PUGEaZVkiwuCU+qVmn5rDb1
a=sendrecv



-----
New “dummy” connection w/o proxy 
——

2013-08-12 10:36:42.384435: 192.168.1.36:61805 -(SIP over UDP)-> 10.xx.xx.xx:5060
INVITE sip:9991xxxxx at tropo185.xxxx.xxxx.xxxxx SIP/2.0
Via: SIP/2.0/UDP 192.168.1.36:61805;rport;branch=z9hG4bKPjAd41oBUQpi82hG8SZVs9w7WOq8ABbmwb
Max-Forwards: 70
From: "John Dyer" <sip:4074740214 at 127.0.0.1>;tag=c4oNSScUBSgmxdpMM.qQcUYgQN66WBuZ
To: <sip:9991xxxxx at tropo185.xxxx.xxxx.xxxxxt>
Contact: <sip:79512640 at 10.6.96.92:61805>
Call-ID: QzfmZT4rEEymU.aepaSzHDOe.9dJWaRw
CSeq: 12965 INVITE
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER
Supported: 100rel, replaces, norefersub, gruu
User-Agent: Blink Pro 3.1.0 (MacOSX)
Content-Type: application/sdp
Content-Length:   556

v=0
o=- 3585307002 3585307002 IN IP4 10.6.96.92
s=Blink Pro 3.1.0 (MacOSX)
c=IN IP4 10.6.96.92
t=0 0
m=audio 50026 RTP/AVP 108 99 98 9 0 8 96
c=IN IP4 192.168.1.36
a=rtcp:50027
a=rtpmap:108 opus/48000
a=rtpmap:99 speex/32000
a=rtpmap:98 speex/16000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:O8UEKlRBwcCSYFeZZGAj6cOCSkEQ0T9SKkwjy2NU
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:PiXB3qmj7rAP1fr84A1ntzf2Iv6zpWisSI9KHN2L
a=sendrecv

———

In both cases you can see two ip’s for IN IP4, and it seems to be honoring the second, which is not going to work over the VPN.  Any idea how I can remove the second IP from the INVITE?  FWIW, this behavior seems to be new to Blink 3.0.x and seems like a bug.  

Thanks

-John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20130812/ed42db69/attachment.html>


More information about the Blink mailing list