Solved Outbound call rules

[phil_]

Hi, I am able to make outgoing call to numbers starting 01 but I can not manage to make calls to numbers starting 07.

 

[leejor]

Have you created any outbound rules? Could your provider be blocking "premium" calls. This is assuming you are in the UK, and attempting to call a mobile number, which may be a higher rate than a landline.

 

[phil_]

I have created an outbound rule but I am not sure what I am missing?

 

[leejor]

So, with the outbound rule, do calls to 01 numbers and 07 numbers work? What about calls to numbers like 02, or something else? When a call fails, what do you get, a recording, busy signal?

If your version allows access to the Activity Log, then that will show you what rule is used, and where the calls are routing, if they are being sent to your provider. You may have to set to Verbose mode to show any details.

 

[TheodorosG_3CX]

You have added a restriction for 11 digits length, removing this restriction allow you to make the call?

 

[phil_]

Thanks for the help all my outgoing calls are working now.

I'm also having issues answering incoming where when I try to answer the call from any of the extensions it hangs up and on the recipients end says line busy even though I have answered the call.

 

[leejor]

It might be that some of the required ports are not open. Have you successfully run the Firewall checker?

 

[phil_]

I'm running 3CX SMB Free 10 in the cloud and can't see the option for the firewall checker.

 

[leejor]

Probably not a port problem then. Could be a Codec issue, if you have put in any restrictions on which ones the sets can use.
This is where the Activity Log comes in handy, but, unfortunately, it is not available on some of the versions.
Are you able to call extension to extension with no issue? What about an unanswered call that goes off to voicemail, does that complete properly?

 

[phil_]

Calls between extensions work with no issues.

Calls aren't going to voicemail either.
even trying to answer calls through the 3CX app on the recipients side it just comes as line busy.
In my call log it keeps showing that I have terminated the call

 

[TheodorosG_3CX]

Are you using the Web Client?

 

[phil_]

Yes I have been using it for all setup

 

[TheodorosG_3CX]

Are notifications allowed on your browser?

 

[phil_]

I have two Yealink T54Ws and one mobile connected through the 3CX app for calls.
they receive the call but when I go to answer the call it hangs up and on the recipients end says line busy.
I have tried answering calls through the web client but the same thing happens.

 

[leejor]

Which provider are you using?

 

[phil_]

I'm using VoiceHost

 

[leejor]

Did you make any changes to the 3CX default settings for his provider?

https://www.3cx.com/docs/sip-trunk/voicehost-uk/

I'm going to assume that when a call is answered, an unacceptable reply is received by the provider, then the call is dropped. Without being able to see the 3CX Activity log, or using something like Wireshark, or getting your provider to help troubleshoot, it is all a guess at this point.

 

[phil_]

I have called Voicehost but they said to contact 3CX since everything on Voicehost's side is working.
I have not made any changes to the default settings.
I have downloaded Wireshark.
When I answer the call on the Yealink T54W or the 3CX app it just hangs up with no message but on the recipients side it says line busy.
Looking on the call record for Voicehost it doesn't show that an incoming call was attempted but on the 3CX call log it does show an incoming call was attempted and says it got terminated.

 

[TheodorosG_3CX]

Line is busy in not generated from 3CX.
You mentioned also that "everything on Voicehost's side is working" meaning that they do not have an outage or your account is tested and is working properly?

 

[phil_]

Voicehost do not have an outage and everything from Voicehost's side is working properly with my account. I'm just having issues answering calls through 3CX