Chapter 3: Administering Communication Manager - Avaya 96X1 Series Using Instructions

Chapter 3: Administering Communication
Before you begin
Communication Manager must connect with Session Manager in a non-IP Multimedia Subsystem
(IMS) signaling group for Call Center functionality.
Ensure that the field option in the IMS Enabled field on the SIP Signaling Group screen is n to
prevent Feature Invocation Failure when an agent logs in to the system.
Verify the field settings and values in the following fields on the System-Parameters Customer-
Options screen:
• ISDN-PRI
• IP Trunk
• Expert Agent Selection (EAS)
• Maximum Administered SIP Trunks
• Maximum Off-PBX Telephones-OPS
Ensure that the field option in the DID/Tie/ISDN/SIP Intercept Treatment field is attd and the
Trunk-to-Trunk Transfer field is restricted.
About this task
You can use SIP agents when you administer Communication Manager as an evolution server.
As an evolution server, Communication Manager uses the full-call model. In the full-call model, call
processing is a single step procedure, that is, Communication Manager processes the origination
and termination parts of the call without a break.
For information about IMS signaling flow and full-call model, see Implementing End-to-End SIP.
Procedure
1. Change the dialplan analysis.
2. Change the Feature Access Codes (FAC) for Automatic Alternate Routing (AAR) and
Automatic Route Selection (ARS).
3. Add a SIP domain in each network region, and administer an IP node name for the IP
address of the Session Manager Security Module.
4. Add a SIP signaling group for each Session Manager Security Module. For message
interchange between Communication Manager and the SIP server, select y in the Peer
Detection Enabled field on the Signaling Group screen.
June 2019
Manager
Using 96X1 SIP agent deskphones with Call Center Elite
Comments on this document? infodev@avaya.com
10