Announcing the UC320W 2.3 Release Candidate firmware

Unanswered Question
Aug 6th, 2012
User Badges:
  • Silver, 250 points or more


General availability release announcement can be found here:



Today  we are announcing the release of the Cisco UC320W 2.3.1 Release Candidate firmware feature release. Release Candidate quality means that is has gone through Cisco’s internal testing, but there might be a few new issues that surface in real world deployments.  Partners are encouraged to test the firmware in their labs before deploying on their customers systems.  Installation instructions, features and bug fixes are described in the 2.3.1 release notes below.

NOTE: The open source tar file will not be available upon request because this is an RC release.  Proceed with the installation of this firmware only if you agree with these terms and conditions.


The 2.3.1 firmware version is available via the Cloud now by using the attached Platform Modification File (PMF).   This firmware will not be posted on CCO.  A General Availability release will be made available at a later date.



  1. Perform a system backup of the UC320W before loading the PMF file.
  2. Download the PMF and save to your PC.
  3. Unzip the PMF file.
  4. Launch and log into the UC320W Configuration Utility.
  5. Click on the Status option at the top.
  6. Click on Devices submenu.
  7. Click on Alter PMFs button.
  8. Click Add PMF from your PC button, select the unzipped file and install.
  9. Click Done to close the dialog.

NOTE:  If  you are on a release version lower than 2.1.2, please see this  discussion for more information and a workaround for the Adobe Flash  Player version 11 compatibility issue:

Release Notes can be found here:  >>> LINK <<<

Any problems found on the Release Candidate firmware should be reported  immediately to the Cisco Small Business Customer Support Center.  When calling the SBCS please indicate that you  are a Release Candidate participant and specify the firmware version  found on the UC320W Configuration Utility login or About screen as well as your Region.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
danplacek Tue, 08/07/2012 - 13:17
User Badges:
  • Silver, 250 points or more

Just installed this for a client who was having issues.

The upgrade went smoothly.

Thumbs up on the UI improvements and additional diagnostic tools!

Philip Denton Wed, 08/08/2012 - 22:49
User Badges:

Daniel, what issues did the upgrade fix for your client?  I'm in the middle of an install myself but I'm a little wary of installing software that's not out for general release just yet...

danplacek Thu, 08/09/2012 - 08:19
User Badges:
  • Silver, 250 points or more


The customer was having issues with a phone freezing and BLF being inaccurate (showing amber for a phone that was not offline or offhook)... so far that hasn't happened on this new firmware.

We have another customer who is unable to read his CDR's in excel because of a bug that is fixed in this firmware -- I'll be upgrading that one this week as well.

mikejobson Thu, 08/09/2012 - 03:50
User Badges:

I noticed a couple of things...

If I get a missed call now the number to redial is now 9 and the number with the steering digit added but it appears in the format 944... etc. This doesn't work to redial as it needs to be 90044... etc. It appears the number coming in on the header begins with +44 and so it either needs to add in the 00 or lose +44 and replace with 0. This is probably specific to the UK but it's now worse as I have to edit the number more!

Also the ringtone issue in the UK is still a problem.



rbordner Thu, 08/09/2012 - 07:26
User Badges:
  • Cisco Employee,


Thank you for your comments, I will check with the team on the UK support of the Missed Call feature.

Also please provide any additional info on the UK ringtone issue is so I can understand the issue better.



mikejobson Thu, 08/09/2012 - 07:33
User Badges:

I have solved the missed call feature by requesting my provider masks the +44 and places a 0 instead on the headers. Not ideal though so I'll leave that with you.

The ringtone has been a problem since the unit was released as if you go to User Prefs / Audio Prefs and play the ringtones they only play about 0.5 seconds of the clip twice in succession. This obviously is to make the Retro one sound like a UK ring but affects all but the Cisco Synth one.

Paul Williamson Sat, 08/11/2012 - 04:11
User Badges:

I have to say this is a very disappointing firmware release.  As far as I see it, one of the main reasons for purchasing a VOIP PBX has to be the ability to have remote users connect as if they are sat at their desk in the office.

This is a much requested feature and one I have read is on the roadmap.  Is it ever likely to be implemented on the UC320 and if so, what kind of timescale are we looking at?

I think the majority of users who need this facility would rather know if it's worth waiting or whether it would be better to dump the UC320 and look at other equipment.

