Feature request list

[mark.boyce]

Thought I'd start a public feature wish list.  I'll try and keep them within the scope of where the product is aimed :-)

Route to particular trunk based on number pattern

I would like the ability to say that numbers which match a particular pattern always get sent out on a particular trunk.  ie emergency 999 / 911 calls I'd like to go out on FXO port, or maybe all calls to USA should go via VoIP trunk 2 as I get a better rate from that provider.

Don't drop lead digit on Internal Dialing

Can we have the option to not drop the lead digit on the "Meaning of first digit dialled" table?  We tend to configure our switches now to behave in the same way as you would dial a mobile.  So users always dial the full number (including area code even if local).  This means that all numbers starting with a Zero are outbound calls making the need for 'dial 9 for a outside line' obsolete.

Prefix / Append to number dialled

It may be useful to have the ability to prefix particular numbers before they are sent to the PSTN.  eg a user may have a pre-dial carrier for cheap calls to a particular country which is activated by prefixing '1234' to the outgoing number

PoE on PBX

PoE on the UC320 ethernet would be nice

DHCP Assign Addresses

There appears to be no way to see IP Addresses given out by DHCP server

Codecs

Any chance of some more codecs such as g726/32 ?

SIP DTMF

Ability to set SIP DTMF Mode on the VoIP Trunks

SIP Trunk Registration

Seems to use the first DID assigned to the trunk to register as.  Surely using authentication ID would be better?

Non Flash Admin

Is there any chance of having the non flash based admin available again? (Was in v.01 of the firmware).  The flash based wizard although very nice is not always practical.

VPN / Firewall

If UC320 is deployed as the public facing device, as would be implied by the inclusion of the WAN port. Are we going to get any VPN / Firewall features other than port forwarding?   (Thinking mainly teleworker at the moment)

Questions

BLF Notification System

System seems to use the SPA9000 style multicast to send notifications & updates for BLF and Line status rather than Skinny like UC500?

More as I confirm it's not me missing something :-)

[samuande]

Mark,

Can I ask for more information on the admin pages request?  Can you expand on what you mean by "is not always practical"?

Thanks,

Sam

[mark.boyce]

Hi Sam

a lot of the time when we're doing support from odd places, like now, we're working on things like an iPad which wont run flash and/or running over slow 3g connections.

I haven't actually checked to see how large the wizard flash module is but it has to be lager than html with images turned off?

We've also been working in two corporates recently who do not allow flash on their machines at all.  Admittedly they're much bigger than the UC320 target market.

CLI would be really nice for remote diags, after all the box is running linux :-)

Mark

[Andrew Hickman]

Hi Mark,

Great feedback - thanks for the input.

The main design aims for the UC320 was to provide a solution that is very easy for partners to use (i.e. with absolutely minimal training) and for Cisco to support.

Flash was selected as being able to provide an appropriate interface to satisfy these goals.  I know that you have used the SPA9000 in the past and while this had the simplicity of html, I think that you'd agree, it wasn't the most intuative of interfaces.  It's the same logic that keeps us away from CLI - sure that would be lightning fast in the right hands. For an partially trained technician though, this could be confusing and frustrating.

Cheers

Andy

[nalbert]

Route to particular trunk based on number pattern

Mark: The base unit has a max of four FXO ports expandable to 12 with SPA 8800s. We are expecting 80% or more of our deployments at this time to be FXO based. We are going to have increased ability to route calls to FXO / SIP trunks and choose where your call goes how ever have no plans of making this as granular as you are talking about. Do you think this market needs that leverl of granularity. Do small organizations typically have more than one service provider. Could you please elaborate with a Use cases so we can understand this well.

Don't drop lead digit on Internal Dialing

This should be possible. I will let Andy Comment about this.

Prefix / Append to number dialled

This is our first round of feedback from Europe. We will definitely consider this for our future releases.

PoE on PBX

We are definitely considering this. This a price of platform  vs use case decision.

DHCP Assign Addresses

This feature is under construction. Should be in the GA release.

Codecs

Any chance of some more codecs such as g726/32 ?

Is there a use case for this? Does any one really use there codecs?

SIP DTMF

This should be embedded within the drop down xml file for SIP trunks thus hiding complexity and still working seemlessly.

SIP Trunk Registration

I will investigate this. I am not sure if that is still true.

VPN / Firewall

Under constructions. Should be in for 3.0 of product.

[mark.boyce]

Andrew,

I take your point at the targeted user audience and agree that the flash front end would be appropriate for that.

Maybe the interface guys can add us an 'advanced things you shouldn't really play with unless you're willing to chance everything stopping working' tab to enable a tweaks section?  Could always treat it as an unsupported danger zone. (You play with the advanced tweaks you're probably on your own if you break it)

Alternatively simply honouring, and not breaking on subsequent edits, advanced tweaked setting we make directly in the XML saved config would work.

Navin,

Route to particular trunk based on number pattern

I'm expecting to target the UC320 at the small / medium office market with 1-4 existing FXOs, then up-sell them reduced costs and dynamic expandability of SIP Trunks. Sort of;  "Hey look! This will work as a drop in replacement to your existing switch, do everything the old one did and more.  Even better than that, by adding SIP trunks we can reduce your call costs and offer expansion on demand without ever buying another phone line"

Once the user has been converted over to SIP trunks as the default route out we'd still want to send emergency 999/911/112 calls out via local FXO.  This is the major requirement.

A secondry use would be to have the ablility to take on a second SIP Trunk for cheaper calls to certain destinations.  This I agree is much less likely.

Don't drop lead digit on Internal Dialing

A simple tick box on the interface saying 'dont remove lead digit' would suffice.

PoE on PBX

PoE vs Platform price .... personally I think my vote would be to keep the platform price down if it's going to impact it significantly.

Codecs

Personally we use g726 as a compromise between G729 and G711.  G729 can sound a bit compressed and can be lousy for music on hold due to the way it's optimized for speech.  G711 can often be just far too wide a bandwidth for normal DSL circuits.

VPN / Firewall

Great news, VPN for teleworker phone would be sexy but may be outside the remit of the target market for the device.

Mark