100 likes | 208 Vues
This document outlines the Interdomain Profile Version 2.1 for voice and fax services across administrative domains, focusing on Gateway-to-Gateway (GW-GW) and Gatekeeper-to-Gatekeeper (GK-GK) interoperability. It specifies protocols such as H.323v2 for voice and T.38 for fax communication, ensuring mandatory support for Clearinghouse functions. Special considerations regarding bilateral agreements and access control are addressed. Key implementation strategies and identified issues related to Annex G are also discussed, providing guidance for successful deployment in interdomain scenarios.
E N D
iNOW! Interdomain Profile Version 2.1 (AG Approved) SIG Chairs: Boaz Michaely, VocalTec Comm. Ltd boaz@vocaltec.com Terry L. Anderson, Lucent Technologies tla@lucent.com
Interdomain v2.1 Overview • Scope • phone-to-phone, fax-to-fax service across administrative domains. • GW-GW, GK-GK • Specific Points of reference: • GW to GW voice: H.323v2 using fast connect. • GW to GW Fax using T.38. • GK to GK using H.225.0 Annex G. • GRC and DRC allowed • Focus on Clearinghouse support
CH Anx G - mandatory GK V2 GK/BE GK/BE V2 GK Annex G Usage OSP optional (V3 ?)
Supported Models Zone A Zone B Annex G GK GK GW GW GW GW GW GW Inter Zone
Supported Models Domain A Domain B Annex G GK/BE GK/BE GK GK GW GW GW GW GW GW Bilateral Agreement between domains
Supported Models Clearing House BES Domain A Domain B CH/BE GK/BE GK/BE GK GK GW GW GW GW GW GW Clearing House
GW Supported Models Clearing House BES Domain A Domain B CH/BE GK/BE GK/BE GK GK GW GW GW GW GW GW CH/Inter Exchange (Aggregate)
Ability of CH to control access and monitor usage (CDR) on per-call online basis. Domains may be able to have similar control on access to each other. Supported prefixes are provisioned offline. Online provisioning (supported in Annex G) is optional - usage left unspecified. Requirements
Expected Implementation Focus • Annex G: new, not all problem were envisioned. • Fax: usage of T.38. Similar reasons.
Implementer’s Guide Scope • Delimited by the scope of iNOW v2: • Gateway to gateway and gatekeeper to gatekeeper. • Follow requirements specified in profile. • Stick to the scenarios described in the profile - do not add or delete! • Criteria for inclusion : • Ambiguities - “how to proceed when receiving message…” • Inconsistencies . • Significant performance penalty and security holes.