How to Fix Outbound Call Problems with Grandstream HT813 and FreePBX?

Hello,

I have set up an internal extension system using a Grandstream HT813 and RasPBX (FreePBX). The office’s analog telephone line is connected to the FXO port of the HT813. The system is functioning well—internal extensions work flawlessly, and incoming calls are successfully received on mobile apps like Zoiper and PortSIP installed on the users’ phones.

However, I’m encountering an issue when making outbound calls from these apps (Zoiper, PortSIP, etc.). When dialing an external number through the Outbound Routes following the configured dial pattern, I hear a continuous tone, similar to the one heard when picking up a traditional analog phone (a dial-tone). At this point, I need to open the app’s dial pad and manually input the number again to successfully connect the call.

As far as I understand, the HT813 is supposed to automatically transmit the dialed number to the external line without requiring manual input.

To troubleshoot, I have adjusted the “Wait for Dial-Tone” and “Stage Method” settings under the Channel Dialing section of the HT813 in various combinations, but the issue persists.

Could you suggest any steps or settings I might try to resolve this problem?

Thank you in advance for your guidance!

See Make outgoing calls by eliminating two-step dialing - #3 by Stewart1 If no luck, turn on pjsip logger, make a test call to a number you don’t have to redact such as a local McDonald’s, paste the Asterisk log for the call at pastebin.com and post the link here.

1 Like

@Stewart1, Thank you so much for your quick response! I truly appreciate your help.

Out of the five suggestions you provided, I’ve already tried all except for number 2.

  1. On the FXO page, Stage Method should be 1
  2. Set Dial Plan to { [*x]+ }
  3. Set DTMF Digit Length and DTMF Dial Pause to 100
  4. Set Wait for Dial Tone to No.
  5. Set Min Delay Before Dial PSTN Number to 1000

Currently, my Dial Plan on the HT813 is set as:
{ x+ | \+x+ | *x+ | *xx*x+ }

Could you please clarify the purpose of changing it to { [*x]+ }? Is it to make the pattern more inclusive or generalized?

Thanks again for your support!

I suggested something simple that matches numbers mentioned by the OP of that thread. You don’t have to change your dialplan. Just paste a log and we’ll go from there.

2 Likes

Thank you for the clarification.
I enabled logging and made a test call as suggested. Here are some notable logs that stood out:

[2024-12-20 04:58:47] ERROR[26131]: res_pjsip_header_funcs.c:410 remove_header: No headers had been previously added to this session.  
[2024-12-20 04:58:49] WARNING[26131]: res_pjsip_pubsub.c:3345 pubsub_on_rx_publish_request: No registered publish handler for event presence from 101  

Do you think these logs are related to the issue, or should I look for something else? Let me know if you need additional details.

Thank you again for your guidance.

No, just paste the whole log for the call (with pjsip logger on).

1 Like

Ah, my apologies for the confusion earlier.

This might be the full log.
I’ve uploaded it to Pastebin for your review:

Log: Pastebin.com - Locked Paste
Password: icYddEpnk2

The first is not a real error, in FreePBX.

The second just means a capability the phone is requesting doesn’t exist, but shouldn’t affect calls.

1 Like

First of all, thank you for your reply.
So, you’re saying those two logs aren’t really related to my current issue, right?

Your paste shows that the called number is missing from the INVITE sent to the HT. But we can’t see why, because you pasted console output, not the Asterisk log, which can be found in /var/log/asterisk/full .
Paste the section created by your test call. Leave the paste expiration at the default (never) so future visitors to the thread can follow along.

Also, post screenshots of your trunk and Outbound Route, including the advanced and pattern tabs.

Just guessing, if you have Outbound Proxy set for the HT trunk, try removing it (set it blank).

@Stewart1
I have attached a screenshot of the relevant settings.

FreePBX IP: 192.168.1.20
HT813 IP: 192.168.1.160








@Stewart1
Can you see the last screenshot?

The Outbound Route is a problem, though I don’t know whether it is the only problem.
As a test, in the route To-HT813, remove the prefix (leave it blank) and put
X.
(X followed by a dot) in the match pattern.
Dial a number in the same format as you would on an analog phone connected to the PSTN line.
If the call fails, paste the Asterisk log (not the console output), including pjsip logger.

If the call succeeds, tell us how you want the patterns to work. Give an example of what you would dial and what should be sent on the PSTN line.

2 Likes

WHHHAATTT! I can’t believe it WORKED!

Your suggestion was absolutely worked.

As a test, in the route To-HT813, remove the prefix (leave it blank) and put
X.
(X followed by a dot) in the match pattern.

This was the key to resolving the issue!

I can’t thank you enough for your incredible guidance. You’ve truly saved the day!

I do have two of follow-up questions:

  1. I’d like to allow external calls only for the following phone number formats:

    • XX-XXXX-XXXX
    • XX-XXX-XXXX
    • XXX-XXX-XXXX
    • XXXX-XXXX-XXXX
    • XXXX-XXXX

    How should I configure this without causing the same kind of errors I encountered before?

  2. Is there a way to speed up the dialing process on the HT813? Currently, I have to wait 5–7 seconds after dialing before the call connects.

Thank you once again for your amazing support! I can’t express how grateful I am!

1 Like

I also wanted to mention another minor issue.

In the FreePBX CDR Reports, calls are marked as “ANSWERED” even though they haven’t actually been picked up yet.

Is this also a solvable issue?
I’m sorry for asking too many questions.

I’m following this topic too.
@Stewart1, yes, it also works for me with the dialplan set this way " X." :wink:
As @jungeon mentioned, I also have to wait about 10 seconds before the outgoing call is actually initiated, but only on the analog line (FXS) connected to the HT813. I don’t have this problem with VoIP phones.
I tried reducing the numbers as you suggested in my other topic, but it seems they have no effect. I wonder if this is normal.

For me it is no big deal, just a curiosity, but perhaps for others the wait might be problematic.

Sorry, I stand corrected, even for my VoIPs the wait is several seconds, between all the steps, although a little faster than FXS.

My logic is that it is usually 3 seconds per call. In this case, 2 calls are made, one to the gateway and the other to the outgoing number.
Maybe that’s why it comes to 6/7 seconds.
But that’s my guess. I don’t know if there is a way to adjust these times.

1 Like

@casabenedetti That’s correct, even for me, VoIP has almost no delay, but for outgoing via FXO port, it takes 5-7 seconds.

But I’m glad that the call through the FXO port is normal :grinning:

1 Like

I found benefits by setting (HT813/FXS):

No Key Entry Timeout: 1

3 seconds less than before :wink: :blush:.