Provisioned VoIP profile not “active” until it has been “touched” on the phone

[henjam]

I made the two changes described here to Kannel, and configuring SIP and VoIP profiles now works very well. The patch for kannel 1.4.1 is below.

Interestingly, all the other parameter values specified in frodek's patch are not required for configuring a VoIP profile using a simple WLAN AP (on an E60 with current firmware). In fact, for me, using them actually causes the provisioning SMS to be ignored by the device.

Also frodek, I think your patch has a typo in it! In the CR doc from the OMA site the "ENCAPS" value is stated as 0x4b rather than 0x5b. But currently I can't make that ENCAPS thing work at all (which I complain about in this thread).

Here's the simple patch to make Kannel compile provisioning messages that correctly create the link between the VoIP profile and the SIP profile on S60:

diff -ur gateway-1.4.1/gw/ota_compiler.c gateway-1.4.1.s60/gw/ota_compiler.c
--- gateway-1.4.1/gw/ota_compiler.c     2006-09-25 11:01:43.000000000 +0100
+++ gateway-1.4.1.s60/gw/ota_compiler.c 2007-06-25 17:46:09.000000000 +0100
@@ -331,6 +331,8 @@
     { "NAME", "TO-PROXY", 0x39, 1 },
     { "NAME", "URI", 0x3A, 1 },
     { "NAME", "RULE", 0x3B, 1 },
+    { "NAME", "APPREF", 0x3C, 1 },
+    { "NAME", "TO-APPREF", 0x3D, 1 },
     { "NAME", "INLINE", 0x5 },
     { "VALUE", "IPV4", 0x85 },
     { "VALUE", "IPV6", 0x86 },

Apply it to http://www.kannel.org/download/1.4.1...y-1.4.1.tar.gz as follows:
1. Extract the above tarball.
2. cd gateway-1.4.1
3. Copy and paste the patch into some file patch_filename.
4. patch -p1 < patch_filename.

[frodek]

Interestingly, all the other parameter values specified in frodek's patch are not required for configuring a VoIP profile using a simple WLAN AP (on an E60 with current firmware). In fact, for me, using them actually causes the provisioning SMS to be ignored by the device.

Should have learned to always test stuff like this before posting it. I just tried my patch on some WLAN configuration and can confirm that it really do not work! Sorry about this. I'm not sure why but I guess the specifications in the OMA Change Request document from nokia (OMA-DM-CP-2005-001R02-CR_CP-WLAN-.doc) was not fully implemented.

Anyway, it seems that the terminals accepts inline-text WBXML encoding of the WLAN related attribute value prefixes so use this patch on libwbxml instead (similar to your patch henjam):

--- wbxml_tables.c.org  2006-07-11 13:47:45.000000000 +0200
+++ wbxml_tables.c      2007-09-10 15:06:54.000000000 +0200
@@ -1333,6 +1333,11 @@
     { "name",        "URI",                 0x01, 0x3a }, /* OMA */
     { "name",        "RULE",                0x01, 0x3b }, /* OMA */

+    /* From OMA-DM-CP-2005-001R02-CR_CP-WLAN-.doc */
+    { "name",        "APPREF",              0x01, 0x3c }, /* OMA */
+    { "name",        "TO-APPREF",           0x01, 0x3d }, /* OMA */
+    { "name",        "REALM",               0x01, 0x48 }, /* OMA */
+

regards
frodek

[nico-tsl]

Hi,

I'm trying to send the following SIP profile to a Nokia E61 :

