[Blink] Blink & OnSip compatibility question

Adrian Georgescu ag at ag-projects.com
Tue Jan 4 19:11:59 CET 2011

Yes, is bug in Blink, which should handle the wrong unescaped @ without crashing. 

But after this problem is fixed, Blink will never ring for such incoming calls as the INVITE request URI is wrong. The Onsip INVITE is broken because the Request URI does not match the Contact address used in REGISTER. 


On Jan 4, 2011, at 6:49 PM, Carolyn Kelly wrote:

> Hello,
> We have been working with a mutual client who is having difficulty connecting our two services together. At this time, we believe part of the issue may lie with the INVITE - specifically in regards to the second @ in the user address, which shouldn't be read after the semicolon as we send it as an escaped character (%40)
> However, in the capture sent to us - it appears that the address is being unescaped and thus triggering a failure within Blink.
> Would it be possible for your team to confirm if this might be the case?  We'd be happy to send more information examples if necessary - just looking to ensure our mutual client(s) get the most out of both of our products!
> Thanks,
> Carolyn
> JunctionNetworks.com | Onsip.com

More information about the Blink mailing list