I have a UC320 here in the office and have sold the first small job foe to a client. I have worked with a number of platforms over the years, most recently Avaya Partner, Avaya IP office (and IP Office Partner Edition) and Nortel. I am (was?) very excited about the UC320 but now that I have it in my hands I am a bit confused, if not frustrated.
The initial setup interview as somewhat buggy with things like the Dial Plan fields showing <place holders> instead the the field data. The Network Topolgy choices did not appear to "stick" once the setup wizard completed (let alone reflect the current choices and appropriate editable fields during completion) and that is just for starters.
Honestly, I just don't get the network topology choices. The graphics make sense, but the implementation does not. If I choose to use the UC320 to route VOICE only with (for example an SBS server doing DHCP and DATA0, then the device should be smart enough to use the LAN port and the EXISTING DATA network as the gateway to the internet. Yet, the UC320 expects to have the WAN port connected to get TIME, UPDATES, load PMFS, and function in general. This is insane at best. To be blunt, why is this so complicated? Honestly, how is one reasonably supposed to connect both the LAN and WAN ports to the same small business network without jumping through hoops to prevent a loop?
Why do the "network topology" configuration pages not show the currently selected topology after applyiong the changes?
Of note: even when the LAN and WAN ports are connected properly and the UC320 is routing both voice, data and DHCP the PING function only works part of the time.
The list of bugs posted here (from just the last week) including DTMF problems, AA problems, MOH problems, Incoming call group problems, active call notification beep problems, SIP problems, BLF problems, is almost endless. Add that reality to "features" that just don't make much sense to me, like the need to add multiple "extensions" to a handset to allow external and internal calls to ring differently, and this thing is begining to look like a nightmare under the hood.
How in the world is one supposed to put one of these units into a production environment with this many real world call flow problems that effect even 2 or 3 users businesses? Somebody please set me straight...