<?xml version="1.0"?>
<wap-provisioningdoc version="1.2">
<characteristic type="APPLICATION">
<parm name="APPID" value="w9010"/>
<parm name="PROVIDER-ID" value="Testprofile"/>
<parm name="APPREF" value="Testprofile"/>
<parm name="TO-NAPID" value="WaveLAN"/>
<parm name="NAME" value="Test"/>
<parm name="APROTOCOL" value="UDP"/>
<parm name="PTYPE" value="IETF"/>
<parm name="PUID" value="093944444@talk.xyz.net"/>
<parm name="AUTOREG" value="needed"/>
<parm name="SIGNALCMPR" value="yes"/>
<parm name="SECNEG" value="yes"/>
<characteristic type="APPADDR">
<parm name="ADDR" value="sip.xyz.com"/>
<parm name="LR" value="yes"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="5060"/>
</characteristic>
</characteristic>
<characteristic type="RESOURCE">
<parm name="URI" value="talk.nir.net:5060;transport=UDP"/>
<parm name="AAUTDATA" value="xyz2.co.uk"/>
<parm name="AAUTHNAME" value="user"/>
<parm name="AAUTHSECRET" value="1234"/>
</characteristic>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="WaveLAN"/>
<parm name="BEARER" value="WLAN"/>
<parm name="NAME" value="WaveLAN"/>
<parm name="NETWORKMODE" value="Infrastructure"/>
<characteristic type="WLAN">
<parm name="SSID" value="Transatel"/>
<parm name="NetworkMode" value="Infrastructure"/>
</characteristic>
<parm name="INTERNET"/>
</characteristic>
</wap-provisioningdoc>

It's working great when I use libwbxml to compile it, but it's failing when I use kannel.

The two generated wbxml are different that would explain why one is working and not the other one.

libwbxml (with HMAC header manually added) :

70062F1F2DB69181923135304539443533463830333442414638343638303138363043443746414632433041323631324300030B6A00C54503312E320001C6000155018736000006037739303130000187000138000006035465737470726F66696C6500018705034150505245460006035465737470726F66696C65000187220603576176654C414E000187070603546573740001870001370000060355445000018705035054595045000603494554460001870503505549440006033039333934343434344074616C6B2E78797A2E6E657400018705034155544F5245470006036E656564656400018705035349474E414C434D505200060379657300018705035345434E45470006037965730001C6000156018734000006037369702E78797A2E636F6D00018705034C520006037965730001C65301872306033530363000010101C600015901873A0000060374616C6B2E6E69722E6E65743A353036303B7472616E73706F72743D5544500001870503414155544441544100060378797A322E636F2E756B0001870001310000060375736572000187000132000006033132333400010101C6550187110603576176654C414E000187100603574C414E000187070603576176654C414E00018713034D4F4445000603496E6672617374727563747572650001C65003574C414E0001870503535349440006035472616E736174656C00018705034E6574776F726B4D6F6465000603496E6672617374727563747572650001018714010101

kannel :

01062F1F2DB6918192344533413537424332453537303046323338453533433331414232353834423446434136444446340001016A00C501C60187100341505049440011037739303130000187100350524F56494445522D49440011035465737470726F66696C6500018710034150505245460011035465737470726F66696C650001871003544F2D4E41504944001103576176654C414E0001871511035465737400018710034150524F544F434F4C00110355445000018710035054595045001103494554460001871003505549440011033039333934343434344074616C6B2E78797A2E6E657400018710034155544F5245470011036E656564656400018710035349474E414C434D505200110379657300018710035345434E45470011037965730001C601871003414444520011037369702E78797A2E636F6D00018710034C520011037965730001C601871003504F52544E42520011033530363000010101C60187100355524900110374616C6B2E6E69722E6E65743A353036303B7472616E73706F72743D5544500001871003414155544441544100110378797A322E636F2E756B000187100341415554484E414D4500110375736572000187100341415554485345435245540011033132333400010101C6018710034E41504944001103576176654C414E000187121103574C414E000187151103576176654C414E00018710034E4554574F524B4D4F4445001103496E6672617374727563747572650001C601871003535349440011035472616E736174656C00018710034E6574776F726B4D6F6465001103496E667261737472756374757265000101871003494E5445524E455400010101

Moreover kannel is sending this UDH 05040B840B84 whereas I'm usually using 05040B8423F0 for OMA settings.

So, is there anything to do to make this work with kannel ?

Thanks,
Nicolas.

[oliver.eales]

Hello,

we encountered the same problems.
On a phone with german settings you to open the SIP details on the phone and acknowledge a disclaimer regarding emergency calls which automatically opens the first time you "touch" the profile.

When you ack it the phone goes online via SIP.

Regards,
Oliver

[ggodart]

I made the two changes described here to Kannel, and configuring SIP and VoIP profiles now works very well

