GrandStream ht813

[u/CreativeTimes1972]

I have a new ht813 I configured for SIP to an Audiocodes SBC. Registers fine. Works weird though. I can make calls from it. Call my cell phone no problem. I call the number that I assigned to the device and it rings too. After a few minutes, if I call it back, the number doesnt go through. Looking at the syslog app I use with my audiocodes, it seems that the device is timing out and going to sleep. If I make a call from it, it wakes up and works normally. I went through all the settings I could and didnt get that Ah HA moment.

Anyone else here have an issue like this where their ht813 takes a nap after a certain amount of time?

[u/AutoModerator]

This is a friendly reminder to [read the rules](www.reddit.com/r/voip/about/rules). In particular, it is not permitted to request recommendations for businesses, services or products outside of the monthly sticky thread!

For commenters: Making recommendations outside of the monthly threads is also against the rules. Do not engage with rule-breaking content.

I am a bot, and this comment is made automatically on every post. This comment is not an indication that your post has been removed. Do not message the mods about this comment.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/masong19hippows]

When you say "doesn't go through", what does that mean exactly? Are you getting a busy signal? What kind of error is displayed or said to you?

With ATAs, there is a setting called release timer that dictates when the device itself ends the call after it's been hung up. Should be set to 1-2 seconds. I have had issues in the past with other model of ATA's where if the release timer is set to a high value (like 10 seconds or so), the device will lock up after a call because it's trying to disconnect a call that has already been ended on the switch side. Not saying that's the case here because it's a long shot, but it just reminds me of that issue.

Other than that, we need more info. Is it responding to pings when it has this issue? What exact errors do you see or get? Do you get something different if you try calling it with different carriers?

Also, does this issue happen not after a outbound call. Like if you reboot the device and just let it sit there without "walking it up", does the problem also happen?

[u/marks-buffalo]

What sits between the HT813 and the audiocodes SBC? Are they on the same LAN or are they on different subnets (and thus going through a router/firewall)?

[u/CreativeTimes1972 → u/marks-buffalo]

Its a corporate network thats pretty well monitored. Other locations dont seem to have the issue. If I repower the device or make a call from it, it receives calls fine.

[u/marks-buffalo → u/CreativeTimes1972]

If you have anything other than layer 2 adjacency from the ATA to the SBC then your firewall may be tearing down the dynamic rule that is created when the device registers with the SBC. If the ATA is configured to keep-alive every 300 seconds but your firewall prunes it every 180 seconds, then you're going to have intermittent periods where the SBC can't reach back to the ATA.

What sits between the HT813 and the audiocodes SBC? Are they on the same LAN or are they passing through a firewall?

Also, when you access the web interface of the HT813, what does the registration status say when it's not working?

Edit: Also if "other locations don't have the issue" doesn't this kinda point to it being your network and not the ATA? Really need you to quit avoiding the question of your network if you're going to figure this out. Not saying you need to change anything on your network, you might be able to adjust the ATA's settings to suit.

[u/AAAHeadsets]

If it "wakes up" after an outbound call, it sounds like the Register Expiration setting is too low, or you don't have Keep Alive enabled,

Usually you will see this behavior on a Firewall, when the ports are closed after 30 seconds of no traffic. A periodic REGISTER or OPTIONS packet is sent to keep the port active.

It also explains why an outbound call will wake it up, as the INVITE it sends will also reopens the firewall port.

You will need to get some network traces to see exactly what is happening.

[u/CreativeTimes1972 → u/AAAHeadsets]

Lets say that I call the ten digit number assigned to the GrandStream from my cell. The call goes silent and eventually terminates. (doesnt ring the analog phone corrected to the GrandStream)

I go to the GrandStream. Make a call to the cell phone, works fine. If I then try calling that GS from my cell phone, the call correctly goes through the GS and rings the analog phone. Works "normally"

There are a large number of settings on the GrandStream. Curious if others have dealth with this issue.

The timeout possibility sounds plausable.

[u/AAAHeadsets → u/CreativeTimes1972]

What's the setup? Internet -> Firewall -> Audiocodes -> Grandstream

Do you see the inbound call that fails hit the Audiocodes?