How can I handle users w/multiple directory numbers? Here's the scenario: Customer will be running Unity 2.4.6 and CallManager 3.08. They want each user to have two DNs, 1st DN is associated with a DID, 2nd DN is not. 1st DN is to forward on busy to 2nd DN, 2nd DN is to forward no answer/forward on busy to Unity. They want 1st (DID) DN to be user's voicemail extension. How do I get a call forwarded from the 2nd DN to be recognized as a call for the 1st DN voicemail?<br><br>
In Unity 3.0 we will have support for up to 10 IDs (DNs) for each subscriber which will make this scenario a lot simpler.
In Unity 2.4.x youll need to use a call handler for each additional ID you want to associate a mail user with. The easiest way to do this is to configure a call handler with an ID that matches the 2nd DN you mention above. Configure the alternate greeting to be active, set it to blank and set the after greeting action to send to greeting back to the subscriber that owns the 1st DN.
The caller will end up at the greeting of the subscriber regardless of which number the forward from. Just setup the 1st DN to forward to the voice mail on RNA and to the 2nd DN on busy. The 2nd DN should forward to voice mail on RNA or Busy.
In your service parameters of Call Manager (Service -> Service Parameters), make sure that the "RedirectingNumIEDeliveryFlag" is set to TRUE (Default is False). With this, you can forward on no answer/busy multiple times, although the Setup message will always contain the original DN that the call originated from. Therefore, you only need to worry about the main/first DN in Unity. The description for this setting is as follows:
"This flag applies to the SETUP message only on all protocols for the digital access gateway. When the flag is set to True, the RedirectingNumberIE is included in the SETUP message to indicate the first redirecting number and the redirecting reason of the call when Call Forward happens. "
This config is tested, and is how we currently have the Unity integration working with multiple DN's.
So long as folks aren't ever dialing the 2nd line directly (which is not uncommon in a multiple line appearance type sscenario) this will work fine. If you have multiple lines owned by the same subscriber that may or may not get direct calls and need to forward, you'll still have to fall back to the call handler business, at least until 3.0 is out.
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 ...