Use System Manager to administer Communication Manager features to ensure that Communication Manager synchronizes translation files with the System Manager database.
Ensure that the field option in the Expert Agent Selection (EAS) Enabled field on the Feature-Related System Parameters screen is y.
Administer the SIP Endpoint Managed Transfer field on the Feature-Related System Parameters screen as n. You must select n to prevent unexpected events, such as inaccurate reporting or loss of User-to-User Information (UUI).
Communication Manager provides the SIP Agent functionality only with the Evolution Server configuration and not with the Feature Server configuration. Therefore, you must administer the IMS Enabled field as n for all SIP signaling groups. If the field option is y, Communication Manager sends a Feature Invocation Failure error message when an agent attempts to log in to the system.
Add a domain on each IP Network Region screen for all 96X1 SIP agent deskphones within a network region. Ensure that the authoritative domain field on the IP Network Region screen is equal to the SIP domain. If the domain entry is blank, SIP agent deskphones register with Session Manager but do not display agent buttons, such as auto-in, manual-in, aux, or acw.
SIP agent deskphones must have dedicated SIP trunk groups for:
Furthermore, Call Management System (CMS) or Avaya IQ must not measure Off-PBX Station (OPS) SIP trunk groups that carry signaling data because signaling data is inconsistent with the format of call traffic data. Sharing of SIP trunk groups and measuring of signaling data can lead to loss of call traffic data and reporting errors.
To prevent data loss and reporting errors, Communication Manager does not send station signaling-related messages to CMS or Avaya IQ. Furthermore, if CMS or Avaya IQ measure OPS SIP trunk groups, Communication Manager logs a SIP OPTIM TG Meas Error denial event 5073.
Use private settings to ensure that SIP trunks for Off-PBX Telephone Integration and Mobility (OPTIM) OPS signaling are from dedicated SIP trunk groups. To prevent agent extension manipulation, administer the trunk group as private and the number format on the route pattern as unk-unk.
Add SIP trunk numbers on the Private Numbering and the Public Unknown Numbering screens.
Ensure that Session Manager has two entities for Communication Manager: One for inbound call traffic and the other for agent deskphone traffic. All SIP trunks must be on the Processor Ethernet (PE) interface.
Administer different listen port numbers for inbound trunks and SIP agent deskphone signaling trunks. Ensure that each function has dedicated trunk groups. For more information, see Administering the Signaling Group screen.
The Session Manager Profile configuration for SIP agent deskphones must point to the Communication Manager entity that you define for OPS trunk (station) signaling in the 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® Presence Services requires TLS.
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.
