UCCE SIP Dialer not active and PIM neither

[haouaswajih]

Dear Networkers,

We have UCCE 8.5(4) installed.

We have configured and installed aSIP dialer.  The issue is that the SIP dialer is not working and the PIM is not active.

From the Dialer process output I can see the following after enabeling the EMSDisplayToScreen :

18:02:48 Trace: Trying to connect to server: 17.20.10.80 on port: 44027

18:02:48 Trace: socket open on Server=17.20.10.80 port=44027

18:03:09 Trace: Error calling Connect(): 10060

18:03:09 Trace: Could not connect to either CTI Server A or CTI Server B

18:03:09 Trace: CTI Server configuration:

18:03:09 Trace:         CTI Server A: 17.20.10.80, Port: 44027

18:03:09 Trace:         CTI Server B: 17.20.10.80, port: 44027

From the MR PIM process output I can see the following after enabeling the EMSDisplayToScreen :

18:03:40 ADDED\UPDATED 0 PeripheralTargets on Peripheral 5008.

18:03:40 ADDED\UPDATED 0 PeripheralMonitors on Peripheral 5008.

18:03:40 ADDED\UPDATED 2 MediaRoutingDomain on Peripheral 5008.

18:03:40 Trace: Transport: appServerHostName1 = kbprcrmipc01a01

18:03:40 Trace: Transport: appTcpServiceName1 = 38003

18:03:40 Trace: Transport: appServerHostName2 =

18:03:40 Trace: Transport: appTcpServiceName2 =

18:03:40 Peripheral 5008 sending OPC PIM_OK_ACK acknowledgment for command PIM_CONFIGURE_REQ (TransID=0).

18:03:40 Attempting to connect to MR application at IP address 172.20.10.80 port 38003.

18:03:50 Attempting to connect to MR application at IP address 172.20.10.80 port 38003.

18:04:02 Attempting to connect to MR application at IP address 172.20.10.80 port 38003.

18:04:11 ProcessPIMSetIdleReq: Peripheral 5008 going idle.

18:04:14 Peripheral 5008 sending OPC PIM_OK_ACK acknowledgment for command PIM_SET_IDLE_REQ (TransID=33).

18:05:11 ProcessPIMSetIdleReq: Peripheral 5008 going idle.

18:05:11 Peripheral 5008 sending OPC PIM_OK_ACK acknowledgment for command PIM_SET_IDLE_REQ (TransID=34).

For the Dialer process, I can see that the dialer cannot connect the CTI Server on the port 44027, but the CTISVR is active and working fine (CTIOS also).

For the PIM process, I can see that it couldn't connect to the dialer on the port 38003, but the configuration is correct.

Any help please ?

Thanks in advance.

[anchoudh · Accepted solution]

Hi haouaswajih,

After referring to the below link,

http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/outbound_option/outboundoption9_0/installation/guide/UCCE_BK_O4A87BBC_00_outbound-option-guide-for-cisco_chapter_0100.html

Step 10

On the last Outbound Option Dialer Properties dialog box , specify the following        information:  Outbound Option server: The host name or IP address of the Outbound           Option server. This server is typically the same machine where the Outbound Option           Campaign Manager is located. CTI server A: The host name or IP Address of the machine that has           side A of CTI server installed. CTI server port A: The port number the dialer uses to interface with           CTI server side A. The default is 42027. CTI server B: For duplexed installations, the host name or IP Address           of the machine that has side A of CTI server installed. CTI server port B: For duplexed installations, the port number the           dialer uses to interface with CTI server side B. The default is 43027. Heart beat: How often the dialer checks its connection to the CTI           server, in milliseconds. The default value of 500 is acceptable. Media routing port: The port number the dialer uses to interface with           the Media Routing PIM on the Media Routing PG. The default is 3800 to 3801. Call Manager TFTP server: The host name or IP address of the           CallManager TFTP server. This server is the same machine used for the CallManager           publisher.

Could you please crosscheck the CTI ports being used\pointed here in your setup.

Hope this helps,

Anand

Please rate helpful posts !!

[Mark Pareja]

In my experence the default port for ctisvr is 42027 and for the B side 43027, try those values for the sipDialer, this is what I have built and working today. Also you have to make sure the network binding order for your network adapters are set correctly, "Public" first and tcp over net bios .

Also if you are deploying sipDialer TFTP server is not required as the call manager is not serving soft phone ports .

For the PIM "kbprcrmipc01a01" must resolve to the MR PG Public interface , it's always helpful to define the host name in the local host file to avoid DNS complications.

Sent from Cisco Technical Support iPad App

[haouaswajih]

Hi,

In fact it was my CTI server IP address which was wrong !

I checked the Dialer configuration many times but couldn't notice it ! too many IP addresses
Once we corrected the IP address, everything became ok.

Thanks for your help guys