Whilst we are talking about missing features, any news on a WIFI phone becoming available?  I really don't see why it is such an issue to write some new firmware for the WIP310 or another of your wifi handsets, modify the UC320 firmware and make them play nicely together?  Am I missing something or is there another agenda with Cisco for implementing a wifi handset?

Apologies for sounding negative but it does appear that the really useful features are being held back.



mikejobson Sat, 08/11/2012 - 04:47
User Badges:

I agree totally! Some answers on all of the above please!

Philip Denton Sun, 08/12/2012 - 20:36
User Badges:

I'm a mere Cisco partner like the rest of you guys, but I have to say that I consider the UC320W to be fairly full-featured for the price point at which it is offered.  I understand wanting the Wi-Fi phones and remote teleworkers but there's already an SMB product with those features called the UC500 series.  Maybe it's part of the greater positioning strategy for Cisco to leave those features for the UC300's big brother?

If your customers are really burning for Wireless phones that badly couldn't you give them some spiffy analog handsets?  Or perhaps find a low-end Plantronics headset that fits their budget?

Paul Williamson Mon, 08/13/2012 - 01:16
User Badges:

Morning Phil,

The analogue/DECT handsets are a great idea and works really well..... unless you have a fax machine plugged into the port.  Then you're a bit stumped!!

You have hit the nail on the head though about the UC500, which was kind of my point about dumping the UC320 if it's not something that Cisco are going to implement.  I'm sure there's a number of people that have installed UC320's on the basis that these features will be implemented in a future firmware release but surely if Cisco have changed their mind it would be better for them to say, "sorry it's no longer on the roadmap, start installing the UC500 if you need those features".  Although I still maintain that the main point of a VOIP pbx is the ability to have remote workers.

What does everyone else think?

All the best,


nmanglik Mon, 08/13/2012 - 13:40
User Badges:


The teleworker feature is not available in the coming release (2.3) of UC320 and it remains under evaluation. If teleworker feature is a priority, please start installing UC500.



Paul Williamson Thu, 08/16/2012 - 12:52
User Badges:

Thanks Nitin,

I missed your post earlier.  Your candid response is much appreciated.  Given that it's now just under evaluation, does that mean that it's no longer on the roadmap?  Also, any news on wifi phones, ie will that feature happen or is it also just under evaluation?

We are still using the Uc320 for the moment but will now replace it and pop it in a cupboard so to speak in case we can use it in the future at another site if the additional functionality is brought into place.



danplacek Thu, 08/16/2012 - 13:03
User Badges:
  • Silver, 250 points or more

Since when is the teleworker feature "under evaluation"?

It has always been advertised as being "on the roadmap" before...

Alberto Montilla Thu, 08/16/2012 - 14:24
User Badges:
  • Cisco Employee,

Hi Daniel;

Let me explain some of the jargon, teleworker feature has been on the roadmap since day one, although not committed (which is the same as under evaluation).

There is currently no target date for implementing teleworker, so would not like to create false expectation on its availability. That's reason why we are recommending to upgrade to the UC500 if teleworker is a required feature.


hamish.jones Tue, 08/14/2012 - 17:42
User Badges:

Hello Paul,

I too was waiting for the remote worker release, I have a thought would using an SPA525 and using it's VPN ability back to the UC320 could theoretically work as a remote exension work around, I haven't tried it but think it may be an answer to the unwillingness of Cisco to allow this solution,



Paul Williamson Wed, 08/15/2012 - 03:37
User Badges:

Morning Hamish

I'm not sure how successful this would be.  I'm looking for a relatively small system for a branch office so the UC320 looked great.  Without the remote worker facility though it's not plausible for this situation.  Please let me know if you're successful.  I'm just looking at an LG system which has been recommended - which appears to do the job but I'm waiting for pricing information.



Daniel Griego Sat, 08/11/2012 - 22:35
User Badges:

Tested out the 2.3.1 (14) RC on a uc320w with Spa525g2 phones today. Found an annoying issue with Bluetooth and the iPhone 4s. During a call when using the SPA525G2 phone as a Bluetooth accessory, if somebody pages/intercoms my extension, my iPhone conversation drops into hold and I am immediately connected to the person who pages/Intercom'd me. The person in the other end of the cellular call doesn't hear any hold music as they do when I intentionally put them on hold. They just kind of go into outer space Guess I should report it. I'm new to the forums.


