Avaya 96X1 Series Using Instructions page 12

Administering Communication Manager
• 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:
- Call traffic with service providers and other Communication Manager servers.
- Call signaling with Session Manager.
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.
- Do not add extra digits to station extensions and agent extensions on the Private
Numbering or the Public Unknown Numbering screens. The extra digits can cause
Session Manager to send calls to Communication Manager for further processing without
terminating calls to SIP agent deskphones. If private unknown numbering modifies agent
extensions, agents can log out and then log in to the system. However, agents cannot use
feature buttons to change work modes.
- 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
June 2019 Using 96X1 SIP agent deskphones with Call Center Elite
Comments on this document? infodev@avaya.com
12