Forum Nokia
Nokia Connecting People

Login Register

 

Home: Resources: Tools And SDKs: Local Client Provisioning Plug-in for VoIP

Local Client Provisioning Plug-in for VoIP Rel 2.x Beta 1.3

Easily provision your VoIP service on compatible S60 devices.

For S60 devices that can run Nokia VoIP release 2.x, Local Client Provisioning (LCP) enables the creation of SIP-based VoIP settings from a file included in an application’s installation file. The creation of these settings is achieved using OMA Client Provisioning.

For more information on VoIP support in Nokia devices, visit the VoIP technology page »

What can I do with the LCP VoIP Plug-in?

With the LCP VoIP Plug-in, you can eliminate the use of SMS for OTA provisioning of SIP settings for your VoIP application. The plug-in enables you to include all the relevant settings information in a file that is included in an application’s installation (*.sisx) file. Once an application has been installed, you can provide users with access to the Local Provisioning Credentials Query application, which allows them to set their user name and password, as well as link SIP settings to existing access points.

What’s included in the LCP VoIP Plug-in?

The LCP VoIP Plug-in package includes:

  • The Local Client Provisioning API header file.
  • An installation file containing the provisioning component for S60 devices.
  • The link libraries required for builds based on ARMV5 and GCCE.
  • An example application, which includes an XML settings file.
  • The Local Provisioning Connectivity Settings Query application.
  • A developer’s guide.

The latest beta version of the LCP VoIP Plug-in replaces the Local Provisioning Credentials Query application with the Local Provisioning Connectivity Settings Query application. The new application enables users to set their user name and password after the application has been provisioned, as well as link SIP settings to existing access points.

How do I get started with the LCP VoIP Plug-in?

If you are already developing a VoIP application for the S60 platform, you should have no difficulty using the LCP VoIP Plug-in. The specific knowledge required includes: an understanding of XML files; the ability to use command-line tools; the ability to code and test S60 applications using Symbian C++; the ability to build Symbian installation system files; and an understanding of Symbian Signed.

To install the LCP VoIP Plug-in, you need a PC on which you can install one of the S60 3rd Edition SDKs for Symbian OS, for C++ and your chosen IDE. In addition, you will need to download the WBXML Library to convert the XML settings file to the format used by the S60 provisioning component.

For more information, see the Local Client Provisioning Plug-in for VoIP Rel 2.x Beta 1.3 Developer's Guide »

What help does Forum Nokia offer for the LCP VoIP Plug-in?

Forum Nokia offers all developers a wide range of professional and community-based help and support.
(See the box at right for links.)

 
Forum Nokia LCP VoIP Plug-in support links:

Where can I find all the documents about the LCP VoIP Plug-in?

For more information, see the Local Client Provisioning Plug-in for VoIP Rel 2.x Beta 1.3 Developer's Guide »

With which Nokia platforms and devices is the LCP VoIP Plug-in compatible?

You can use the LCP VoIP Plug-in to create SIP provisioning files for S60 devices that include VoIP release 2.0 or later. For a detailed list of supported devices, see the VoIP support in Nokia devices Web page.

Learn how to
download applications

java symbian_os s60 maemo c++

Community highlights

Blog entry of the week

Open Source FLV Player for Symbian!

Champion of the month

Mika Raento
Read more about
Mika on the
Champions web site.

Newsletter sign up

Privacy policy   Archives

Press

Events

Forum Nokia feed

  • Latest devices
  • Latest documents
  • Latest tools
  • Latest blog entries

Terms & Conditions | Privacy policy | Site map | Developer feedback | © Nokia 2008


RDF Facets:


qdcZcoverageQUxhttpE3AE2FE2FforumE2EnokiaE2EcomE2FX
qdcZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ
qdcZtypeQUqfnTypeZE52esourceQ
qdcZtypeQUqfnTypeZWebpageQ
qdcZtypeQUqmarsZManagedE52esourceQ
qdcZtypeQUqwebZInformationE52esourceQ
qdcZtypeQUqwebZPageQ
qdcZtypeQUqrdfsZE52esourceQ
qfnZdistributionQUxhttpE3AE2FE2FforumE2EnokiaE2EcomE2FX
qfnZtypeQUqfnTypeZE52esourceQ
qfnZtypeQUqfnTypeZWebpageQ
qfnZtypeQUqmarsZManagedE52esourceQ
qfnZtypeQUqwebZInformationE52esourceQ
qfnZtypeQUqwebZPageQ
qfnZtypeQUqrdfsZE52esourceQ
qmarsZlanguageQUxhttpE3AE2FE2FswE2EnokiaE2EcomE2FlanguageE2D1E2FenX
qrdfZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ
qrdfZtypeQUqfnTypeZE52esourceQ
qrdfZtypeQUqfnTypeZWebpageQ
qrdfZtypeQUqmarsZManagedE52esourceQ
qrdfZtypeQUqwebZInformationE52esourceQ
qrdfZtypeQUqwebZPageQ
qrdfZtypeQUqrdfsZE52esourceQ