FAQ:Teams

General Questions[edit | edit source]

What are the differences between a "Teams Connect" and a "Teams Virtual" ?[edit | edit source]


	Teams Connect	Teams Virtual
Short Description	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
Analogy	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
VTX Service and Licenses Needed	a "Teams Connect" ( billed per number of concurrent calls + number of numbers ) N/A per user	a VPBX Service ( billed per number of numbers ) a "Teams Virtual" license per user
Microsoft Licenses Needed	Microsoft Teams per user Microsoft Phone System per user	Microsoft Teams per user Microsoft Phone System per user
Pros	- 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
Cons	- 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 ?[edit | edit source]

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 ?[edit | edit source]

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.

Frequent Errors[edit | edit source]

New-CsOnlineVoiceRoutingPolicy - Cannot find specified Online PSTN usage[edit | edit source]

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 FAQ:Teams#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

Teams Error - Cannot Find Online PSTN Usage - Wait a few hours and try again

Cannot Import Module SkypeOnlineConnector[edit | edit source]

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

Get-ExecutionPolicy
Restricted

Solution

Set-ExecutionPolicy RemoteSigned -Force

Get-ExecutionPolicy
RemoteSigned

Error that you are getting

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

Get-CsOnlinePowerShellEndpoint : The remote name could not be resolved: 'lyncdiscover.xxx'[edit | edit source]

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: Please verify and dix your Admin account DNS setup
Workaround : Add the suffix "-OverrideAdminDomain $MSTeamsDomain" to the New-CsOnlineSession command

Incoming Call not working[edit | edit source]

404 Not found : Number hasn't been assigned[edit | edit source]

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

VoIP Analyser - Call sent to Teams but rejected

Manage your Voicemail Settings[edit | edit source]

Symptoms: Your voicemail is answering your call
Solution: Please read https://support.office.com/article/manage-your-call-settings-in-teams-456cb611-3477-496f-b31a-6ab752a7595f

CPE MS Teams[edit | edit source]

Setup a Yealink Teams Edition[edit | edit source]

Plug the phone with MS Teams edition on a working network
Click on the screen asking that you wish to login from a remote PC
Enter https://microsoft.com/devicelogin on your PC
Type the code visible on the phone
Enter the provided credentials

MS Teams - CPE Login from PC