Unsupported xml digitmaps for polycom to autodial

[rattler555]

Hello All.

I was very surprised that we cannot autodial Polycom's out of the box. This should be a standard feature. Anyways, does anyone have a working xml snip of the dialplan?

It would be very much appreciated. US - 10 digit and 11 digit. Thanks.

 

[rattler555]

Hello All.

I was very surprised that we cannot autodial Polycom's out of the box. This should be a standard feature. Anyways, does anyone have a working xml snip of the dialplan?

It would be very much appreciated. US - 10 digit and 11 digit. Thanks.

Here's the config to accomplish this. Will work for 4 digit extension, 911, 933(telnyx 911 testing), 10 and 11 digit dialing. Add this to a copy of the polycom template, and re-provision with these edits.

<dialplan
dialplan.digitmap=""
dialplan.digitmap.timeout=""
dialplan.1.digitmap="911|[1‐9]xxxT|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|933"
dialplan.1.digitmap.timeout="3"
/>

 

[rattler555]

Why is this unsupported? Why isnt this in the default template? Ever other cloud providers has some support for digit maps.

 

[jcostlow]

The templates are made by the manufacturer and any modifications from default make you in an unsupported configuration. You can use it but if you need help 3CX will ask you to put back to the default template.

I would say you could reach out to Polycom and see if they will make the change like Snom did but from previous Polycom experiences I don't think you would get far.

 

[rattler555]

Don't need support from Polycom. This should be a 3CX template supported configuration variable. But, I see it's not. So now, I need to see a bunch of phones with a red highlight.

 

[jcostlow]

I agree lots are used to the auto dial and it stinks that isn't default. When I asked Snom about it they did change the template to auto dial after 6 seconds which helped. That is why I mentioned Polycom support might can adjust the default template.

We have customers we are migrating from legacy KTS systems we have sold for years (I won't mention name as I can't risk losing my certification until all are moved). There are things they have had to adjust to. Pros and Cons to everything.

 

[rattler555]

I agree lots are used to the auto dial and it stinks that isn't default. When I asked Snom about it they did change the template to auto dial after 6 seconds which helped. That is why I mentioned Polycom support might can adjust the default template.

We have customers we are migrating from legacy KTS systems we have sold for years (I won't mention name as I can't risk losing my certification until all are moved). There are things they have had to adjust to. Pros and Cons to everything.

Migrating over to Fanvil, but there are 400 phones, so it'll be mixed for a while until we lifecycle. Autodial with modified template works. It's a little bit of a PITA with provisioning, but having a transparent migration will ensure customer happiness and renewal.

Thanks for the info.

 

[JohnS_3CX]

Hi @rattler555

It's fine, you can still share your solution here if it helps others, but since it requires custom templates it will be labelled as unsupported. You might be very proficient at what you do, but not all our forum members will have that level of skill/knowledge so they should be aware when reading the thread that this will put them in an unsupported scenario.

"Unsupported" means that if you have issues not occurring with the default template, 3CX will not be able to provide you with support.

We will only support the firmware version and template that the manufacturer has interop'd with 3CX, and the rest is entirely up to you to modify, test, maintain, and support.


Now regarding some of the other points:

- Hot desking is not going to happen on Polycom due to software limitations causing a reboot during login as far as I'm aware at least

- Autodial with a timeout might happen at a later stage but no promises on that one!

- Polycom phones are under the "legacy" section so they have limited feature set from the get go. There are no plans on changing their status in the future so what you see now is what you get, unless you can make a case to the manufacturer convincing them to develop the firmware and templates further.


Hope this clears things up!