12-25-2012 09:07 AM - edited 03-14-2019 11:02 AM
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.
Solved! Go to Solution.
12-25-2012 09:28 AM
Hi haouaswajih,
After referring to the below link,
Could you please crosscheck the CTI ports being used\pointed here in your setup.
Hope this helps,
Anand
Please rate helpful posts !!
12-25-2012 09:28 AM
Hi haouaswajih,
After referring to the below link,
Could you please crosscheck the CTI ports being used\pointed here in your setup.
Hope this helps,
Anand
Please rate helpful posts !!
12-25-2012 12:39 PM
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
01-02-2013 06:19 AM
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
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide