This is not directly documented but the bug filed has a work around which implies support of SpeechView and CUC, but not the SMTP relay components involved. There are too many SMTP variations for TAC to support, but, all of the ones I have worked with so far work: Ironport, IIS SMTP Server and Symantec Brightmail. Most networks should have an internal SMTP relay for all sorts of notifications from systems out to the internet. You know the ones that blow you up when something's busted. However, external relays can be tricky with all the nefarious SMTP scammers, spammers and bots. If you have a mail filter (ex. Ironport) or external system (ex. Brightmail) then this should be pretty easy as those flows are in place now and only DNS needs to be updated. Cisco was happy to help read the logs and point out issues that we had to fix along the way. Some notes on the differences.
- Follow the guide and ditch the Exchange part. It's mostly about tricking Exchange into doing your SMTP relay bidding.
- Create a "CUC" subdomain for the mail routing, requires MX record. Ex. cuc.anydomain.com
- The CUC email address can be stt-service@cuc.anydomain.com since you are not tricking Exchange into forwarding.
- Secure the CUC with an SMTP access list and the same with your SMTP server. Don't want to be a relay for the internet. Whitelist the domain ciscostt.nuancevm.com.
- If you have an external relay inbound, you won't need to add firewall rules. Your External DNS MX should resolve to the external service that will say all messages to either cuc.anydomain.com or more specifically stt-service@ from cisco-xx-errors@ciscostt.nuancevm.com.
- Brightmail required a fix to the subject line that removed the original the “encrypted attachment”.
