Put Teams users on your PBX the same way you provision desk phones. TeamMate reads each user’s configuration from your existing provisioning server, sets up their SIP account and number, and registers them, in bulk.
Free 30-day proof of concept for service providers.
With PBX Connector, every Teams user registers to their own SIP extension on your PBX, which normally means entering a SIP user, authentication ID and password for each one. SIP auto-provisioning removes that step. Point TeamMate at the provisioning server your PBX already uses for phones, and it fetches each user’s configuration file, saves their SIP credentials and phone number, and registers them to the PBX. It works in the TeamMate portal and through the API.
TeamMate reads Yealink-compatible configuration files named after the device MAC address, served over HTTPS from the server you already run.
SIP user, authentication ID and password come straight from the file, so there are no typos and no passwords passed around in spreadsheets.
TeamMate takes each user’s number from the file, account.1.label by default, or you set numbers in the portal.
Turn it on for a whole PBX so every user is provisioned, or switch it on user by user.
Load hundreds of users from a CSV with their MAC addresses, validate the file, then submit.
Re-provision a user from the portal, or have the PBX send a check-sync SIP NOTIFY after a password change.
Teams users have no physical phone, so each one gets a stand-in MAC address. Choose who creates it.
Create placeholder MAC addresses for Teams users on your provisioning server, then bulk upload the users with those MAC addresses to TeamMate. TeamMate fetches each file and provisions the user.
Create users in TeamMate with Auto Assign UUID on. TeamMate generates a unique ID for each user, and your PBX admin uses it as the MAC address for that user’s device.
Use HTTPS, add a provisioning username and password for protected files, for the whole PBX or per user, and upload a TLS certificate if your server needs one.
In the PBX settings, turn on SIP auto-provisioning, enter the provisioning server URL and choose the field that holds the phone number.
Add users one at a time or by CSV, with a MAC address or AUTO_ASSIGN. TeamMate fetches each configuration file.
TeamMate saves the credentials and registers each user to the PBX, usually within minutes. The status icon turns from yellow to green.
SIP auto-provisioning has been tested with Metaswitch, NetSapiens and Crexendo, and Phonism. See also PBX Connector, extension dialing and Bespoke Access for onboarding customers from your own portal.
A PBX Connector feature that sets up Teams users on your PBX from the device provisioning server you already run. TeamMate fetches each user’s configuration file, saves their SIP credentials and phone number, and registers them to the PBX, so no one has to copy SIP passwords by hand.
Any server that serves Yealink-compatible plain-text configuration files named after the device MAC address, such as 0015651133aa.cfg, over HTTPS. It has been tested with Metaswitch, NetSapiens and Crexendo, and Phonism.
No. Either create placeholder MAC addresses on your provisioning server and upload them with your users, or let TeamMate generate a unique ID for each user and use it as the MAC address on the PBX.
From a field in the configuration file, account.1.label by default, and you can choose another field. If your files do not carry the number, enter it in the TeamMate portal instead.
Usually a few minutes, and up to 10. A status icon in the users list turns from yellow to green when the user is provisioned, and any errors appear in the activity feed.
Select Sync Auto Provision for the user in the portal, or have your PBX send a check-sync SIP NOTIFY, and TeamMate fetches the configuration again.
Yes. Turn it on for a whole PBX, so every user on it is provisioned, or leave it off for the PBX and turn it on user by user.
Yes. Add a provisioning username and password, for the whole PBX or per user, and upload a TLS certificate if your server needs one.
See SIP auto-provisioning in a live demo, or try it with your own provisioning server.
Free 30-day proof of concept for service providers.