Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Text to speech pronounciation

We have "trianed" Orion to pronounce nodenames properly for alerts. When we test the alerts the nodenames are pronounced properly. But when a real alert is triggered, it does not pronounce the nodename correctly.

Any thoughts on why this does not work?

Thanks,

Rob Milman

Find more posts tagged with

Accepted answers

All comments

DonYonce

Good Question !

Depending of the speech engine you used (yes, Orion can use many different speech engines) you will need to copy the lexical dictionary from your user id to the "System" user ID. The reason for this is that when you configured the pronounciations, you were logged in with your user ID. When you tested the Alerts, you were logged in as your user ID, But... when Orion actually triggers the Alert it is running as the "System" user ID.

So... here's how to copy your pronounciation dictionary to the System user ID for the Microsoft Speech Engine (The Voice named "Sam").

Look in the following directory :
C:\Program Files\Common Files\Microsoft Shared\SpeechEngines\TTS\Lex

There will be a file with your user ID as the name and the extension of ".lex".
Copy this file to the name "System.lex"

By the way... this is a text file that you can edit with notepad.

RobMilman

Thanks Don,

That is what I thought was happening, I just wasn't sure where to begin looking.

Best Regards,

Rob Milman

PS: You don't know where I can find a Cylon voice do you? Just for fun of course!

Rob Milman