Skip to main content

Posts

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...

Teams Calling | Number porting diary - Day 3

Port-out from Microsoft   Interesting requirement came today for me which is port-out from Microsoft. Most common request which we get everyday port-in request, but this requirement which they have fully went on cloud (Teams born) environment both of them look for moving some numbers to local telco with Direct Routing SBC at premises. My customer is trying to achieve on-prem PBX integration and also some numbers are plan to use for elevators and guards with analog devices. Basically on this process, customer need a Microsoft 365 port out PIN to be created.   How to set up your PIN:    1.Sign into Office 365 with your work or school account     2.Go to the Office 365 admin center > Admin centers > Teams Admin Center    3.In the left navigation, choose Voice > Actions (on right top) > Manage Porting  PIN          4.Click Set up and manage the PIN that is used for transferring or porting number...

Teams Calling | Number porting diary - Day 2

Find the LOAs for T eams Calling migration Following URL will be the listed every LOA and LOA format will be different from each market/country and also requirement will be different from telco to telco.   Phone number management for Canada - Microsoft Teams | Microsoft Docs This article will have all the LOA for Subscriber Numbers (DID), Service Numbers (AA, CQ) and Toll-free.  When you submit a LOA it will be important to filled it correctly and include correct information to reduce number rejections from the telco. In this case it will be Microsoft TN support team (PTN) team (which mention in my previous article).  - BTN (Billing Telephone Number) mentioned in the ER (Equipment Record) or  CSR (Customer Service Record).  - Account Number can be found on the bill or ER/CSR - Signatory Name of the person of the organization and this can be change when person is left organization via direct email from the client to respective telco.  - Service Addre...

‎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 cou...

Teams Calling | Number porting diary - Day 1

During my time at Microsoft I did not have a chance to migrate any customer since Microsoft Calling plan was not available for Asia Pacific. The list of articles here are all my experiences with migrations to Teams calling plan and also from Teams calling plan to Telco porting. I searched in several places for documentations by individuals about the process and how to proceed, and I did not have much luck in my search. Hence, I thought why not I give back to the community about my daily hustle in summary. Number porting can be very simple to complex, this completely depends on the environment, the type of numbers available in that environment, their usage, and the level of knowledge the customer has about their own environment. Prior to submitting any order (be it Microsoft or any Telco around the world), number planning is required, and the entire process can consume many hours. Porting request submission  Porting request(s) can be submitted from two locations: 1.   Teams Adm...

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 convinc...