“Can not use the domain as it was not configured for this tenant” when setting up SBC on Direct Routing (New-CsOnlinePSTNGateway )

By -

I had an issue on a customer site today when we were trying to add an SBC to use for Teams Direct Routing.

It brought back the error: “Can not use the domain as it was not configured for this tenant”


Strange, as this domain is a registered domain in the Tenant. 100%...

After some research though, I found that the domain is listed when we checked the Tenant settings:

Get-CsTenant | Select -ExpandProperty Domains

but missing DomainUrlMap:

Get-CsTenant | Select -ExpandProperty DomainUrlMap

Basically what we found was there was no user setup yet using this specific registered domain. There were a number of domains registered in the Tenancy however.

I simply registered a user in the Tenancy using this domain, we also assigned it an ECAL license and gave it 15 mins. I may not have had to assign the license but done no harm, removed once I finished the process. I re-ran the commands above and then seen the domain appear back in the DomainUrlMap. 

Now when we run the New-CsOnlinePstnGateway command we get a success.


Comments

  1. AnonymousDecember 5, 2022 at 5:40 AM

    The offers that appear on this table are from partnerships from which Investopedia receives compensation. This compensation 카지노사이트 could influence how and where listings appear. Investopedia doesn't embody all offers obtainable in the marketplace. Investopedia requires writers to use primary sources to assist their work.

    ReplyDelete

Post a Comment

Popular posts from this blog

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Communicator ports used for communication

By -
Image
We came across an issue with a segmented network with multiple VLANs separated by numerous firewalls. Each VLAN was considered a separate LAN. Rules must be opened on the firewalls to allow video and audio traffic to work inter-VLAN. By default ports 1024-65535 TCP/UDP are used which is pretty much all of them bar 1023 ports - this is a big hole. So instead we can limit the ports used from the client and then on the firewall just open up these ports - minimum 20 ports. Media Port Range This section describes the minimum media port allocation requirements for the client and server. The default UDP/TCP port range used by the Office Communicator 2007 client is 1024-65535. The Real Time Media Communications stack in Office Communicator 2007 allocates the media port dynamically in this range. In order to maintain an adequate level of performance, you can specify a smaller port range for Office Communications Server to use. To control the specific range of ports that need to be open on
Read more

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins
Read more