Per RFC 4694, when a node performs the dip and no routing number is returned (for example a non-ported geographic number), it must still add 'npdi' without an 'rn' parameter.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- sip-signalling
- Deployment
- sip
- Region
- not restricted
- Release range
- RFC 4694
- Checked
- 2026-10-02
Sources
- RFC 4694: Number Portability Parameters for the "tel" URI — IETF / RFC Editor · tier 1 standards and regulators · RFC 4694 Section 5.2.1
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting calls that fail to ported numbers after cutover: source note post-port-routing-troubleshooting-rfc4694-unported-npdi-only. WarmTransfer. https://warmtransfer.net/knowledge/claims/post-port-routing-troubleshooting-rfc4694-unported-npdi-only
BibTeX
@misc{warmtransfer-claim-post-port-routing-troubleshooting-rfc4694-unported-npdi-only,
title = {Troubleshooting calls that fail to ported numbers after cutover: source note post-port-routing-troubleshooting-rfc4694-unported-npdi-only},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/post-port-routing-troubleshooting-rfc4694-unported-npdi-only},
note = {Source note post-port-routing-troubleshooting-rfc4694-unported-npdi-only, checked 2026-10-02}
}