start_h5.fm
A31003-H3590-S100-7-7620, 06/2012
HiPath 3000/5000 V9, Service documentation
6-15
Nur für den internen Gebrauch
Startup and Administration HiPath 5000
Server Networking
6.5.2.5
Quality Assurance Procedures to be Supported
●
Quality of Service (QoS) procedures in accordance with IEEE 802.1q (layer 2)
●
Type of Service (ToS) in accordance with RFC 791 (layer 3), packet prioritization
●
Differentiated Services (DiffServ - DS) procedure in accordance with RFC 2474 (layer 3)
6.5.2.6
Maximum Package Losses
A maximum packet loss of 3% is tolerated. The reduced voice quality associated with packet
loss is greater for G.723.1 and G.729 than for G.711.
6.5.2.7
Minimization of Broadcast/Multicast Traffic
In accordance with the rules of good network design, broadcast/multicast traffic should be kept
to a minimum. The use of routers/layer 3 switches to structure the network (for example VPM)
or the use of layer 2 switches can help detect multicasting traffic.
6.5.2.8
Requirements for Standalone Systems:
●
Switched or shared LAN (Ethernet IEE 802.3/802.3 u) with 10 or 100 Mbps
●
Pure Microsoft TCP/IP network (not a Novell network with IPX/SPX)
●
Fixed IP addresses (no DHCP)
●
The bandwidth required for transferring additional services (CDR and ACD/TAPI informa-
tion) must be taken into account. If the bandwidth is sufficient, a second protocol (e.g. No-
vell) may be possible.
6.5.2.9
Adaptation of QoS Classes to Oscar
Standardization according to the “HiPath QoS Strategy” involves adjusting the assignment of
QoS classes on HG 1500 and in WBM.
Previous allocation in CDB 2.4
New allocation in CDB 2.5
Voice Payload = AF43
Voice Payload = AF12
Call Signaling = AF31
Call Signaling = AF21
Data Payload = AF21
Data Payload = AF11
Network Cont. = AF12
Network Cont. = CS7
Summary of Contents for HiPath 3000 Series
Page 1252: ......
