Inline

On 7/21/19 6:42 PM, David Cunningham wrote:
Hello,

We have the following issue and are looking for some advice on the expected
behaviour:

1. UAC sends SUBSCRIBE to UAS at x.x.x.x:5061, receives 200 OK in response.
2. UAS sends NOTIFY to UAC with Record-Route x.x.x.x:5061, Via
x.x.x.x:5061, and Contact x.x.x.x:56095, receives 200 OK in response.
3. UAC sends SUBSCRIBE to UAS at x.x.x.x:56095, receives no response
because port is not accessible directly from the UAC.

These are all within one dialog. RFC 3261 12.2 says:

    Requests within a dialog MAY contain Record-Route and Contact header
    fields.  However, these requests do not cause the dialog's route set
    to be modified, although they may modify the remote target URI.
    Specifically, requests that are not target refresh requests do not
    modify the dialog's remote target URI, and requests that are target
    refresh requests do.

The NOTIFY is a target refresh request, so presumably the remote target URI
is then considered to be x.x.x.x:56095 as specified in the Contact header.

But dos the Record-Route in the NOTIFY really have no effect on the
subsequent SUBSCRIBE? Can the NOTIFY not tell the UAS to route via
x.x.x.x:5061 instead of sending to x.x.x.x:56095 directly?

Your example is hard to understand because of the repeated use of x.x.x.x - it isn't clear if all instances of that are intended to be the same or if each is intended to carry different values. Please restate your problem, showing exactly what changes in the NOTIFY and what stays the same.

But for your basic question, the route set for a dialog is finalized during dialog establishment. Subsequently only the addresses of the endpoints can be changed. If you need to change the route set you can send an INVITE/Replaces or a REFER/Replaces to establish a totally new dialog to replace the old one.

        Thanks,
        Paul

Thank you in advance!

--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to