Showing posts with label Voice. Show all posts
Showing posts with label Voice. Show all posts

Active Voice Quality Monitoring



A large part of determining whether a voice mobility network is successful is in monitoring the voice quality for devices on the network. When the network has the capability tomeasure this for the administrator on an ongoing basis, the administrator is able to devote attention to other, more pressing matters.
Active voice quality monitoring comes in a few flavors. SIP-based schemes are capable of determining when there is a voice call. This is often used in conjunction with SIP-based admission control. With SIP calls, RTP is generally used as the bearer protocol to carry the actual voice, SIP-based call monitoring schemes can measure the loss and delay rates for the RTP traffic that makes up the call, and report back on whether there are phones with suffering quality. In these monitoring tools, call quality is measured using the standard MOS or R-value metrics.
SIP-based schemes can be found in a number of different manifestations. Wireline protocol analyzers are capable of listening in on a mirror port, entirely independent of the wireless network, and can report on upstream loss. Downstream loss, however, cannot be detected by these wireline mechanisms. Wireless networks themselves may offer built-in voice monitoring tools. These leverage the SIP-tracking functions already used for firewalling and admission control, and report on the quality both measured by uplink and downlink loss. Purely wireless monitoring tools that monitor voice quality can also be employed. Either located as software on a laptop, or integrated into overlay wireless monitoring systems, these detect the voice quality using over-the-air packet analysis. They infer the uplink and downlink loss rates of the clients, and use this to build out the expected voice quality. Depending on the particular vendor, these tools can be thrown off when presented with WPA- and WPA2-encrypted voice traffic, although that can sometimes be worked around.
Voice call quality may also be monitored by measurements reported by the client or other endpoint. RTCP, the RTP Control Protocol, may be transmitted by the endpoints. RTCP is able to encode statistics about the receiver, and these statistics can be used to infer the expected quality of the call. RTCP may or may not be available in a network, based on the SIP implementation used at the endpoints. Where available, RTCP encodes the percentage of packets lost, the cumulative number of packets lost, and interarrivai packet jitter, all of which are useful for inferring call quality. At a lower layer, 802.11k, where it is supported, provides for the notion of traffic stream metrics. These metrics also provide for loss and delay, and may also be used to determine call quality. However, 802.11k requires upgrades to the client and access point firmware, and so is not as prevalent as RTCP, and nowhere near as simple to set up as overlay or traffic-based quality measurements.

[*]Of course, there had to be a catch. Some devices can carry two calls simultaneously, if they renegotiate their one admitted traffic stream to take the capacity of both. Because WMM Admission Control views flows as being only between clients and access points, the ultimate other endpoint of the call does not matter. However, this is not something you would expect to see in practice.

Voice-Aware Radio Resource Management



