[Sip-implementors] Notify and Re-INVITE clarification.

Brett Tate

2014-03-12 11:02:35 UTC

Post by Aditya Kumar
1. If UA is subscribing to MWI (or) reg event..
when it receivesa?immediately NTY with?subscription
state as : Terminated should the UA re-retry to re-subscribe?
As per rfc's/specs in?which?cases does a UE does not re-try to re-
subscribe. (Error codes (or) NTY-?subscription?state)

See RFC 6665 section 4.1.3.

"If a reason code is present, the client
should behave as described below. If no reason code or an unknown
reason code is present, the client MAY attempt to re-subscribe at any
time (unless a "retry-after" parameter is present, in which case the
client SHOULD NOT attempt re-subscription until after the number of
seconds specified by the "retry-after" parameter)."

Post by Aditya Kumar
2. when a UE send session-timer (or) any things in
Supported: header in INVITE. should it include that
header in PRACK (or) Re-INVITE send by the same UA?
(In This case Target also supports session-timer and
it is working between UA-UA. but want to know for
mid-call signalling) and also reference in rfc's.

As indicated within RFC 4028 section 4, the Session-Expires stuff is only
negotiated (activated/deactivated) using UPDATE, INVITE, and re-INVITE.
However, RFC 4028 section 7.1 does indicate the following.

"A UAC that supports the session timer extension defined here MUST
include a Supported header field in each request (except ACK),
listing the option tag 'timer' [2]. It MUST do so even if the UAC is
not requesting usage of the session timer for this session."

--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.