# Voice Notification through VOiP host GS HT-813 Troubleshooting

**URL:** <https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [November 21, 2022, 4:13pm UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757 "2022-11-21T16:13:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniele1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/daniele1/32/31531_2.png) [@daniele1](https://forum.inductiveautomation.com/u/daniele1)\
**Post date:** [November 21, 2022, 4:13pm UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757/1 "2022-11-21T16:13:05Z")

</div>

Hi,  
I'm trying to set up a Voice Alarm Notification with a GrandStream HT-813 using the offical Ignition guide [here](https://support.inductiveautomation.com/hc/en-us/articles/360047175492-How-to-configure-the-Grandstream-HT-503-and-HT-813-for-use-with-Ignition-Alarming-voice-).  
After setting the HT-813, connecting it to the the telephone line on the FXO port and the LAN with my gateway I registered it on Ignition and using a test pipeline I tried to send a call but didn't succeded.  
At first I had the I/O error below regarding the network, so I turned off the firewall and and don't get that error anymore (btw what are the port that I have to open?).

 ![immagine](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/2/82bd2346b3190753f98a6f7efcc7ed105c686599.png)

Now I don't get any errors, the only logs are the ones below but I don't get any calls.

 ![immagine](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/e/7eb87cd2c96f6368afc504cfa4be2209f8a46a93.png)  
 ![immagine](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/d/9d83151da5bbd7d229c7a73486b1ae6987fc1124.png)

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [November 21, 2022, 8:24pm UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757/2 "2022-11-21T20:24:04Z")

</div>

While I don't have one of those devices, I'm pretty familiar with VoIP in general.  
What status does the web interface on the device show when trying to make a call?  
Have you enabled debugging level on the logger for "Alarming.Notification.Voice.CallManager.Agent" to get additional information?

For call setup, the module needs port 5060 (udp/tcp) and for audio, it needs port 8000 (udp) by default, but these can be configured in the advanced settings of the VoIP alarm notification profile.

---

<div class="post-metadata">

**Author:** ![daniele1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/daniele1/32/31531_2.png) [@daniele1](https://forum.inductiveautomation.com/u/daniele1)\
**Post date:** [November 22, 2022, 8:02am UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757/3 "2022-11-22T08:02:49Z")

</div>

Hi,  
thank you for your response.  
From the web interface of the device it seems like the device doesn't responde: I place a call with a test pipeline and the FXO port stays Idle

 ![immagine](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/1/c1a9d98e7895197c329f09b95df57623aa58281b.png)

I've activated trace level debug on Alarming.Notification.Voice.CallManager.Agent, I get this message

 ![Immagine 2022-11-22 085346](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f6f6c685b822759b0f159659961f86747d59d97e.png)

The IP of the of the VOiP device is 192.168.1.32 while my gateway address is 192.168.1.123 (I'm connected through LAN at the moment).  
I don't understand what is the 192.168.1.142 device you an see in the message, if I use and IP scanner it seems it's my still my gateway  
 ![immagine](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/3/13e3997e3d136f90cd4285943e2db8dfb37646f9.png)

---

<div class="post-metadata">

**Author:** ![daniele1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/daniele1/32/31531_2.png) [@daniele1](https://forum.inductiveautomation.com/u/daniele1)\
**Post date:** [November 22, 2022, 4:58pm UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757/4 "2022-11-22T16:58:30Z")

</div>

I've understood what the 192.168.1.142 was, it's my gateway IP under the wifi network.  
I put the gateway and the VOiP under a different subnet but the receiver IP is set still on 1.142, even after deleting and recreating the notification.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [November 22, 2022, 5:01pm UTC](https://forum.inductiveautomation.com/t/voice-notification-through-voip-host-gs-ht-813-troubleshooting/66757/5 "2022-11-22T17:01:41Z")

</div>

Under advanced options in the notification profile, you can set a bind address to the 192.168.1.123 address to force it to use that IP when connecting to the device.

You might also try using wireshark to do a packet capture as it has a VoIP analyzer in it to show the call flow and conversation between the 2 devices to help see what's getting stuck or what's breaking.
