Traditional ICM TDM interface to Avaya ACD question?
Hi I have a question regarding plain old ICM/UCCE interfacing to an Avaya AES and CMS. Recently we've been having issues with ICM seeing a different number of trunks available than what the ACD says are available (i.e., we use expression tester in RTTest to query the TG6.NumberTrunksAvailable). RTTEST comes back with 6 when there are 130 or so available trunks.
The question is: how does ICM derive the Number of trunks available?
CMS provides Agent state information, AES provides call information. Does ICM get the trunk information from the CMS or AES (MAPD/ASAI), or does it do it's own calculations based on call data and information received from the CMS and AES?
Can you direct me to a document that explains this? I know I've seen it before, but can't remember where.
Notice that these are Bri updates that indicate these are AES updates.
Did the PG trunk values match the rttest expr values? They should be close. If not, I suggest to revalidate the trunk config. I had problems where the telecom team did trunk changes on the ACD and I started to get strange trunk updates and I had to find out what they did to fix it.
Re: Traditional ICM TDM interface to Avaya ACD question?
Check in the registry for the G3BugTrunkGroupBitShift DWORD. I believe it's still set to 4 by default, and you have >127 trunks. If you set this back to 0 it should report the number of trunks correctly.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...