RFC 3398 maps ISUP cause 22 (number changed) to 410 Gone, or to 301 Moved Permanently when a diagnostic carrying the new number is present.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- ISUP-SIP interworking
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3398 as published
- Checked
- 2026-10-02
Sources
- RFC 3398: Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping — IETF / RFC Editor · tier 1 standards and regulators · Section 7.2.4.1 (ISDN Cause Code to SIP Status Code mapping table), cause 22 rows
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-rfc3398-cause22-to-410. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3398-cause22-to-410
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-rfc3398-cause22-to-410,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-rfc3398-cause22-to-410},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3398-cause22-to-410},
note = {Source note sip-404-484-troubleshooting-rfc3398-cause22-to-410, checked 2026-10-02}
}