While dialing from Teams, Getting errorYou are not allowed to dial-out to this destination. Please contact your administrator

Aditya Tripathi 75

Hi,

Thanks for the help in advance.

I am trying to dial from Teams and I am unable to place the call. Error as screenshot below.

User's image

I have already checked the configuration. User is assigned with Global Policies for all the policies. Private calling is allowed. Dial to any destination from Audio Conferencing setting is already there. I am using Domestic calling plan for US location.

Please advise. Thanks!!

JimmyYang-MSFT 48,551 Reputation points Microsoft Vendor

2023-02-02T07:24:31.7866667+00:00

Hi @Aditya Tripathi

Do you have any operations before this issue occurred?

Which countries did you call?

Licensed users can call out to numbers located in the country/region where their Microsoft 365 license is assigned to the user based on the user's location. So we recommend you check if the destination country is in the support list. You could check it from:

https://learn.microsoft.com/en-us/microsoftteams/country-and-region-availability-for-audio-conferencing-and-calling-plans/users-can-make-outbound-calls-to-these-countries-and-regions
Aditya Tripathi 75 Reputation points

2023-02-13T10:11:35.5133333+00:00

Hi

I am dialling within US and user is assigned to the US Location only. Calling plan is also not working. Getting an error when checked the diag log "Get outbound direct routing, no trunk config found by LBR Selection criteria". But I do not have any direct routing setup and Also I am using Global Voice Routing policy with default settings.

Wondering whats going on. I have tried my best from location to policies.
JimmyYang-MSFT 48,551 Reputation points Microsoft Vendor

2023-02-13T10:19:47.96+00:00

Please make sure you meet these key considerations before making outbound calls in MS Teams:

https://support.nhs.net/knowledge-base/using-microsoft-teams-for-outbound-telephone-calls/
Rohit Mahajan 0 Reputation points

2023-04-03T07:14:51.94+00:00

We have a very simple setup for Microsoft Teams direct routing. Everything is working fine with incoming and outgoing calls.

We are facing problems after implementing LBR. I am stating a problem as it is with respect to the setup we have.

We have users who are sitting in the office , using team applications on their PCs and were able to make and receive calls.

Now we have implemented LBR to restrict these users to make calls when they are not connected to the office network or restrict when they are trying to make calls from any network except the office.

Now in the office the private network is 192.168/168.0/24 and public IP is X.X.X.X/27.

I have defined the private subnet in the network topology subnet And public IP's in the trusted IPs list.. So , ideally the call should work when users are trying from the office network. But the problem is calls are not working even from the office network which should be allowed as per the LBR.

Users are getting error : calls failing with Get Outbound Direct routing - no trunk config found by LBR selection criteria.
CurtisParker-6802 5 Reputation points

2023-08-28T14:36:33.1266667+00:00

We saw this message "Your admin does not allow phone calls from this location." also while doing a proof-of-concept of Teams Phone. This error is only a symptom of the underlying problem. For us, the problem started with call queues. We setup a call queue for one office and it worked great when we tested it at our desks. But when we had the end-users try it, we found that when a call came in, they would not get the pop-up notification of the call. Some users would see it for a second then it would go away.

Eventually, I found under network topology that we had only added our IT network and the WiFi network. I found that if the computer was on WiFi or the IT subnet, it worked, on any other network, it failed. So I added all the rest of our internal networks in this campus to the network site (we only have one) under network topology and that seemed to resolve the problem. Except that it still didn't work when someone was working from home. My Microsoft Technology Specialists (helping us with the proof-of-concept) said that shouldn't have solved the problem. They said the network site is related to the emergency policy, not general calling. So we went hunting for some other setting that didn't look right.

We found the culprit under the Global calling policy. "Prevent toll bypass and send calls through the PSTN". It was on. It needs to be off. We turned it off and Bob's your Uncle! Now it works for remote users as well. So apparently, I didn't need to add all our internal networks in the network site. This setting would have solved both the call queue issue and error, "Your admin does not allow phone calls from this location."

4 answers

Rohit Mahajan 0 Reputation points

2023-04-01T11:48:27.6233333+00:00

I am facing the exact same issue, Could you please help sharing the workaround to fix this issue ?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Rob Fuller 1 Reputation point

2023-06-09T13:50:19.0566667+00:00

Facing a very similar issue all users unable to make calls after purchasing some Microsoft Calling Plans.

The only clue thus far is from the logs in the Teams Client

errorMessage: https://: line 1: [Report Only] Refused to load the script 'https://' because it violates the following Content Security Policy directive: "script-src 'nonce-W1sMzB6E61PxVbn7Hb968Q==' <-- The reason for the call being denied stating it violates a Content Security Policy directive

Not sure what Content Security Policy it could be, this effect devices on and off our network.
Please sign in to rate this answer.
Jarno Lernou 0 Reputation points

2023-07-12T11:18:39.4966667+00:00

Hi Rob, were you able to fix the above issue? I'm encountering something similar.
Sign in to comment
Rob Fuller 1 Reputation point

2023-07-12T13:44:45.9633333+00:00

Yes I did. Microsoft support had given up and wanted to charge to fix the issue so we started going through everything. We noticed a messaging policy had an orphaned group assigned which it couldn't resolve. The policy didn't have anything special that would stop voice so we decided to remove it anyway and bingo users could make calls. My gut feeling is when a call is make it checks various policies and as this one couldn't match a group it just failed by default. So worth looking at t all your policy and double check everything is assigned as it should and user(s) are not getting policies not intended for them.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
E. Lynette Stone 0 Reputation points

2023-10-14T16:55:50.23+00:00

Same issue. Microsoft support gave up on us as well after trying for about 30 mins to figure out a way of accusing us of not paying for the service. Under "Calling Policies" there are options "allow calling" and "disallow calling". Add each users who is allowed to dial out for calling to "allow calling".
Please sign in to rate this answer.

0 comments No comments
Sign in to comment