International calls disabled by administrator

Status
Not open for further replies.

djdanster

Joined
Aug 20, 2014
Messages
13
Reaction score
0
We're trying to call a company in the states (we're based in the UK) and it appears that all outbound US calls (only tried US) are blocked. we can call UK lines fines.

When calling we get a "call forbidden by administrator" however under Settings > Security > Allowed Country Codes tab, they are all enabled so in theory users should be allowed to phone the number.

The E164 settings are also configured.

There are no logs for the call in the Server Activity Log.

What is going wrong?
 
...and your outbound rules are configured properly? There should be 3CX logs unless the sets internal dialplan is set to block the call being sent to 3CX. The Verbose setting provides a lot more information.
 
leejor said:
...and your outbound rules are configured properly? There should be 3CX logs unless the sets internal dialplan is set to block the call being sent to 3CX. The Verbose setting provides a lot more information.

I changed the log settings so it's picking up more info now.

L:1.1[Extn] failed to reach Line:10001>>001602530000, reason Forbidden

That number is when phoning Google CS
 
djdanster said:
When calling we get a "call forbidden by administrator" however under Settings > Security > Allowed Country Codes tab, they are all enabled so in theory users should be allowed to phone the number.

Was this blocked at one time and then unblocked recently, perhaps requiring a system re-start to take affect?

Have you tried calls from more than one extension? You don't have the outbound rules set to apply to a certain extension range, do you?

Did this just start recently?
 
leejor said:
djdanster said:
When calling we get a "call forbidden by administrator" however under Settings > Security > Allowed Country Codes tab, they are all enabled so in theory users should be allowed to phone the number.

Was this blocked at one time and then unblocked recently, perhaps requiring a system re-start to take affect?

Have you tried calls from more than one extension? You don't have the outbound rules set to apply to a certain extension range, do you?

Did this just start recently?


I have restarted the service, so I that would have updated anything that was stopping it. Still having the issue though.


tried from my extension and the user who is also having the issue.

Outbound rules are set to apply to extension 100-900 (only have around 30) so that would cover everybody. However as I stated in the OP, there are no restrictions that I know of for international calls.
 
djdanster said:
Outbound rules are set to apply to extension 100-900 (only have around 30) so that would cover everybody.

Given the wide range of extension numbers that the outbound rules apply to, I'm surprised that you didn't just leave that blank and let them apply to all.

Off-hand I can't think of anywhere else that would only block calls to certain regions, although, it has been a while since I waded through the security settings/restrictions.

Did this, (calls to North American numbers) work for you at one time?
 
leejor said:
djdanster said:
Outbound rules are set to apply to extension 100-900 (only have around 30) so that would cover everybody.

Given the wide range of extension numbers that the outbound rules apply to, I'm surprised that you didn't just leave that blank and let them apply to all.

Off-hand I can't think of anywhere else that would only block calls to certain regions, although, it has been a while since I waded through the security settings/restrictions.

Did this, (calls to North American numbers) work for you at one time?

So I changed it to blank but still same situation.

Yep calls to US have worked and still do for some phones. I've got 3 extensions that I can confirm work with the US number, however mine and others still do not.
 
Starting to think it's related to the phones themselves as when I change my subscriber credentials on my Cisco SPA5045G phone to a colleagues that can call US numbers it still doesn't work.
 
Update: the message given does seem to be consistent with a 3cx error.
 
Hi,

Check your outbound rules, and the order in which they are placed in the table.
The PBX processes the rules based on a 1st matching, not a best matching rule.

So if you have calls to 00 being blocked and after that a 001 being allowed, you will not be allowed to make calls to US.
 
3CXNP said:
Hi,

Check your outbound rules, and the order in which they are placed in the table.
The PBX processes the rules based on a 1st matching, not a best matching rule.

So if you have calls to 00 being blocked and after that a 001 being allowed, you will not be allowed to make calls to US.

I think our outbound rules are pretty relaxed.

GrOOd6c.png


1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50

Above is what is in the "Calls to Numbers with a length of" box.
 
Try creating a rule just for North American numbers. I don't know if you use any prefix digits, this example assumes not.

Numbers starting with prefix 001

length of 13

Route out to trunk group, strip 0 digits

As mentioned, put this above your general rule.
 
leejor said:
Try creating a rule just for North American numbers. I don't know if you use any prefix digits, this example assumes not.

Numbers starting with prefix 001

length of 13

Route out to trunk group, strip 0 digits

As mentioned, put this above your general rule.


39weUlR.png


These are the settings I've used. Still blocking me though :(
 
the only thing that i can think of is that it is something to do with your e164 settings. I attempted to uncheck (disallow) some regions in the settings, but because I have not set-up anything in e164 (have not had to up to this point), it prevents any changes.
You might try (just on a temporary basis for testing, after hours) remove all of the settings you have in e164, returning it to the default. See if that makes a difference, if it does, then add the settings back one at a time, doing a test after each change until it starts to fail again.
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,834
Messages
589,287
Members
164,663
Latest member
svdDGS