As it says in the Subject, is this possible in Unity? Can a subscriber have 2 extensions (2 lines in Call Manager, 1 IP Phone) but have a common voice mailbox?<br><br>Otherwise, things really get split up. E.g. if we have 2 lines, "111" and "222", we'd have to dial into Unity as "111" to get "111" messages and as "222" to get "222" messages.<br><br>Thanks,<br>Loong<br><br>
I have 2 lines, 1111 and 9999. 9999 was added after 1111 was created, so on Unity, there is a subsriber named "Loong" with the extension 1111. All calls that come to this line drop to my voice mail box.
If I add 9999 to my alternate extensions for subscriber "Loong", I can call Unity with 9999 and I will access 1111 voice mail box.
In call manager, for the 9999 line, I set Forward No Answer and Forward Busy to Unity. If I call 9999, and it is busy/there is no answer, should it go to my 1111 voice mail box?
Yes, you are correct. It should forward to the subscriber's box that has the primary DTMF ID of 1111. If it's not, you are probably running into CSCdw06277.
This should be fixed in 3.0.4 and 3.1.2. What version of Unity are you running? The release notes of this defect mention that there is no workaround for this, but there really is. The easiest way to do work around it is to create a forwarding call routing rule that says when the forwarding ID is 9999, send the call to the greeting of 1111. There's also extension remapping. If you have a lot of dual extensions like this, extension remapping is probably the better way to go. If you only have a few of these dual extensions, then routing rules will do the trick.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.