IPMA proxy line configuration.

-
IPMA feature, as the name suggests, is provided in a manager / assistant environment to work together more effectively with enhanced sub-features.
Cisco Unified Communications Manager Assistant supports two modes of operation: proxy line support and shared line support. Shared line configuration is explained in the next post.

Before we start the configuration process, please note that this is sample configuration, which is tested in Lab environment.

Pre-requisites-
Configure CTI RP same as Manager's DN:- so that call routes via CTI RP to hit IPMA, else call with directly routes to manager's DN.

Start CTI Manager service on required node.

Create partitions/ CSS for Manager, CTI RP and PSTN gateway
Partitions:-
Partition Manager
Partition PSTN gateway
Partition CTI RP

CSS:-
CSS 1 includes manager and PSTN gateway
CSS 2 includes CTI RP and PSTN gateway

Manager Phone:- DN=1000, Partition Manager and CSS2.
Assistant Phone personal line:- DN=3001, partition PSTN and CSS2
Assistant Phone proxy line:- DN=3000, partition PSTN and CSS1.
PSTN gateway:- partition PSTN and CSS2
CTI RP:- DN=1XXX, partition CTI and CSS2


Steps to configure IPMA proxy line-
1. Configure phone service IPMA and assign it to manager and assistant phone.
IPMA service URL-
http://<ip address>/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#

2. Navigate to System > service parameter > IPMA and set below parameters-
CTI manager primary IP address, IPMA primary IP address, phone service and CTI route point.

3. Provide partitions and CSS on all devices - Manager, Assistant, PSTN gateway and CTI route point.
Also, provide 'Standard manager' softkey to Manager and 'standard assistant' softkey to Assistant phone.

4. Configure End users:-
Manager end user:-
Add manager's phone in the controlled devices.
Navigate to manager configuration > uncheck auto-configuration.
Populate device name.
Provide intercom line, if you are using.
Associate the concerned assistant and select manager's lines.

Assistant end user:-
Add assistant's phone in controlled devices.
Navigate to assistant configuration > uncheck auto-configuration.
Populate device name and provide primary line
Provide intercom line, if you are using.
Associate manager's line to be proxied by Assistant, under manager line.
Select manager name
Provide proxy line as available line.

5. Restart IPMA, CTI manager from CUCM seviceability page.
Restart tomcat service from SSH, run command "utils service restart Cisco Tomcat"
Cisco Tomcat loads the Cisco IPMA service, a servlet.

6. Download IPMA console from plugins and log in using assistant ID.

References.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more