The concept of voice-aware radio resource management is to build upon the measurements used for determining network capacity and topology, and integrate them into the decision-making process for dynamic microcell architectures.
Basic radio resource management is more concerned with establishing minimum levels of coverage while avoiding interference from neighboring access points and surrounding devices. This is more suitable for data networks. Voice-aware RRM shifts the focus towards providing a more consistent coverage that voice needs, often adjusting the nature of the RRM process to avoid destroying active voice calls. Voice-aware RRM is a crucial leg of voice mobility deployments based on microcell technology. (Layered or virtualized deployments do not use the same type of voice-aware RRM, as they have different means of ensuring high voice quality and available resources.)
The first aspect of voice-aware radio resource management is ironically to disable radio resource management. Radio resource management systems work by the access points performing scanning functions, rather similar to those performed by clients when trying to hand off. The access point halts service on a channel, and then exits the channel for a short amount of time to scan the other channels to determine the power levels, identities, and capacities of neighboring access points. These neighboring access points may be part of the same network, or may belong to other interests and other networks. Unlike with client scanning, in which the client can go into power save to inform the access point to buffer frames, however, access point scanning has no good way for clients to be told to buffer frames. Moreover, whereas client scanning can go off channel between the packets of the voice call, only to return when the next packet is ready, an access point with multiple voice calls will likely not have any available time to scan in a meaningful way. In these cases, scanning needs to be disabled. In RRM schemes without voice-aware services, administrators often have to disable RRM by hand, thus nullifying the RRM benefits for the entire network. Voice-aware RRM, however, has the capability to turn off scanning on a temporary basis for each access point, when the access point is carrying voice traffic. There are unfortunately two downsides to this. The first is that RRM is necessary for voice networks to ensure that coverage holes are filled and that the network adapts to varying density. Disabling the scanning portion of RRM disables RRM, effectively, and so voice-aware RRM scanning works best when each given access point does not carry voice traffic for uninterrupted periods of time. Second, RRM scanning is usually the same process by which the access points scan for wireless security problems, such as rogue access points and various i ntrusions. Disabling scanning in the presence of voice leaves access points with voice more vulnerable, which is unacceptable for voice mobility deployments. Here, the solution is to deploy dedicated air monitors, either as additional access points from the same network vendor, but set to monitor rather than serve, or from a dedicated WLAN security monitoring vendor, as an independent overlay solution.
The second aspect of voice-aware radio resource management is in using coverage hole detection and repair parameters that are more conservative. Although doing so increases the likelihood of co-channel interference, which can have a strong downside to voice mobility networks as the network scale and density grows, it is necessary to ensure that the radio resource management algorithms for microcells do not leave coverage holes stand by idle. Coverage holes disproportionately affect the quality of voice traffic over data traffic. Increasing the coverage hole parameters ensures that these coverage holes are reduced. Radio resource management techniques often detect the presence of a coverage hole by inferring them from the behavior of a client. RRM assumes that the client is choosing to hand off from an access point when the loss becomes too high. When this assumption is correct, the access point will infer the presence of a coverage hole by noticing when the loss rate for a client increases greatly for extended periods of time. This is used as a trigger that the client must be out of range, and informs the access point to increase its power levels. It is better for voice mobility networks for the coverage levels to be increased prior to the voice mobility deployment, and then for the coverage hole detection algorithm to be made less willing to reduce coverage levels. Unfortunately, the coverage hole detection algorithms in RRM schemes are proprietary, and there are no settings that are consistent from vendor to vendor. Consult your microcell wireless network manufacturer for details on how to make the coverage hole detection algorithm be more conservative.
The final aspect of voice-aware RRM is for when proprietary extensions are used by the voice client and are supported by the network. These extensions can provide some benefit to microcell deployments, as they allow the network to alter some of the tuning parameters that clients use to hand off. Unfortunately, the aspects of voice-aware radio resource management trade off between coverage and quality of service, and so operating these networks can become a challenge, especially as the density or proportion of network use of voice increases. Monitoring tools for voice quality are especially important in these networks

Power Control | Voice Mobility with Wi-Fi


Power control, also known as transmit power control (TPC), is the ability of the client or the access point to adjust its transmit power levels for the conditions. Power control comes in two flavors with two different purposes, both of which can help and hurt a voice mobility network. The first, most common flavor of power control is vested in the client. This TPC exists to allow the client to increase its battery life. When the client is within close range to the access point, transmitting at the highest power level and data rate may not be necessary to achieve a similar level of voice performance. Especially as the data rates approach 54Mbps for 802.11a and 802.11g, or higher for 802.1 In, the preamble and per-packet backoff overhead becomes in line with the over-the-air resource usage of the voice data payload itself. For example, the payload of a voice packet at the higher data rates reduces to around 20 microseconds, on par with the preamble length for those data rates. In these scenarios, it makes sense for the client to back off on its power levels and turn off portions of the radio concerned with the more processing-intensive data rates, to extend battery life while in a call. To do this, the client will just directly reduce its transmit power levels, as a part of its power saving strategy. This mechanism can be used for good effect within the network, as long as the client is able to react to an increase in upstream data loss rates quickly enough to restore power levels should the client have turned power levels down too low for the range, or if increasing noise begins to permeate the channel.
The other TPC is vested within the network. Microcell networks, specifically, use access point TPC to reduce the amount of co-channel interference without having to relocate or disable access points. By reducing power levels, cell sizes in every direction are reduced, keeping in line with the goals of microcell. Reducing co-channel interference is necessary within microcell networks, to allow a better isolation of cells from fluctuations in their neighboring cells, especially those related to the density of mobile clients.
Network TPC has some side effects, however, that must be taken into account for voice mobility deployments. The greatest side effect is the lack of predictability of coverage patterns for the access points. This can have a strong effect on the quality of voice, because voice is more sensitive than data to weak coverage, and areas where voice performs poorly can come and go with the changing power levels, of both the access point the client is associated to and of the neighbors. Unfortunately, power levels in microcell networks usually fluctuate on the order of a few seconds or a few minutes, especially when clients are associated, as the network tries to adapt its coverage area to avoid causing the increase in packet rate and traffic caused by the clients from affecting neighboring cells. Site surveys, which are performed to determine the coverage levels of the network, are always snapshots in time and cannot take TPC into account. However, the TPC variation is necessary for proper microcell operation, and unfortunately needs to happen when phones are associated and in calls. Therefore, it can cause a strong network-induced variation in call quality. It is imperative, in microcell deployments, for the coverage and call quality to be continuously monitored, to ensure that the TPC algorithms are behaving properly. Follow the manufacturer's recommendations, as you may find in Voice over WLAN design guides, to ensure that problems can be detected and handled accordingly. 

