 |
- SDK Overview
- Why Use This SDK?
- What Can Be Built
- SDK Contents
- Download
- Key Concepts
- Development Approach
- API Access
- Merchant Accounts
- File Upload and Flow
- Documentation
- API Reference
- Ringtone Editor
- API WSDL
- API Test Harness
- SOAP Definitions
- Sample Code
- Custom Ringtone Store
- Editor Initializing
|
 |
 |
|
Demo and Downloads
|
|
Run It Download Source
|
Custom Ringtone Store - Host Account & Billing
|
Overview
This sample shows how to create a complete custom ringtone store from an existing audio content library on your site. It demonstrates:
- transfering audio files from the host site into Phone Sherpa
- using the Flash editing client
- the host site doing its own account and billing
- creating a ringtone via the API
- delivering a ringtone via the API
Prerequesites
- Phone Sherpa WSAccessKey to make API calls
- Phone Sherpa MerchantID to run the Flash editor client
- Audio files that are accessible via a fully qualified URL
- Client environment that enables Flash embed tags and Javascript
Skill Level
Web developer with familiarity making web service calls and writing custom application code.
|
Sample Details
|
A custom ringtone store enables existing libraries of audio content to be quickly deployed as ringtone content. All ringtones are dynamically generated when requested and the host never needs to store additional audio files.
Conversion, editing, and delivery of ringtones happens within the Phone Sherpa system. Thus, the source audio must be transfered from the host to Phone Sherpa as a first step. When a particular source file is selected to be made into a ringtone, the host makes a server call to securely send Phone Sherpa the file. This prevents the user client from being exposed to the location of the source file.
Once the source is in the system, the Flash editing client component can be launched allowing the user to select a ringtone from the source audio. The editor colors can be modified to fit into most host schemes. When the user presses "Continue" in the editor, the component makes a client-side Javascript call to redirect the user's browser to a host defined URL. Included in this redirect are the editor paremeters to be used later when clipping the source audio into a ringtone.
In this sample, it is up to the host to gather user phone information. This can be accomplished any number of ways, such as collecting the information via a form or loading it from a store user account within the host system. Should the host chose to charge for the ringtone or otherwise decrement a subscription, it can do so within its own application code.
The user's phone delivery information is used to determine what format the final ringtone clip should take. The phone model, referenced using Phone Sherpa's phone model identifier, along with the parameters from the editor client are used to generate the proper ringtone for the user via the audio editor API.
Delivery of the ringtone is accomplished via a single method call taking the clipped ringtone file and user phone delivery information as parameters. Phone Sherpa's phone model database contains many phone model specific instructions for installing ringtone content. These instructions can be requested from the API by referencing the Phone Sherpa phone model ID.
|
|
|
|
 |