1 / 10

SIP-H.323 Interworking Requirements Overview and Guidelines

This document outlines the interworking requirements between SIP and H.323 protocols, focusing on signaling gateways (SGWs) and service considerations. It discusses three drafts regarding direct mapping and capability resolution, highlighted by implementation approaches. The interworking principles ensure seamless communication between SIP User Agents (UAs) and H.323 end points (EPs) while maintaining procedural compliance. The guide delineates a two-phase approach: Phase 1 covers basic call setups and address resolution, while Phase 2 addresses advanced services such as call transfer and conferencing.

yazid
Télécharger la présentation

SIP-H.323 Interworking Requirements Overview and Guidelines

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. SIP-H.323 InterworkingRequirements Joon Maengjoon_maeng@vtel.com Dave Walkerdrwalker@ss8networks.com

  2. Background • 3 drafts • draft-ietf-singh-sip-h323-00.txt • onus on SGW to resolve capabilities • University of Brussels thesis • focuses on direct mapping • Agrawal/Palawat draft • emphasis on services • 3 approaches => different implementations • together: an excellent start Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  3. Guiding Principles • SIP UA and H.323 EP communicate • terminals are unaware of interworking • compatible with H.323v2 and RFC 2543 • procedurally compliant • why not H.323v1? why not v3? v4? • may use compliant standard extensions Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  4. SIP-H.323 Signalling Gateway • no media capabilities • optional? not req’d for interoperability (RTP based) • H.323 personality • equivalent to GK in GK-routed but no RAS - so EP • SIP personality • SGW is logically equivalent to proxy/redirect server • not typical UA (no media) • UA since “safer” as peer to H.323 EP Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  5. Logical Model registrar H.323 EP H.323 EP SIP UA UA H.323 GK proxy/redirect Signalling Gateway Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  6. Configurations reg reg EP EP SGW SGW UA UA GK GK proxy proxy reg reg EP EP SGW SGW UA UA GK GK proxy proxy Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  7. Two Phases • Phase 1 - Basic Call • needed now • well understood • Phase 2 - Services • not needed now • less well understood • some desired services under development Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  8. Phase 1 - Basic Call • address resolution (registration & location) • incoming and outgoing call • call signalling • H.323 GK-routed and direct signalled • SIP proxy and redirection • Fast Connect • H.245 tunneling • TCS, MSD, OLC, CLC, EndSession, RTD • no H.323v1 logical channel control • robustness and stability Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  9. Phase 1 - Basic Call (cont’d) • calling/connected line/party services • mid-call signalling • out-of-band: INFO method and User Input Indication • in-band: using RTP (kind of out of scope) • pre-granted ARQ Dave Walker - SS8 Networks Joon Maeng - Onscreen24

  10. Phase 2 - Services Interworking • overlap sending • conferencing • session change (re-INVITE, ModeRequest) • call transfer • call forward • call hold • security: authentication, authorization, privacy • QoS signalling Dave Walker - SS8 Networks Joon Maeng - Onscreen24

More Related