Quality of Service with WMM-How Voice


Quality of Service with WMM-How Voice and Data Are Kept Separate

The first challenge is to address the unique nature of voice. Unlike data, which is usually carried over protocols such as TCP that are good at making sure they take the available bandwidth and nothing more, ensuring a continuous stream of data no matter what the network conditions, voice is picky. One packet every 20 milliseconds. No more, no less. The packets cannot be late, or the call becomes unusable as the callers are forced to wait for maddening periods before they hear the other side of their conversation come through. The packets cannot arrive unpredictably, or else the buffers on the phones overrun and the call becomes choppy and impossible to hear. And, of course, every lost packet is lost time and lost sounds or words.
On Ethernet, as we have seen, the notion of 802.1p or Diffserv can be used to give prioritization for voice traffic over data. When the routers or switches are congested, the voice packets get to move through priority queues, ahead of the data traffic, thus ensuring that their resources do not get starved, while still allowing the TCP-based data traffic to continue, albeit at a possibly lesser rate.
A similar principle applies to Wi-Fi. The Wi-Fi Multimedia (WMM) specification lays out a method for Wi-Fi networks to also prioritize traffic according to four common classes of service, each known as an access category (AC):
  • 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
The underscore between the AC and the two-letter abbreviation is a part of the correct designation, unfortunately. You may note that the term "best effort" applies to only one of the four categories. Please keep in mind that all four access categories of Wi-Fi are really best effort, but that the higher-priority categories get a better effort than the lower ones. We'll discuss the consequences of this shortly.
The access category for each packet is specified using either 802.1p tagging, when available and supported by the access point, or by the use of Diffserv Code Points (DSCP), which are carried in the IP header of each packet. DSCP is the more common protocol, because the per-packet tags do not require any complexity on the wired network, and are able to survive multiple router hops with ease. In other words, DSCP tags survive crossing through every network equipment that is not aware of DSCP tags, whereas 802.1p requires 802.1p-aware links throughout the network, all carried over 802.1Q VLAN links.
There are eight DSCP tags, which map to the four access categories. The application that generates the traffic is responsible for filling in the DSCP tag. The standard mapping is given in Table 1.
Table 1: DSCP tags and AC mappings 
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
There are a few things to note here. First is that the eight "priorities"—again, the correct term, unfortunately—map to only four truly different classes. There is no difference in quality of service between Priority 7 and Priority 6 traffic. This was done to simplify the design of Wi-Fi, in which it was felt that four classes are enough. The next thing to note is that the many packet capture analyzers will still show the one-byte DSCP field in the IP header as the older TOS interpretation. Therefore, the values in the TOS column will be meaningless in the old TOS interpretation, but you can look for those specific values and map them back to the necessary ACs. Even the DSCP field itself has a lot of possibilities; nonetheless, you should count on only the previous eight values as having any meaning for Wi-Fi, unless the documentation in your equipment explicitly states otherwise. Finally, note that the default value of 0 maps to best effort data, as does the Priority 3 (DSCP 0×18) value. This strange inversion, where background traffic, with an actual lower over-the-air priority, has a higher Priority code value than the default best effort traffic, can cause some confusion when used; thankfully, most applications do not use Priority 3 and its use is not recommended here as well.
A word of warning about DSCP and WMM. The DSCP codes listed in Table 1 are neither Expedited Forwarding or Assured Forwarding codes, but rather use the backward-compatibility requirement in DSCP for TOS precedence. TOS precedence uses the top three bits of the DSCP to represent the priorities in Table 6.1, and assign other meanings to the lower bits. If a device is using the one-byte DSCP field as a TOS field, WMM devices may or may not ignore the lower bits, and so can sometimes give no quality-of-service for tagged packets. Further complicating the situation are endpoints that generate Expedited Forwarding DSCP tags (with code value of 46). Expedited Forwarding is the tag that devices use when they want to provide higher quality of service in general, and thus will usually mark all quality-of-service packets as EF, and all best effort packets with DSCP of 0. The EF code of 46 maps, however, to the Priority value of 5—a video, not voice, category. Thus, WMM devices may map all packets tagged with Expedited Forwarding as video. A wireless protocol analyzer shows exactly what the mapping is for by looking at the value of the TID/Access Category field in the WMM header. 
This mapping can be configured on some devices. However, changing these values from the defaults can cause problems with the more advanced pieces of WMM, such as WMM Power Save and WMM Admission Control, so it is not recommended to make those changes. (The specific problem that would happen is that the mobile device is required to know what priority the other side of the call will be sending to it, and if the network changes it in between, then the protocols will get confused and not put the downstream traffic into the right buckets.)
Once the Wi-Fi device—the access point or the client—has the packet and knows its tag, it will assign the packet into one of four priority queues, based on the access categories. However, these queues are not like their wired Ethernet brethren. That is because it is not enough that voice be prioritized over data within the device; voice must also be prioritized over the air.
To achieve this, WMM changes the backoff procedure. Instead of each device waiting a random time less than some interval fixed in the standard, each device's access category gets to contend for the air individually. Furthermore, to get the over-the-air prioritization, higher quality-of-service access categories, such as voice, get more aggressive access parameters.
Each access category get four parameters that each determine how much priority the traffic in that category gets over the air, compared to the other categories. The first parameter is a unique per-packet minimum wait time called the Arbitration Interframe Spacing (AIFS). This parameter is the minimum amount of time that a packet in this category must wait before it can even start to back off. The longer the AIFS, the more a packet must wait, and the more it is likely that a higher-priority packet will have finished its backoff cycle and started transmitting. The key about the AIFS is that it is counted after every time the medium is busy. That means that a packet with a very high AIFS could wait a very long time, because the amount of time spent waiting for an AIFS does not count if the medium becomes busy in the meantime. The AIFS is measured in units of the number of slots, and thus is also called the AIFSn (AIFS number).
The second value is the minimum backoff CW, called the CWmin. This sets the minimum number of slots that the backoff counter for this particular AC must start with. As with pre-WMM Wi-Fi, the CW is not the exact number of slots that the client must wait, but the maximum number of slots that the packet must wait: the packet waits a random number of slots less than this value. The difference is that there is a different CW min for each access category. The CWmin is still measured in slots, but communicated to the client from the access point as the exponent of the power of two that it must equal. This exponent is called the ECWmin. Thus, if the ECWmin for video is 3, then the AC must pick a random number between 0 and 23 − 1 = 7 slots. The CWmin is just as powerful as the AIFS in distinguishing traffic, by making access more aggressive by capping the number of slots the AC must wait to send its traffic.
The third parameter is similar to the minimum backoff CW, and is called the CWmax, or the maximum backoff CW. If you recall, the CW is required to double every time thesender fails to get an acknowledgement for a frame. However, that doubling is capped by the CWmax. This parameter is far mess powerful for controlling how much priority one AC gets over the other. As with the CWmin, there is a different CWmax for each AC.
The last parameter is how many microseconds the AC can burst out packets, before it has to yield the channel. This is known as the Transmit Opportunity Limit (TXOP Limit), and is measured in units of 32 microseconds (although user interfaces may show the microsecond equivalent). This notion of TXOPs is new with WMM, and is designed to allow for this bursting. For voice, bursting is usually not necessary or useful, because voice packets come on regular, well-spaced intervals, and rarely come back-to-back in properly functioning networks.
The access point has the ability to set these four AC parameters for every device in the network, by broadcasting the parameters to all of the clients. Every client, thus, has to share the same parameters. The access point may also have a different set for itself. Some access points set these values by themselves to optimize network access; others expose them to the user, who can manually override the defaults. The method that WMM uses to set these values to the clients is through the WMM Parameter Set information element, a structure that is present in every beacon, and can be seen clearly with a wireless packet capture system. Table 2 has the defaults for the WMM parameters.
Table 2: Common default values for the WMM parameters for 802.11 
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


