Martin Gibney - Microsoft Teams

I notice tonight when trying to set up a new Call Queue for a customer that things are changing currently in relation to using Direct Routing. Previous to tonight we were able to simply use the command: Set-CsOnlineVoiceApplicationInstance -Identity “mghuntgroup@domain.ie” -OnPremPhoneNumber + 35311234567 But today when we run this command we get the error: A parameter cannot be found that matches parameter name 'onpremphonenumber'. So what has happened to this parameter, it worked last week!! While checking out the TAC, I also noted that when we check out Assign/unassign under the Resource Account associated with the CQ that we now see on-premises  listed under the Phone Number Type . In here we actually see the numbers already associated with users who have Enterprise Voice enabled in Teams: This is different, but how do i add an unused number here now so I can use them? Hopefully more to come here....watch this space!!

I recently had a customer who was mid migration from Skype for Business Server On-Premise to Microsoft Teams. During the initial testing phase we got confirmation from users that all features were working just fine.... first mistake, always check all features and functions yourself!! My mistake. What was reported to be happening here was a call would come in to the Skype for Business user on reception, they would search for the Teams user, it would only show "Presence Unknown" and not allow the call to be transfered. In actual fact, the issue was more straight forward than this, they were not able to even call the Teams user from SFB. There were a few things to check here: First, ensure  SharedSipAddressSpace is set to True  in Office 365. Get-CsTenantFederationConfiguration Identity                            : Global AllowedDomains                      : AllowAllKnownDomains BlockedDomains                      : {} AllowFederatedUsers                 : True A

Microsoft have recently announced the rollout of PSTN reports in Teams. I have noticed this in a number of tenancies this week and gives some nice information. To access these reports, simply open the TAC (Teams Admin Center) and go to Analytics & Reports > Usage Reports  then when in here click on View Reports  and select PSTN Reports Select the report you want (PSTN Usage) and the Date Range  and click Run Report . This gives us a nice graph of usage and under this is a full detailed breakdown of calls broken down by Calling Plan  and Direct Routing, so click on the section you require. You can now Export to Excel  using the icon in the upper right corner. I think this will be a very good feature for customers to view CDR data very easily.

I had an issue today whereby a customer reported that users on conference calls were complaining that their calls were dropping. I checked the Teams logs and could not see any pattern, sometimes short and sometimes long calls. All other calls didn't seem to have any issues that were being reported. We contacted the ITSP and they advised: "ITSP has a 60 second RTP timeout, this has always been the case. It's typically used to make sure the call is still active otherwise there could be a lot of invalid or fraudulent calls. Typically when your muting a call, a PBX/Skype system will play a white noise in the background to make sure the call remains active. This seems not to be happening here and unfortunately it's beyond our control.” So after a quick email to an ever helpful FAE in AudioCodes he advised to change the simple setting in the ITSP IP Profile: Generate RTP = Until RTP Detected A quick save then I was able to make a test call of over 15 m

As part of my dive into automating as much as possible of a Microsoft Teams implementation or migration from Skype for Business On-Premise, I am focusing on scripting as much as possible. This post focuses on the licensing element. You are unable to enable users in Teams unless they have the correct licenses already assigned. The following commands will allow us to check what licensing is available to the tenant. To check this you must first connect to the Microsoft Online Service. Run: Connect-MsolService You will be prompted for your O365 credentials and any MFA (you have MFA enabled right...) Now run:  Get-MsolAccountSku You will see the output on the screen of the different licenses on the tenant: In the output the first element before the license type we have the tenant name XXXXX: followed by the License type and how many units of each, warnings and ConsumedUnits (Assigned Licenses) This ties in with what we see in the GUI in Office 365 Admin Center: Thes

Why can't things just be easy.... Now that Microsoft Teams allows "Guest Access" it is important to note that you need to enable this in a few locations in Office 365 unfortunately and not just in the Teams Admin Portal as (I) and most people seemed to think.  Teams Portal: Log in to the  Microsoft Office 365 Admin Center Under  Admin Centers , select  Teams  Go to  Org-Wide Settings Under  External Access , you can enable this if you want to let your Teams and Skype for Business users communicate with users that are outside of your organization. You can also whitelist specific domains here. Under  Guest Access , you’ll want to turn on the  Allow Guest Access in Teams button Office 365: Log in to the  Microsoft Office 365 Admin Center Under  Settings , go to  Security & Privacy Click  Edit  beside Sharing Turn on  the setting for  Let Users Add New Guests To The Organization From here, you can also click on the  Site Settings  link to verify

So the most common issue I come across is edge server replication issues in Skype for Business during a build stage. I had one today and I followed all the details in my previous post on replication yet still had UpToDate: FALSE. This was getting very annoying and certs were checked and Front End and Edge both used same CA, so that  looked good....except when i dug a little deeper, it seemed that the SQL server where the CMS was hosted was using a different CA and of course the CA was not in the Trusted Root Certificate Authority store on the edge server. I found this by running the CLS Logger on the Front end and ran an Invoke-CsManagementStoreReplication , waited about 30 seconds then stopped logging. The result showed: Issue with Remote Source  - which means where it is coming from, NOT the Edge server. I confirmed the SQL Cluster has a certificate from a different CA, installed the cert to the Trusted Root Certificate Authority store on Local Machine  and off it went!!!.

After a period of uncertianty; In that it was announced last year thet users of Skype for Business Online would be automatically moved to Teams -- and some were, Microsoft, today announced that the last day for Skype for Business Online is 31st July 2021. This means that customers have two years exactly today to move to Microsoft Teams instead. https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Skype-for-Business-Online-to-Be-Retired-in-2021/ba-p/777833  The service will be "Inaccessible" after this date we are being told. This is good news for Microsoft Partners like me, but there are still some vital features missing such as Call Center applications, Call Recording and transfer directly to Voicemail to name but a few. It is hoped that the long awaited API will be released in the coming months. I would bet that by November we will have a lot of information for the annual Microsoft Ignite event in Orlando. We are actively migrating customers from on-premise d