Outbound Dialer Port C=10 R=0

[erwin.stevanus]

Hi,

I have an issue with my Outbound Dialer Ports. On the Dialer Window Title it's showing C=10 R=0 B=0.

I've checked in the Call Manager and the Dialer Ports (VIP 30 Device) are shown as registered.

One thing though, the Dialer is configured to connect to a TFTP Server which is different than where the Dialer ports are registered to.

Ex:

CM Pub 192.168.1.1

CM Sub 192.168.1.2

CM TFTP 192.168.1.3

Dialer TFTP Server = 192.168.1.3

Dialer Ports are assigned to Device Pool in Subcriber 192.168.1.2

I have tried the DialogicTest app on the Dialer and were able to call out using the ports.

The ports have been associated with PG_User.

However, I suspect that this issue is related to jtapi communication between the Dialer and CM.

does anybody have any suggestion?

Regards

Erwin

[Riccardo Bua]

Hi Erwin,

do you have any issue with the import list? Guess the dialer is running out of records, the title is saying 10 records were processed and closed.

Check on the campaign scheduling and make sure you have records to dial.

Regards,

Riccardo

[erwin.stevanus]

Hi Riccardo,

No, not really.

The issue seems to be related to pguser association. Although the ports have been associated with pguser, i don't seem to see any activity on the jgw1 process on the CM PG.

I have logged a tac case for this one and in the middle of investigation.

will let you know how it goes.

Regards

Erwin

[Sheraz Saeed Lodhi]

Hi Erwin,

i am also facing the same error but i am using CUCM 6.1.2 only Pub no Subcriber. on VMWare machine

[Edward Umansky]

Have you checked Dialer logs? Restart the dialer and see if any errors stand out in the logs.

[voiceops]

Erwin,

What ever happened with this issue?

I'm having the same exact problem.

thanks

[CLAUDIO RIVAS]

I have the same issue, seems to be a configuration problem but on the dialer logs i've found this error:

failure code: 13 [CF_INVALID_CSTA_CONNECTION_IDENTIFIER], peripheral error code: 10137 [C_??CAUSE??]

So i think this is what i'll try to follow.

Regards,

Claudio.

[CLAUDIO RIVAS]

Just to let it documented,

The first thing to notice is that ports are registrated on CUCM but are not reflected as registrated on Dialer process.

I've noticed on CUCM that when i imported the file with the template i created it was not creating the first port on the list, so i deleted the first port on the list of the dialer and cycled the Dialer process and the next time Dialer process restarted the ports was registered.

One important thing is that you must have a minimum of 4 ports on the dialer, other way it won't sabe your configuration.

Hope this helps someone else because i think this is not documented on any post.

Regards,

Claudio.

[BorisRus]

Dear, have you found a solution to this problem?
I also get Ports C: 4, R: 0,
CCM devices are registered and added to the PGuser.
in the logs of the dialer itself shows this:
dialer-baDialer Trace: (CLMGR_IP) Control failure event, port: 000, id: 1000000069, failure code: 12 [CF_INVALID_CSTA_DEVICE_IDENTIFIER], peripheral error code: 11004.

[bill.king1]

You will likely have to provide more information, such as version, if this is the old SCCP dialer vs. SIP, etc., as the way the dialer works is much different than outlined in this original post.

[BorisRus]

Hello Bill,

UCCE 10.5.1

UCM 10.5.2

Option Outbound Dialer SCCP

status dialer:

icm-Dialer BADialer_IP [CM-A] [CTI-A] [Ports C:4,R:0,B:0] [MR-A]

status PIM for Outbound:  icm-PG2A MR_PIM - pim1 - [MR_PG ACTIVE]

for Device UCM type "Cisco 30 VIP" registered.

Application User CCM_PG add device controlled.

