Any one know of a hack to allow Unity to fire MWIs on multiple DIFFERENT integrations at the same time?
e.g. User has both a Centrex and a Call Manager extension in two different locations. I need to light the MWI on both the Call Manager and the Centrex. (e.g. send an SMDI MWI activate and also send a TAPI MWI activate)
Even though in Unity I can list up to 9 separate MWI numbers the documentation leaves out that they all need to be using the same integration. (oops)
That works really well if you've got a single integration configured on Unity and what to add a "partial" integration for alternate MWIs only. But since in this case the serial engine is already in use by the Centrex integration I'm not sure if the CCM integration will be able to load a serial MWI method. We're going to poke at this a bit in our lab in Seattle to see if it blows up. I'll post the results here.
Bad news, doesnt look like this is going to work. I tried it two ways. First, adding a MWIType=Serial alternate MWI method to the Cisco0002.ini switch file. This caused some serious errors on startup and none of the serial integration worked. So next I tried adding a MWIType=TAPI alternate MWI method to the Centrex0008.ini file. With this, Unity attempted both serial MWI and a dialout MWI for my test subscriber (test subscriber was associated with the Centrex integration). Sadly, Unity would only look for available ports for the dialout amongst the Centrex ports. It wont do the dialout on the CCM ports.
Unfortunately, having a single subscriber with extensions on both sides of a dual integration is not something that was planned for during design time. Youll run into similar problems with transfers, yes? Probably the official recommendation should to be pick one phone system to send the MWI request to and just send message notification dialouts to the other. Not nearly the same, I know, but might be the best option within the designs of Unity.
That said, Ive got a couple hacks I want to try out. Let me get back to you on this one.
Wow, I got it to work. I half dont believe it myself so bear with me while I go over the process
1. Make a copy of the AVSMDI.AVD configuration file and name it AVSMDI2.AVD
2. Edit AVSMDI2.AVD so that it uses COM port 2 rather than 1
Toward the bottom you should see something like
Port=1 <- change this to a 2
3. Add the following section to the end of the Cisco0002.ini file
4. Now for Subscribers associated with the CCM integration, add additional MWI extensions such as this
(the Z fires the alt MWI method and 9015551212 is the 10-digit Centrex phone number that you want to send the request for)
My test failed previously because when the CCM integration loaded the alt MWI method requested use of COM1. Then when the Centrex integration initialized it also requested COM1 but was blocked. I ended up with no serial integration at all. With the config above, CCM requests COM2 fine. Then the Centrex requests COM1, no problem. Now, heres the cool part. Youre asking, but how will this work with MWIs firing out of both COM1 and COM2? Turns out Unitys serial engine has no chance of running both COM ports at the same time. When the second integration loads it overrides the serial configuration of the first integration. In my case, everything ended up going in and out of COM1. Note that if youre integrations initialize in the other order (Centrex then CCM) then you might need to flip-flop the COM1-2.
Finally, everything above is well outside intended and tested configuration for Unity. If you want to try it out, I can help you a bit on this forum but beyond that youre on your own.
BTW My other harebrained idea involved spitting off the SMDI cable from the Unity server and running the CMI service on the CallManager.
Oh well. I tried the various settings and got the box totally hosed. I'm rebooting it again and hopefully it will come back up operating.
I changed the ports on the AVSMDI to 1 and AVSMDI2 to 2, and the SMDI completely broke. Now I'm trying it the opposite way. Worse comes to worse I'll just put all the settings back. Turns out on the 10-digit idea I had to change the number of one of the call processors to 10 digits to get it to work.
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...