Placing a call may seem very simple to us modern users of voice mobility. Remove the phone from your pocket, purse, automobile cup holder, or wherever you may keep your phone, find the name of the person you wish to call, and press the Send or Yes button to dial the caller. However, underneath that simple experience lies a vast wealth of technology, with electronic gears turning to produce a sound that not only sounds like a human, but is actually recognizable as the person on the other end of the phone, even if you are driving at 65 miles an hour down the interstate.
The voice call is made of a number of moving parts. Figure 1 illustrates the basic example.

Figure 1: The Anatomy of a Voice Call
Each handset contains all of the technology necessary to place a phone call. The phone must have a microphone to capture the voice call and a speaker to play out the audio from the other party. But beyond that, the phone must have a way of converting the analog voice information into encoded digital signals, using audio codecs with possible compression to ensure that high-fidelity voice quality can be carried over lower-bandwidth links. The phone must also have one or more wireless radios, complete with technology stacks and engines that allow the phone to connect to each of the networks, or even to hand off between the networks. These stacks must fully understand and adequately implement the necessary protocols to provide high voice quality over the network, something easy for voice-oriented technologies but much harder for data-oriented packet-switched networks. Finally, the phones must also support a rich telephony application. This application needs to look like, act like, and have the features of a common telephone, and yet, for voice mobility, must now often store the addresses and phone numbers of crucial contact information, provide access into the enterprise directories, allow for dialing as if in the office, and be manageable by network administrators. Many of these applications are not necessarily native to the phone itself, but created by third-party vendors to tie multiple telephone systems together to appear as one. The telephony applications must support all of the necessary protocols to create a phone call, set up the audio channels, and deal with advanced features such as voicemail and three-way calling.
The call itself is composed of two separate flows of information. The more obvious flow is what is known as the bearer channel. The bearer channel, a term borrowed fromIntegrated Services Digital Network (ISDN) technology, carries the voice of the callers. Looking back to analog telephones, there is only one channel, an analog audio channel that provides both the callers' voices and the necessary tones to tell the caller what to do. Dial tones, busy signals, and other beeps and clicks are used to communicate the number being dialed and the state of the call. In voice mobility networks, however, the audio is kept separate from the communication that is used to set up the call and keep it running. This is known as out-of-band signaling. Voice can be encoded in a variety of ways, and the bearer channel is more likely to be carried in a number of digital formats. The communication about what the phone call is for, how it is being set up, and what state it is in is encoded in the signaling channel. The signaling protocol is used to dial out to set up the call, provide feedback as to whether the other phone is ringing or busy, and to finally set up the bearer channel when the call goes through.
The signaling information needs to go somewhere, and that somewhere is to a telephone switch. For private telephone networks, where the handsets are maintained by the enterprise or organization who owns the network, these switches are also owned by the enterprise and are called private branch exchanges (PBX). The term exchange and switchare interchangeable, and these devices are the electronic equivalent of the old manual switchboard, creating connections between two calls. The PBX (or PBXs) for analog systems are proper switches, with internal analog phone lines that run from the handset directly into the PBX. But for Internet Protocol (IP)-based telephone networks, the PBX is more of the central call manager, providing for the list of extensions—users, basically, as well as the telephone numbers each user has—and the dialing plan—the notion of how to route calls based on the phone numbers dialed. PBXs also implement all of the advanced features of voice mobility calling, including voicemail, call forwarding, and multiple ring.
The PBXs define the internal voice network, but calls need to be able to be routed back onto the real, public telephone network, to allow calls in and out from the outside world. IP PBXs rely on a module or a separate device, known as a media gateway, which has the responsibility of converting the signaling and bearer traffic into a format and onto a wire that is provided by the telephone company. Media gateways thus bridge the inside world to the outside.
Let's get a better look at each component.

