Source note · SIP OPTIONS pings and trunk keepalives
RFC 3261 says the response to an OPTIONS should be the one an INVITE would get: 200 if the server would accept an INVITE, 486 Busy Here if it currently cannot take new sessions.
Checked 2026-09-24
- Vendor
- IETF
- Product
- SIP
- Subsystem
- OPTIONS method
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261 (June 2002)
- Checked
- 2026-09-24
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 11.2 'Processing of OPTIONS Request'
Cite this note
APA
WarmTransfer. (2026, September 24). SIP OPTIONS pings and trunk keepalives: source note sip-options-keepalive-rfc3261-response-mirrors-invite. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-options-keepalive-rfc3261-response-mirrors-invite
BibTeX
@misc{warmtransfer-claim-sip-options-keepalive-rfc3261-response-mirrors-invite,
title = {SIP OPTIONS pings and trunk keepalives: source note sip-options-keepalive-rfc3261-response-mirrors-invite},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-options-keepalive-rfc3261-response-mirrors-invite},
note = {Source note sip-options-keepalive-rfc3261-response-mirrors-invite, checked 2026-09-24}
}