Implementing Communication Manager on a data network
338 Avaya Application Solutions IP Telephony Deployment Guide
The bandwidth required for control network traffic depends on the number of port networks
(PNs), the number of endpoints (both trunks and stations), and the number and complexity of
the calls being controlled. The network must be engineered to support the basic connectivity
and background activity on the port network, arriving call traffic, and periodic maintenance.
There will be cases where the control path traverses several network segments, each with
different configurations and sometimes carrying several signaling channels. In these cases,
each segment must be engineered for its specific needs.
Table 81
lists the bandwidth required
on the control network.
The network bandwidth should be engineered to assure that the idle bandwidth (approximately
11kbps), plus the call volume bandwidth, plus additional bandwidth to assure a good grade of
service given the random nature of call events. Typically, 20kbps additional bandwidth is
sufficient to achieve acceptable latency on the connection.
End-to-end delay across the control network should be held below 100 ms. Above 100ms,
users may notice sluggishness in the user interface. Above 300ms, or with significant packet
loss, there will be excessive retransmission at the application layer that will bring the link down.
Delays, even momentary delays exceeding 300ms, may cause the interchange of control
networks or servers, and may generate alarms. Where a common path is used to reach IPSIs,
significant delays will cause a Port Network Warm (or COLD) restart.
Choose a routing protocol that is robust and will converge quickly when there are changes in
the network configuration. OSPF is a highly scalable, non-proprietary Interior Gateway (routing)
Protocol (IGP) that can achieve network convergence within 10 seconds. OSPF also supports
multipath routing, where parallel paths are used concurrently. When properly configured, OSPF
is an appropriate choice for a routing protocol across the control network.
Table 81: Control Network Bandwidth Requirements
Parameter
Value
Units
Notes
Idle BW
(active IPSI)
10
Kbps
This background sanity checking remains
constant, independent of load. Downlink
traffic is greater than uplink. Allow 10kbps
for good performance.
BW (standby
IPSI)
1
Kbps
This value is nearly constant. [To Be
Verified]
Incremental
traffic per call
2500
Octets
With both endpoints controlled by the
same IPSI, less if only one endpoint is
controlled by the IPSI. This value will vary
depending on the complexity of the call.
21
Packets
This typical value, associated with 2500
octets per call yields an average packet
size of 120 octets. This is useful for
calculating Overheads.
Summary of Contents for Application Solutions
Page 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Page 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Page 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Page 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Page 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Page 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Page 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...