[Blink] GRUU-related no ACK problem behind sipX

[Jeff Pyle]

Since I don't need GRUU support, I'm worked around this issue by editing
line 120 in /Applications/Blink
Pro.app/Contents/Resources/lib/sipsimple/account/registration.py.  I've
changed "Supported: gruu" to "X-Supported: pizza".  While not elegant, it
prevents Blink from receiving a pub-gruu contact on its registration.
 Calls establish without a problem.



- Jeff



On Tue, Jul 1, 2014 at 10:13 AM, Adrian Georgescu <ag at ag-projects.com>
wrote:

> This is the first GRUU related question from the real world!
>
> We will investigate this!
>
> Adrian
>
>
> On 01 Jul 2014, at 15:49, Jeff Pyle <jpyle at fidelityvoice.com> wrote:
>
> Hello,
>
> I run Blink Pro (v3.9.1 build 14012) behind sipXecs.  I have a problem
> where Blink does not receive the ACK after the INVITE's 200 OK, because the
> sipX proxy does not send the ACK once received from the originating side.
>  I'm trying to figure out why.  Before I go to the sipX folks I wanted to
> get some clarification on expected GRUU behavior.
>
> On an inbound call Blink changes the Contact URI in its replies from the
> 100/180 messages to the 200 OK.  The 100/180s have the RURI of the INVITE
> as Contact, while the 200 OK uses the public GRUU URI returned during
> initial registration.  I think this is confusing sipX's proxy.
>
> Is this expected behavior?  If so, since sipX claims to support GRUU, an
> RFC to cite would be helpful when I open a ticket with them.
>
>
> - Jeff
>
>  _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
>
>
> --
> Adrian
>
>
>
>
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20140707/6256b200/attachment.html>