Attempting to monitor a hunt-group where acd=n gives an error "invalidDeviceID" in the DMCC Dashboard.exe:

Start Application Session Response: 1 Session ID: 19B6D5A47B07EBE441E3E4817DD97245-10 Duration:180 Protocol Version: http://www.ecma-international.org/standards/ecma-323/csta/ed3/priv4
Get Device Id Response (Device.Phone):2 Device Id:21050:S8800:10.10.0.24:0
Start Monitor Response (Call Information):3 Monitor ID:80005
Start Monitor Response (Device.Phone):4 Device ID:21050:S8800:10.10.0.24:0 Monitor ID:34 User State:Device.Phone 19B6D5A47B07EBE441E3E4817DD97245-10
Start Monitor Response (Media):5 Device ID:21050:S8800:10.10.0.24:0 Monitor ID:35
Session Management Start Monitor Response:7 Monitor ID:37 Device ID: 21050:S8800:10.10.0.24:0
Start Monitor Response (Third Party Call Control):6 Error:<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>invalidDeviceID</operation></CSTAErrorCode>

Changing the hunt-group from acd=n to acd=y, allows the monitor to proceed correctly.
How can we monitor hunt-group activity where acd=n?


Thanks

your description reads backwards.

a non ACD hunt group (presumably on a system where agents/skills is not enabled) should be monitorable via TSAPI and DMCC Call Control services. It is supposed to provide call events for calls traversing the hunt group. I have only ever tested the TSAPI case (can you monitor the hunt group withTSAPI when it is not a acd type)? What types of events are you receiving?

A monitor on a acd hunt group will only provide agent login/logout events.

The normal guidance is to monitor the VDN that is feeding calls to the hunt group (for the ACD case). This approach will work regardless of how the hunt group is configured. Use the monitorCallsViaDevice() method to initiate a VDN monitor.

I'm not using TSAPI, only dotNET dmcc. Using DMCC dashboard.exe to test

DMCC uses TSAPI services for all call control services... e.g. putting call monitors on stations, VDNs and hunt groups.

ok, but do you know why I'm getting an error returned when attempting monitor a huntgroup with acd=n ?

Start Monitor Response (Third Party Call Control):6 Error:<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><operation>invalidDeviceID</operation></CSTAErrorCode>

Any help would be appreciated. I don't know where to proceed from here.

no I don't. I rarely work with systems where EAS is disabled (where the system allows acd=n huntgroups).

so
1) does the request to create the monitor even go to Communication Manager (use the g3trace file to understand this) see the FAQ related to enabling TSAPI tracing?
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/index.gsp#10

What exact error code is being returned by CM to the request?

2) if you have CM access look deeper at the ASAI trace using MST, find the domain control and look at the ASAI response code.

3) Again with CM access check to see if EAS is enabled on the system, I don't think that by itself would block creating a monitor but it may since the hunt group is non acd and EAS is set. This is on page 7 of the "display system-parameters customer-options" form.