login | register
Sun 07 of Sep, 2008 [01:25 UTC]

voip-info.org

History

Polycom 430 Notes

Created by: 3.141592pie,Last modification on Tue 21 of Nov, 2006 [14:30 UTC] by stoffel

Polycom 430 Notes


The 430 will need it's own page eventually which I don't really have the experience to author. Here are a couple of notes and gotchas in the meantime.

Firmware support

The IP 430 supports firmware 1.6.6.0046 and higher. The release notes for some inexplicable reason refer to this as 1.6.6 B. Please note that 1.6.6.0032 is not supported by the 430 and won't load correctly via FTP. If you need firmware it can be found at http://www.freedomphones.net/polycom/files/.

Always use the current sip.cfg files provided with the firmware updates! Failure to do so may cause problems in your environment!

Stock Firmware Limitations

The Stock Firmware and Bootrom that comes with the phones (As of 8/20/06) has several problems. Using the stock config settings of the phone and pulling from FTP, boot times can be upwards to an hour. Trying to install the new firmware 1.6.7 and bootrom 3.2.1 via FTP can causes the phone to go into constant reboot loop. It seems that the phone gets hung up somewhere in installing either the bootrom or the firmware through FTP. At this point, the phone won't be able to get any type of firmware or bootrom from the server via FTP. Even trying the latest 3.2.2 bootrom and 2.0.1 firmware yielded no results. After talking with support at TelephonyDepot.com and the #asterisk channel on Freenode, it seems the some people were not having issues with the phones. TelephoneDepot.com said they use TFTP and the ip430's work fine for them and suggested trying TFTP instead of FTP. After setting up atftpd to just provide new firmware and the bootrom, and configuring the phone to use tftp instead of ftp, the ip430 pulled the new 2.0.1 firmware and the 3.2.2 bootrom. The phone was transformed from a paper weight to what it should have been. Boot times are 2-4 minutes, and the improvements to the boot process are much appreciated. Changing the phone back to using FTP works fine now. However, everything is not happy yet. Bootrom 3.2.2 and firmware 2.0.1 causes a new set of problems.

Bootrom 3.2.2 & SIP 2.01

  • Be sure you use the LATEST config files that CAME with the v2.01 firmware!
  • If you do not, your phones may not work properly.
  • Found a bug with the 430s and 2.0.1 SIP and it invoves the SIP.cfg file and dialmaps: You can not use a "," in your dialmap with the 430 otherwise when it reaches it, it will lock up. This does not happen on the 601 and only seems to effect the 430.

Headset distortion SIP 2.01 with default SIP.cfg

I had some noise distortion with firmware 2.01 and the supplied sip.cfg.
After searching around in the sip.cfg I adjusted the following parameter:

  • Original value: voice.headset.txag.adjust.IP_430="39"
  • My new value: voice.headset.txag.adjust.IP_430="0"


The info below is invalid, but kept it for reference.

"Bootrom 3.2.2 and Firmware 2.0.1 problems
So after installing the new firmware and bootrom, it looked like all the problems were solved. Except for one tiny, major issue, the new firmware caused all the phones that were updated with it (IP430's and IP601's at this point) to not register with the asterisk server. Only by hard coding the IP address and UDP Only in the sip configuration options on the phone would it register with the Asterisk server again. It seems that this problem is caused by not using the new phone1.cfg file included with 2.0.1. So you will need to update your configs with this new file."

Flash settings reset

All other polycom phones will reset their flash settings when the keys 4,6,8,* are held simultaneously, but the IP 430 uses 1,3,5,7 instead.

Comments

Comments Filter
222

333Set IP430 to use SIP INFO for DTMF Tones

by pjrouse, Tuesday 20 of February, 2007 [10:26:24 UTC]
Does anyone know if or how you can set the IP430 to use SIP INFO for sending DTMF tones?

I have a Swyx IP PBX which will not give users with Polycom phones access to their voicemail, unless the DTMF tones are sent via SIP INFO.

Thanks in advance.

Paul Rouse
222