1 The People and Their Devices: Phones

Phones come in a number of shapes and sizes. Some have the latest features for consumers, such as music playing, video recording and camera functions, global positioning, and touch screens with tactile feedback. Some are designed for enterprise users, and have large screens, with strong email access and integration, spreadsheet and document editing capabilities, and large storage for use as a computer away from the laptop. Others are simple and rugged, meant for use in physically demanding environments where the phones need to withstand a beating. Some have nearly no buttons at all, and are even designed for nearly hands-free operation.
All in all, each phone may seem wildly different from the next. But, underneath, they are made of the same stuff: a microphone to pick up voice; a speaker to play it back; maybe another speaker for speakerphone operation or to play ringtones, so as not to deafen the user who happens to have accidentally hung up on a conversation and is being called back; some way to dial; some way to see or hear who is calling; a battery for mobility; and one or more radios to connect back to the network.
Within those components, the description becomes even more common. There is a digital sampler and a codec engine, to convert voice into digital data and back. There is a CPU somewhere, orchestrating everything, along with memory and some nonvolatile storage. The radios have antennas, all folded neatly into the small device. Voice operates the same on every one of these devices, and users will become just as irritated by poor audio quality as they will be pleased by good quality. The best voice mobility network is the one that users forget is even there, or is anything unique or special. They get out of the way, so to speak, and let the voice mobility user do her work.

