Call2Teams - Customer/Partner
In order to maintain the users existing phone number when calling to/from Microsoft Teams, the Single Number Reach feature of the CUCM shall be utilized. This functionality utilized is such that upon any call into the users existing numbers, other numbers may simultaneously be called. Users may pick up an incoming call on either Teams or any legacy registered devices/numbers and the call in progress is handled by Teams.
Instructions on how to configure Single Number Reach for Cisco Call Manager may be found here.
When configuring the Remote Destination profile, this is done by setting the users normal number, prepended with an 8 (or other similar determinable digit) as the Destination Number. The routing pattern is later configured to route calls out to Call2Teams when the leading 8 is detected
1. Navigate to the Services tab and select Trunk, Then select the Cisco CUBE (CUCM) Template
2. Add the number ranges to be serviced by the trunk. This can be a small test range to begin with
3. Add the public IP address or FQDN of the PBX/Proxy into the SIP Domain filed and IP into the Trunk Source IP’s field. Select the appropriate Authentication Type for your PBX/Proxy
4. Once saved, make note of the IP addresses assigned. These are the endpoints the SIP trunk from your PBX/Proxy should be set up to connect to
Step 1: Remote Destination Profile Configuration
Create a Remote Destination Profile (RDP) for the end user.
In order to create a new RDP profile, navigate to Device > Device Settings > Remote Destination Profile > Add new.
Click Save, now you can see an option to add a new Directory number (DN).
Click Add a new DN to navigate to directory number configuration, where you need to specify the directory number of the desk phone with which you need to associate the RDP and then click Save.
It is also important to note that the CUCM attempts to reach the remote destination through the Rerouting calling search Space
It is recommended to ensure the Maximum Wait Time for Desk Pickup is set to ZERO in order for Teams to properly end the call without delay on hang up.
After you save the directory number, specify the correct CSS against Rerouting calling search space, click Add a New Remote Destination, as shown in the image:
Remote Destination Configuration
Specify the Destination number, as this is the number for your Remote destination. This is where we shall assign the users normal number, pre-pended with 8
Ensure that the check box, Enable Unified Mobility features, Enable Single Number Reach, Enable Move to Mobile is checked.
Under the section Timer information, you can specify the amount of delay before which the Remote Destination should ring. In case if the Remote Destination is required to ring immediately, you should set the Wait* as zero.
It is also important to calibrate the time in which the service provider of the remote destination sends the call to the voice-mail of the remote destination. The Stop ringing this phone after value should be set lesser then that to ensure that call does not go to the voicemail of the cell phone. This time value is specified against Stop ringing this phone after.
Step 2: Create Route Pattern
Create a route pattern with the RDP number as 8.extension and set the Gateway/Route List to the newly created Call2Teams trunk.
Discard PreDot digits and create a mask for the route pattern that is as long as the extension
Please note, the above is used as an illustration for handling US numbers of 11 digits with +1 country code provided. This should be adjusted according to your requirements and in line with the route pattern to match the SBC requirement.
Call2Teams Setup - Adding Users
You can now go back to the Call2Teams portal and assign the Trunk Numbers to users and run a sync.
INVITES out from Teams should honour the translation and call through the CUCM.
INVITES from CUCM should also be passed through to the Call2Teams Trunk and ring the Teams client associated.