1 / 7

Multimedia Access Platforms

Multimedia Access Platforms. Glen Freundlich Avaya, Inc. ggf@avaya.com. IP Telephony Gateways. Gateway. Network A. Network B. Gateway converts between 2 networks: signaling conversion media (bearer) conversion service conversion

walter
Télécharger la présentation

Multimedia Access Platforms

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. Multimedia Access Platforms Glen Freundlich Avaya, Inc. ggf@avaya.com

  2. IP Telephony Gateways Gateway Network A Network B • Gateway converts between 2 networks: • signaling conversion • media (bearer) conversion • service conversion • Networks could be same types (firewall, NAT).

  3. IP-ISDN Gateway Signaling conversion Gateway D channel H.323, SIP B channel RTP Bearer conversion Gateway consists of multiple functions which need not co-exist in same physical box.

  4. Gateway Decomposition Gateway Signaling Gateway Media Gateway Controller Media Gateway H.248/Megaco

  5. IETF/ITU Collaboration • Work begun independently in 1998 in IETF, ITU-T SG16, ETSI TIPHON • ETSI TIPHON and MSF became suppliers of requirements • Agreement at management level in March 1999 • IETF Megaco WG and ITU-T SG16 Q14 develop gateway control protocol as a joint project • Megaco to own requirements document • Q14 to own final protocol standard

  6. Gateway Control Protocols NCS/J.162 IPDC TGCP/J.171 MGCP SGCP MDCP H.248/Megaco others

  7. Future Collaboration? • Additions to H.248 for a Version 2 • Package coordination • reduce or eliminate overlap • validate architecture • check for completeness • Interoperability/testing • Interworking (e.g., to H.323, SIP, BICC) • ???

More Related