[Blink] GRUU-related no ACK problem behind sipX

[Adrian Georgescu]

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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20140701/9c969636/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20140701/9c969636/attachment.pgp>