[Blink] GRUU-related no ACK problem behind sipX
Saúl Ibarra Corretgé
saul at ag-projects.com
Fri Jul 18 22:58:39 CEST 2014
On 18 Jul 2014, at 19:39, Jeff Pyle <jpyle at fidelityvoice.com> wrote:
> Hi Saúl,
>
> I've heard back from eZuce. They say the problem is the contact is being modified with a transport parameter, and thus failing a match.
>
> Specifically, the gruu contact obtained in one registration is "~~gr~ReZQUTUDuTi at sip.host.net;gr", but the contact returned in a call's 200 OK is "~~gr~ReZQUTUDuTi at sip.host.net;transport=tcp;gr".
>
> The registration domain has a NAPTR record indicating equal weights for UDP and TCP SRV records. I force the registration to TCP with primary proxy value that includes ;transport=tcp. Maybe this is relevant, maybe it's not.
>
> Anyway, their interpretation of the RFC is that, and I quote, "The UA must not modify the GRUU string."
>
> Thoughts?
>
Thanks for looking into this, Jeff. I’ll read the RFC again and come back to you.
Regards,
--
Saúl Ibarra Corretgé
AG Projects
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20140718/d8d5ddcc/attachment.pgp>
More information about the Blink
mailing list