Ubuntu Wiki

• Launchpad Entry: arm-m-telephony-stack

• Created: May 5, 2010

• Contributors: David Sugar

• Packages affected: sipwitch, ofono, telepathy

Summary

To create a unified approach to VoIP and telephony for the Ubuntu desktop, sipwitch is being proposed as desktop mediation service. This blueprint provides an overview of issues required to make this happen, and what changes within this broader goal we believe can be focused on within the Maverick timeframe. The overall roadmap for this can be found at DavidSugar/telephony and likely will iterate over multiple releases.

Release Note

To better integrate and improve VoIP integration for the Ubuntu desktop, a new user preference panel offering tools to configure and use sipwitch as a VoIP and telephony mediation service is being offered. These initial tools and services are optional for Maverick but may become a standard part of the Ubuntu desktop experience in the future.

Rationale

The goal, within Maverick, is to further complete work started in Lucid to use sipwitch to manage and route VoIP services and offer a standardized means to configure SIP clients and telephony services. The purpose is to create a unified, reliable, consistent, and much easier to configure desktop telephony experience regardless of the user's preferred front-end desktop telephony client. This is part of a larger goal to create a unified desktop telephony stack and user experience.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• data migration, if any
• redirects from old URLs to new ones, if any
• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

CategorySpec