You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing docs@inductiveautomation.com.
The Voice Notification module adds the ability to deliver alarm notifications to users via telephone, using any SIP compatible phone system (common for VOIP systems). Messages are constructed in text and are delivered through a high quality text-to-speech engine. The engine supports multiple voices and languages.
Video recorded using: Ignition 8.3
[00:00] (melodic sound) In this lesson, we'll demonstrate how to create a voice notification profile in Ignition, so that text-to-speech alarm notifications can be delivered to users via a SIP-compatible phone system. Messages are generated dynamically using text-to-speech, or TTS, with support for multiple languages and user acknowledgments. Just a quick note before we begin: if you're interested in using Twilio for voice notifications instead, we'll cover that in an upcoming video. First, let's talk about the prerequisites for this type of notification profile. The voice notification module allows us to create the profile, and that's dependent on the alarm notification module, so both modules will need to be installed on your Gateway. In addition, a specific voice module for your preferred language also needs to be installed. Below this video, we'll provide a link to a Knowledge Base article with download links that'll help you explore your options. Some voices and languages are only available with specific versions of Ignition. Finally, since the notification profile sends these voice messages over the telephone using SIP or VoIP, a compatible system will need to be set up. To create our profile, we can start by navigating to the Services section of the Gateway webpage.
[01:20] We'll find Alarming and select Notification. From here, we can click Create Profile. Let's select VoIP Voice Notification from the list and click Next. We'll begin with a name for the profile. Then we'll enter the VoIP Gateway settings, starting with the Gateway address, which is the SIP Gateway's IP address or domain name. Next, we need to provide the username or account, which is typically a phone system extension. Since no password is required for the demo, we can choose None. I'm not using a proxy, so it's okay to leave this field blank. We can then configure the call settings if we want to change any of the defaults. For example, we can specify a max call duration for any call before the system terminates it.
[02:04] We can also choose the amount of time the system will wait for the call to be answered before it moves on to the next contact. If we enable the use fair scheduling setting, the system would place only one call per notification job at a time. If it's left at its default setting of False, it'll attempt all calls for one notification job before moving on to the next. Here, we can adjust the voice rate to the desired playback speed. Under Auditing, this notification profile can also be linked to an audit profile. This allows call and acknowledgement events to be stored to the audit system. Expanding the advanced properties reveals several additional fields. The first is an authorization ID, which may be required by your service in addition to the user or account name. The others include the SIP and RTP ports, and both local and public bind addresses. If desired, call audio can also be recorded and stored in the Ignition temporary directory for debugging purposes by setting Media Debug Enabled to True. With that, I'll click the Create button at the bottom.
[03:06] Once it's registered, we've successfully created a voice notification profile.