RFC 3398 places overlap dialling mechanisms (use of the ISUP Subsequent Address Message) outside its scope.
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 4 (scope note on overlap dialling)
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-overlap-out-scope. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3398-overlap-out-scope
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-rfc3398-overlap-out-scope,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-rfc3398-overlap-out-scope},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-rfc3398-overlap-out-scope},
note = {Source note sip-404-484-troubleshooting-rfc3398-overlap-out-scope, checked 2026-10-02}
}