Beruflich Dokumente
Kultur Dokumente
323
Ng Tai Hung
Introduction
We have learned
IP, UDP, RTP Signaling ISUP, Integrated Services Digital Network User Part
Internet Telephony
4-2
Visual Telephone Systems and Equipment for Local Area Network which Provide A Non-Guaranteed Quality of Service Packet-based Multimedia Communications Systems Widely implemented in VoIP solutions
Version 2, 1998
Version 4
Internet Telephony
4-3
Entities
Terminals Gateways Gatekeepers MCUs Parts of H.225.0 - RAS, Q.931 H.245 RTP/RTCP Audio/video codecs
Protocols
Internet Telephony
4-4
H.323 Architecture
Internet Telephony
Internet Telephony
4-6
Terminals
Endpoint on a LAN Supports real-time, 2-way communications with another H.323 entity Must support:
Voice - audio codecs Signaling and setup - Q.931, H.245, RAS Video Data
Optional support:
Internet Telephony
4-7
Internet Telephony
4-8
Gateways
Interface between the LAN and the switched circuit network Mandatory Functions
Transmission Format Translation Communication Procedure Translation Call Setup and Clearing On Both Sides Media Format Translation
Optional Function
Internet Telephony
4-9
Gatekeepers
Manage a zone (a collection of H.323 devices) Usually one gatekeeper per zone
Mandatory functions:
Address translation (routing) Admission control Minimal bandwidth control - request processing Zone management Call control signaling - direct handling of Q.931 signaling between endpoints Call authorization, bandwidth management, and call management using some policy Gatekeeper management information (MIB) Directory services
Internet Telephony 4-12
Optional functions:
MCUs
Endpoint that supports conferences between 3 or more endpoints Can be stand-alone device or integrated into a gateway, gatekeeper or terminal
MC - handles control and signaling for conference support MP - receives streams from endpoints, processes them, and returns them to the endpoints in the conference
Internet Telephony 4-13
MC and MP
Terminal 1
MC
Terminal 2
Gatekeeper 1
MC
Gatekeeper 2
MC MP
Gatekeeper 3
LAN
MC
MC
MP
MC
MP MCU 2
MC
Gateway 1
Gateway 2
Gateway 3
MCU 1
T1521250-96
Centralized Conference
Terminal
Terminal
Terminal
De-centralized Conference
MCU
(MC)
Terminal
Terminal
Internet Telephony 4-16
Terminal
video stream (multicast)
MCU
video stream (multicast)
(MC+MP)
audio stream (unicast) audio stream (unicast) control message control message
Terminal
Terminal
Terminal
MCU (MC+MP)
Terminal
Terminal
multicast audio and video unicast audio and video
Terminal
Audio codecs (G.711, G.723.1, G.728, etc.) and video codecs (H.261, H.263) Media streams transported on RTP/RTCP
RTP carries actual media RTCP carries status and control information
RAS - registration, admission, status (over UDP) Q.931 - call setup and termination H.245 - capabilities exchange
Internet Telephony 4-19
The set-up and tear-down of connections Call signaling or Q.931 signaling Registration, Admissions, and Status Between endpoints and gatekeepers
RAS signaling
Used between two or more endpoints Manage the media streams of a session
Capability exchange
H.323 Addressing
E.g., ras://GK1@somedomain A port number appended RAS, a default port number = 1719
An id for a particular logical channel at a given entity GK UDP Discovery Port = 1718 GK UDP Reg and Status Port = 1719 Call-signaling TCP Port =1720
Internet Telephony 4-23
Codecs
H.261 QCIF
RAS Signaling
Since a GK is optional GK Discovery Registration Unregistration Admission Bandwidth Change Endpoint Location: GK (address translation) Disengage Status Resource Availability: GW GK Non-standard
Defined in H.225.0
Gatekeeper Discovery
Several GKs, backup GK Known addresses, multicast 224.0.1.41:1718 GK id: if empty, soliciting GKs Optionally, indicating one or more GKs to try
GRQ GK-request
GCF GK-Confirm
GRJ GK-Reject
GK Discovery
An address for RAS messages An address for call-signaling messages An alias One or more redundant addresses and aliases Optional TTL, keepAlive parameters
UnregistrationRequest (URQ)
Endpoint Location
To a GK or the GK discovery multicast address A GK can also send an LRQ A call-signaling address An RAS signaling address The endpoint is not registered
LocationConfirm (LCF)
LocationReject (LRJ)
Admission
The type of the call (e.g., two-party or multi-party) The endpoints own id A call identifier (a unique string) A call-reference value (an integer) Information of the other party
AdmissionConfirm (ACF)
callModel
AdmissionReject (ARJ)
With a reason
Pregranted Admission
to minimize call setup delay A GK provide an endpoint with admission in advance the RCF includes the parameter preGrantedARQ
Bandwidth Change
BandwidthRequest (BRQ)
BCF BRJ The GK can also request an endpoint to change the bandwidth
Status
Call id, call reference value, call type, the bandwidth RTP session information (CNAME, RTP/RTCP address, etc.)
willRespondToIRR parameter
IACK INACK
Disengage
DCF DRJ
Resource Availability
ResourceAvailableIndicate (RAI)
An gateway sends to a GK The available call capacity and bandwidth for each protocol almostOutofResource parameter
RseourceAvailableConfirm (RAC)
Service Control
Request in Progress
A given request takes longer the the timeout period The expected delay and the reason After timeout, the RAS message can be retransmitted
Call Signaling
For the establishment and tear-down of calls Q.931 modified by rec. H.225.0
Reuse some messages with few modifications Specify a number of rules regarding the usage of information elements defined in Q.931
E.g., no Transit Network Selection, Certain Q.931 mandatory information forbidden or optional
Convey all of the extra information needed in H.323 E.g., H.245 addresses to be used for logical channel
Setup
The first call-signaling message Q.931 Protocol Discriminator A call reference Bearer Capability
RTP information, such as payload type A gateway needs to perform the mapping
Mandatory: Call id, call type, conference id, the caller information Optional: source alias, destination alias, H.245 address, destination call-signaling address
Internet Telephony 4-43
Call Proceeding
Protocol discriminator, call reference, and message type, user-to-user User-to-user: similar to the setup message
Alerting
The called user is being alerted The same parameters as Call Proceeding
Progress
sent by a called gateway the Cause information in-band tones the User-to-User info. same as Call-Proceeding
Connect
The called party has accepted the call Must be sent if the call is to be completed
User-to-User information
Release Complete
Facility (Q.932)
A call should be redirected Also be used for supplementary services User-to-User contains reason parameter
E.g., routeCallToGatekeeper
Internet Telephony 4-46
Call signaling: call establishment and tear-down H.245: the negotiation and establishment of media streams When to begin the exchange of H.245 messages?
Call Scenarios
Reliable transport
EP <-> GK <-> GK <-> EP ARJ with a cause code of routeCallToGatekeeper A Facility with a reason indicating the call be rerouted
Agree on the media formats and bandwidth Multiplexing multiple media streams No actual media A generic protocol for the control of media streams How it works in an H.323?
Requests
Require the recipient to perform some action and response In reply to Requests Require the recipient to perform some action, but no response is necessary Of an informational nature only
Response
Commands
Indications
A Logical channel
A unidirectional media path An IP address and port number Has a number Two logical channels exist Potentially in different formats Or a bidirectional channel consists of two logical channels Logical channel number and media information (RTP payload type) An RTP port Permanently open
Internet Telephony 4-56
A two-party conversation
H.245 Procedures
Capabilities Exchange
Share information regarding receive and transmit capabilities Indicate a preference TerminalCabilitySet message
A request message A sequence number plus the types of audio and video formats Empty with a sequence number With a reason for rejection
TerminalCapabilitySetAck
TerminalCapabilitySetReject
TerminalCapabilitySetRelease
If no response within a timeout period Request terminal Capability information Request to indicate all of its capabilities Or request confirmation about specific capabilities A command message that is replied
SendTerminalCapabilitySet
Master-Slave Determination
Of particular importance for the setup of a multi-party conference A terminal type value
A terminal without an MC: 50 A gateway without an MC: 60 An MCU for audio, vedio: 190 An MCU managing a conference: 240 (the highest)
CloseLogicalChannel, CloseLogicalChannelAck Only the initiator can issue Or the receiving end can humbly request A bidirectional channel can be closed by either end Once all logical channels are closed
A Slow Start
Fast-connect Procedure
The Setup
A faststart element
OpenLogicalChannel requests
is encapsulated with Q.931 messages Set the element h245Tunneling true in the first Q.931 message The h245Control element contains the encapsulated data Conflict with the faststart element Use Facility
when no Q.931 message can be used to start a separate H.245 control channel
Conference Calls
Specify all the sessions in the conference The transmit requirements of each endpoint, not the receive requirements
An Ad-Hoc Conference
H.235 - security and authentication, i.e. passwords for registration with gatekeeper H.450.x - supplementary services such as call transfer and forwarding Fast call setup:
Bypasses some setup messages Triggered by Q.931 Fast Start message that contains basic capabilities
Mechanism to specify alternative gatekeepers to endpoints Gatekeeper can request forwarding of Q.931 information on direct routed calls; only RADCOM can play back H.323 streams off a network: a true differentiation Smoother integration of T.120 (optional standard for data)
Transport Data Multipoint Delivery Internetworking PSTN, ISDN LAN (TCP/IP, IPX)
Inter-Gatekeeper Communication: Current H.323 standards do not provide an inter-zone model that scales well for large networks Inter-gatekeeper protocols being discussed to enable gatekeepers to efficiently locate one another to route calls to non-local address Hierarchical arrangements with clearing house gatekeepers have been proposed This is critical for widespread interoperability between VoIP service providers
H.323 Version 3
Modest improvements to H.323 version 2 Maintaining and Reusing Connections Conference out of Consultation Caller ID Language Preference Usage of Annex E/H.323 Remote Device Control Generic Capabilities Annex G/H.225.0 - Communication between Administrative Domains
Internet Telephony 4-74
Annex E/H.323 - Protocol for Multiplexed Call Signaling Transport Annex F/H.323 - Simple Endpoint Type H.341 - H.323 Series MIB Supplementary Services
H.323 Version 4
Many new enhancements Gateway Decomposition Multiplexed Stream Transmission Supplementary Services Annex K/H.323 Annex L/H.323 H.450.8 - Name Identification Service H.450.9 - Call Completion H.450.10 - Call Offer H.450.11 - Call Intrusion
Internet Telephony 4-76
Additive Registrations Alternate Gatekeepers Usage Information Reporting Endpoint Capacity Caller Identification Service Tones and Announcements Mapping Aliases Indicating Desired Protocols Bandwidth Management Reporting Call Status
Internet Telephony 4-77
Enhancements to Annex D (Real-Time Fax) Call Linkage Tunneling QoS H.245 in Parallel with Fast Connect Generic Extensibility Framework H.323 URL Call Credit-Related Capabilities DTMF Relay via RTP
Internet Telephony 4-78