Namespaces

Variants
Actions

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 over the next few weeks. Thanks for all your past and future contributions.

Provisioning VoIP and SIP Profiles using OMA DM commands

From Wiki
Jump to: navigation, search
Article Metadata
Tested with
Devices(s): Nokia E71, E66, N95
Compatibility
Platform(s): S60 3rd Edition, FP1
S60 3rd Edition FP1
Article
Keywords: n/a
Created: User:Kbwiki (30 Jun 2009)
Last edited: hamishwillee (15 Jun 2012)

Contents

Overview

VoIP and SIP profiles can be provisioned remotely using device management (DM) commands.

Description

The DM servers like Funambol and Sync4j can be used for remote provisioning of VoIP and SIP profiles. The settings of the VoIP and SIP profiles can also be modified using DM commands.

Solution

VoIP Profile Creation

Using the Add command, a new VoIP profile can be created:

 ./VoIP/<VoIPId0000000011>
./VoIP/VoIPId0000000011/SettingsName <<VoIP profile name>>

The above two commands are essential for the creation of a VoIP profile. The provisioned VoIP profile gets linked to the existing SIP profile if one exists. Otherwise, it gets linked when a new SIP profile is created.


SIP Profile creation

Using the Add command, a new SIP can be created:

 ./SIP/<SIPId0x01000002> 
./SIP/<SIPId0x01000002>/AddressOfRecord <<Address>>
./SIP/<SIPId0x01000002>/Default False
./SIP/<SIPId0x01000002>/EnableAutoRegistration True
./SIP/<SIPId0x01000002>/EnableSecurityNegotiation False
./SIP/<SIPId0x01000002>/EnableSignalCompression False
./SIP/<SIPId0x01000002>/LooseRouting False
./SIP/<SIPId0x01000002>/Name <<SIP profile name>>
./SIP/<SIPId0x01000002>/ProfileLock False
./SIP/<SIPId0x01000002>/ProfileType IETF

Proxy Server Settings

 ./SIP/<SIPId0x01000002>/OutboundProxy   
./SIP/<SIPId0x01000002>/OutboundProxy/Host <<Host Address>>
./SIP/<SIPId0x01000002>/OutboundProxy/Passwd <<Password>>
./SIP/<SIPId0x01000002>/OutboundProxy/Port <<Port No>>
./SIP/<SIPId0x01000002>/OutboundProxy/Realm <<Realm>>
./SIP/<SIPId0x01000002>/OutboundProxy/Transport UDP
./SIP/<SIPId0x01000002>/OutboundProxy/Username <<username>>

Registry Server Settings

 ./SIP/<SIPId0x01000002>/RegistrarServer   
./SIP/<SIPId0x01000002>/RegistrarServer/Host <<Host Address>>
./SIP/<SIPId0x01000002>/RegistrarServer/Passwd <<Password>>
./SIP/<SIPId0x01000002>/RegistrarServer/Port <<Port No>>
./SIP/<SIPId0x01000002>/RegistrarServer/Realm <<Realm>>
./SIP/<SIPId0x01000002>/RegistrarServer/Transport UDP
./SIP/<SIPId0x01000002>/RegistrarServer/Username <<username>>

When EnableAutoRegistration of the SIP profile is set to True, the SIP profile gets registered by connecting to the default AP specified. The Transport field can take the values UDP/TCP. Similarly, ProfileType can be IETF/Nokia 3GPP. The settings can be modified according to requirements using the Replace command.

To remove the provisioned VoIP/SIP profiles, the following commands can be used:

 Delete ./VoIP/<VoIPId0000000011>
Delete ./SIP/<SIPId0x01000002>

Related article

Funambol DM Server

This page was last modified on 15 June 2012, at 00:49.
43 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×