Martin Gibney - Microsoft Teams

Yes people still use Fax machines and analog handsets in enterprise environments.... and also more importantly, have requirements to use analog handsets plugged into your new shiny SIP trunk. While setting this up recently for a customer, I found it quite unwieldly. Configuring a FAX or Analog handset on an AudioCodes Mediant M800 is harder than it needs to be, or at least the config is not clear in their documentation.  Hopefully the details below help to clear it up: To set up a FAX or Analog handset on one of the ports on the M800, first plug into a free port and note the port, we use the first available port: Then we need to configure the following:   SIP Interface with GW Applications   Under Setup > Signaling & Media > Core Entities > SIP Interfaces ·        Create a new SIP Interface and set the following details: o    Network Interface: <This is your SIP Interface for incoming provider> o    Application Type: GW -- (If you cant pick GW then

The Walkie Talkie feature is now available in Teams but is not getting too much attention from what I have seen. It is only available in Android so bear this in mind if you are going to deploy for your organisation. Its actually quite simple to implement in your organisation. To do this simply follow the proceeding steps: In the Microsoft Teams admin center , under Teams app > Setup policies, you should have A llow user pinning set to On . Then, under the Pinned Apps section, click +Add Apps . On the Add pinned apps panel that appears on the right, use the Search textbox to look for Walkie Talkie . When you have it as a search result, select the Add button to the right of the name to add it to your list. The Walkie Talkie app should now appear on the Pinned Apps list, and be available for use once you click the Save button. Walkie Talkie is available under all CALs that have Teams, which is good news, but remember only on Android devices. Now on your Android, open the Teams App,

 Excel can be a super tool for managing number phone number migrations but if like me you are fed up of seeing the numbers show up like this: OK... then let's change the format of the cell to Text , this fixes it...right? Wrong! Try to do a find and replace on tel: now and you will see it keeps removing the + from the prefix. I found a fix! In the Format Cells  window, under Category  select General , now in Type, type +# ?/? exactly like this: Apply this to the column or cells you want to have in the E164 format, now even if you don't type the + at the start, it will automatically put it in for you, format looks good and numbers are now correct!

With everything we can do in any O365 Admin Portal possible to do, even easier and better, in PowerShell, I have tried to create scripts to automate as much of my tasks as possible. When I run these manually its fine, I enter my credentials and approve my MFA popup on Authenticator App.  But what about scripts I want to run regularly, or automatically based on another event happening? Well, basically we need a few things. The first is to have an O365 Admin account, with only the bare minimum role we need, created and NOT enabled for MFA. This is a risk of course but if it can be restricted and controlled (think Conditional Access here) within your environment then this will be more of a benefit than it is a risk. Once we create this account, we now need to securely save the credentials somewhere so they can be used in an automated/scheduled task. Storing credentials securely Step 1: Store your credentials in a variable - for this session only On the server you are going to run your

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 &