Running a dual integration with Call Manager 4.1 , Avaya V11.5 G3R PBX (with 5 digital PIMG units), and Unity 4.1 with off box Exchange 2k3. We have a long delay between PBX to PIMG calls from tie line (off site) locations. Local site calls work as advertised with all data and timeframes acceptable. The off site PBX's are where the problem lies. The PIMG's answer the call from the hunt group and quit ringing, then waits 20 soconds of silence before it passes the call to Unity. This is due to the PIMG not picking up the calling name/ANI of the calling party. Is there somewhere I can change this timeout to not wait so long? Any help you can give would be very much appreciated.
See CSCsd48815. The problem occurs when the PIMG cannot find a numeric Calling Number in the display. If possible, you need to configure your PBX so that it forces some number (any number will do) into the display for these calls. For example, if the display is showing the trunk 'name' then adding a numeric character to that name could be a workaround.
OK, well I spoke a little too soon. Putting a number in the name field resolved some of the issue, but we are still coming up with "unknown name" on some of the other trunks. I understand this is on the list of things fixed for Unity Version 4.3. Are there some registry settings or an ES that we can apply in the interim on our 4.1 system. Any help you can provide would be greatly appreciated.
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: firstname.lastname@example.org 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 ...