RFC 6141: Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc6141.txt

Published

2011-03-01

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• A 488 to a hold or resume re-INVITE does not by itself end the call under the SIP rules; a drop that follows is a decision by one of the devices (for example sending BYE), not a consequence required by the rejection. inferred in context
• When re-INVITE glare occurs, the UAS returns 491 (Request Pending) and the UAC retries the offer after a randomly selected time that depends on which user agent owns the dialog's Call-ID, as specified in RFC 3261 sections 14.1 and 14.2. in context
• If a re-INVITE is rejected with a non-2xx final response, no session state change is made and the session continues with its previously negotiated parameters. in context
• A UAC that receives an error response to a re-INVITE for which changes were already executed SHOULD send a new re-INVITE or UPDATE so both user agents share the same view of the session state. in context
• If any change requested in a re-INVITE, or in a transaction within it, has already been executed, the UAS SHOULD return a 2xx response rather than an error. in context
• A UAS should return an error response to a re-INVITE only if no session state changes have been executed since the re-INVITE was received. in context

Cite this source record

APA

WarmTransfer. (2011, March 1). RFC 6141: Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-6141-reinvite-handling

BibTeX

@misc{warmtransfer-rfc-6141-reinvite-handling,
  title  = {RFC 6141: Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)},
  author = {{WarmTransfer}},
  year   = {2011},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-6141-reinvite-handling},
  note   = {IETF / RFC Editor, accessed 2026-09-30}
}