Active Voice Quality Monitoring
Voice-Aware Radio Resource Management
Power Control | Voice Mobility with Wi-Fi
Quality of Service with WMM-How Voice
Quality of Service with WMM-How Voice and Data Are Kept Separate
- AC_VO: highest-priority voice traffic
- AC_VI: medium-priority video traffic
- AC_BE: standard-priority data traffic, also known as "best effort"
- AC_BK: background traffic, that may be disposed of when the network is congested
DSCP
|
TOS Field Value
|
Priority
|
Traffic Type
|
AC
|
|---|---|---|---|---|
0×38 (56)
|
0×E0 (224)
|
7
|
Voice
|
AC_VO
|
0×30 (48)
|
0×C0 (192)
|
6
|
Voice
|
AC_VO
|
0×28 (40)
|
0×A0 (160)
|
5
|
Video
|
AC_VI
|
0×20 (32)
|
0×80 (128)
|
4
|
Video
|
AC_VI
|
0×18 (24)
|
0×60 (96)
|
3
|
Best Effort
|
AC_BE
|
0×10 (16)
|
0×40 (64)
|
2
|
Background
|
AC_BK
|
0×08 (8)
|
0×20 (32)
|
1
|
Background
|
AC_BK
|
0×00 (0)
|
0×00 (0)
|
0
|
Best Effort
|
AC_BE
|
AC
|
Client
|
Access Point
|
CWmin
|
TXOP limit
| |||
|---|---|---|---|---|---|---|---|
AIFS
|
CWmax
|
AIFS
|
CWmax
|
802.11b
|
802.11agn
| ||
Background (BK)
|
7
|
210− 1 = 1023
|
7
|
210 − 1 = 1023
|
24− 1 = 15
|
0μs
|
0μs
|
Best Effort (BE)
|
3
|
210− 1 = 102
|
3
|
26− 1 = 63
|
24− 1 = 15
|
0μs
|
0μs
|
Video (VI)
|
2
|
24− 1 = 15
|
1
|
24− 1 = 15
|
23− 1 = 7
|
6016μs
|
3008μs
|
Voice (VO)
|
2
|
23− 1 = 7
|
1
|
23− 1 = 7
|
22− 1 = 3
|
3264μs
|
1504μs
|
The Anatomy of a Voice Call | Voice Mobility Technologies
1 The People and Their Devices: Phones
2 The Separate Channels: Signaling and Bearer
3 Dialing Plans and Digits: The Difference between Five- and Ten-Digit Dialing
4 Why PBXs: PBX Features
- Dial-by-name directory: A computer voice system that allows callers to find out an extension and dial it by interactively pressing a few buttons, usually the first portion of the name. This directory is driven by the autoattendant feature.
- Autoattendant: The automated telephone operator, represented by a series of recorded prompts. Autoattendants allow users to access and even manage their account on the PBX simply by calling in. Autoattendants are also the anchor for the interactive voice response systems that outside callers might get into a call center line, whose PBX is advanced enough to guide callers through the menu of options.
- Call forwarding: The user can set the line up to forward to another extension, or an outside line, rather than ring the phone. This is useful for when the user is out of the office. Call forwarding is also done automatically when the user does not answer the phone after a certain number of rings.
- Find-me/Follow-me/Hunting: These three names for broadly the same feature allow the user to have a number of different alternative phone numbers. When the user does not answer his or her primary line after a certain number of rings, the system hunts down the list, forwarding the call to the next number until it gives up.
- Simultaneous ring: Instead of hunting through a series of numbers, the PBX can call out to each of them at once. The first one to answer gets the incoming call. This is useful when the user has a desk phone and a mobile phone, or multiple other phones, and might be at any of them.
- Call transferring: Allows the user to send the answered phone call to another phone.
- Call park: Allows the call that is already in place to be placed on hold and transferred to another extension, where the user can remove the call from hold. Unlike call transferring, which would ring the other phone and cause the user to have to run until voicemail picks up, call parking allows the user to take more time.
- Do-not-disturb: Rejects the call before it rings the phone, usually sending it to voicemail or back to whomever transferred the call. Similarly, a user can often use this feature manually on an incoming call by pressing a button on the phone to terminate the incoming call and bounce it back.
- Voicemail: Answers the phone and records a message.
- Hold music: PBXs provide a series of options and selections for the caller to be subjected to while on hold. For some unknown reason, even advanced PBXs often play a short, few-second-long segment of supposedly relaxing music in an endless loop. Administrators can, however, often replace the hold music with a prerecorded selection. This is most useful for queuing of calls in call centers, where the hold music might be interspersed with the autoattendant informing the caller of the expected wait time.
- Time-based policies: PBXs can change their configuration based on the time of day, routing calls to the autoattendant instead of the corporate operator, for example, after hours.
- Conference calling: PBXs can join together a limited number of lines for ad hoc conferences, such as three-way calling, for which multiple parties are needed to be on at once.
H.323 Call Setup
After discovery, registration, and call placement are complete, the H.323 call moves into the call setup stage. At this stage, the gateways are communicating directly to set up the connection. An alternative is gatekeeper-routed call signaling, where all call setup messages traverse the gatekeeper. Figure 1 helps us conceptualize this process.
The call setup is based on the ITU-Q.931 (H.225 is a subset of Q.931), which provides a means to establish, maintain, and terminate network connections across an ISDN. This process comprises six distinct phases, as shown in Figure 1.
-
Gateway X sends an H.225 call-signaling setup message to Gateway Y to request a connection.
-
Gateway Y sends an H.225 message back to Gateway X, advising that it may proceed with the call.
-
Gateway Y sends an RAS message (ARQ) on the RAS channel to the gatekeeper to request permission to accept the call.
-
Gatekeeper confirms that the call can be accepted by sending a message (ACF) back to Gateway Y.
-
Gateway Y sends an H.225 message to Gateway X, alerting that the connection has been established.
-
Gateway Y sends an H.225 message to Gateway X, confirming call connection to establish the call.
Logical Channel Setup
After call setup, all communications travel over logical channels. The H.245 manages these logical channels. Multiple logical channels of varying types (video, audio, and data) are allowed for a single call.
The H.245 Logical Channel Signaling Entity (LCSE) opens a logical channel for each media stream. Channels may be unidirectional or bi-directional. Figure 2 helps us visualize how the H.323 utilizes virtual channels.
The H.245 control channel is established between Gateway X and Gateway Y. Gateway X uses H.245 to identify its capabilities via a Terminal Capability Set (TCS) message to Gateway Y. The media channel setup flow is as follows:
-
Gateway X exchanges its capabilities with Gateway Y by sending an H.245 TCS message.
-
Gateway Y acknowledges Gateway X's capabilities by sending an H.245 TCS Acknowledge message.
-
Gateway Y exchanges its capabilities with Gateway X by sending an H.245 TCS message.
-
Gateway X acknowledges Gateway Y's capabilities by sending an H.245 TCS Acknowledge message.
-
Gateway X opens a media channel with Gateway Y by sending an H.245 Open Logical Channel (OLC) message and includes the transport address of the RTCP channel.
-
Gateway Y acknowledges the establishment of the logical channel with Gateway X by sending an H.245 OLC Acknowledge message, including:
-
RTP transport addresses (used to send the RTP media stream) allocated by Gateway Y
-
RTCP address previously received from Gateway X
-
-
Gateway Y opens a media channel with Gateway X by sending an H.245 OLC message and includes the transport address of the RTCP channel.
-
Gateway X acknowledges the establishment of the logical channel with Gateway Y by sending an H.245 OLC Acknowledge message and includes:
-
RTP transport addresses (used to send the RTP media stream) allocated by Gateway X
-
RTCP address previously received from Gateway Y
-
Figure 3 highlights this process:
Media Stream and Media Control Flows
RTP media streams are transported over UDP ports 16384 through 16384 + 4x (where x is the number of voice ports on the gateways). For example, a Cisco 3620 router with four E&M ports would use UDP ports 16384–16400 for RTP flows.
RTCP manages media streams in the H.323 call flow by supporting QoS feedback from receivers. The source may use this information to adapt encoding or buffering schemes. RTCP uses a dedicated logical channel for each RTP media stream. Figure 4 illustrates the steps in this stage of the H.323 call flow.
In the example shown in Figure 9.34, four actions are occurring:
-
Gateway X sends the RTP encapsulated media stream to Gateway Y.
-
Gateway Y sends the RTP encapsulated media stream back to Gateway X.
-
Gateway X sends the RTCP messages to Gateway Y.
-
Gateway Y sends the RTCP messages back to Gateway X.
Endpoints may seek changes in the amount of bandwidth initially requested and confirmed. The gatekeeper must be asked for bandwidth increases or decreases. Endpoints must comply with gatekeeper responses and requests. The bandwidth change flow is diagramed in Figure 5. This process consists of six stages:
-
The initiating gateway sends a bandwidth request (BRQ) to the gatekeeper to request the desired bandwidth.
-
The gatekeeper responds with a bandwidth confirmation (BCF) message for the requested bandwidth.
-
A logical channel is established between the two gateways with the specified bandwidth.
-
A BRQ is sent from the remote router to the gatekeeper to change the bandwidth of the connection.
-
The gatekeeper responds to the gateway with a BCF to confirm the new bandwidth.
-
The logical channel is re-established with the new bandwidth.
Call Termination
Call termination stops the media streams and closes the logical channels, and may be requested by any endpoint or gatekeeper. It ends the H.245 session, releases H.225/Q.931 connections, and provides disconnect confirmation to the gatekeeper via RAS. Figure 6 shows call termination flow and is described as follows:
-
Gateway Y initiates call termination by sending an H.245 End Session Command (ESC) message to Gateway X.
-
Gateway X releases the call endpoint and confirms with an H.245 ESC message to Gateway Y.
-
Gateway Y completes the call release by sending an H.245 Release Complete message to Gateway X.
-
Gateway X and Gateway Y disengage with the gatekeeper by sending a RAS DRQ message.
-
Gatekeeper disengages and confirms by sending DCF messages to both Gateway X and Gateway Y.