2 The Separate Channels: Signaling and Bearer

In the analog telephone days, there was only one line per extension. This analog line has to do everything. It carries the voice, but it also has to ring the phone, send busy or dial tones, and handle the beeps corresponding to each button being pressed.
With digital phone calling, the signaling and bearer channels are separated. All the beeping, humming, and chirping that is meant to tell the caller what is going on with the call is removed from the audio stream and sent separately in the signaling channel. The bearer channel holds the human voice, and nothing else. The advantage of this having been done for IP-based voice mobility networks is that it allows the call setup part of the network to operate differently from the voice encoding and decoding part. IP PBXs may be configured to never carry a single voice packet, because their job is simply to figure out how to route calls—much like how Internet DNS servers are so critical in figuring out what"www.google.com" refers to without carrying a byte of Google's web traffic. Media gateways can be created that specialize in conversion of media formats, and then only need to implement the basic signaling protocols, and do not need to be concerned with advanced PBX features.

3 Dialing Plans and Digits: The Difference between Five- and Ten-Digit Dialing

For all the advancements in the digital age, with email accounts, instant-messaging handles, avatars, and what not, phones still work with the concept of dialing a series of numbers. But not all numbers are created alike. In the telephone network, someone needed to determine what all of the digits mean. This meaning is known as the dialing plan.
Think of the dialing plan as a series of simple rules that tell the phone system when you are done dialing and where the numbers are to go. In the United States, the dialing plan for our public telephone lines specifies that every phone number is seven digits long. Type an extra digit, and the phone ignores it. However, some calls are not in the same area code. This area code concept is a part of the dialing plan. To get to other blocks of phone numbers, outside of the block of numbers that you can dial the most conveniently, you need to dial a "1", followed by the area code, followed by the seven-digit number. Other calls require even more digits. An international call requires dialing "011" before the country code, and then whatever digits are necessary to place a call in that country. And the first "0" must be followed by the first "1" quickly enough to prevent the phone from thinking you are done, and connecting you to the operator. Finally, some calls, like "411", require only three digits. In the office, things can be a bit more complicated. Many people may have four-digit extensions. Only those four need to be dialed. Some companies may use longer extensions, however, with access codes in front of them. Finally, to dial out to the public network, you may need to dial a "9". But not just any "9" will do! The "9" must be followed by a pause, to let the system present a new, outside-world dial tone, where the rest of the digits can be placed.
The dialing plan defines all of this behavior. Every PBX system provides an incredible amount of depth into how these dialing plans can be created, and whether some of the digits are just part of the extension number and others are meant to shift the call over to another PBX somewhere else (like the "9" did to dial outside, but even the "1" for long distance does the same thing) to figure out the meaning.
A lot is mentioned about having four- or five-digit dialing within voice mobility networks. There is an added convenience, and it is true that users of a PBX may not remember the outside number corresponding to an extension, especially if the rest of the number is different for different extensions. (Picture a system in which the 6xxx extensions are reached from outside the office by dialing 487-6xxx, but the 7xxx extensions are reached by dialing 935-7XXX.)