Did you succeed sending VoIP codec parameters ? Should I add some lines for the "CODEC" tag ?





PS : With kannel I'm now able to send wifi+SIP+VoIP without codec values then my E51 is correctly configured but voip doesn't works because it needs one codec information. I need to send one codec parameter, which I was able to send with nowsms (but keeping the "touch" problem of this topic)

[paipeng]

Did you succeed sending VoIP codec parameters ? Should I add some lines for the "CODEC" tag ?





PS : With kannel I'm now able to send wifi+SIP+VoIP without codec values then my E51 is correctly configured but voip doesn't works because it needs one codec information. I need to send one codec parameter, which I was able to send with nowsms (but keeping the "touch" problem of this topic)

yes, i am using Nowsms Gateway 2008.06.03. And after provisioning, before successfully using SIP/VoIP, I must touch the VoIP-Profile.

Before touching VoIP-Profile, the GSM-call is enable to use.

[ggodart]

Actually I quoted henjam :-)

[ggodart]

I have coded a server in Java that creates the xml provisioning-doc

Where did you find the wbxml table linking xml tags and their binary hexadecimal value ?

[ggodart]

the APPREF reference - selection of the SIP profile in VoIP profile with "<parm name="TO-APPREF" value="sipref"/>" is not compiled correctly i.e.

I made the patching described on this topic and it worked. But if I send CODEC parameters my E51 phone doesn't react when receiving the SMSes. The problem is related here :
http://discussion.forum.nokia.com/fo...d.php?p=489199
but the proposed solution is not good for a kannel user.

Any Idea ?

[paipeng]

Hello,


after NowSMS problem, I am now trying to figure out the SMS Provisioning with Kannel.

But the WBXML binary data, converted by Kannel, can't be provisioninged by Nokia Symbian Local Provisioning Client. (The SMS sent by Kannel can't insert the configuration on device, althrough can be opened and saved.)

I am using the 1.4.3 (1.4.2) version of Kannel. Does anyone work with Kannel for SMS Provisioning successfully?


Regards

Pai

[ericram]

Just confirmed using now.sms (www.nosms.com) that this problem also exists using their software.

To summarize current findings:

1. There is three different Client Provisioning solutions that all fails to send a VoIP profile that is activated without manually touching it on the phone.
2. The problem is seen on Voip Providers release 2.0 phones (N80ie, E61i, E65) and E61 with release 1.0
3. The problem seems to not be related to the XML provisioning document since the same behavior is also seen when using the original Nokia Example provisioning document from "Example VoIP settings with needed SIP and AP settings" from w9013.txt in Client_Provisioning_Registration_v1_7.zip
4. Also, since the phones in all other cases silently discards configuration messages with errors the problem seems not to be caused by an ill formatted provisioning document

Based on this, I conclude that the probability is high that is a "feature" in the Nokia phone.

regards
frodek

Thank you so much for clearing this up. I was a bit confused at first but this really helped me understand.

Eric
EIP International Calling

[neomax21]

Hi Guys,
I'm having the same problem. I went thru this entire discussion. But my problem still persists. I still need to "touch" the settings, especially
Menu -> Tools -> Settings -> Connection -> Internet Tel. -> <Profile Name> -> SIP Profiles . From there I can cancel and back out without changing any settings and it will reflect in the active SIP profile list in Menu -> Communications -> Internet Tel. (E71 navigation).
I patched the libwbxml that I'm using by changing the 2 lines mentioned in the pdf file.

Locate the string { "name", "RULE", 0x01, 0x3b }, /* OMA */ from wbxml2-0.9.2\src
\wbxml_tables.c file and add the following rows after it:
• { "name", "APPREF", 0x01, 0x3c }, /* OMA */
• { "name", "TO-APPREF", 0x01, 0x3d }, /* OMA */

Plz help.

[neomax21]

Hi,
My problem is solved. TO-APPREF and APPREF values were not matching in my XML file. matched that and now its working fine.

I have one more query though. I still need to go into Menu -> Communications to select a WLAN network to connect through. Can this be automated somehow?? I know its a silly qts, but ne clues about what can be done abt this?? As far as possible I don't want the user to enter ANY settings like window.

[traud]

nemax21, does this help?