Feedback on the BE3000

Question

Hello Everyone,
This is a post to Cisco for a bit of feedback regarding the BE3000. I've been using the device in the lab for the past few days and I wanted to make the follwoing points regarding the BE3K.
Just outline where I'm coming from I have a BE 3K with 8.6.4 installed with UK locale. I'm used to designing and deploying CUCM, CUC, CUPS, and integration with UCCX and UCCE, so I like to see alot of customisation in my CUCMs.
The redial key with outbound calls has a 6 second timer before the call connects. I have tested this with the Cisco 6945 which displays nothing but after 6 seconds the redial number displays and the call connects, and the Cisco 3905 which displays the last dialled number but again takes 6 seconds to connect.
Voicemail on the BE3K is very limited. It is a bit annoying to not be able to access Unity voicemail on the server. I would have liked to be able to see the users mailbox with the ability to import messages using Media Master (if the box is running Unity Connection) or set custom settings on the mailbox such as the behaviour after playing greetings. This could be most beneficial to add extra messages to an IVR where dummy phones could be inserted into the system to relay messages to voicemail for information recordings.
Fax with the VG224 and a SIP ITSP is very tempremental. Now this would be the same for any implementation of fax over SIP with a CUCM, it is never going to be easy, but it would be beneficial to be able to setup the VG224 using MGCP to see if this asssits the issue. Currently I the VG224 can be added as a SCCP device, which is great for analogue handsets, but it could be useful to have MGCP.
Updating from USB is very problematic. Installation of COP files hangs and times out requiring a reboot of the server. Luckily you can use SFTP with no issue.
The lack of customisation for SIP trunks without the SIP Trunk Connection Generic COP file. It is frustrating to see a wide variety of SIP configuration options in the documents and not be able to implement them without the COP file that unlocks advanced configuration. I understandthat Cisco are trying to make deploying the boxes easier for less technical users but teh absence of these options without installing the COP file which cannot be downloaded via the software page is unacceptable.
The boot time for the BE 3000 is unbelievably long compared to CUCM. I've watched the boot sequence and this takes a while but the activation of services once the CUCM has loaded the OS is very long. I imagine it's to do with the hardware of the BE 3K so it's not likely to get faster, but it is really slow.
The lack of options on the CLI. There is no ability to run the standard "show", "utils", and "set" commands on the CLI. The ability to issue the "utils service list paged" command would be beneficial.
This seems like I'm poking holes in the device but I actually believe it could be really good. There is a lot about the box that I like, it is great for unexperienced users, it's a breeze to deploy (I set my one up in less than a day with a customised dial plan), and it's competitively priced for the SMB. I'd like to see more attention to the Unity and IVR on the server, and the unlocking of the advanced configuration options.
It would be really good for Cisco to release a roadmap for the features due to be implemented on the BE3K, or perhaps if it exists someone could point me towards it.
Cheers,
James McMichael

Answer 1

James & Adam,
Thanks for the feedback. It helps us greatly in creating the roadmap for the product.
Responding to some of your specific points:
1) As Adam mentioned, please clarify whether it is a PSTN call or an internal number. There may be some delay in getting the alert/progress from the PSTN network, if it is a pstn call. I tested on myself, and there is some delay, if redial is to a PSTN number.
3) Will look into this, Meanwhile the FAX solution is to use FXS on SPA8800.
4) Will see if there is an problem with uploading COP file using USB.
5) The Cisco supported configuration of SIP trunk is to connect to a CUBE. The configuration options which are exposed on SIP trunk page are configuration items which are required, if SIP trunk is connected to a CUBE. There is a smart design guide which provides details on what configuration is required on CUBE.
If you are not connecting SIP trunk to CUBE, then you would require advanced connection pack, if you want to expose more configurable options for SIP trunk settings.
6)  We understand that the boot time is high. It should be reduced in upcoming releases.
2 & 7) These items are asking for advanced configuration options, which partners like you, who have worked with CUCM, CUP etc. are used to.  This product is mainly targeted to SMB customers or partners who may not have that kind of expertise with advanced configuration options.
We understand that it is important to meet requirement from advanced partners also. We will take this feedback and see how we can expose these parameters and keeping the system simplified at the same time. I do not have any timeline on when it will be done, since there is lof ot work required to fix things like high reboot and upgrade time.
Thanks