View source for FAQ:Teams

==General Questions==

=== Where can I find Microsoft Teams Admin and End User trainings ? ===

* '''Information''': On the VTX wiki, you will find documentation and tips regarding MS Teams Direct Training connectivity towards VTX Telephony Platform, but not related to Teams Global Training
* '''Solution''': To get access to Microsoft Teams training, please refer the links below
** '''Admin trainings for Teams''' : https://docs.microsoft.com/en-US/microsoftteams/itadmin-readiness
** '''End User trainings for Teams''' : https://support.office.com/article/microsoft-teams-video-training-4f108e54-240b-4351-8084-b1089f0d21d7

===What are the differences between a "Teams Connect" and a "Teams Virtual" ?===


{| class="wikitable"
|+
!
!'''<big>Teams Connect</big>'''
!'''<big>Teams Virtual</big>'''
|-
|'''<big>Short Description</big>'''
|VTX handles "only" the connection between Teams Cloud and the Telephony Network allowing you to operates real phone numbers on your Teams Client
|Teams Virtual allows an hybrid environment with SIP Phones and Teams Phones
The Intelligence remains handled in the VTX Kiosk
|-
|'''<big>Analogy</big>'''
|Like a VTX ConnectPBX product but to be used only with Teams Cloud ( preconfigured for Teams by VTX with a lot of automation )
|a VTX VPBX service allowing you to use MS Teams client in parallel of normal SIP phones
|-
|'''<big>VTX Service and Licenses Needed</big>'''
|a [https://www.vtx.ch/fr/corporate/telephonie/teams-connect "Teams Connect"] ( billed per number of concurrent calls + number of numbers )
N/A per user
|a VPBX Service ( billed per number of numbers )
a [https://www.vtx.ch/fr/corporate/telephonie/teams-virtual "Teams Virtual"] license per user
|-
|'''<big>Microsoft Licenses Needed</big>'''
|'''Microsoft Teams''' per user
'''Microsoft Phone System''' per user 
|'''Microsoft Teams''' per user
'''Microsoft Phone System''' per user
|-
|'''<big>Pros</big>'''
| - Simple and Basic solution from VTX to add real numbers to your Teams accounts
- "Cheap" solution to use Microsoft Teams
| - Allows an hybrid solution if you do not wish to have all your users and landing Zone to
use Microsoft Licenses.

- You can use a mix of simple SIP phones ( Gigaset, Snom, Yealink,... ), VTX Softphones (DeskopControl / MobileControl), Teams Softphones and Yealink Teams phones within the same user or on different users

- Allows to handle all Time Conditions and IVR and Groups within VTX Kiosk
|-
|'''<big>Cons</big>'''
| - Management of all intelligence in Teams Admin in less sexy than in the VTX Kiosk
- Doesn't allow to operate simple SIP phones within the same VTX service
|
|}

===Keep my '''@company.ch''' domain : Can I use VTX Teams service with my own Teams domain '''@company.ch''' ?===

{{Notice|1=There is no need for you to change the domain of your users with a '''@xxxx.teams.ipvoip.ch''' VTX domain, your Teams users will stay with '''@company.ch''' domain}}

*'''Problematic''': You do own a Microsoft Teams domain like '''company.ch''' and you would like to integrate the accounts you have within a "VTX Teams Connect" or "VTX Teams Virtual"
*'''Information''': 
**When subscribing to a VTX Teams service, VTX will provide you with a teams domain like '''xxxx.teams.ipvoip.ch''' . This domain will be used to bridge your own Teams accounts ending with "@company.ch" with the VTX service. You will never need to force this domain for your end user
**During the VTX Teams service setup, you will be asked to create one temporarily user with the @xxxx.teams.ipvoip.ch domain, but only one, and you can delete it as soon as service is running
**The scrips provided by VTX will allow you to assign numbers to your '''@company.ch''' Teams users
*'''Conclusion''': Yes, you can use your own Teams domain '''@company.ch''' with VTX Teams service, no need to change your users domain

===Multi-Provider : Can I use VTX Teams service in parallel of other provider services ?===


*'''Problematic''': You do already have another provider that handles the telephony Direct trunking and you wish to also integrate a VTX Teams service
*'''Information''': VTX does provide a unique teams domain per service and also create unique Call Routing rules including this unique ID
*'''Conclusion''': Yes, it is possible to setup a VTX Teams service in parallel of an existing service from another provider. You will select which number is handled by which provider.

== Migration ==

=== How to use Teams in parallel of my existing PBX ? ===

* '''Problematic''': You have some of users within a VTX "Connect PABX" that wish to use Teams ( keeping their number )
* '''Information''': Teams can be completely embedded within a VTX VPBX with the [[VoIP:VTX_Teams_Virtual|VTX Teams Virtual]] service. For PBX, integration is different.
* '''Solution''': There are 2 possible solutions

''Solution 1: Move some numbers to Teams''
# '''(VTX)''' Subscribe to a [[VoIP:VTX_Teams_Virtual|VTX Teams Virtual]] or [[VoIP:VTX_Teams_Connect|VTX Teams Connect]] depending on your needs
# '''(Teams)''' Prepare your user in Teams with the desired number
# '''(VTX)''' Ask VTX to move the number from the PBX to Teams 
# '''(PBX setup)''' Remove the number from PBX setup
# '''(PBX setup)''' Redirect internal number to full number. So if an internal user calls the short number or the full number of the colleague, it will go out from the PBX->VTX->Teams


''Solution 2: Use Teams in parallel of existing phones behind the PBX: Incoming calls ringing on PBX + Teams, outgoing calls possible from PBX + Teams''
# '''(VTX)''' Subscribe to a [[VoIP:VTX_Teams_Virtual|VTX Teams Virtual]] or [[VoIP:VTX_Teams_Connect|VTX Teams Connect]] depending on your needs
# '''(Teams)''' Prepare your user in Teams with another VTX number ( new number provided by VTX that won't be shown when calling out )
# '''(Teams)''' Follow [[FAQ:Teams#CLIP_:_Number_Display_-_I_wish_to_display_a_different_number_than_my_direct_line_for_my_outgoing_calls]] to have this Teams account displaying the PBX number
# '''(PBX setup)''' Setup the PBX to have a parallel ringing between the user account on the PBX and the VTX Teams account

== License Management == 


=== Microsoft Teams Shared Devices - Not working anymore on Web + Desktop Client - "You don't have the required permissions to access this org" ===

* '''Symptoms''': You are using a "Teams Shared Devices" license and are trying to connect to Teams v2 Client and you get an error "You don't have the required permissions to access this org"
* '''Explanation''': The "Teams Shared Devices" is now not working anymore on Desktop and Web Client
* '''Solution''': Either upgrade to a more expensive license or only use the Mobile Client 
* '''Additional Information''': https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/teams-shared-device-license 




==Features ==

=== Main Teams Features not related to VTX ===

The idea of this wiki is not to document how Teams App is working, but this Microsoft is doing a great job. So if you have questions about specific features in Teams ( not related to VTX), please have a look at their documentation 
* Ex: Teams Video Training : https://support.microsoft.com/en-us/office/microsoft-teams-video-training-4f108e54-240b-4351-8084-b1089f0d21d7
* Other solution : https://letmegooglethat.com/?q=microsoft+teams+app+write+your+question+here 



=== Teams GAB (Global Address Book) Directory Missing ===


* '''Status''': As incredible as it sounds, It doesn't seems possible to enable a Global Address Book directory for several Teams users
* '''Actions''': We have tried it and with Ops Team and even with an Azure Active Directory Premium license, it is not possible to create a global directory
* '''Information'''
** The feature request for a GAB ( Global Address Book ) was visible in E365 Roadmap in 2020 but was deleted afterwards
** With a Team Virtual, it would be possible to have incoming call reverse lookup ( and only incoming call reverse lookup ) ! But not with a Connect Teams, info added in [[VoIP:VTX_Teams_Virtual#VTX_Teams_Virtual_value_added_features]]
** Some external paying tools seems to allow to sync an external directory with each individual Teams Directory, but it gets tricky
* '''References''':
** https://www.msxfaq.de/teams/pbx/teams_rnl.htm
** https://erwinbierens.com/microsoft-teams-using-reverse-number-lookup/


* '''Conclusion''': 
** VTX is not responsible for the lack of this missing features in Teams, and indeed this one doesn't seem to be possible
** Some tweaks might be possible with full Office 365 integration but we haven't tested it





=== Delegate : Share a phone line with a delegate ===

* '''Information''': Microsoft Teams allows to delegate management of incoming and/or outgoing calls allowing a colleague/secretary to handle your calls, cf https://support.microsoft.com/en-us/office/share-a-phone-line-with-a-delegate-16307929-a51f-43fc-8323-3b1bf115e5a8
* '''Problematic''': You would like to use this feature
* '''Solution''': Follow one of the solution below depending on your service
# For "Teams Connect" users, you can already use this feature, it is allowed on VTX side, cf https://support.microsoft.com/en-us/office/share-a-phone-line-with-a-delegate-16307929-a51f-43fc-8323-3b1bf115e5a8
# for "Teams Virtual" users, please contact VTX support with this URL as reference to have VTX enabling this feature. ( VTX internal reference for automation is "Redmine #93076" )


=== Use Teams to follow "tel:" or "callto:" URL  ===


* '''Information''': Once you have selected a default app to perform outgoing call, you will need to manually change it to use another Application to handle the tel: uri
* '''Problematic''': You wish to setup your PC to use Teams app for tel: and callto: URLs to directly call numbers from web browsers 
* '''Solution ( Windows 10 )''' : Change the default app for tel uri
# Click on the link below to verify id your system is already setup to use Teams for tel: and callto: URLs, if not continue to follow the steps
# Go in Control Panel / Programs / Default Programs and click the "Set your default programs"
# Go in the bottom of the menu to "Set Defaults by app" and click on Teams
# Click the "Choose a default" and select Teams / Manage
# For '''URL:callto''' and '''URL:tel''' select "Teams"
* '''Example''': You can use the links below to perform tests
** +41225117902 : VTX Echo test number without any link except if your browser is able to detect this as a number
** [tel:+41225117902 tel:+41225117902]: VTX Echo test number with tel: URI syntax
** [callto:+41225117902 callto:+41225117902]: VTX Echo test number with callto: URI syntax

<table>
<tr><td>
[[Image:Windows-10-Default-App-Tel-URI.png|thumb|1200px|left|Windows 10 - Default Program - Change tel uri for Teams]]
</td></tr>
<tr><td>
[[Image:Windows-10-Default-App-Tel-URI-02.png|thumb|1200px|left|Windows 10 - File type and protocol associations - Change tel uri for TEams]]
</td></tr>
</table>

==Frequent Errors==

===New-CsOnlineVoiceRoutingPolicy - Cannot find specified Online PSTN usage===

*'''Problem''': When we run the script to create the call routing, you might get a red error that New-CsOnlineVoiceRoutingPolicy is not working
*'''Symptoms''': When running the script to create the call routing, you might get an error "Cannot find specified Online PSTN usage"
*'''Possible Explanation''': 
**You forgot to create the temporary User "enableteams"
**MS Teams platform is getting some delay and between the time we create the Online PSTN usage and the time we use it in Online Voice Routing Policy, we need to wait for Teams platform to get up to date
*'''Solution''':

#Verify that you did create the "enableteam" user, cf [[{{FULLPAGENAME}}#Create_a_temporarily_user_in_the_.3Cservicenumber.3E.teams.ipvoip.ch_domain]]
#Wait up to 4h and try again to use the script again


''As you can see after some time, the same command did work''
<table>
<tr><td>
[[Image:Teams-script-error-Cannot-Find-Online-PSTN-Usage.png|thumb|1200px|left|Teams Error - Cannot Find Online PSTN Usage - Wait a few hours and try again]]
</td></tr>
</table>


===Cannot Import Module SkypeOnlineConnector===

*'''Information''': By default, it is not allowed to execute powershell scrip on a Windows PC, you need to explicitly allow it
*'''Problem''': If you did not follow the Microsoft documentation while installing the SkypeOnlineConnector module, you will not be able to import it
*'''Symptoms''': You will get the powershell error below
*'''Solution''': Open a powershell prompt as admin and set "Set-ExecutionPolicy RemoteSigned -Force" ( cf below )
*'''Additional Information''': cf https://docs.microsoft.com/en-us/SkypeForBusiness/set-up-your-computer-for-windows-powershell/download-and-install-windows-powershell-5-1


''Confirmation of the problem, here Execution Policy is Restricted, i.e disabled''
<source lang="powershell">
Get-ExecutionPolicy
Restricted
</source>

''Solution''
<source lang="powershell">
Set-ExecutionPolicy RemoteSigned -Force

Get-ExecutionPolicy
RemoteSigned
</source>


''Error that you are getting''
<source lang="powershell">
Modules d'importation : Le fichier "C:\Program Files\Common Files\Skype for Business
Online\Modules\SkypeOnlineConnectorSkypeOnlineConnectorStartup.psm1" ne peut pas être chargé, car l'exécution de
Les scripts sont désactivés sur ce système. Pour plus d'informations, voir "about_Execution_Policies".
(https:/go.microsoft.com/fwlink/?LinkID=135170).
En ligne:1 Caractère:1
+ modules d'importation "C:\Program Files\Common Files\Skype for Business Onlin ...


+ CategoryInfo : Erreur de sécurité : ( 🙂 [Modules d'importation], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.ImportModuleCommand
</source>


===Get-CsOnlinePowerShellEndpoint : The remote name could not be resolved: 'lyncdiscover.xxx'===

*'''Problem''' : You get an red colored error when using the scripts
*'''Symptoms''': When starting to use a powershell script or command, you get an error like Get-CsOnlinePowerShellEndpoint : The remote name could not be resolved: 'lyncdiscover.xxx'
*'''Possible Explanation''': You are using an admin account where needed lyncdiscover.$DOMAIN DNS entry is not set correctly
*'''Solution''': You need to create the needed DNS entries on your main domain enabling the "Skype For Business" DNS check on your main domain in https://admin.microsoft.com/AdminPortal/Home#/Domains
*'''Workaround''' : Add the suffix "-OverrideAdminDomain $TeamsDomain" to the New-CsOnlineSession command


<table>
<tr><td>
[[Image:MS-Teams-Error-lyncdiscover.png|thumb|1000px|left|Teams Script - lyncdiscover error because DNS entry doesn't exist]]
</td></tr>
<tr><td>
[[Image:MS-Teams-setup-DNS-lyncdiscover.png|thumb|1000px|left|Teams DNS entries - Create the needed DNS entries]]
</td></tr>
</table>


==AD Sync Problem==


=== What are the numbers defined and used in Teams ? ===

* '''Information''': Teams is using the LineURI and OnPremLineURI parameters to define the number to be used by Teams ( cf below )
* '''Problem''': If you do have an AD sync with Azure Cloud that is overwriting these parameter, Teams telephony calls towards external numbers will stop working
* '''Symptoms''': You are getting a [[{{FULLPAGENAME}}#404_Not_found_:_Number_hasn.27t_been_assigned|"404 Not found" error]] on incoming calls
* '''Solution''': Please follow the procedure below
# Use [[{{FULLPAGENAME}}#Verify_User_Setup]] to verify that number currently set for the Teams user
# Make sure your AD sync is not overwritten these fields or make sure it does set the same numbers
# Re-assign the number in Teams using [[{{FULLPAGENAME}}#Number_Mapping_:_Assign_numbers_to_Microsoft_accounts]]


''Output of a Teams user listing all fields that contains a Switzerland number''
 # Set Variables
 $TeamsUserEmail = "first.last@MSDOMAIN.onmicrosoft.com"
 # Connect to Microsoft Teams management
 Connect-MicrosoftTeams
 # Get the numbers used by a user
 Get-CsOnlineUser -Identity $TeamsUserEmail | Out-String -Stream | Select-String -Pattern "41\d{9}"
 OnPremLineURI                        : tel:+412156600xx
                                          <tollNumber>41434307500</tollNumber>
 LineURI                              : tel:+412156600xx
 # Logout
 Disconnect-MicrosoftTeams

=== 'OriginalRegistrarPool' with identity 'xxx' assigned to 'sip:first.last@MSDOMAIN.onmicrosoft.com' has been removed from configuration store ===

* '''Symptoms''': When assigning a number to your user, you set this error """OriginalRegistrarPool' with identity 'xxx' assigned to 'sip:first.last@MSDOMAIN.onmicrosoft.com' has been removed from configuration store"""
* '''Information''': When you are assigning a Teams number to a user, it might cleanup some old parameters used by old Lync setup like the OriginalRegistrarPool. This is normal and only a WARNING, not a ERROR
* '''Solution''' : Please follow the procedure below
# Use [[{{FULLPAGENAME}}#Verify_User_Setup] to verify that number has been correctly setup for your user
# Use the command "Get-CsOnlineUser -Identity $TeamsUserEmail" to get the full details output of the user you are debugging and look at the "TeamsUpgrade" and "RegistrarPool" outputs 
# Search your error on Teams Forum
# If needed, get help from VTX


 PS H:\> Get-CsOnlineUser -Identity $TeamsUserEmail | Out-String -Stream | Select-String -Pattern "TeamsUpgrade"
 TeamsUpgradeEffectiveMode            : TeamsOnly
 TeamsUpgradeNotificationsEnabled     : False
 TeamsUpgradePolicyIsReadOnly         : ModeAndNotifications
 TeamsUpgradePolicy                   :
 TeamsUpgradeOverridePolicy           :

 PS H:\> Get-CsOnlineUser -Identity $TeamsUserEmail | Out-String -Stream | Select-String -Pattern "RegistrarPool"
 TargetRegistrarPool                  :
 RegistrarPool                        : sippoolAM48976.infra.lync.com



==Incoming Call Problem==


===403 Forbidden : License Problem / User is not Enterprise Voice enabled ===

* '''History''': 
** '''2023-08''': We had a nice problem where setup was not working because only some "Microsoft Teams Shared Devices" licenses were setup and not a single "Phone System". It was blocking setup of resources. In this case, please order one real "Phone System License" (@VTX: cf example t1990043)
* '''Symptoms''': You are calling a Teams number and you get a 403 error all the time from Teams
* '''Solution''': Use [[{{FULLPAGENAME}}#Verify_User_Setup]] to verify that your user is setup correctly and enable back the correct license

<table>
<tr><td>
[[Image:MS-Teams-VoIP-Analyser-403-Not-Authorized.png|thumb|1000px|left|VoIP Analyser - Call Rejected because of bad license]]
</td></tr>
</table>

 SIP/2.0 403 Forbidden
 ...
 CSeq: 1 INVITE
 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
 Server: Microsoft.PSTNHub.SIPProxy v.2020.11.29.1 i.EUWE.3
 Reason: Q.850 ;cause=63 ;text="...;User is not Enterprise Voice enabled."

===404 Not found : Number hasn't been assigned===

*'''Problem''': You cannot call a Microsoft Teams number
*'''Status''':  You have assigned a number to a "Microsoft Teams Virtual" in the Kiosk Hardware Module or the number belongs to a "Teams Connect", but incoming call towards this number are not working and are rejected.
*'''Symptoms''': When calling the number, you get a "404 Not Found" Number hasn't been assigned error
* '''History''':
** '''2023-10''': Setting up extension from routing can trigger problem, do not setup numbers like "+14025557334;ext=334", cf https://www.google.com/search?q=MC487014 
*'''Check to perform 1''':

#'''(VoIP Analyzer for VTX Partners)''' Using VoIP Analyser, check the status of the number and verify that call was rejected by Microsoft Proxy with a 404 error
#'''(Teams Domain)''' Verify in https://admin.microsoft.com/AdminPortal/Home#/Domains that you did enable the <service_number>.teams.ipvoip.ch domain for MS Teams
#'''(Teams + Phone System)''' Verify in https://admin.microsoft.com/AdminPortal/Home#/users that you did enable Teams + Phone System to your user
#'''(Number)''' Verify in https://admin.teams.microsoft.com/users that you did assign the correct Phone number to your user


<table>
<tr><td>
[[Image:MS-Teams-VoIP-Analyser-404-Not-Found.png|thumb|1000px|left|VoIP Analyser - Call sent to Teams but rejected]]
</td></tr>
</table>

===480 Temporarily Unavailable : Call ringing for 20s then cut with this error ===


* '''Symptoms''': You are calling a Teams number , call is ringing for 20s then call is cut with a 480 error
* '''Possible Explanation''': You have a 20s redirection setup on the Teams client towards nothing
* '''Solution''': Please read [[{{FULLPAGENAME}}#Disable_Call_redirection_to_Voicemail]] section below


<table>
<tr><td>
[[Image:MS-Teams-VoIP-Analyser-480-Temporarily-unavailable.png|thumb|1000px|left|VoIP Analyser - Call rejected with 480 after 20s]]
</td></tr>
</table>

 SIP/2.0 480 Temporarily Unavailable
 ...
 CSeq: 1 INVITE
 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
 SERVER: Microsoft.PSTNHub.SIPProxy v.2020.11.29.1 i.EUWE.3
 Reason: Q.850 ;cause=31 ;text="...;'''Could not obtain destination from voicemail workflow'''."


=== Calls answered by voicemail all the time ===

{{Warning|1=If you redirect call to a Teams user that is not connected, all calls will be answered anyway by a voicemail ! By default all Teams users do have a redirection towards their voicemail.}}

* '''Symptoms''': All calls towards a number are answered by a voicemail
* '''Example''': You have 3 users within a VPBX group and one of them is not connected ( PC shutdown ), all calls will be answered by his voicemail
* '''Solution''': Please read [[{{FULLPAGENAME}}#Disable_Call_redirection_to_Voicemail]] section below

=== Spam Call Blocking - Caller being asked : "Please press XX to connect the call" ===

* '''Symptoms''': Some incoming calls towards your Teams number are being requested to press 2 digits to connect the call
* '''Explanation''': When you receive a call from someone that is changing its number to a service number like a 058.. or a 0848.. or calling from a number that Microsoft classified as suspicious, caller could be impacted by this feature
* '''History''': 
** '''2021-09''': This feature is being pushed by Microsoft since September 2021 ( cf link below ) 
** '''2021-11''': This feature is not only showing a popup about possible Spam, but it is also blocking calls with an IVR asking to enter 2 digits in English and it is not possible to see it from Web Admin Center
* '''Additional Information''': Please refer to https://techcommunity.microsoft.com/t5/public-sector-blog/september-2021-microsoft-365-us-public-sector-roadmap-newsletter/ba-p/2745689 and search for "MC277640 – Spam Notification in Call Toast"

* '''Solution''': Follow procedure below 
# Start a powershell window
# Use command '''Connect-MicrosoftTeams''' and enter your Teams Admin credentials
# Use command '''Set-CsTeamsCallingPolicy -Identity Global -SpamFilteringEnabledType "Disabled"''' 
# Wait a few minutes for the change to be active
# Disconnect from Teams Management

<source lang="powershell">
 # Connect to Microsoft Teams management
 Connect-MicrosoftTeams
 # Disable the SpamFilteringEnabledType option, if needed, you can enable it back by setting parameter back to "Enabled" value
 Set-CsTeamsCallingPolicy -Identity Global -SpamFilteringEnabledType "Disabled"
 # Unfortunately for the time being, you cannot see your changes in command line nor in https://admin.teams.microsoft.com/policies/calling 
 Get-CsTeamsCallingPolicy -Identity Global -Verbose
 # Logout
 Disconnect-MicrosoftTeams
</source>

<table>
<tr><td>
[[Image:MS-Teams-MC277640.png|thumb|1000px|left|MC277640 – Spam Notification in Call Toast|link=https://techcommunity.microsoft.com/t5/public-sector-blog/september-2021-microsoft-365-us-public-sector-roadmap-newsletter/ba-p/2745689]]
</td></tr>
</table>

=== Busy on Busy - Disable Call Waiting ===

* '''Information''': By default call waiting is enabled on Microsoft Teams which mean that if you are already on the phone, you will keep receiving incoming calls that will trigger a popup and a bip even if you are already on the phone
* '''Problematic''': You would like to enable "Busy on Busy" or disable "Call Waiting" not to be bothered by an incoming call when you are already on the phone
* '''Solutions''': Follow one of the 2 solutions below
**  (Virtual Teams) : You can disable "Call Waiting / Signal d'appel" from the Kiosk on your user
** Assign to your users a new '''Calling Policy''' "Disable Call Waiting", cf below

''Create a Calling Policy "Disable Call Waiting"''
# Read the "Busy on Busy" section from https://docs.microsoft.com/en-us/microsoftteams/teams-calling-policy
# Connect to https://admin.teams.microsoft.com/policies/calling and create a new Calling Policy
## Name : Disable Call Waiting
## Description : Allow to disable Call Waiting by enabling Busy on Busy feature
## Tick Busy on busy is available when in a call
## Keep all other settings with default values
# Select the user you wish to modify in https://admin.teams.microsoft.com/users
## Go in the "Policies" tab of the user
## Edit the "Assigned policies" and set "Calling policy" = "Disable Call Waiting"
# Save the setting

<table>
<tr><td>
[[Image:MS-Teams-Admin-Busy-on-Busy-01.png|thumb|1000px|left|Teams Admin - Create a calling policy - Disable Call Waiting]]
</td></tr>
<tr><td>
[[Image:MS-Teams-Admin-Busy-on-Busy-02.png|thumb|1000px|left|Teams Admin - Add Calling Policy to a user]]
</td></tr>
</table>

==Outgoing Call==


=== I cannot call a colleague not using Teams yet / not using Teams anymore dialing his +e164 number on this VTX Teams service ===

* '''Information''': Once you have assigned an +e164 number to a Teams user using [[{{FULLPAGENAME}}#Number_Mapping_:_Assign_numbers_to_Microsoft_accounts]], if you dial this number from Teams, it will be intercepted by Teams as a local call and will ring only on the Teams account of your coworker
* '''Symptoms''': I am calling a colleague with Teams dialing his +e164 number and it is not working because this colleague is not using Teams on this service anymore / yet
* '''Solution''': Use one of the 2 solution below to have you call towards your colleague +e164 number going out to VTX to be handled as a normal call 
# Use [[{{FULLPAGENAME}}#Number_Mapping_:_Assign_numbers_to_Microsoft_accounts]] to remove the number to from the Teams user
# or simply remove the "Phone System" license from this user. Warning: Once license is removed, it is not possible to purge the "OnPremLineURI" from the user, but it is not used anymore anyway



=== Caller ID policies : I am not able to set a Caller ID policy ===

* '''Information''': This feature is still under development from Microsoft cf https://docs.microsoft.com/en-us/microsoftteams/caller-id-policies
* '''Problem''': You would like to change the Caller ID of a user using a "Caller Id policy" from https://admin.teams.microsoft.com/policies/callinglineid but you are not able ot
* '''Symptoms''': When trying to add a policy, the dropdownlist are empty 
* '''Solution''' : Change the CLIP from the Kiosk, cf next section [[{{FULLPAGENAME}}#FAQ:Teams#CLIP_:_Number_Display_-_I_wish_to_display_a_different_number_than_my_direct_line_for_my_outgoing_calls]]

<table>
<tr><td>
[[Image:FAQ-Teams-Caller-ID-Policies-01.png|thumb|800px|left|Teams - Caller ID Policies - Cannot define a number]]
</td></tr>
</table>



=== CLIP : Number Display - I wish to display a different number than my direct line for my outgoing calls ===

*'''Problematic''': For outgoing calls, you wish to display a number that is different than your direct line number
*'''Information''': By default, you will be allowed to display any number belonging to your trunk ( visible in Kiosk ). If you try to display a number that doesn't belong to your trunk, the system will fallback to your direct line
* '''Solutions''': 2 solutions are possible, one from Teams Admin Center, and another one from VTX Kiosk
* '''Solution from Teams''':
# Read https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies : You can create Caller-ID policy to have some users displaying some resources account numbers (Auto Attendant or Call Queue)
# Go in https://admin.teams.microsoft.com/policies/callinglineid and create a new Caller-ID policy by setting the number that you wish to display
# Go in https://admin.teams.microsoft.com/users and set the new caller-ID policy to the users that need to use it
# Wait some minutes
# Now these users will display the service number for outgoing calls
*'''Solution from VTX Kiosk''': 
# '''Display my company main number''' : Connect to your Kiosk https://kiosk.vtx.ch/VoIP/ListNumbers.aspx ( My Services / Telephony / Manager your numbers ) / Edit number / Outgoing calls and change number to be displayed
# '''Display another number belonging to me like my Mobile or a 08x number''' : Contact VTX to add a "Virtual Number"
# '''Display any number / Forward Caller Number''' : Contact VTX to enable "Special Arrangement"


''Change number to be displayed in Teams Admin Center''
<table>
<tr><td>
[[Image:FAQ-Teams-change-CLIP-Teams-Admin-Center-01.png|thumb|800px|left|Teams Admin Center - Create Caller-ID policy]]
</td><td>
[[Image:FAQ-Teams-change-CLIP-Teams-Admin-Center-02.png|thumb|800px|left|Teams Admin Center - Assign Caller ID Policy to users]]
</td></tr>
</table>



''Change number to be displayed in Kiosk''
<table>
<tr><td>
[[Image:FAQ-Teams-change-CLIP.png|thumb|800px|left|Kiosk - Change number to be displayed]]
</td></tr>
</table>


''Here is a table explaining what number will be displayed
{| class="wikitable"
|+
!'''Number you wish to display'''
'''(From SIP Header)'''
!'''Number you wish to Bill'''
'''(P-Preferred-Identity)'''
!'''"Special Arrangement" setting in VTX CRM'''
!'''Option D'affichage in Kiosk'''
(PS: Any number belonging to you could be added by VTX in this list as "Virtual Number")
!'''Number that will be displayed'''
'''(out From SIP Header)'''
!'''Real Caller Number'''
'''(out P-Asserted-Identity)'''
|-
|Your direct line A
|Your direct line A
|%
|Your direct line A
|Your direct line A
|Your direct line A
|-
|Your direct line A
|Your direct line A
|%
|Another number belonging to you B '''and managed by VTX'''
( like a group number, headnumber, INA number... )
|Another number belonging to you B
|Another number belonging to you B
|-
|Your direct line A
|Your direct line A
|%
|Another number belonging to you B '''and not managed by VTX'''<br />
|Another number belonging to you B
|Your direct line A
|-
|An external number like a mobile
|Your direct line A
|No
|N/A
|Your direct line A
|Your direct line A
|-
|An external number like a mobile
|Your direct line A
|Yes
|N/A
|An external number like a mobile
|Your direct line A
|}

===Special Arrangement : I wish to keep the number of the caller being displayed when redirecting call to an external number===

*'''Problematic''': You are redirecting incoming call towards and external number and you wish to keep the number of the caller being displayed on remote destination
*'''Problem''': Since you are trying to display a number that doesn't belong to your trunk, it is not allowed and caller id will fallback to your direct line
*'''Solution''': Ask VTX to enable the "Special Arrangement" on your trunk, and also ask VTX to add a "+1" to push the project "#2304 - [Kiosk] ConnectPABX - Be Able to Manage Special Arrangement and Number Format from Kiosk Directly"


=== CLIR : Hide my phone number ===


* '''Problematic''': You would like to hide your number when calling out
* '''Information''': You could also setup CLIR / "Anonymous Call" from the Kiosk, but please either do it from Teams or from the Kiosk, but not from both in the same time, cf  [[{{FULLPAGENAME}}#CLIP_:_Number_Display_-_I_wish_to_display_a_different_number_than_my_direct_line_for_my_outgoing_calls]]
* '''Solution''': Follow the solution below
# Open your Teams app, go in the Settings menu / Calls tab
# Scroll down to the "Caller ID" part
# Tick the option "Hide my phone number and profile information for all calls"
# Now you can call out hiding your number

''Teams app settings - Hide my phone number and profile information for all calls''
<table>
<tr><td>
[[Image:FAQ-Teams-hide-CLIP.png|thumb|800px|left|Teams - Hide my caller ID]]
</td></tr>
</table>

== Check CDR and Audio Quality Problem ==


=== Control Call Quality ===

* '''Problematic''': You had a report of poor call quality and you wish to check the statistics of the call
* '''Solution''': Follow the procedure below

# Connect to https://admin.teams.microsoft.com/users
# Select your user 
# Go in the "Call history" tab
# Select the call you wish to analyze ( and look at the "Audio quality" )
# Click on the "Network" icon to get access to network stats
## '''Call Quality''' : Look at the call quality Good Quality or Poor Quality
## '''Round-Trip-Time''' : Look at the Round-Trip-Time, it should be below 150ms, above it, you have a network problem
## '''Packet Loss''': On a perfect network, there should not be any packet loss, but some packet loss could appear during call setup.


<table>
<tr><td>
[[Image:MS-Teams-call-history.png|thumb|1000px|left|Teams Admin - Call History ]]
</td></tr>
<tr><td>
[[Image:MS-Teams-Session-MOS-02.png|thumb|1000px|left|Teams Admin - Call Logs - Bad Call Quality]]
</td><td>
[[Image:MS-Teams-Session-MOS.png|thumb|1000px|left|Teams Admin - Call Logs - Good Call Quality]]
</td></tr>
</table>

=== Audio Delay problem  ===

* '''Symptoms''': You have huge delay over your Teams client that prevent you from having a normal interaction with your interlocutor 
* '''Possible Audio Delay source''' : RDP, Internet Connection, VPN, Team cloud problem
* '''Problematic''' : You need to perform some tests to identify the source of the problem
* '''Test Call numbers'''
** "/testcall" ( "/Testanruf" in German ): Teams test call number that can be used to test latency within Teams Cloud. Simply call "/testcall" ( "/Testanruf" in German ) from Teams Call Tab to test latency between your Teams_Client <-> Teams_Cloud
** '''+41225117902''' : VTX Echo Test number will echo back what you are saying allow you to check audio latency between your Teams_Client <-> Teams_Cloud <-> VTX_SBC <-> VTX_Echo_Test_Server
* '''Checks to perform''' : Here are checks to perform to find the source of the latency
# '''Control Call Quality''': Use previous section to check the call Quality of the calls, cf [[{{FULLPAGENAME}}#Control_Call_Quality]]
# '''Teams Service  Health Check''' : Control if Teams is acknowledging a problem  [[{{FULLPAGENAME}}#Service_Health_-_Get_notified_when_there_is_a_problem_with_MS_Teams]]
# '''Testcalls''': Use testcall numbers above to test if problem comes from Teams cloud or from Teams Cloud <-> VTX Platform interconnection
# '''RDP/VPN''' : Disable RDP ( use a local Teams client ), disable your VPN and test again
# '''Speedtest''' : Use https://speed.vtx.ch to test your connection
* '''How to solve the problem'''
# Teams Cloud Problem : Wait that Microsoft solves the problem
# Network Problem
## '''RDP''' : Try using a local Teams client and not one over RDP
## '''VPN''' : Try to disable your VPN and test again 
## '''QOS''' : If you have an intelligent Firewall that could setup QOS, you should setup QOS towards Teams Platform, cf [[Network:Firewall:Configuration#Teams_Connect.2FVirtual_Firewall_Rules]]
# Get help from VTX Support if needed

<table>
<tr><td>
[[Image:MS-Teams-testcall.png|thumb|1000px|left|Teams - Echo Test  /testcall ]]
</td></tr>
</table>

== Voicemail Management ==

=== Disable Call redirection to Voicemail ===

* '''Problem''': If you Teams client is not started, all your incoming calls will be redirected to Teams Voicemail instantly
* '''Problematic''': You would like to disable redirection towards your voicemail
* '''Additional Information''': Please refer to https://support.office.com/article/manage-your-call-settings-in-teams-456cb611-3477-496f-b31a-6ab752a7595f
* '''Solution''': Follow the following procedure
# Open Microsoft Teams Application
# Click on your user icon and go in the '''Settings''' parameters
# Go in the '''Calls''' tab
# In the "If not answered" section, select "Do Nothing" instead of "Voicemail"

<table>
<tr><td>
[[Image:MS-Teams-Disable-Voicemail.png|thumb|1000px|left|Teams Settings - Calls - Disable redirection to voicemail]]
</td></tr>
</table>

PS: You can also disable the Voicemail using Powershell ( cf https://docs.microsoft.com/en-us/powershell/module/skype/set-csonlinevoicemailusersettings?view=skype-ps for more information )

<source lang="powershell">
Set-CsOnlineVoicemailUserSettings -Identity login@domain.ch -VoicemailEnabled $false

VoicemailEnabled                         : False
PromptLanguage                           : en-US
OofGreetingEnabled                       : False
OofGreetingFollowAutomaticRepliesEnabled : False
OofGreetingFollowCalendarEnabled         : False
ShareData                                : False
CallAnswerRule                           : RegularVoicemail
DefaultGreetingPromptOverwrite           :
DefaultOofGreetingPromptOverwrite        :
TransferTarget                           :

</source>




=== Change Voicemail Settings ( Language, record prompt, Text to speech, ...) ===

* '''Problematic''': You would like to change some settings of your voicemail like the language of the prompt
* '''Information''': The default language of your user will depend on the default language selected by your administrator. But you can change it in this menu
* '''Solution''': Follow the following procedure
# Open Microsoft Teams Application
# Click on your user icon and go in the '''Settings''' parameters
# Go in the '''Calls''' tab
# Click on the Configure Voicemail" button and change the settings you wish to change ( Language, record record prompt, Text to speech, ... )

<table>
<tr><td>
[[Image:MS-Teams-Settings-Voicemail.png|thumb|1000px|left|Teams Settings - Calls - Setup Voicemail]]
</td></tr>
</table>


PS: You can also change the Voicemail Language settings using Powershell ( cf https://docs.microsoft.com/en-us/powershell/module/skype/set-csonlinevoicemailusersettings?view=skype-ps for more information )

<source lang="powershell">
Set-CsOnlineVoicemailUserSettings -Identity login@domain.ch -VoicemailEnabled $true -PromptLanguage de-DE
Set-CsOnlineVoicemailUserSettings -Identity login@domain.ch -VoicemailEnabled $true -PromptLanguage fr-FR
Set-CsOnlineVoicemailUserSettings -Identity login@domain.ch -VoicemailEnabled $true -PromptLanguage en-US


VoicemailEnabled                         : True
PromptLanguage                           : en-US
OofGreetingEnabled                       : False
OofGreetingFollowAutomaticRepliesEnabled : False
OofGreetingFollowCalendarEnabled         : False
ShareData                                : False
CallAnswerRule                           : RegularVoicemail
DefaultGreetingPromptOverwrite           :
DefaultOofGreetingPromptOverwrite        :
TransferTarget                           :

</source>



==CPE MS Teams==

=== Easy Login for an IP Phone Teams Edition using a PC ===

{{Notice|1=Login in on a phone is complex because you cannot copy paste login and password that can be quite long. But you can use this procedure to login a Teams phone without entering any credentials on it !}}

#Power up the MS Teams edition phone on a working network
#Click on the screen asking that you wish to login from a remote PC
#Click on this link on your PC https://microsoft.com/devicelogin
#Type the code that it visible on the phone
#Enter the Teams credentials of the phone
#Done, your phone will connect with the correct account


<table>
<tr><td>
[[Image:MS-Teams-Login-from-PC.png|thumb|800px|left|MS Teams - CPE Login from PC]]
</td></tr>
</table>


=== SIP Devices Phone Management ===

* '''Information''': Since 2022, you can now also link a lot of SIP Phones with your Teams account in order to receive Teams Phone calls on them
* '''Problematic''': You wish to map a SIP Phone to your Teams account
* '''Solution''': Follow the procedure below ( Additional Information available in https://docs.microsoft.com/en-us/microsoftteams/sip-gateway-configure )
# '''Compatible CPE''': Verify that your Phone model is listed in https://docs.microsoft.com/en-us/microsoftteams/sip-gateway-plan#compatible-devices
# '''Allow SIP Devices''': Go to the Teams Admin Center / Voice / Calling policies : https://admin.teams.microsoft.com/policies/calling 
## Edit the Main Calling Policies you are using ( usually the "Global" one )
## Enable "SIP devices can be used for calls", and then select Save. You might need to wait a little bit afterwards
# '''CPE Reset'''
## Remove your SIP Device from any provisioning or redirection server ( @VTX: Simple unmap the SIP account in the Kiosk )
## Factory reset the phone
# '''Declare CPE''' : Go to the Teams Admin Center / Team devices / SIP devices : https://admin.teams.microsoft.com/devices/sipdevices
## Click the "Actions" top right corner button / Provision Devices
## Add the MAC address of the phone 
## Connect to the phone web interface and set the provisioning URL to http://emea.ipp.sdg.teams.microsoft.com
## Restart the phone.
## It will get a Teams logo and might upgrade/downgrade firmware
## Follow wizard in web interface, you will be asked to dial a number from the phone to authenticate it like '''<nowiki>*55*<code></nowiki>'''
## Then the phone will be linked to the platform, now you need to link it with a user
# '''Link phone with a Teams account'''
## Keep following the wizard
## You will be asked to ask end user to connect to https://microsoft.com/devicelogin and enter the activation code to link the phone with the Teams account
## Once done, you can wait or reboot the phone and you will start receiving Teams calls on your SIP device


<table>
<tr><td>
[[Image:Teams-SIP-Device-01.png|thumb|1200px|left|Teams - add SIP Device]]
</td></tr><tr><td>
[[Image:Teams-SIP-Device-02.png|thumb|1200px|left|Teams - Link SIP Device to Users]]
</td></tr>
</table>

=== Teams Edition Phone Management ===
==== Use a configuration Template to setup Language and Timezone on the phones ====

* '''Information''': Phone setup could be managed from Teams Management interface. You can setup some parameters like language, timezone and other options, ...
* '''Solution''': Follow the procedure below 
# Connect to https://admin.teams.microsoft.com/devices/ipphones-configprofile and click the Add button
## Create a new Configuration Profile changing default parameters with your needs
## Timezone: Warning, Switzerland location timezone for Daylight Saving mode is buggy, please use Paris timezone instead. Bug reported to Yealink in " Issue: T58V MS Teams - Daylight Daving problem Switzerland/Bern (ID:105846)"
## If it is still not working afterwards and pending Fix, connect on the phone, go in Time&Date setup and set "Location = Paris"
# Connect to https://admin.teams.microsoft.com/devices/ipphones
## Select the phones for which you wish to set the new profile
## Click the "Assign configuration" button and select the newly created profile you created
# Be patient, it takes a few minutes/hours for the change to be push towards the phones

<table>
<tr><td>
[[Image:MS-Teams-IP-Phone-Profile-01.png|thumb|800px|left|MS Teams Admin - Create a configuration profile|link=https://admin.teams.microsoft.com/devices/ipphones-configprofile]]
</td><td>
[[Image:MS-Teams-IP-Phone-Profile-02.png|thumb|800px|left|MS Teams Admin - Assign a configuration to some phones|link=https://admin.teams.microsoft.com/devices/ipphones]]
</td></tr>
</table>


==== Manage your Teams IP Phones ( firmware upgrade, reboot, screenshot, network capture,... ) ====

{{Warning|1=When performing changes, you need to be really really patient, it can take several hours for your actions to be executed}}

* '''Information''': You can manage your phones behind your Teams environment directly from Teams Admin Web Interface

# Connect to https://admin.teams.microsoft.com/devices/ipphones and execute the actions you wish to do
# Ex: Firmware Update : Select all your phones and enable automatic update with a 90 days delay, so you keep your phones up to date but you are not the 1st customer to beta test a new firmware


=== Contacts Management ===

==== "Your contacts are out and about - Let's bring them in" : Empty contact list ====

* '''Symptoms''': When you go in the contact tab of your Teams phone, you do see an empty list with the message "Your contacts are out and about - Let's bring them in"
* '''Explanation''': This tab will only show you your own and favorites contacts
* '''Solution''': Use the following procedure
# Use the search icon at the top right corner to search for a Teams Contact ( you can call it from there )
# Once you have displayed the contact, you can also use the "..." menu to add this contact if your "All Contacts" list

<table>
<tr><td>
[[Image:MS-Teams-Contact-Tab-01.png|thumb|500px|left|MS Teams Phone - Empty list]]
</td></tr>
</table>


=== Debug Phone ===

==== Download Device logs ====

{{Notice|1=The device logs might be truncated after 12h, so it is important to get the logs as soon as you have a problem}}
{{Notice|1=If the device firmware is not up to date, start by updating it, reporting a bug on a deprecated version doesn't make any sense}}

* '''Problematic''': You wish to get the phone device logs to be able to analyze a problem
* '''Solution''': Follow the procedure below
# Connect to https://admin.teams.microsoft.com/devices/ipphones 
# Select the phone you wish to analyse by clicking on its name
# Click the "Download device logs" button
# Wait 10 minutes
# Click the "History" tab to download the "Diagnostic file"

<table>
<tr><td>
[[Image:MS-Teams-Phone-Debug-01.png|thumb|1000px|left|MS Teams Phone - "Download device logs"]]
</td></tr>
<tr><td>
[[Image:MS-Teams-Phone-Debug-02.png|thumb|1000px|left|MS Teams Phone - "Get Diagnostic file"]]
</td></tr>
</table>

==Other Questions==
===External Access - Allow to chat and call any other Microsoft Teams user===

*'''Problematic''': You would like to be able to chat and talk with other company also using Microsoft Teams ( and also Skype )
*'''Solution''': Follow the procedure below

#Connect to https://admin.teams.microsoft.com/company-wide-settings/external-communications
#Set '''Users can communicate with other Skype for Business and Teams users''' = On

{{Notice|1=You can also decice to allow only some domains}}

<table>
<tr><td>
[[Image:MS-Teams-allow-external-access.png|thumb|1000px|left|Microsoft Teams Admin - Allow external access]]
</td></tr>
</table>


===Service Health - Get notified when there is a problem with MS Teams===

*'''Information''': You can setup Teams Service Health notification in the Admin Center . It will allow you to receive emails when there is a problem with MS Teams platform, or new features
*'''Solution''' : Follow the procedure below

#Connect to https://admin.microsoft.com/adminportal/home#/servicehealth
#Go to '''Preferences''' / '''Email''' tab
##Setup an email and tick '''"Send me email notification about service health"'''
##In '''"Include these issue types"''' : Tick '''"Incidents"''' and '''"Advisories"'''
##In '''"Include these services"''' : Tick at least '''"Teams"'''


<table>
<tr><td>
[[Image:MS-Teams-Service-Health.png|thumb|1000px|left|Microsoft Admin Center - Service Health - Notification]]
</td></tr>
</table>


===How to unassign numbers===

*'''Problematic''': You would like to unmap a number from Teams
*'''Solution''': Use one of the procedure below

# If the user is not needed anymore you can simply delete the user in admin center, it will unmap the number
# (Virtual Teams only): Additionally you need to unmap the "Microsoft Teams Virtual" license in the Hardware Module: [[VoIP:VTX_Teams_Virtual#Hardware_Management_Module_:_Assign_the_Microsoft_Teams_Virtual_license|Unassign the Microsoft Teams Virtual license]]
# Use the VTX Powershell Script "VTX_Teams_Assign_Numbers.ps1" to remove the number from a user: [[VoIP:VTX_Teams_Virtual#Assign.2FUnassign_numbers_using_a_VTX_Powershell_Script_VTX_Teams_Assign_Numbers.ps1|Unassign numbers using the VTX Powershell Script VTX_Teams_Assign_Numbers.ps1]]
# Use Powershell Command Prompt "Remove-CsPhoneNumberAssignment" to manually remove the number from the user:  [[VoIP:VTX_Teams_Virtual#Or_Unassign_numbers_manually_in_Powershell_Command_Prompt|Unassign numbers manually in Powershell Command Prompt - Remove-CsPhoneNumberAssignment]]