I have three Unity systems in the same Domain. All Unity users are in the same AD. When I receive a message from a user on a different Unity system, I can't not reply to that user. Is this a limitation to Unity or is it a configuration issue?
Digital networking works for all the Unity systems. That is, I can compose and send a message from my mailbox to any other mailbox on any server. I can then do a reply to that message, that all works fine.
This is what I am trying to accomplish: When I call a Unity user, on a different server, from my desk phone, I leave a message. The user receives my message. In the message header, it states that the call was received from 716-XXX-XXXX, this is my phone number and it is also my mailbox number. However,the CLID in the header is my phone number. Should I be able to press "4" and reply to the message. When I press 4, Unity responds "you can not reply to this call". However, if I leave a message for someone on the same Unity server, reply works.
To Verify Identified Subscriber Messaging Between Networked Subscribers - Do this test if the Cisco Unity servers have been configured for identified subscriber messaging between networked subscribers.
Step 1 Verify that Cisco Unity plays an internal greeting for subscribers who leave messages, by doing the following sub-steps:
a. From a subscriber phone, call a subscriber associated with another Cisco Unity server, and allow the call to be forwarded to voice mail.
b. Verify that the internal greeting plays.
c. Leave a test message.
Step 2 Verify that subscribers are identified when the recipient listens to a message, by doing the following sub-steps:
a. Log on to the applicable Cisco Unity server as the recipient subscriber and listen to the test message you recorded in Step 1.
b. Verify that the subscriber conversation announces who the message is from by playing the recorded voice name of the sending subscriber.
c. After listening to the message, verify that the subscriber conversation allows you to reply to the message.
If you have a UM implementation, you should see the Display Name of the Unity subscriber on the other server that sent you the message in the Subject column of the voice message, i.e. Message from Kavan. Ginger. If you see instead the CLID as you mentioned of the phone number, then Unity is not recognizing the CLID information it is getting from your PBX as the extension of a subscriber. On your Unity server, make sure you have either Dialing Domain or Global Directory specified for your Primary Location's addressing option search as well as the check box "Include locations in search". Do this on each server. If that is set OK, you might consider using Alternate extensions and code the CLID information you see in the header as an alternate extension for a subscriber and repeat the tests.
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 ...