Nortel TAPI Reference Manual

Also see for Symposium TAPI Service Provider for Succession 3.0: User guide

Nortel TAPI Reference Manual Manual pdf 33 page image

Chapter 3 Server engineering guidelines 33Engineering Guidelines for Symposium TAPI Service Provider for Succession, release 3.0• Microsoft TAPI messagesIf your TAPI services include IVR and networking of call data, you must allowadditional bandwidth for:• IVR messages• Call data networking messages between TAPI serversSuccession Link protocol messagesThe network traffic on the LAN relating to Succession Link protocol messages isdirectly proportional to the number of lines monitored and the number of callsappearing in the switch on these lines. During the life of a basic call, normaloperations performed include MAKECALL, ANSWER, HOLD, UNHOLD andDROP.To calculate the load on a LAN assume that every inbound call appearing in theCall Center does ANSWER, HOLD, UNHOLD and DROP operations. The totalnumber of bytes required for the messages related to these operations is 763 bytesper call. Therefore, to calculate the LAN requirements for Succession Linkprotocol messages, for 10,000 basic calls per hour, use the following formula:(763 x 10,000) / 3600 (seconds per hour) = 2120 bytes per secondIVR messagesThe LAN requirements for IVR messages are very dependent on the customerimplementation. Nortel Networks is currently conducting tests and sample datawill be provided before Symposium TAPI SP, release 3.0 is issued for generalavailability (GA).Call data networking messages between TAPI serversThe network traffic overhead due to call data networking messages is directlyrelated to the following:• the number of calls overflowed from one Meridian switch to a remoteMeridian switch