RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction

Publisher

RFC Editor / IETF

URL

https://www.rfc-editor.org/rfc/rfc4320.html

Published

2006-01-01

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); short excerpts and locators only

Source notes citing this source

• RFC 4320 finds that a 408 response to a non-INVITE request always arrives too late to be useful. in context
• RFC 4320 forbids a transaction-stateful SIP element from sending a 408 response to a non-INVITE request. in context
• RFC 4320 forbids answering a non-INVITE request with 100 over an unreliable transport such as UDP before the client's Timer E would have reached T2. in context
• On the wire, a REGISTER timeout in an RFC 4320-compliant path usually shows as repeated REGISTER retransmissions with no final response, and any 408 a phone reports is probably generated locally by its own transaction layer rather than received. inferred in context

Cite this source record

APA

WarmTransfer. (2006, January 1). RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-4320-non-invite-actions

BibTeX

@misc{warmtransfer-rfc-4320-non-invite-actions,
  title  = {RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction},
  author = {{WarmTransfer}},
  year   = {2006},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-4320-non-invite-actions},
  note   = {RFC Editor / IETF, accessed 2026-09-25}
}