I have a CCM 6.1 system with several key hunt groups setup. Is there anyway using the CISCO reporting to trace where the calls to the hunt groups passed to which extensions or how to create a report to so who is logged out of hunt group at any one time?
We have a similar issue to Mark, when using CUCM7.1. Users in a Hunt Group complain that distribution of Calls is uneven and some agents get far more calls than others. We have setup sequential Hunt Group to round-robin through the agents so this is not theoretically possible. We have also manually monitored the calls without seeing uneven distribution.
Is there any way CUCM can report on the distribution of calls to a Hunt Group? i.e. Call A at 9:05.23 went to Agent A, Call B at 9:05.24 went to Agent B and so forth.
This would enable us to show the supervisor that calls are being round robined.
All of the reporting CAR does is for billing purposes and billing purposes only so it won't have a very good way to track distribution of calls through a hunt pilot.
That said all of the info is in the CDRs so the raw data is there. You can try doing CDR searches from within CAR to find all calls to your hunt pilot and then look at what field gets populated with the directory number that eventually received the call. Otherwise there may be a 3rd party CDR analysis tool that has this feature built-in.
Reporting on hlog activity is going to be more tricky because that's not reported in a CDR, but in the db. You can use AXL to query on the devicehlogdynamic table. The columns you want are fkdevice (pkid of the entry in device table) and hlog (true = logged in, false = logged out).
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...