Nortel TAPI Product Support Bulletin page 2

The SAPphone-based integration enables the ability to screen pop customer data
based on information collected by an IVR system connected to the Meridian* 1* and
Symposium* Call Center Server. Nortel Networks Service Update 1 for TAPI SP 2.3
for the Meridian 1 provides fast deployment with out-of-the-box integration with the
mySAP CRM Customer Interaction Center desktop without the need for complex
configuration or custom development assuring timely deployment without business
disruption.
Engineering Guidelines – TAPI SP Server provisioning
The engineering guidelines to be issued with Service Update 1 for TAPI SP 2.3 for
the Meridian 1 will state the server engineering guidelines for deployment of the
TAPI SP product. The TAPI SP product must be deployed on a server meeting the
requirements of these guidelines in order to operate to design specification and
meet the support requirements of Nortel Networks.
TAPI SP and SAPphone* server application co-residency engineering assessment
and validation has not been conducted. The potential interaction effects of the two
applications, and the potential impact upon server engineering resources, such as
CPU and memory load is not known at this time.
Nortel Networks therefore do not recommend and are unable to support co-
residency of the SAPphone* server application with Service Update 1 of the
TAPI SP 2.3 for the Meridian 1.
Provisioning of the SAPhone* server application should follow the
recommendations of mySAP™ CRM solutions.
Refer to the following SAP* Bulletins OSS 501643 and OSS 458628 for further
information.
* Nortel Networks, the Nortel Networks logo, the Globemark, Symposium, Meridian and
Meridian 1 are trademarks of Nortel Networks. SAP, mySAP, mySAP.com, and SAPphone are
trademarks of SAP AG.
For further information please contact your Nortel Networks representative.
Issued Martin Walker
By: Product Manager CTI
Nortel Networks
Mervue Business Park, Galway, Ireland.
Tel: +353 91 732706
E-Mail: mtwalker@nortelnetworks.com
END OF DOCUMENT
2 of 2