Avaya 96X1 Series Using Instructions page 13

Origination Application Sequence field and the Termination Application Sequence
field. For more information, see Administering the Signaling Group screen. Without this
administration, Session Manager cannot use relevant signaling trunks for call delivery to
SIP agent deskphones. This administration is important for a configuration where you use
the same Communication Manager entity for all traffic, but now you want to separate the
entity into dedicated inbound call traffic and OPS signaling data.
- Administer sequenced applications for users based on whether the user is on the
originating or on the terminating side of a call. When you design the sequence for
applications that act on deskphones that Communication Manager Evolution Server
controls, you must ensure that Communication Manager is the last application that you
define on the origination side of a call and the first application on the termination side of
the call. This sequence is critical because the evolution server uses the full-call model for
call processing, and all origination and termination feature processing occurs on the
origination side of the call.
For more information, see Implementing End-to-End SIP.
- For dedicated SIP trunk groups for deskphone signaling with Session Manager, administer
the Measured field on the Trunk Group screen as none. This administration prevents
CMS or Avaya IQ reporting issues, including loss of reporting.
• Use the phone number as the primary handle when you administer Session Manager. Do not
use alphabets.
• Ensure that the phone type on the Station screen is one of the 96X1SIPCC types, and assign
an agnt-login button on the Station screen for each SIP agent deskphone.
• The following are some guidelines for Secure Real-time Transport Protocol (SRTP):
Use the Transport Layer Security (TLS) protocol for signaling between Session Manager and
SIP agent deskphones and between Communication Manager and Session Manager.
Connection to Avaya Aura
However, if you must use Transmission Control Protocol (TCP), ensure that you add the
following parameters in the SIP settings file:
- Administer ENABLE_OOD_MSG_TLS_ONLY as 0. If you administer
ENABLE_OOD_MSG_TLS_ONLY as 1, third-party call control Computer Telephony
Integration (CTI) applications and Supervisor Assist do not work.
- Administer the configuration parameter ENABLE_PPM_SOURCED_SIPPROXYSRVR as
0. If the parameter is not 0, the proxy server information from Personal Profile Manager
(PPM) overwrites the information in the settings file.
For more information, see Implementing End-to-End SIP.
• Configure the Simple Network Time Protocol (SNTP) server for SIP agent deskphones
because Communication Manager checks the time on the certificate to validate the
certificate.
• Administer media encryption parameters with the same cryptosuites on Communication
Manager and SIP agent deskphones. The default cryptosuite is aescm128–hmac80.
• Administer none on the IP Codec Set screen for no encryption. The default setting is 9 that
corresponds to the setting on the Communication Manager administration screen.
• Do not configure SIP agent deskphones with EC500 buttons because Communication
Manager as an evolution server does not support EC500.
June 2019
®
Presence Services requires TLS.
Using 96X1 SIP agent deskphones with Call Center Elite
Comments on this document? infodev@avaya.com
Administration tips
13