1 / 9

Telephone Number Mapping (ENUM) Service Registration for MGCP

IETF 69 – ENUM WG. Telephone Number Mapping (ENUM) Service Registration for MGCP. < draft-chenbo-enum-mgcp-01 > CNNIC-Lab. July, 2007. Background-3W. Why ENUM-MGCP? MGCP is widely used in VoIP No MGCP-relative ENUM RFCs or IDs

tolla
Download Presentation

Telephone Number Mapping (ENUM) Service Registration for MGCP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF 69 – ENUM WG Telephone Number Mapping (ENUM) Service Registration for MGCP <draft-chenbo-enum-mgcp-01> CNNIC-Lab July, 2007

  2. Background-3W • Why ENUM-MGCP? • MGCP is widely used in VoIP • No MGCP-relative ENUM RFCs or IDs • What can we do if we want to call from a SIP or H.323 VoIP system to MGCP system using ENUM? • Where is ENUM-MGCP mainly used? • ENUM-MGCP is mainly used in carrier networks. • What is ENUM-MGCP mainly for? • making a unified addressing intra or inter MGCP system or even between other VoIP systems and MGCP systems.

  3. Introduction • ENUM is a system that uses Domain Name System (DNS) to translate telephone numbers into URIs • MGCP decomposes a multimedia gateway into two parts, a call agent and a media gateway. MGC (Media Gateway Controller), known as Call Agent, takes charge of all of the call-control “intelligence”, while MG (Media Gateway) is just accountable for the media conversion • This document registers the MGCP Enumservice according to the guidelines given in RFC3761

  4. ENUM Service Registration - MGCP • Enumservice Name: "MGCP" • Enumservice Type: "mgcp" • Enumservice Subtype: "tel" • URI Scheme: "tel:" • Functional Specification: This document defines an 'E2U+mgcp:tel' Enumservice for MGCP. The scheme of the URI that will appear in the regexp field of a NAPTR record using the 'E2U+mgcp:tel' Enumservice is 'tel'. • Intended Usage: COMMON

  5. Address of record in MGCP • The address of MGCP end-points includes two parts. One is the domain name of attributive gateway, the other is the local name of this terminal in the gateway. Endpoint names are of the form: local-endpoint-name@domain-name Local name usually uses the form of physical interface/circuit number. As an example, MGCP address “hrd4/56@gw23.example.net” means that the attributive gateway is gw23.example.net, and the physical interface Is hrd4 , while the circuit number is 56.

  6. Example • An example ENUM record referencing to "MGCP" could look like: $ORIGIN 9.2.1.3.1.8.8.5.0.1.6.8.e164.arpa. @ IN NAPTR 10 100 "u" "E2U+mgcp:tel" "!^.*$!tel:hrd4/56@tst.cn!" .

  7. Application scenario SIP-MGCP the simplified ENUM-based call procedure between SIP-based system and MGCP-based system MGCP-based system Call agent SIP-based system 4 CRCX hrd4/56@tst.cn 1 invite:+861058813100 MG: sf.cn 3 ENUM query answer 2 ENUM query 5 RINGING T1(ip terminal) sip:chenbo@cnnic.cn T2 T1 ENUM Simplified Call signal ENUM query $ORIGIN 0.0.1.3.1.8.8.5.0.1.6.8.e164.arpa. @ IN NAPTR 10 100 "u" "E2U+mgcp:tel" "!^.*$!tel:hrd4/56@sf.cn!" .

  8. Conclusion • This document registers the MGCP Enumservice according to the guidelines given in RFC 3761 and ID "Guide and Template for IANA Registrations of Enumservices" (draft-ietf-enum-enumservices-guide-04 ) • as a supplement to RFC3762(ENUM-H.323) and RFC3764(ENUM-SIP)

  9. Thank you! enum@cnnic.cn

More Related