# Polycom dial string problems involving "#"

**URL:** <https://community.asterisk.org/t/polycom-dial-string-problems-involving/5504>\
**Category:** Asterisk Support\
**Created:** [April 4, 2006, 5:22pm UTC](https://community.asterisk.org/t/polycom-dial-string-problems-involving/5504 "2006-04-04T17:22:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pete\_Rittwage](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@Pete\_Rittwage](https://community.asterisk.org/u/Pete_Rittwage)\
**Post date:** [April 4, 2006, 5:22pm UTC](https://community.asterisk.org/t/polycom-dial-string-problems-involving/5504/1 "2006-04-04T17:22:40Z")

</div>

Hello,

This isn’t an Asterisk problem per se.

Has anyone experience or found a way to fix the configuration of the new Polycom firmwares (\> 1.6.2) so that you can have a “#” symbol in the dial string? 1.6.3, 1.6.4, and 1.6.5 seem to not allow it any more- you just get a busy signal and communication to the \* server never occurs. All earlier versions of the firmware allow this.

I’ll have to rewrite a lot of dialplans to upgrade the phones if it isn’t possible, and painfully retrain users. ☹

Pete Rittwage