rbordner Mon, 08/13/2012 - 07:52
User Badges:
  • Cisco Employee,


Thank you for your feedback.  I will ask the team how the Blue tooth call is handled when a page is received.

There is a phone option "Auto Ans Page on Active Call" and the default value is No.  The issue is how to handle the Page during a BT call (the call is actually remains on the cell phone).   Let me check with the team and I'll update the thread.



James Davies Mon, 08/13/2012 - 11:35
User Badges:

With this new release, has anyone noticed any improvement with these issues...

-Line hissing (white noise)

-Poor speakerphone volume

Phones used are mostly SPA 504's & 508's

We are utilizing 3 FXO lines from a Comcast voice modem.



iamtelecom Tue, 08/14/2012 - 07:19
User Badges:

Thanks for Dialable (generic) Intercom.  I did search the forums and find the *96 work-around, but honestly didn't find that until I searched for "generic intercom" after seeing the label in yesterdays update.  Nonetheless, it's a basic feature that's good to see in this platform.  I've always been a bit perplexed by its absence.

rbordner Wed, 08/15/2012 - 09:32
User Badges:
  • Cisco Employee,

Update on the iPhone bluetooth call when a page is received on SPA525G(2).

The page is auto answered and the bluetooth call is placed on hold automatically (and far end of iPhone call hears silence).

Once the page call is completed then the iPhone call can be resumed on the SPA525G(2).



Hoping someone has encountered this issue so I'm not alone.

I have loaded 2.3.1(14) and I was configuring it to use the day/night feature for different call routing during different times of the day.  I setup the schedule and it seems to turn to night mode just fine, but when it is day, the system does not revert back to day mode.  Also, the force night function toggle does not bring it back to day mode as well.  Is this a bug, or am I doing something wrong here?

Also, I have some feature requests:

- Separate schedules for Call Routing, AutoAttendant, and Call Forwarding would be nice

- Under Call forwarding - having the ability to put in different values for the time to forward (i.e. 20 secs) for day/night would be nice (currently there is only 1 value that applieds to both)

Thank you.

Ed Tsai

rbordner Mon, 09/17/2012 - 16:36
User Badges:
  • Cisco Employee,

Hi Edward,

Thanks for your feedback on the different schedules for

Call Routing, AutoAttendant, and Call Forwarding.

Can you please check the Status -> Devices -> and check the system time and the status of the Night Time Ring Mode when the system should transition from night to day mode.  Possibly the Time Zone offset is incorrect.

If needed I can look at your configuration to help isolate the issue.



Thank you for getting back to me - much appreciated.

This is why I think it's a bug. Time is set correctly as well as the time zone, but the system still won't transition from night to day. Perhaps you can duplicate my scenario in your enviornment -I have a unique customer requirement for this feature which may be triggering this issue (but nevertheless I still feel it's a bug becuase it's not behaving as expected) The customer needs to be 'day' 24x7 except for Thursdays between 8:30am-4:30pm where this is 'night'. In order to test this configuration functionality I set the current day (in this case it was Saturday 9/16) to be 'night'. What I found that it did indeed set the mode to 'night' - however when I reverted back to the desired schedule (turned Saturday back to 'day' the night mode wouldn't switch back, even though I set back Saturday to be 'day'. If I disabled night/day mode it would go back to day, but when I put it back to the day/nigh schedule (with the desired schedule) - it would go back to 'night' mode incorrectly as Saturday was scheduled as 'day'. I then enabled the force night button on one of the phones which (correct me if I'm wrong) should allow me to toggle the modes. In corresponding with the mode, the phone button indicated amber, but when I pressed it it would turn green, but the Status -> Devices would still show that 'night' mode was still on. I also confirmed that it wasn't an error in display, when it was in 'night' mode it would behave as such with the corresponding call routing rules in place.

I hope this makes sense - I would welcome you to take a look at the system but I need to arrange this with my customer.

Ed Tsai
primamedica Sat, 09/29/2012 - 04:32
User Badges:

WAN type connection PPTP DHCP and L2TP DHCP does not work correctly.

UC320W is connecting to the server, recieving settings via DHCP(IP, MASK, GW) and then TX WAN is freezing. After XX seconds timeout it is disconnecting and then all of this is repeating again and again.  When the connection is established, there is no traffic going out through WAN port.

VPN Server properties: IPv4, No Secure, CHAP

Log attached.



This Discussion

Related Content