No, the customer requirements should come from the customer. You can use the SRND to educate yourself on the interoperability considerations, application requirements, scalability factors, etc. Having that knowledge will help you guide the customer to a solution that meets their requirements but it won't define the requirements for you or them.
If you are looking for tools to help you with the discovery phase of the project (where technical and business requirements are defined) then you may want to access the Steps to Success partner portal on CCO. If you are a Cisco partner you should have access to this portal from the partner pages.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...