02-27-2015 02:05 AM - edited 03-14-2019 02:29 PM
I have installed CUCM PG, MR PG, and Dialer installed on one Server.
My Dialer status is :
Solved! Go to Solution.
03-02-2015 01:02 AM
i see your pim is trying to connect to MR application on port 42067, even if you have specified the port as 38001.
please cycle the dialer and PG and if possible attach logs of badialer and MR pim here, so we can walk through logs.
regards
Chintan
02-27-2015 05:23 AM
must be config issue, can you please share a dialer installation steps?
and also MR PG installation steps, specifically for MR pim configuration?
Chintan
03-01-2015 10:18 PM
(CVP PG,AW/HDW,ROuter,LOgger) -- 192.168.1.22
(CUCM PG,CTIserver,Dialer,MR PG) -- 192.168.1.91
Dialer Configuration
**Node Manager Properties
Production Mode: Enabled
Auto Start at system startup: Enabled
**Dialer Type
SCCP
**Outbound option Dialer Properties
Campaign Manager Server: 192.168.1.22
CTI Server A: 192.168.1.91
CTI Server Port A: 42067
Heart Beat: 500
Media Routing Port: 38001
CUCM TFTP server 192.168.1.51
MR PG COnfiguration
**Logical Controller ID-- 5002
** Pripheral Interface Managers
Peripheral Name MRPG_1
Peripheral ID 5002
Application Hostname 192.168.1.91
Application Connection Port 38001
** PG Interface 192.168.1.91
Router 192.168.1.22
03-02-2015 01:02 AM
i see your pim is trying to connect to MR application on port 42067, even if you have specified the port as 38001.
please cycle the dialer and PG and if possible attach logs of badialer and MR pim here, so we can walk through logs.
regards
Chintan
03-02-2015 02:05 AM
Hey Chintan
Attaching the Logs:
MR PG: PIM, PGAG, MDS, OPC
Dialer: Badialer
Logger: BAimport, CampaignManager.
also can you tell me is my configuration correct or wrong
is there any dependance on installation on the same server, and also 1 point i in my lab have not configured private IPs are they essential.
03-02-2015 06:21 AM
oh yes your configuration looks good, but i also was able to catch the cause:
looking at the dialer logs, its trying to register with campaign manager. but failing to do so,and that is why it has not started to listen on MR instance.
11:45:34:193 dialer-baDialer Trace: Attempting EMT connection to computer [192.168.1.22/192.168.1.22], port [40072]. 11:45:35:207 dialer-baDialer Trace: Unable to establish an EMT connection:. 11:45:35:207 dialer-baDialer Trace: error value [10060], text: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.. 11:45:37:219 dialer-baDialer Trace: Attempting EMT connection to computer [192.168.1.22/192.168.1.22], port [40072]. 11:45:38:234 dialer-baDialer Trace: Unable to establish an EMT connection:.
and looking at campaign manager now looks like dialer is not configured.
11:47:06:329 la-CampaignManager Trace: Dialer on computer MRPG hasn't been configured. 11:47:06:329 la-CampaignManager Trace: Dialer on computer MRPG hasn't been configured. 11:47:06:329 la-CampaignManager Trace: Configuration request: the dialer with id 4 has no configuration data. 11:47:07:344 la-CampaignManager Trace: Dialer with connection id 4 is already connected.
have you configured dialer and campagn in configuration manager? if yes can you please post screenshot here?
regards
Chintan
03-02-2015 09:36 PM
03-02-2015 11:11 PM
please check the hostname where Dialer is installed matches with host-name configured on Dialer Configuration in AW (Computer name field in Dialer config).
also please check Dialer Name matches in Dialer Installation and Configuration tab.
i see some mis configuration on above
Chintan
03-02-2015 11:29 PM
please check the hostname where Dialer is installed matches with host-name configured on Dialer Configuration in AW (Computer name field in Dialer config).
-->
In AW Configuration for Dialer the Computer name was wrongly configured
i have correct it (computer Name : MRPG) -- should i use FQDN or only computer name is enough.
also please check Dialer Name matches in Dialer Installation and Configuration tab.
in dialer installation it doesnt ask for dialer name ??
03-03-2015 12:34 AM
thank you chintan my PIm is up and Dialer status is showing
icm9-Dialer BADialer_IP [CM-A] [CTI-A] [Ports C:6,R:0,B:0] [MR-A] : 01:04:37
I am using CIPC for outbond dialing.
i have extracted phone as per disgn giude. and registered one phone.
but i am not able to login on any agent on that phone.
in Finesse it is giving Generic error and in CTI ToolKit it is giving invalid user name and password
03-03-2015 01:01 AM
one question (Once my agent get login then only my R:'x' will show count in Dialer service ???)
Can we use CIPC for Outbond dialing.
i am not able to login on that extension
CTI tool kit error: agent not permited to login.
in CTIOS logs i get:
14:21:21:350 CTIOS1-ctios Trace: [agent.5000.1234] SetAgentState: AgentInstrument mismatch. Using AgentInstrument from request args: 1000.
14:21:21:350 CTIOS1-ctios Trace: <-SND[Sushant-PC123-4436-8324][agent.5000.1234]:eAgentInfoEvent.
14:21:21:351 CTIOS1-ctios Trace: >>CG:[agent.5000.1234]:eControlFailureConf(2):The request is not compatible with the object. PeriphErr:10145(FailCode:2 PrphErrCode:10145 UniqObjID:agent.5000.1234 MsgID:eControlFailureConf MsgTyp:eSetAgentStateRequest TgtCILClntID:Sushant-PC123-4436-8324).
14:21:21:351 CTIOS1-ctios Trace: [SYSTEM]SB:CONTROL_FAILURE_CONF,Object(agent.5000.1234) Type(agent) REMAINS in object map, FailureCode:2=The request is not compatible with the object.,PeripheralErrorCode:10145,TargetClientID:Sushant-PC123-4436-8324..
14:21:21:351 CTIOS1-ctios Trace: <-SND[Sushant-PC123-4436-8324][agent.5000.1234]:eControlFailureConf(2):The request is not compatible with the object. PeriphErr:10145.
14:21:21:414 CTIOS1-ctios Trace: XXX CLIENT[Sushant-PC123-4436-8324], CLOSE.
14:21:21:414 CTIOS1-ctios Trace: CClient::Close: CLIENT[Sushant-PC123-4436-8324][0x23121d8, CLOSE(), Calling OnConnectionClosed().
14:21:21:414 CTIOS1-ctios Trace: ->RCV[Sushant-PC123-4436-8324 a=1234]:eOnConnectionClosed.
14:21:21:414 CTIOS1-ctios Trace: icm9_CTIOS1 ctios server [10.5 02042] [ACTIVE, CG: 192.168.1.91, CGPort: 42067, Connections (Agent Mode: 0; Monitor Mode: 0)].
14:21:21:414 CTIOS1-ctios Trace: [1] OnConnectionClosed, Client[0x023121D8][Sushant-PC123-4436-8324].
03-03-2015 01:07 AM
You cant login on dialer port, dialer ports are virtual phones that dialer uses to dial out from CUCM or VG.
if you are using sccp dialer ports then you first created ports on Dialer configuration --> export them in csv file --> and run bat job on cucm to create ports on CUCM out of csv file--> and then once the ports are created on CUCM you assign them to PG user of agent PG on which dialer resides.
once all this done, you ports will be in Ready state.
the agent logs into the normal phone, and you have to associate that phone to agent PG user.
you must follow the outbound option guide, it has all the information step by step.
03-03-2015 01:41 AM
yes i have done that:
added port map in dialer --> extracted the ports with correct cucm version selected --> in cucm created correct phone template --> then created correct phones using the Extracted file --> got properly configured.
Assigned the ports to PG users.
Recyled the Dialer service still not a singleport is getting registered.
does need to recycle anything else.
03-03-2015 01:51 AM
reset your ports and cycle dialer and if possible post your badialer logs here.
we will look into that.
03-03-2015 03:20 AM
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