I have site A & Site B. Subscriber in Site A should be able to address a message to subscriber in Site B. There is no directory replication.<br>What should be done ?<br><br><br>Create non-default location obj for remote site ?<br>Blind addressing ?<br>Install IMS ?<br>Use extention address utility ?<br><br><br>
some or all of the above... you have a couple options here:
You can create internet subscribers that correspond to each user in the remote site on each box. If you have a small directory this is kind of nice since users can address by ID or by name and get voice name confirmation and some other flexible things. Outside callers, for instance, can't destinguish the difference between an internet subscriber (which is home on the remote Unity server) and subscribers (homed on the local Unity server). Handy for audio text type applications.
The other option is to create a non primary location object (refered to as a delivery location object in 3.x) that points to the remote Unity server, give it an ID and allow users to address to remote users via blind addressing. This must be done by ID only, of course. You'd address using . So if the non primary location object had an ID of 111 and the remote user at that location had an extension of 2345 you'd address to them from your local Unity server by 1112345. The down side is you get no voice name confirmation, of course, and you must address by ID.
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: email@example.com 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 ...