Professional Documents
Culture Documents
created by djoksimovic on Jul 30, 2014 8:26 AM, last modified by panagent on Jul 30, 2014 8:31 AM
Overview
A good starting point when troubleshooting H.323 issues is to have a clear picture of the H.323 call flow
process. The purpose of this document is to describe message exchange mechanism in order to properly
analyze pcap files and packet-diag logs of H.323 traffic.
Details
H.323 is an umbrella recommendation from the International Telecommunications Union (ITU) and is used for
audio, video and data communication over IP/TCP networks. It uses H.225 and H.245 protocols for call
signaling and call setup and RTP/RTCP for media transport, RTP for carrying actual media and RTCP for
carrying status and control information.
A flow of H.323 call is described through the call flow diagram, which covers the following steps:
- H.225/Q.931 Call Setup
- H.245 Negotiation and Voice Path Setup
- RTP/RTCP Based Voice Communication
After master-slave election, H.245 protocol performs Voice Path setup using the following steps (the same
messages are exchanged for video path setup as well):
1. The calling party opens a RTCP socket for controlling the RTP stream
2. The calling party opens a RTP socket for voice communication over the Internet
3. It then sends channel open request to the called party. RTCP port number is included in the message.
4. The called party opens a RTCP socket for controlling the RTP stream.
5. The called party also opens a RTP socket for voice communication over the IP/TCP network.
6. It then sends channel open request to the calling party. RTCP port number is included in the message.
7. Caller acknowledges the message. The RTP and RTCP port numbers are included in the message.
8. Called party acknowledges the message. The RTP and RTCP port numbers are included in the message.
(9 ratings) (9 ratings)
0 Comments