# HT503 VOIP Disaster

**URL:** <https://forum.inductiveautomation.com/t/ht503-voip-disaster/17305>\
**Category:** Ignition\
**Created:** [March 9, 2018, 10:10pm UTC](https://forum.inductiveautomation.com/t/ht503-voip-disaster/17305 "2018-03-09T22:10:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jenkinsbradm](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jenkinsbradm](https://forum.inductiveautomation.com/u/jenkinsbradm)\
**Post date:** [March 9, 2018, 10:10pm UTC](https://forum.inductiveautomation.com/t/ht503-voip-disaster/17305/1 "2018-03-09T22:10:50Z")

</div>

I"m trying to work with a GRANDSTREAM HT503 to do some voip.  
I’ve followed a suggested setup, but I keep getting the FXO busy signal on the grandstream device.  
I don’t know what I’m missing. Any ideas?

---

<div class="post-metadata">

**Author:** ![David.Reed.Schmidt](https://avatars.discourse-cdn.com/v4/letter/d/5f9b8f/32.png) [@David.Reed.Schmidt](https://forum.inductiveautomation.com/u/David.Reed.Schmidt)\
**Post date:** [March 10, 2018, 4:28am UTC](https://forum.inductiveautomation.com/t/ht503-voip-disaster/17305/2 "2018-03-10T04:28:41Z")

</div>

There are a lot of links in the chain needed to get the HT503 running. Once I was trouble shooting a set up and I swear everything was set up correctly. I called the company administrator for the phone system who was able to access a log file on there end. The company phone system was configured to append the area code to the number the HT503 was dialing out resulting in two area codes because Ignition was also sending the area code as well. The HT503 is not going to tell you these sorts of things and you may need to branch out into troubleshooting in other systems.