Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Archived:Creation of SIP & VoIP profiles with LCP plug-in fails (Known Issue)

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Creation of SIP and VoIP profiles using the Local Client Provisioning (LCP) plug-in for VoIP fails on S60 3rd Edition Feature Pack 1 when the proxy and registrar settings have the same realm value but a different username and password.

Article Metadata
Tested with
Devices(s): Nokia N95, Nokia E66, Nokia E71
Platform(s): S60 3rd Edition, S60 3rd Edition, FP1
S60 3rd Edition FP1
Keywords: LCP, SIP, VoIP
Created: User:Technical writer 1 (10 Mar 2009)
Last edited: hamishwillee (18 Jun 2012)


The LCP plug-in creates SIP and VoIP profiles using the parameters given in the settings.xml file. While provisioning the proxy and registrar server settings, the LCP plug-in fails to create the profiles if the realm of both servers is the same but the username and password are different.

How to reproduce

  1. Set the proxy and registrar settings in the settings.xml file as shown below and convert the xml file into a wbxml file.
        <characteristic type="APPAUTH">
    <parm name="AAUTHNAME" value="proxy_username"/>
    <parm name="AAUTHSECRET" value="proxy_password"/>
    <parm name="AAUTHDATA" value="realm"/>
    <characteristic type="RESOURCE">
    <parm name="URI" value="RegistrarAddress:5060;transport=UDP"/>
    <parm name="AAUTHNAME" value="registrar_username"/>
    <parm name="AAUTHSECRET" value="registrar_password"/>
    <parm name="AAUTHDATA" value="realm"/>
  2. Run the Local Client Provisioning example using the generated settings.wbxml file.



  • set the same username/password pair to one realm, or
  • do not use proxy at all unless it is really needed (which is rarely the case if proxy and registrar server are on the same realm)

Using different credentials is allowed in the same realm in S60 3rd Edition, FP2 onwards.

This page was last modified on 18 June 2012, at 23:23.
58 page views in the last 30 days.