I have an AMIS account created in Unity (say extension 5210 on both Unity and Remote system). From the remote system of this same 5210 account, I sent a message to a real Unity account (say extension 6220 in Unity). Will Unity be able to pick up the sender's inforamtion and announce the name of this AMIS account for the recepient of this message? I tried but it would always announced - "Network ID xxx, extension 5210" instead of the name of this account.
AMIS doesn't have any provision for sending user data back and forth between systems (i.e. like VPIM or OctelNet protocols do). As such if you don't have an AMIS subscriber with a voice name recorded on it you wont get voice name confirmation when addressing to that ID.
The Cisco Unity Bridge offers this type of functionality with OctelNet (i.e. the first time you message a user "blindly" we get information back about that account including their voice name and we create a local contact with that data so the next time you address to that user you get name confirmation).
If you have created an AMIS subscriber in Unity for the remote user, and have recorded a voice name for the AMIS subscriber (you can record the voice name in the Unity SA), then when a Unity subscriber gets a message from that remote AMIS subscriber, over the TUI, the message is announced as from " at location
Also, not related to spoken name but similar behavior, in Outlook, the From field will display as "" rather than _
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 ...