RFC 4694: Number Portability Parameters for the "tel" URI

Publisher

IETF / RFC Editor

URL

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

Published

2006-10-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions; short excerpts and locators only

Source notes citing this source

• Per RFC 4694, a node that performs the dip and retrieves a routing number must add both the 'rn' and the 'npdi' parameters to the tel URI. in context
• The RFC 4694 'npdi' tel URI parameter tells downstream servers or switches that a number portability database dip has already been performed for the number. in context
• Per RFC 4694, a network node receiving a tel URI that contains 'npdi' must not retrieve number portability information for a geographic number again, even if it is configured to do so. in context
• RFC 4694 defines an 'rn' parameter for the tel URI that carries the routing number associated with a telephone number that has been ported out from a donor carrier to another carrier. in context
• RFC 4694 states that the number portability tel URI parameters are meant for use between call signalling entities that share a trust relationship. in context
• 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. in context
• When converting ISUP to SIP for a ported geographical number, RFC 4694 requires the routing number found in the ISUP Called Party Number to be carried in the rn parameter of the routing tel URI. in context
• RFC 4694 requires the cic parameter on the routing tel URI when the ISUP Carrier Identification Parameter is present. in context
• RFC 4694 requires the number marked as ported number in the ISUP Generic Address Parameter to become the telephone number of the routing tel URI. in context
• RFC 4694 says a node MAY put rn on the caller-information tel URI when the ISUP Jurisdiction Information Parameter is present; JIP does not populate the routing URI. in context
• Under RFC 4694, a network node MUST NOT retrieve number portability information for a geographical number if the tel URI already carries the npdi parameter. in context
• RFC 4694 requires npdi on the routing tel URI when the Ported Number Translation Indicator bit in the ISUP Forward Call Indicators is set to 1. in context

Cite this source record

APA

WarmTransfer. (2006, October 1). RFC 4694: Number Portability Parameters for the "tel" URI. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-4694-tel-uri-np-params

BibTeX

@misc{warmtransfer-rfc-4694-tel-uri-np-params,
  title  = {RFC 4694: Number Portability Parameters for the "tel" URI},
  author = {{WarmTransfer}},
  year   = {2006},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-4694-tel-uri-np-params},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}