URI schemes is defined for the "Service number translation" use case. Their use is undefined for otherĪ new value for the "cause" URI parameter of the 'sip:' or 'sips:' The procedures it defines are intended for networks Partnership Project (3GPP) to identify the serviceĪccess number. This document also answers a need expressed by the Third Generation Guidance for using the "cause" URI parameter in conjunction with the Relation has not been described in, this document provides The History-Info header field defined in. Services, usage of the "cause" URI parameter is only relevant within In order to provide full call forwarding or access number translation Service access number requested before its translation to the final The mechanism will allow a SIP network to insert and convey the With SIP signaling with the ISUP called IN number and original called Perform service access number translation, and to enable interworking Well-known services, such as premium or toll-free services that This specification proposes a solution to allow the identification of Needs to be translated into a routable SIP or tel URI to process the This special number is not a globally routable number therefore, it Refer to the dialable number by which a specific service is reached. The term "service access number" is used in this specification to Of the requested service access number prior its translation The "original called IN number" parameters to capture the information Services, ISDN User Part (ISUP) introduced the "called IN number" and (VPN), Freephone, etc.) based on greater flexibility and newĬapabilities as described in. Universal Personal Telecommunication (UPT), Virtual Private Network Indeed, IN aims to ease the introduction of new services (i.e., Translation of the called number as mentioned in. Introduced by the Intelligent Network (IN) services based on a Services Digital Network (ISDN), there is another kind of retargeting In the Public Switched Telephone Network (PSTN ) / Integrated The concept of "retargeting" is defined in Values equivalent to the TDM (Time Division Multiplexing) Redirecting Target URI identifies the reason for retargeting and has defined defines a mechanism to identify retargeting due to callįorwarding supplementary services. Handling and Processing the Service Number Translation Interaction with Request History Information. The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 8119 Cause for Service Number Translation March 2017Ĭopyright (c) 2017 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Not all documentsĪpproved by the IESG are a candidate for any level of Internet Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This document is not an Internet Standards Track specification it is The History-Info header field, since this use is mandatory in some IP Was missing in RFC 4458, for using the "cause" URI parameter within This document also provides guidance, which Specific service action leading to the translation of a called To cover service number translation for cases of retargeting due to This document updates RFC 4458 by creating a new predefined value for the "cause" URI parameter Is used to indicate a reason why the request arrived to the UserĪgent Server (UAS) receiving the message. Parameter, which may appear in the Request-URI of a SIP request, that RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI SIP "cause" URI Parameter for Service Number Translation Internet Engineering Task Force (IETF) M. RFC 8119: SIP "cause" URI Parameter for Service Number Translation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |