Issue 2.0
SV9100 Networking Manual
5-3
users. If packet drops become epidemic, the quality of all transmissions
degrades. Packet loss rate must be less than five percent for minimum quality
and less than one percent for toll quality.
2.2 Voice Quality Improvements
This section describes various techniques that can be used to improve the voice
quality.
Increase available bandwidth:
This can sometimes be the most basic solution and the easiest of the solutions.
If running a System IP Phone using G.711 with a 30ms fill time over Ethernet, for
only one call, 90Kbps of bandwidth is needed. If that same user only has a 64K
line, they do not have a decent IP voice call. The user can increase the
available bandwidth to slightly exceed the 90Kbps requirements and their voice
quality dramatically increases. This solution might not be viable if no more
bandwidth is available.
Use a different CODEC:
The CODEC contains possible compression algorithms to be used on the voice.
Lets take the example above again. The user only wants one voice line over a
64Kbps data connection. They also want to maintain their current fill time of
30ms. Change to a G.729. For one line, only 34Kbps is required for a call. This
fits well within the 64Kbps of available bandwidth.
Increase the number of frames per packet:
To continue with the example above, the user has moved to a G.729 CODEC.
But now, the user wishes to add two more System IP Phones. Their current
64Kbps line can handle one call, because it is only 34Kbps. Two more System
IP Phones would increase the total to 102Kbps so obviously there is not
sufficient bandwidth.
The user can now increase the fill time to 50ms. This reduces the bandwidth per
call to 19.8Kbps (3x 19.8 = 59.4Kbps). The savings in bandwidth comes from
the fact that with a longer fill time, fewer packets are needed to send the voice.
With fewer packets, less header information needs to be attached and
transmitted.
Change Layer 2 Protocols:
Ethernet is most commonly used for IP packets. Unfortunately, Ethernet has a
fairly large overhead of 34 bytes. So every IP voice packet going over Ethernet
has a 34-byte Ethernet header attached to it. As the number of packets add up,
this header data can become significant. Frame Relay has a 7-byte header and
Point-to-Point Protocol (PPP) has a 6-byte header. With this decrease in header
length at layer 2, some significant savings in bandwidth use can be achieved.
The down side to this is that most networks may not have these services
available, where Ethernet is very widely used. This is usually outside the control
of the installer and therefore NEC strongly advises users to do more research
on other layer 2 protocols before trying to implement them in their voice
network.
Implement Quality of Service (QOS):
Now, assume a derivative of the above example. The user needs only one voice
line over their 64Kbps connection. They are using G.729 with a 30ms fill time.
This requires 34Kbps of their available bandwidth. Also assume that this line is
Summary of Contents for Univerge SV9100
Page 1: ...Networking Manual A50 035910 004 AU Issue 2 0...
Page 20: ...xviii Table of Contents Issue 2 0...
Page 26: ...xxiv List of Figures Issue 2 0...
Page 33: ...Book 1 SV9100 K CCIS...
Page 49: ...Issue 2 0 1 16 General Information US Only Figure 1 15 Circuit Identification Codes CIC...
Page 53: ...Issue 2 0 1 20 General Information US Only...
Page 61: ...Issue 2 0 2 8 Hardware Installation US Only...
Page 195: ...Issue 2 0 4 116 Features and Specifications...
Page 242: ...Book 2 SV9100 IP Networking...
Page 256: ...Issue 2 0 2 12 IP Networking...
Page 312: ...Issue 2 0 4 48 Programming...
Page 376: ...Issue 2 0 6 30 SIP Trunking...
Page 391: ...Issue 2 0 7 14 H 323 Trunking...
Page 467: ...Issue 2 0 8 76 IP Multiline Station SIP...
Page 551: ...Issue 2 0 10 64 SV9100 NetLink Conditions None Feature Cross Reference None...
Page 567: ...Issue 2 0 10 80 SV9100 NetLink Conditions None Feature Cross Reference None...
Page 579: ...Issue 2 0 11 6 NAPT...
Page 580: ...Issue 2 0 SV9100 Networking Manual 11 7...
Page 581: ...Issue 2 0 11 8 NAPT...
Page 582: ...Issue 2 0 SV9100 Networking Manual 11 9...
Page 583: ...Issue 2 0 11 10 NAPT...
Page 584: ...Issue 2 0 SV9100 Networking Manual 11 11...
Page 595: ...Issue 2 0 12 4 All DSP Busy Indication...
Page 671: ...Issue 2 0 13 76 AspireNet Conditions None Feature Cross Reference None...
Page 685: ...Issue 2 0 13 90 AspireNet Department Calling Flexible System Numbering Intercom...
Page 707: ...Issue 2 0 13 112 AspireNet Default Trunk Port Number Name 1 Line 001 2 Line 002 400 Line 400...
Page 713: ...Issue 2 0 13 118 AspireNet Department Calling...
Page 765: ...Issue 2 0 13 170 AspireNet...