Succession Link Protocol Messages; Ivr Messages; Call Data Networking Messages Between Tapi Servers - Nortel TAPI Reference Manual

• Microsoft TAPI messages
If your TAPI services include IVR and networking of call data, you must allow
additional bandwidth for:
•

IVR messages

•

Call data networking messages between TAPI servers

Succession Link protocol messages

The network traffic on the LAN relating to Succession Link protocol messages is
directly proportional to the number of lines monitored and the number of calls
appearing in the switch on these lines. During the life of a basic call, normal
operations performed include MAKECALL, ANSWER, HOLD, UNHOLD and
DROP.
To calculate the load on a LAN assume that every inbound call appearing in the
Call Center does ANSWER, HOLD, UNHOLD and DROP operations. The total
number of bytes required for the messages related to these operations is 763 bytes
per call. Therefore, to calculate the LAN requirements for Succession Link
protocol messages, for 10,000 basic calls per hour, use the following formula:
(763 x 10,000) / 3600 (seconds per hour) = 2120 bytes per second
IVR messages
The LAN requirements for IVR messages are very dependent on the customer
implementation. Nortel Networks is currently conducting tests and sample data
will be provided before Symposium TAPI SP, release 3.0 is issued for general
availability (GA).
Call data networking messages between TAPI servers
The network traffic overhead due to call data networking messages is directly
related to the following:
• the number of calls overflowed from one Meridian switch to a remote
Meridian switch
Engineering Guidelines for Symposium TAPI Service Provider for Succession, release 3.0
Chapter 3 Server engineering guidelines 33