333Can't find delete key

by NateBell, Wednesday 24 of January, 2007 [17:16:54 UTC]
I haven't managed to find an answer elsewhere, so I'll ask here:
When entering text with the 430, how do I erase a mistake I've made. The only solution I can find is to cancel my changes and start again, but there has to be a better way! Any help would be much appreciated!

Edit: Nevermind. I found it. It's the context sensitive key labeled <<
222

333Polycom 430 no sntp sync

by gtsupport, Thursday 30 of November, 2006 [16:38:03 UTC]
I have 5 Polycom 430's running 3.2.2 and 2.0.1 and none of them will adjust for the time zone. I have tried internal SNTP servers and public SNTP servers. I have also tried several combinations of firmware + SIP and they all perfrom the same. The phones sync with GMT but will not adjust for the time zone (EST -5)

Any ideas?
222

333Polycom 430 + Aptela service

by manical, Friday 29 of September, 2006 [23:40:33 UTC]
I have been having a slight problem with the quality of the calls into the phone.

Everything seems to work well until someone calls in with either a Sprint or Verizon cell phone. It cuts in and out and there is a lot of static. Is there something I can do about it?

Thanks...

222

333Bug with SIP 2.01 and IP430

by danursuline, Friday 29 of September, 2006 [19:56:39 UTC]
  • Found a bug with the 430s and 2.0.1 SIP and it invoves the SIP.cfg file and dialmaps: You can not use a "," in your dialmap with the 430 otherwise when it reaches it, it will lock up. This does not happen on the 601 and only seems to effect the 430.
222

333Bootrom 3.2.2.0019 - SIP 2.01.0291

by danursuline, Friday 22 of September, 2006 [16:00:56 UTC]
If everyone is OK with it I would like to redo this page to make it current! Almost all the info above is inaccurate - I have had no problems with v1.67 or 2.01 firmware upgrading or downgrading etc etc... Any problems are most likely config problems and not actual issues with the firmware.

I have updated my 601 and 430 phones to the latest firmware without any issues.

ALWAYS use latest sip.cfg and phone1.cfg !! And remember to document everything!
There are significant changes from 1.x to 2.x versions.
There are absolutely no problems with the firmware and can 100% say that its most definitely a problem with your config if your having an issue with the v2.0 firmware.

Email me dbaker@ursulinestl.org if you have questions.


222

333V2.0 firmware?

by wpns, Monday 18 of September, 2006 [17:38:06 UTC]
Has anyone successfully updated IP430 phones to BootROM 3.2.2, SIP 2.0.1? After Paul Skinner's problems, I'm a bit leery of upgrading...

Thanks!

222

333Proper SIP.CFG

by bengrech, Thursday 14 of September, 2006 [08:29:32 UTC]
May I ask you guys with a proper SIP.CFG to upload a sample for the IP430, or any other config files to get things working a treat!
222

333Make sure you are always USING CURRENT sip.cfg

by danursuline, Wednesday 13 of September, 2006 [22:22:59 UTC]
Please everyone - before you say your 430 is broken, make sure your config isnt to blame! I have never had a problem with the 430s I have close to 80 of them here along with another 20 601s, and all provisioned.

1) dont mess with the sip.cfg file unless you *KNOW* what your doing - you can do alot of good and ALOT OF BAD!
2) DOCUMENT ALL sip.cfg changes, so when new sip versions come out, you can *READ* the release notes and find out what has changed! If you do not document your sip.cfg and then just blindly update your sip app you WILL have problems sooner or later.
3)If you want to mess with your config do not change your global sip.cfg, but make a new copy just for the phone your playing with (dont mess up all your users because your curious)

Hey if anyone needs help with this phone email me :
daniel.baker AT gmail.com
222

333follow-up <resolution>

by dolesec, Tuesday 12 of September, 2006 [16:58:49 UTC]
it was simply the config file ...

the partner we used to purchase the phones ( http://www.netxusa.com ) assisted us and everything is perfect - we are continuing with the roll-out of the Ip430's