Wrong Normalization / Dial Plan applied to Phones in SfB Online Environment with CCE inside

[Anonymous]

Hello,

we have a Problem regarding to the Normalization Rules on Phones.

Inside the SfB Online environment there is an Cloud Connector Edition for local PSTN-Breakout.

With the Skype for Business Client the users are able to make Calls, the Normalization for Germany works fine (Default Tenant Settings, none Custom Rules).

With Polycom VVX Phones there is an issue and the normalization for Germany is not applied. 
Checking the Information under Diagnostics > Skype for Business Status i have the following entry for Dial Plan:

^011(\d+)$@+$1|^((\+)?(\d+))(;)?(ext|extn|EXT|EXTN|x|X)(=)?(\d+)$@$1;ext=$7|^1(\d+)$@+1$1|^(\d{10})$@+1$1| 

This seems not correct for me (as i am not understand how to build regular expressions).

In a Skype for Business Environment with a Microsoft Dial Plan applied and Cloud PSTN-Breakout, the same phone shows me the following Dial Plan:

^00(\d+)$@+$1|^((\+)?(\d+))(;)?(ext|extn|EXT|EXTN|x|X)(=)?(\d+)$@$1;ext=$7|^0(\d+)$@+49$1|

Can anyone help me to fix this issue? I have to find a solution cause people cannot use their phone

[SteffenBaierUK]

Hello @HV_MA,

welcome to the Polycom Community.

It is always useful to include the currently used UC Software version as issues experienced or a question asked may already be addressed in a newer release.

This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.

The above is also stated in the "Must Read First" and is the absolute minimum requirement every new post should include. .

In addition providing us with this basic information gives Polycom an idea what Software Versions are used in the field and avoids wasting time trying to troubleshoot issues which have already been addressed.

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP or UC Software Version of my Phone?
Resolution: Please check here

Most likely the Digitmap is the result of the inbound provisioning from the Skype for Business Server so I suggest you check with our Partner Microsoft once you confirmed that the phone is running a currently supported software version like UC Software 5.7.1

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

Hi guys,

Microsoft has basically two normalization rules on Skype for Business Online that are "DialPlan" and "TenantDialPlan". DialPlan is a set of normalization rules predefined by Microsoft and is automatically assined to the users based on their location. TenantDialPlan allows us to create custom normalization rules and assigned them to the users. Actually, both sets of rules are asigned to the user, but TenantDialPlan has higher priority over DialPlan, so, we are able to create any digit manipulation we want.

There is a Powershell command where we can check the current normalization rules assigned to a user and it will show TenantDialPlan rules followed by DialPlan rules.

In my case, all of the configurations on Microsoft side are correctly and TenantDialPlan is working perfectly on Skype for Business for Windows, but it is not working on Polycom endpoints (Trio or VVX).

When I browse to "Miscellaneous info" and I check "Dialplan", I think I should see exactly the same rules I see when I check via Powershell, but instead my rules, I see exactl the same rules listed by the user HW_MA.

I am running version 5.8.1 on my VVX 600 and 5.7.1 on my Trio 8800.

It looks like Polycom endpoints are not able to read Microsoft's dialplans.

I have three other customers with the same problem.

I would like to understand what is the problem and how to solve that, because dial in E.164 is not easy to normal users.

Thanks,

[SteffenBaierUK]

Hello @rui.carvalho,

welcome to the Polycom Community.

I can only ask you to raise this with our support team as we are 3PIP qualified and we would have many more support tickets raised if there was a known issue.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

End Customers are unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter providing your MAC address or your Polycom devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Polycom device from.

If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

Hi 

I was wondering, were you able to solve your issue?

I have the same issue right now. When i test the DialPlan via PowerShell it get's translated correctly but the VVX does not receive the correct DialPlan from the SfBO Cloud.

I have managed to implement a workaround but this has to be done on every phone manually which is very frustrating.

Please let me know if you have found a solution for this issue. Thanks

[Anonymous]

Hi everybody,
Sorry for my delayed reply.
I found out what was going on.
The default normalization on Microsoft Tenants were always based on online dialplans and if you wish to use an onpremises dialplan you needed to define that using the following command:

Set-CsTenantHybridConfiguration -UseOnPremDialPlan $True

The default configuration was always False.
For some reason, this option was defined as True in many Tenants that I manage, so, I just ran this powershell command and the problem was solved:

Set-CsTenantHybridConfiguration -UseOnPremDialPlan $False

It defined that you will use online dialplans instead of onpremises ones.
It looks like Polycom endpoints don't read online dialplans with this option set to True, which is correct on my understanding. I just don't know why Skype for Business client didn't have the same behavior.
What is important is that everything is working perfect now!
Thanks for all help.