Accepted Solutions
If you want to control incoming calls to a directory number you would need to put the directory numbers in a partition that is seen only by whoever that should be able to make a call to the directory number. For outbound calls you’ll control that by what partitions that you make available in the calling search space of the device that makes the the call.
I see. Thanks for the clarification. Likely due to English not being your first language you where not very clear in what you wrote. You actually wrote that there is a delay for 4-5 rings before the call rings the IP phone and then it reaches Teams after an undefined time. See the screenshot where I have marked the various parts to make it clearer.
That said have you verified that there is no delay defined on your RD/RDP combo? As an example see this screenshot where there is a 4 second delay before the call will ring to the defined remote destination number.
Can you please explain how you have configured the integration on the CM end? Are you using Mobile Connect features for the same time ringing on the two platforms?
Not very into how calling works on the MS platform, but wouldn’t what you suggest also turn off the ability to receive inbound calls?
When we evaluated Teams calling in integration with our CM system we used Mobile Connect to get both sides to ring simultaneously. That’s why I asked if the OP also used that for their integration.
With Mobile Connect functionality and the fact that it does a reverse call anchor for calls that originates from the remote destination number of the remote destination profile or from the mobile identity remote destination number if TCT/BOT/TAB type of devices are used for the integration you can control where it can call by the device CSS. If the call is properly identified as coming from the remote destination number it will honour the restriction(s) set by the CSS on the MC device.
This is often overlooked as the calling number might not make a match and therefore not anchor the call to the MC device.
This is in essence a matter of having correct configuration so that the calling number matches what is defined on the remote destination number.
My personal preference is to make the needed adjustment on the SBC(s) that integrates the two disparate systems so that the calling number that egress the SBC to CM makes a match.
@shahulhameed I described how you can do what you ask about in CM. If there was something unclear in my answer please ask for specifics on that part and I’ll try to explain that in more details.
To add to my previous answer I would recommend you to use the older style of Mobile Connect configuration with RDP and RD, instead of the newer option where the Webex/Jabber mobile device (TCT/BOT/TAB) has a Mobile Identity, as that would impose the calling restriction onto these devices as well, ie not just for the Teams client, and that might not be what you want. If you isolate the integration for Teams to use the RDP and RD combination you’ll have the possibility to put the restriction on this alone as you can set the CSS on the RDP to something that restricts the calls to what you want.
Please have in mind that there are two configuration values on a RDP that has the word CSS in it, CSS and Redirecting CSS. The later is used for routing calls to the remote destination number on the RD and the former is what controls where you can call to from the RDP “device” when the call is identified as coming from the remote destination number.
As there is not one way for how this can be setup it would be better if you where to share how your Mobile Connect configuration for the integration looks like so that I can make specific suggestions on how to configure the RDP and RD. In general you can follow any configuration guide for how to configure RDP and RD, just set the Reroute CSS to point to your SBC(s) that integrates with the Microsoft Teams calling platform. For the calling part I’ve already outlined what you’d need to do to make the call anchor on the RDP so that it uses the CSS set on the RDP.
Great, thank you! So by the look of it you have the basics of the whole setup in place. If I understand you correctly you add the prefixed 8 on the RP? I would recommend you to do this already on the RD number and have the RP match the 8 + the number. What you then need to do is to make sure that the calling number from Teams comes into CM with the prefixed 8 so that it matches with the number on the RD. By this it will anchor the call to the RDP and use the CSS that you have configured the RDP to use. Adding the 8 is easily done in the SBC as it traverses it on its way to CM. There is not more to it than that.
