Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to SIP Services

...

 

The SUBSCRIBE method is used to by the

Spacevars
0product
 to request the current state and state updates from the remote node. The subscription is valid until the expiration of the subscription timer (indicated in Expires header), or by explicit removal of the subscription (by sending SUBSCRIBE with expires 0, or sending NOTIFY with subscription state as terminated).

...

Note that the received Route header is applicable for INVITE only.

The

Spacevars
0series4product
maintains a context for SUBSCRIBE for duration of subscribe timer (the expires value in SUBSCRIBE request). During subscription, if any in-dialog SUBSCRIBE/NOTIFY is received, then routing is based on record-routes present in SUBSCRIBE or 200 OK to SUBSCRIBE or NOTIFY if it comes before 200 OK to SUBSCRIBE.

...

  1. When the
    Spacevars
    0product
    receives initial SUBSCRIBE with record-route, the 
    Spacevars
    0product
    stores the received record-routes in subscription context and forwards the received in-dialog requests based on the route set that is formed from received record-route headers.
  2. When the
    Spacevars
    0product
    receives 200 OK to initial SUBSCRIBE with record-route, the
    Spacevars
    0product
    stores these received record-routes as a route set on egress side and uses the same route set to forward the further in-dialog requests towards core.
  3. When the 
    Spacevars
    0product
    receives initial NOTIFY from core before receiving 200 OK to initial SUBSCRIBE, the
    Spacevars
    0product
    forms the egress route set based on the received record-routes in initial NOTIFY and uses the same route set to forward further in-dialog requests (refresh SUBSCRIBE) towards core.

...