Unity does not support msgs sent to its distribution list via AMIS. (as documented in the AMIS guide). Is there anyway to work around this? (my own workaround was setting up a Call Handler with its msg recipient configured to be the designated DL - Haven't tried it because I am not sure whether it is supported in this AMIS integration). The bad part in this case is: the customer's VM box is able to accept msgs coming in to its Octel distribution list via AMIS. So they are wondering why the same thing can't be done in Unity. <br><br>Systems Engineer
Inbound AMIS messages, by default, can only be delivered to a fully qualified Unity subscriber. Inbound searches will only look for subscriber type of 1 (i.e. no internet subscribers, no DLS, no non subscribers). The subscribers can live on any Unity server on the network but they need to be a subscriber end-point. Using a call handler as you suggest wont work. You cannot address a message to a handler only to a mail user.
That said, there IS a super-secret registry setting that will allow public DLs with Ids assigned to them to be targets for inbound AMIS messages. However, you dont want to use this. Its not supported, for one, and theres a reasonably good reason we turned this off by default:
When you send a message to a remote AMIS user you have to supply a local subscriber that can get an NDR and act as the sender information when delivering via the AMIS protocol. Most systems dont allow for anonymous messages from unknown users at remote locations.
AMIS messages that come directly to a distribution list present a problem here the distribution list can contain AMIS recipients on remote systems. So when we turn around to send those messages out to AMIS recipients we dont have a local recipient to act as the sender. Problem. As such youll get errors for all AMIS recipients that might have been in the DL.
If youre real careful not to add AMIS recipients to a DL that is setup for inbound delivery of AMIS messages you can get away with this but in generally Id go the easier route: You can deal with DLs reasonably easy by creating a dummy subscriber that forwards its messages to a DL. This dummy subscriber can act as the sender so even if the DL contains AMIS users youre cool. Just be careful to only forward messages that contain a voice attachment, AMIS doesnt like you sending emails, faxes, NDRs etc Also, be careful not to do something cool like setup looping messages (DLs on one box forwarding to a DL on another box that forward back to the orignal box... keep your ports real busy if you're not careful).
If youre feeling really oppressed by this limitation, ping me at my corporate and Ill give you the skinny on the registry setting thatll allow for DL addressing if you want to try it. Just be aware if something goes odd with the AMIS stuff, the first thing well have you do is turn that off.
Great. With that said, will I be able to setup a dummy Unity subscribers that accepts incoming AMIS message and THEN forward it to a DL WITHIN Unity? (I can get the other way working) I want to be able to allow people in the Octel box to send to a DL in Unity (and fool the system to do it without hassle). Client doesn't want to modify any registry settings to make it into an "unsupported" solution but yet still wants to have that functionality.
I can't seem to be able to forward a message to a DL within Unity under the Message page. Let me know if i can get by using Auto-EMail forwarding in Exchange.
you'll have to do the forwarding of the message itself for the subscriber in Exchange... we don't expose the functionality for that via the SA. You'd need to setup a dummy subscriber with the appropriate ID and then in Exchange administrator for that mailbox and forward all incoming mail to the public distribution list you desire.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...