David Cunningham writes:
> I must say RFC 6665 4.4.1 does seem to make it clear that the route set in
> the NOTIFY should be used, and therefore it's incorrect that the
> re-SUBSCRIBE sends directly to the Contact address rather than using the
> Record-Routes in the NOTIFY. It's very helpful to
Zuñiga, Guillermo writes:
> Hi fellows,
>
> I would like you can help me with the following doubt.
>
> I am having a user is Registering ok to a Registrar Server.
> Seeing the authorization values I can see that we have the Authorization
> Header wiht the following Authentication-URI value=
Though I notice that RFC 6665 4.4.1 also says:
unless the NOTIFY request contains a "Subscription-State" of
"terminated."
And in our case the subscription state is "terminated". The dialog is then
over, so I guess that the other RFCs then apply.
On Thu, 25 Jul 2019 at 21:43, David
Thank you Paul, and thank you Richard.
I must say RFC 6665 4.4.1 does seem to make it clear that the route set in
the NOTIFY should be used, and therefore it's incorrect that the
re-SUBSCRIBE sends directly to the Contact address rather than using the
Record-Routes in the NOTIFY. It's very
On 7/25/19 5:53 AM, David Cunningham wrote:
Though I notice that RFC 6665 4.4.1 also says:
unless the NOTIFY request contains a "Subscription-State" of
"terminated."
And in our case the subscription state is "terminated". The dialog is
then over, so I guess that the other RFCs then