4 Why PBXs: PBX Features

PBXs serve as a lot more than just the anchor or administrative server of the phone network. They also provide a long list of features that people have come to expect from enterprise phone lines—features that they probably do not have at home, even with today's rich cellphone feature sets.
PBX vendors compete with each other by making the feature set as useful and fancy as possible. There are a number of important PBX features. Some are listed here:
  • 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.
  • Call pickup: Allows a user to answer another user's phone when it is ringing by entering their extension number. It can also be used in the same sense as simultaneous ringing can, in that an incoming call to a department might ring multiple extensions, and the first to pick it up wins.
  • 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.
As you can see, PBXs are designed to have a broad series of functions. Thankfully, PBX features are generally independent of voice mobility networking, in the sense that every PBX has a good number of features, and these features will generally work on IP PBXs, no matter what IP-based protocol the user is using. On the other hand, fixed-mobile convergence (FMC) solutions and PBXs do interact

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.

Figure 1: H.323 Call Setup

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.

  1. Gateway X sends an H.225 call-signaling setup message to Gateway Y to request a connection.

  2. Gateway Y sends an H.225 message back to Gateway X, advising that it may proceed with the call.

  3. Gateway Y sends an RAS message (ARQ) on the RAS channel to the gatekeeper to request permission to accept the call.

  4. Gatekeeper confirms that the call can be accepted by sending a message (ACF) back to Gateway Y.

  5. Gateway Y sends an H.225 message to Gateway X, alerting that the connection has been established.

  6. 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.

Figure 2: Media Channel Setup

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:

  1. Gateway X exchanges its capabilities with Gateway Y by sending an H.245 TCS message.

  2. Gateway Y acknowledges Gateway X's capabilities by sending an H.245 TCS Acknowledge message.

  3. Gateway Y exchanges its capabilities with Gateway X by sending an H.245 TCS message.

  4. Gateway X acknowledges Gateway Y's capabilities by sending an H.245 TCS Acknowledge message.

  5. 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.

  6. 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

  7. 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.

  8. 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:

Figure 3: Media Channel Setup Call Flow

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:

  1. Gateway X sends the RTP encapsulated media stream to Gateway Y.

  2. Gateway Y sends the RTP encapsulated media stream back to Gateway X.

  3. Gateway X sends the RTCP messages to Gateway Y.

  4. 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:

Figure 5: Bandwidth Change Request.
  1. The initiating gateway sends a bandwidth request (BRQ) to the gatekeeper to request the desired bandwidth.

  2. The gatekeeper responds with a bandwidth confirmation (BCF) message for the requested bandwidth.

  3. A logical channel is established between the two gateways with the specified bandwidth.

  4. A BRQ is sent from the remote router to the gatekeeper to change the bandwidth of the connection.

  5. The gatekeeper responds to the gateway with a BCF to confirm the new bandwidth.

  6. 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:

Figure 6: Call Termination (H.245/H.225/Q.931/RAS)
  1. Gateway Y initiates call termination by sending an H.245 End Session Command (ESC) message to Gateway X.

  2. Gateway X releases the call endpoint and confirms with an H.245 ESC message to Gateway Y.

  3. Gateway Y completes the call release by sending an H.245 Release Complete message to Gateway X.

  4. Gateway X and Gateway Y disengage with the gatekeeper by sending a RAS DRQ message.

  5. Gatekeeper disengages and confirms by sending DCF messages to both Gateway X and Gateway Y.

H.323 Endpoint-to-Endpoint Signaling

Assuming that endpoints (clients) know each other's IP addresses, the H.323 signaling is shown in Figure 7.

Figure 8: H.323 Endpoint-to-Endpoint Signaling

Telecom Made Simple

Related Posts with Thumbnails