Session Initiation Protocol (SIP) — Client Service Offerings Project
On this page:
Background and Overview
Session Initiation Protocol (SIP) and Open Source for Voice and associated Data applications is fast becoming a priority pursuit for IT organizations to explore and develop their own host of innovative applications and services by using SIP. The attraction to SIP is that telephony becomes another converged application and integrates easily into other applications and services. Basically, SIP enables the opportunity to easily bridge Voice and Data applications and services together to provide a host of collaborative service offerings.
Stanford ITS recognizes that SIP is a powerful influence for the industry’s next generation Voice and associated Multi-Media product development roadmaps. Therefore, Stanford ITS sees great potential and opportunity in establishing Stanford’s own SIP Open Source suite of service offerings with a goal to ultimately identify attractive, fully integrated Voice and Data applications that the Stanford community will want to use. The scope of this discovery-level project will be to identify and pilot select SIP clients within the Stanford University environment and make a recommendation on how to proceed with SIP as a part of the ITS service portfolio. This project will not include a production offering phase, but that may be recommended as a future phase based upon the pilot findings.
Risks of Not Doing Project
- With SIP being the telecom industry’s next generation protocol of choice, Stanford will lose momentum in exploring, developing, and leveraging next generation VoIP and Multi-Media technology application and client service offerings.
- This effort is key to delivering on the promise of Work Anywhere. Without this effort, IT Services will be unable to deliver services required for Stanford telecommuting and mobility.
|Project Sponsor||Bert Stubbs|
|Project Manager||Gary Buchanan|
|Product Manager||Jimmy Hale|
|Business Owner||Bert Stubbs|
|Operations Owner||Christine Moe|
|Client||All existing voice subscribers|
- Develop recommended future roadmap for SIP clients.
|Procurement||Identify and purchase clients for testing.|
|SIP Soft Phone Client Pilot||SIP Soft Phone Pilot within ITS.
Secondary SIP Soft Phone Pilot with outside clients.
|SIP Handheld Client Pilot||SIP Handheld Pilot within ITS.
Secondary SIP Handheld Pilot with outside clients.
|SIP Soft Phone Client — Acceptance||Work with appropriate teams to agree, ensure compliance with architecture, engineering, security, and support.|
|SIP Handheld Client — Acceptance||Work with appropriate teams to agree, ensure compliance with architecture, engineering, security, and support.|
|Support Strategy Plan||Work with appropriate support teams to identify support model — Networking, Network Monitoring, Communication Services, CRC, PCG, etc.|
|Recommendation on go-forward production plan.||Recommendation to ITS Mgmt on whether to rollout SIP clients as a service offering and, if so, what that offering will look like.|
|Number of ITS pilot participants||25|
|Number of client pilot participants||25|
|Project Phase||Major Milestone||Estimated Completion Date|
|Execution||Start SIP Soft Phone Client: ITS Technical Pilot||10/1/2007|
|Start SIP Handheld Client: ITS Technical Pilot||10/1/2007|
|SIP Client Pilots: Market Pilot Solicitation at October, 2007 IT Fair||10/2007|
|SIP Soft Phone & Handheld Pilots: Evaluation, Feedback, and Acceptance||3/31/2008|
|Service Offering Recommendation to ITS||4/2/2008|
|In Scope||Out of Scope|
Issues, Risks, and Mitigating Factors
|Issue/Risk||Likeli-hood (HML)||Impact (HML)||Mitigation|
|Network Infrastructure Quality of Service (QoS) readiness||H||H||Required to deliver service offerings.|
|Organizational Risk — Voice and Data Network will not settle current ownership and strategic direction conflict, which will hamper project teamwork.||H||H||SIP Strategy and roadmap needs to be clearly defined prior to project initiation. This may require high-level organizational directive.|