[cisco-voip] Feature Request *gasp*

[Chris Ward (chrward)]

Very new… (last 3-6 months)

+Chris
Unity Connection TME

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Thursday, February 14, 2013 4:37 PM
To: Chris Ward (chrward)
Cc: cisco-voip at puck.nether.net; Jason Aarons (AM)
Subject: Re: [cisco-voip] Feature Request *gasp*

Thanks Chris!

Can you comment as to how old/new this tool is?

Lelio


---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Chris Ward (chrward)" <chrward at cisco.com<mailto:chrward at cisco.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Jason Aarons (AM)" <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Thursday, February 14, 2013 4:12:38 PM
Subject: RE: [cisco-voip] Feature Request *gasp*


Your Cisco account teams now have a tool called Innovous which they use to submit and “vote” on product enhancements. I would make sure your desired features are listed in there and that your account teams are voting and providing the business cases for each. This is how the Bus are going to start to build roadmaps with customer feature requests. Not sure if the tool extends past the UC suite yet.

+Chris
Unity Connection TME

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, February 14, 2013 3:57 PM
To: Jason Aarons (AM)
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Feature Request *gasp*


I'm sure there are plenty of ways to go about it, both to protect them legally, i.e. "all ideas become ours", as well as resource wise, one user suggested feature per quarter, voted on bugzilla or something.

It's just sad that right now, there's real no way to get it done.



---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Jason Aarons (AM)" <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Thursday, February 14, 2013 3:47:41 PM
Subject: RE: [cisco-voip] Feature Request *gasp*

I suggested being able to press the Call Forward button on Secondary Lines around 2001 to a Cisco TME that came onsite and our Cisco AM ☺

You need to push your Cisco AM to setup a meeting with the BU Product Manager and speak to him/her.

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, February 14, 2013 3:36 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Feature Request *gasp*



I haven't raised this ugly beast in a while since I had all but given up that there's a chance.

Has anyone had any luck recently getting a true customer feature request implemented into a Cisco product? I don't mean a feature that you requested that happened to be on their list of things to do, but something they didn't think about, you thought about, and were able to get them to acknowledge the idea and bring it forward.

CIPTUG had tried to get this going a while back with some promising results but it didn't really go anywhere. When I looked at the Collaboration Group feature request documents they were years old with no updates.

The biggest one I have right now is to move any admin pages onto a different port than the user pages. Right now, we use a reverse proxy to protect the admin pages. But even that is complicated because some of the user pages use resources from the admin directories, rather than a shared resource directory. This will work for now, but more and more things won't work with reverse proxies and will need direct access. I just shudder at the thought of someone typing in the URL without any path and landing on a page that announces where the admin pages are.

Web apps have been separating admin pages and user pages for ever, not sure why Cisco continues to keep them running on the same port.

Any comments would be greatly appreciated.

Lelio


---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130214/7c61430b/attachment.html>