pg1a-pim3 Trace: AddressInService: Addr=6162.
10:45:24:929 pg1a-pim3 Trace: JTAPIClient::ActivateJTAPIClient: sending msgAddPeripheralMonitor.
10:45:24:929 pg1a-pim3 Trace: DeskLinkPeripheral::AddMonitoredDevice: NetTgtID=5380, Instrument=6162, DevType=MONITORPHONE.
10:45:24:929 pg1a-pim3 Trace: AddressInService: Addr=6163.
10:45:24:929 pg1a-pim3 Trace: JTAPIClient::ActivateJTAPIClient: sending msgAddPeripheralMonitor.
10:45:24:929 pg1a-pim3 Trace: DeskLinkPeripheral::AddMonitoredDevice: NetTgtID=5381, Instrument=6163, DevType=MONITORPHONE.
10:45:24:930 pg1a-pim3 Trace: AddressInService: Addr=6160.
10:45:24:930 pg1a-pim3 Trace: JTAPIClient::ActivateJTAPIClient: sending msgAddPeripheralMonitor.
10:45:24:930 pg1a-pim3 Trace: DeskLinkPeripheral::AddMonitoredDevice: NetTgtID=5378, Instrument=6160, DevType=MONITORPHONE.

ERROR

10:45:26:808 pg1a-pim3 Trace: CSTAQueryDeviceInfo: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0229006 Dev=6161.
10:45:26:808 pg1a-pim3 Trace: PRIVATE_DATA: DataRequest=0.
10:45:26:809 pg1a-pim3 Trace: CSTAUniversalFailureConfEvent: TPServices::CSTAUniversalFailureConfEvent InvokeID=0xf0229006 Error=INVALID_CSTA_DEVICE_IDENTIFIER.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: PeripheralErrorCode=0x2afc(11004).
10:45:26:809 pg1a-pim3 Trace: CSTAQueryDeviceInfo: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0229007 Dev=6163.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: DataRequest=0.
10:45:26:809 pg1a-pim3 Trace: CSTAUniversalFailureConfEvent: TPServices::CSTAUniversalFailureConfEvent InvokeID=0xf0229007 Error=INVALID_CSTA_DEVICE_IDENTIFIER.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: PeripheralErrorCode=0x2afc(11004).
10:45:26:809 pg1a-pim3 Trace: CSTAQueryDeviceInfo: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0229008 Dev=6160.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: DataRequest=0.
10:45:26:809 pg1a-pim3 Trace: CSTAUniversalFailureConfEvent: TPServices::CSTAUniversalFailureConfEvent InvokeID=0xf0229008 Error=INVALID_CSTA_DEVICE_IDENTIFIER.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: PeripheralErrorCode=0x2afc(11004).
10:45:26:809 pg1a-pim3 Trace: CSTAQueryDeviceInfo: Peripheral::ProcessCSTAThirdPartyServiceRequest InvokeID=0xf0229009 Dev=6162.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: DataRequest=0.
10:45:26:809 pg1a-pim3 Trace: CSTAUniversalFailureConfEvent: TPServices::CSTAUniversalFailureConfEvent InvokeID=0xf0229009 Error=INVALID_CSTA_DEVICE_IDENTIFIER.
10:45:26:809 pg1a-pim3 Trace: PRIVATE_DATA: PeripheralErrorCode=0x2afc(11004) 

[bill.king1]

These 616X numbers, they don't overlap/conflict with anything else in your UCCE or UCM system (like agent extension ranges for instance)? And just as a test, have you disassociated and reassociated one of them with PG user to see if it looks any better?

[BorisRus]

UCM   List Route Plan Report only device Cisco 30 VIP associated with these numbers.

UCCE no label, no Dialed Number.

in UCCE Configuration Manager -> Device Target Explorer created by Device Target for Dialer

Dialer_5010_616X

Confuguration parameterts /devtype monitorphone /dn616X /monitor 5010. Where 5010 ID Dialer.

Label for Device Target no.

Is it necessary to create label PIM CCM and PIM for Dialer ?

there is no effect when decoupling and binding to the PG user

[bill.king1]

I could be mistaken, but are you sure you need to add them as device targets in this scenario?

Also, did you try the diagnostics?

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_10_5_1/User/Guide/UCCE_BK_O62BE51D_00_outbound-option-guide-for-ucce/UCCE_BK_O62BE51D_00_outbound-option-guide-for-ucce_chapter_0101.html#UC...