Teams Direct Routing with Ribbon 8k - WebGUI is not loading

Note: I start using Substack for my articles please please follow at https://kloudnews.substack.com/

Recently got an alert due to connectivity of the Ribbon 8k (strange) with OS 24.0, nothing wrong with networking. However, SolarWinds shows a failure.  

End up checking the SBC via GUI and got following 502 Bad gateway,

SBC is running but no idea why GUI failing, in this situation very limited things can do. Started with Putty and connected via console. 

Following are the command to find the status of the SBC VMs status 

Sudo -i 

Virsh list - Will help me to understand status of the SBCSWeEdge 

Podman ps - Will help me to understand status of the OS, dockers/container status

sys-tools debug - Will help me to run debug via CLI 

Anyway above cmds not helping to resolve the problems, but i end up running a reboot middle of a day :( 

systemctl reboot

This was help to bring back GUI after few minute time. While this is happening all the calls routed via DRaaS. We are using Call Tower as vendor still provide DRaaS even though NEW customer required to go with Operator Connect for Teams. 

Additional info

I have checked the debug logs (Ribbon 8K) couldnt found any storage issues.

Filesystem               1K-blocks    Used Available Use% Mounted on

devtmpfs                      4096       0      4096   0% /dev

tmpfs                      8172244    4944   8167300   1% /dev/shm

tmpfs                      3268900    9896   3259004   1% /run

efivarfs                       128      43        81  35% /sys/firmware/efi/efivars

/dev/mapper/vg00-root     36798464 6819696  29978768  19% /

/dev/sda4                   983040  279988    703052  29% /boot

/dev/sda3                   613160    7220    605940   2% /boot/efi

/dev/sda1                  8993268 6738272   1776568  80% /e8k-data

/dev/loop0                 3378444 3378444         0 100% /LocalRepos

/dev/mapper/vg00-storage   5054464   68300   4986164   2% /storage

/dev/mapper/vg00-var       2031616  851120   1180496  42% /var

/dev/mapper/vg00-var_log   2031616 1420064    611552  70% /var/log

/dev/mapper/vg00-var_tmp    983040   40116    942924   5% /var/tmp

/dev/mapper/vg00-tmp       2031616   47332   1984284   3% /tmp

If you like to learn more about Microsoft 365 world, Copilot Security, Ribbons, Microsoft Teams Direct Routing, Operator Connect or Calling plan or legacy voice product integration - https://kloudnews.substack.com/ 

Enterprise Guide to Unassigned Number Routing in Microsoft Teams

Note: I start using Substack for my articles please please follow at Madushka Dias writes | Kloud | Substack

Teams Voice Configure routing options for unassigned phone numbers 

Deprovisioned users still receiving calls 

Legacy telephony world this feature it called many words - Catch-all routing, Default destination routing, Vacant Number routing etc. This feature was introduced beginning of 2025 to most of the Tenants by Microsoft. This will fix lot of lost calls to route back to Voice application (Auto Attendant), Greeting or Person in Organization.

Every organization today at least maintain a room of 10-20% DIDs for future, if it is multinational, it will be every country and region sometimes.

Unassign Number routing in Teams will takecare all the unused, unassigned DID will provide meaning full option instead of unrouteable call.

Understanding media flow 

Following diagram AI created for me, first of did by #ClaudeAI and second did by #Copilot

Following diagram build by #Copilot

Following diagram build by ClaudeAI

  

PowerShell and Teams Admin Center

PowerShell Script you can find below copy or Github Teams_unassigned_number_template.html also made a HTML GUI, if organization do lot of expansion this will help every time when you add unassigned number range to TAC.

# --- DE BER Reception AA ---

$RAOId = (Get-CsOnlineApplicationInstance -Identity SL-BER-Reception-AA@kloudnews-uc.onmicrosoft.com).ObjectId

New-CsTeamsUnassignedNumberTreatment -Identity “DE BER Reception AA” -Pattern “\+4930(XXXXXX[0-9])$” -TargetType ResourceAccount -Target $RAOId -TreatmentPriority 1

# --- FR PAR Reception AA ---

$RAOId = (Get-CsOnlineApplicationInstance -Identity SL-PAR-Reception-AA@kloudnews-uc.onmicrosoft.com).ObjectId

New-CsTeamsUnassignedNumberTreatment -Identity “FR PAR Reception AA” -Pattern “\+331(XXXXXX[0-9])$” -TargetType ResourceAccount -Target $RAOId -TreatmentPriority 2

# --- IT ROM Reception AA ---

$RAOId = (Get-CsOnlineApplicationInstance -Identity SL-ROM-Reception-AA@kloudnews-uc.onmicrosoft.com).ObjectId

New-CsTeamsUnassignedNumberTreatment -Identity “IT ROM Reception AA” -Pattern “\+3906(XXXXXX[0-9])$” -TargetType ResourceAccount -Target $RAOId -TreatmentPriority 3

# --- ES MAD Reception AA ---

$RAOId = (Get-CsOnlineApplicationInstance -Identity SL-MAD-Reception-AA@kloudnews-uc.onmicrosoft.com).ObjectId

New-CsTeamsUnassignedNumberTreatment -Identity “ES MAD Reception AA” -Pattern “\+3491(XXX XXX[0-9])$” -TargetType ResourceAccount -Target $RAOId -TreatmentPriority 4

# --- NL AMS Reception AA ---

$RAOId = (Get-CsOnlineApplicationInstance -Identity SL-AMS-Reception-AA@kloudnews-uc.onmicrosoft.com).ObjectId

New-CsTeamsUnassignedNumberTreatment -Identity “NL AMS Reception AA” -Pattern “\+3120(XXXXXX[0-9])$” -TargetType ResourceAccount -Target $RAOId -TreatmentPriority 5

At our customer environments, we work extensively with Microsoft Teams Direct Routing and Operator Connect. While Microsoft Teams handles unassigned number routing at the tenant level, SBC platforms such as Ribbon SBC 1000, 2000, and 8000 enable a range of advanced capabilities that are not natively supported within Microsoft Teams.

Microsoft Article - Configure routing options for unassigned phone numbers - Microsoft Teams | Microsoft Learn 

Teams SIP Phone BulkSignIn powershell cmd is not working "Set-CsTeamsSipDevicesConfiguration -BulkSignIn"

I found something missing when we try this following command, thought something to do with PS module, or missing some update etc.  

Set-CsTeamsSipDevicesConfiguration -BulkSignIn "Enable" 

as you know this cmd enable the organization-wide Teams SIP devices configuration which contains settings that are applicable to SIP devices connected to Teams using Teams Sip Gateway.

It is being modify but article not been update by Microsoft yet. Following cmd will fix your problem. 

Set-CsTeamsSipDevicesConfiguration -Identity "Global" -BulkSignIn "Enabled"

Required to update
https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamssipdevicesconfiguration?view=teams-ps 

Teams Direct Routing with Ribbon 8k - How to reboot using CLI / WebGUI is not loading

Recently got an alert due to connectivity of the Ribbon 8k (strange), nothing wrong with networking. However, SolarWinds shows a failure.  

End up checking the SBC via GUI and got following 502 Bad gateway,

SBC is running but no idea why GUI failing, in this situation very limited things can do. Started with Putty and connected via console. 

Following are the command to find the status of the SBC VMs status 

Sudo -i 

Virsh list - Will help me to understand status of the SBCSWeEdge 

Podman ps - Will help me to understand status of the OS, dockers/container status

sys-tools debug - Will help me to run debug via CLI 

Anyway above cmds not helping to resolve the problems, but i end up running a reboot middle of a day :( 

systemctl reboot

This was help to bring back GUI after few minute time. While this is happening all the calls routed via DRaaS. We are using Call Tower as vendor still provide DRaaS even though NEW customer required to go with Operator Connect for Teams. 

Additional info

I have checked the debug logs (Ribbon 8K) couldnt found any storage issues.

Filesystem               1K-blocks    Used Available Use% Mounted on

devtmpfs                      4096       0      4096   0% /dev

tmpfs                      8172244    4944   8167300   1% /dev/shm

tmpfs                      3268900    9896   3259004   1% /run

efivarfs                       128      43        81  35% /sys/firmware/efi/efivars

/dev/mapper/vg00-root     36798464 6819696  29978768  19% /

/dev/sda4                   983040  279988    703052  29% /boot

/dev/sda3                   613160    7220    605940   2% /boot/efi

/dev/sda1                  8993268 6738272   1776568  80% /e8k-data

/dev/loop0                 3378444 3378444         0 100% /LocalRepos

/dev/mapper/vg00-storage   5054464   68300   4986164   2% /storage

/dev/mapper/vg00-var       2031616  851120   1180496  42% /var

/dev/mapper/vg00-var_log   2031616 1420064    611552  70% /var/log

/dev/mapper/vg00-var_tmp    983040   40116    942924   5% /var/tmp

/dev/mapper/vg00-tmp       2031616   47332   1984284   3% /tmp

‎Teams administrator permission doesn't allow to create/modify resource accounts anymore! - MC780743 (Updated) Changes to Administrator Permissions Required to Create and Manage Teams Resource Accounts

This started with MC780743 change and following will explain as a summary,

Summary

The message details an update on the rollout timeline for changes to Teams administrator permissions required for creating and managing Teams Phone Resource Accounts. The change, rolling out in December 2024, will require Microsoft 365 Global Admin or User Admin roles for these tasks, affecting Teams Administrator, Teams Communications Administrator, and Teams Telephony Administrator roles. Organizations should prepare by adjusting processes accordingly.

However this was pushed to some of my client tenant recently or many notice recently :). 

Issue

Before change people able to create Resource Accounts without having User Administrator Roles in Tenant and also able to modify those accounts. After MC780743 change, everyone required to have User Administrator Role and i had that attached to my admin account too. However, even after Teams administrator and User administrator both active i couldn't modify the resource accounts and It was giving following error. Basically i created the Resource accounts in bulk and assigned AA or CQ later.

Microsoft article - Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn

Solution

Surprise :D This was not documented by Microsoft article but randomly found old Skype for business related article during SfB and Teams beginning. Required to add Skype for Business administrator role in addition to "Teams administrator and User administrator"

• Teams administrator
• User administrator
• Skype for Business administrator
  
  

Found in old article Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn

Microsoft Teams Auto Attendant/Call Queue - We can't upload the audio file. Verify the contents of the file and try again.

Many companies are migrating to Teams Voice, transitioning from legacy PBXs such as Cisco, Avaya, and Coral. In the past, for Hunt and IVR voice prompts, they would reach out to professionals or companies that specialize in these prompts, or they would record them internally as a low-cost option.

Option #1: You can convert speech to text and use it for Teams CQ/AA greetings and menus.

Option #2: You can use existing WAV or MP3 files and upload them as they are.

I decided to write this article based on my own experiences with various failures, such as the following:

Error: Microsoft Teams Auto Attendant/Call Queue - We can't upload the audio file. Verify the contents of the file and try again.

Solution: Change the sampling rate to something Teams CQ&AA supported. 

https://techcommunity.microsoft.com/t5/microsoft-teams/phone-system-upload-wav-greeting-to-call-queue/m-p/1525267 

How it is been done: I had heard about this tool before, but I was recently convinced by my colleague Lawrence, and it's a free tool. I’ve seen similar articles, but I’ve never come across one that offers a proper resolution

Open the existing WAV or MP3 file; it doesn't matter what sample rate it was recorded at as long as you can listen to it. If you don’t need to cut or change anything, the next step is to EXPORT. 

What I did was export to a low sample rate of 8000 Hz, without making any other changes in the following window.

Export to file location,

Upload this file afterward to Teams CQ/AA; it should work without any problems. This method was also used recently with WebEx Contact Center.

Setting Up PLAR on Microsoft Teams Common Area Phones

Configuring Private Line Auto Ringdown (PLAR) on Microsoft Teams common area phones can significantly enhance communication efficiency in shared spaces. Here’s a comprehensive guide to help you set it up:

Amazing feature, However a bit of delay from Microsoft end even though Teams certified phones were in the market. Cisco call manager or Cisco DI had it for a longest time according to what i learn! Having said that this feature must be there with other legacy PABX for sure. 

What is PLAR/Hotline? 

PLAR, or Private Line Auto Ringdown, is a feature that allows a phone to automatically dial a pre-configured number when the handset is picked up. This is particularly useful in common areas where quick access to specific contacts or services is essential.

Why Use PLAR on Common Area Phones? 

Mostly following features: Good for emergency, safety &  compliance, convenience

Steps to Set Up PLAR on Microsoft Teams Common Area Phones

1. Assign license - Microsoft Teams Shared Device License 

2. Set up the PLAR Number & Turn on TAC and Teams Phone Device

    -     Sign into the Teams admin center with a Microsoft 365 admin account. 

    -     From the left navigation, select Teams devices, select Phones and then select the Configuration profiles tab.

    -    From the list, select the configuration profile assigned to your common area phone. 

    -    Under the Call settings section, turn on the Enable hotline toggle and then select Save.

Note: Verify the Advanced Calling setting is disabled when you are enabling the hotline setting in Teams admin center. Also verify the Team app version on the Android phone is version 1449/1.0.94.2023082303 or later.

    -     Sign into your Teams phone device and select Settings > Device settings > Admin only > Calling > Hotline.

    - Enter a contact or phone number to be autodialed.

    - Enter the display name you want to show on the phone's home screen and Save. 

3. [Optional] Create a policy and assign. to disable Advanced Calling settings and push all the site available phones bulk. 

Reference from Microsoft - Set up the common area phones for Microsoft Teams - Microsoft Teams | Microsoft Learn