Forum Discussion
Teams Direct Routing Extension Transfer Failed
Hi Mufarak,
Of course it is E.164.
I have this kind of setup for TEL URI "TEL:+2XXX" to all Teams user extension and I also setup internal extension as false globally. Do I have to set internal extension as true for this "2XXX" format perhaps? So it won't get thrown into SBC.
Are you using User Dial Plan for the Users? Normally how i setup is.
User tel URI : +62191012XXX By Default Service Country Dial Plan applies and will create user dial plan with 2XXX & 3XXX with internal set to false. if i set to false and configure pstn usage and route, it will route the calls to GW.
From there, we will divert back to Teams. with Prefix as +6219101 2XXX . Its workaround. Hope you know how Online Dial Plan works but still check the below links for understanding. Apart from Service Location dial plan, we can create User Dial plan as per our requirements. If internal extension is set to false, it will route the calls to PSTN GW only .
https://blog.insynctechnology.com.au/skype-business-cloud-pbx-tenant-dial-plans-landed
With Service Dial Plan you mean country specific Service Dial plan based on location of the user? I thought that country service dial plan is basically merged with user defined tenant dial plan or global tenant dial plan. Anyway all the time as merged and service one in place. Isn't it like that?
Internal Extension parameter set on true or false will not result in different behavior of routing the call. I believe that this parameter has only some effect if you have OptimizeDeviceDialing in place of the dialplan. Reading the documentation I assume this is just for ignoring the need of prefix access code for external call (if set).
