Problems setting up P800 internet accounts via OMA | Search |
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through August 01, 2006 ⬆ |
◄ ► |
Author | Message | |||
Gary Chapman Unregistered guest |
Hi, I'm having a nightmare time trying to send simple Internet Account settings to my P800. The following is rejected by the handset: <characteristic type="NAPDEF"> <parm name="NAME" value="internet"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAP-ADDRESS" value="apn1.mydomain.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> </characteristic> whereas the following is accepted by the handset: <characteristic type="NAPDEF"> <parm name="NAME" value="internet"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAP-ADDRESS" value="apn1.mydomain.com"/> </characteristic> However, when I look at the address (Control Panel->Internet Accounts->Edit <account>->Advanced) it's empty (and should contain the NAP-ADDRESS value). These are the only <characteristic> blocks within my XML document. Do I need to define something else? All I want to do is provision several GPRS Internet Accounts, each one having its own APN. Could someone please point me in the right direction? I've read through the SonyEricsson P800/P900 WAP Provisioning and OTA Settings doc as well as the OMA ProvCont doc but neither seem to address how to perform this seemingly simple task. Is this even possible via OMA, or do I need to use individual older-style OTA messages? Thanks, Gary | |||
Anonymous |
Hi, Same problem with me, on P800. I have copied same setting as given in the document wap_provision_ota_p800_p900_r2a.pdf. The first example (Simple exmple) given in page 14 is not accepted by phone also another example (Advance) given in page 16 is accepted by phone but the pin 1111, as given in document is not accepted. I have successfully pushed OTA settings using "older-style OTA messages". Please help. Thanks, Abhi | |||
Gary Chapman Unregistered guest |
Hi Abhi, Try this as the MAC Parameter block for example 1: 33414534313332354638463637424137434646453733423532423342364142334333303130313637 00 Try this as the MAC Parameter block for example 2: 39344644413835463738434632444444394238333645324238314532383536304135353546434535 00 PIN is still 1111 in both examples. Does the P800 accept them now? The mistake they made was to take the MAC value, eg "3AE41325F8F67BA7CFFE73B52B3B6AB3C3010167" and convert the letters to lowercase. Gary | |||
Abhi Unregistered guest |
Hi Gary, Thanks for your suggestion. I have tried second example but it not works. First i have received message "New browser settings have been received. Enter PIN for PROV_NAP_ADV... validate the received information". Then i have entered PIN 1111. But PIN is not accepted. Error is "Invalid PIN". My complete WBXML string is, 00062F1F2DB6918192 39344644413835463738434632444444394238333645324238314532383536304135353546434535 00 020B6A0045C655018707060350524F565F4E41505F41445600018711060350524F565F4E41505F41 44560001871006AB01C65A01870C069B01870D0603666F6F0001870E060362617200010101C65101 8707060350524F565F5741505F4144560001871C06037777772E666F6F6261722E636F6D0001C652 01872006033132332E3132332E3132332E313233000187210685018722060350524F565F4E41505F 4144560001C65301872306033932303100010101C659018719069C01871A0603666F6F0001871B06 036261720001010101 The second line is MAC parameter block, as suggested by you. Please help me to solve this problem. Can you give me a completed WBXML, that works in your phone. Abhi | |||
Gary Chapman Unregistered guest |
Hi Abhi, I used this XML: <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd"> <wap-provisioningdoc> <characteristic type="NAPDEF"> <parm name="NAME" value="PROV_NAP_ADV"/> <parm name="NAPID" value="PROV_NAP_ADV"/> <parm name="BEARER" value="GSM-GPRS"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="CHAP"/> <parm name="AUTHNAME" value="foo"/> <parm name="AUTHSECRET" value="bar"/> </characteristic> </characteristic> <characteristic type="PXLOGICAL"> <parm name="NAME" value="PROV_WAP_ADV"/> <parm name="STARTPAGE" value="www.foobar.com"/> <characteristic type="PXPHYSICAL"> <parm name="PXADDR" value="123.123.123.123"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="PROV_NAP_ADV"/> <characteristic type="PORT"> <parm name="PORTNBR" value="9201"/> </characteristic> </characteristic> <characteristic type="PXAUTHINFO"> <parm name="PXAUTH-TYPE" value="HTTP-BASIC"/> <parm name="PXAUTH-ID" value="foo"/> <parm name="PXAUTH-PW" value="bar"/> </characteristic> </characteristic> </wap-provisioningdoc> And it produced this WBXML: 01062F1F2DB691819239344644413835463738434632444444394238333645324238314532383536 30413535354643453500020B6A0045C655018707060350524F565F4E41505F414456000187110603 50524F565F4E41505F4144560001871006AB01C65A01870C069B01870D0603666F6F0001870E0603 62617200010101C651018707060350524F565F5741505F4144560001871C06037777772E666F6F62 61722E636F6D0001C65201872006033132332E3132332E3132332E31323300018721068501872206 0350524F565F4E41505F4144560001C65301872306033932303100010101C659018719069C01871A 0603666F6F0001871B06036261720001010101 It worked ok on my P800. Please let me know if you work out how to just add a simple GPRS Internet account with an APN. Gary | |||
Abhi Unregistered guest |
Hi Gery Many Thanks for a quick revert. The above example works. I am trying to do "simple GPRS Internet account" and let you know. Just a few queries about the above suggestion Who do we calculate WSP header? I know in "01 06 2F1F2D B6" 01 is trans ID 06 is for PDU type: push and 06 is for application/vnd.wap.connectivity-wbxml. But how to calculate '2F1F2D'. If i change values in above example do i have to calculate WSP again? Can i save the settings without using a PIN? If yes then please send me a example WBXML. Thanks again | |||
Gary Chapman Unregistered guest |
Hi Abhi, // HeadersLen (see WAP-230 WSP 8.2.4.1) 2F = 47 bytes of header data in total // Content-Type 1F = length quote; the following value is > 0x1F 2D = 45 bytes of content-type data this is followed by 45 bytes of data counting to the end of the MAC block. Without using a PIN, it will look like this: 01 06 01 // header length B6 // application/vnd.wap.connectivity-wbxml02 // End of headers, Start of WBXML 02 // WBXMLVersion 1.2 .. .. etc. Gary | |||
Abhi Unregistered guest |
Hi Gary, When i am pushing OTA without PIN i am getting 'syntactical error'. Without PIN my WBXML is 010601B6020B6A0045C655018707060350524F565F4E41505F41445600018711060350524F565F4E 41505F4144560001871006AB01C65A01870C069B01870D0603666F6F0001870E0603626172000101 01C651018707060350524F565F5741505F4144560001871C06037777772E666F6F6261722E636F6D 0001C65201872006033132332E3132332E3132332E313233000187210685018722060350524F565F 4E41505F4144560001C65301872306033932303100010101C659018719069C01871A0603666F6F00 01871B06036261720001010101 What is wrong with it. One more question when i am changing values of some parameter, example provided by you, the same error, 'syntactical error', occured. Abhi | |||
Gary Chapman Unregistered guest |
Hi Abhi, It looks like the P800 won't accept some messages if they don't have a PIN. If you send the WBXML that I posted 2 messages ago (on Thursday, December 09, 2004 - 05:59 am) it is accepted by the phone. Gary | |||
Abhishek Pandey New member Username: Abhishek_pandey Post Number: 1 Registered: 12-2004 |
Hi Gary, I have noticed that in the WBXML exmample given by you if i change values of some paramters then P800 doesn't accept setting, giving syntactical error, with PIN and without PIN. For example i have changed value of <parm name="AUTHNAME" value="foo"/> to <parm name="AUTHNAME" value="bar"/> and convert it to WBXML i.e. "626172" now my final WBXML is, 01062F1F2DB691819239344644413835463738434632444444394238333645324238314532383536 30413535354643453500020B6A0045C655018707060350524F565F4E41505F414456000187110603 50524F565F4E41505F4144560001871006AB01C65A01870C069B01870D06036261720001870E060362617200010101C651018707060350524F565F5741505F4144560001871C06037777772E 666F6F6261722E636F6D0001C65201872006033132332E3132332E3132332E313233000187210685 018722060350524F565F4E41505F4144560001C65301872306033932303100010101C65901871906 9C01871A0603666F6F0001871B06036261720001010101 When in the same above WBXML i have removed 00, end on inline string, which is my mistake, the setting are accepted P800 asking for PIN when i have entered 1111 as PIN P800 showing error "Invalid PIN". This WBXML is 01062F1F2DB691819239344644413835463738434632444444394238333645324238314532383536 30413535354643453500020B6A0045C655018707060350524F565F4E41505F414456000187110603 50524F565F4E41505F4144560001871006AB01C65A01870C069B01870D060362617201870E060362617200010101C651018707060350524F565F5741505F4144560001871C06037777772E 666F6F6261722E636F6D0001C65201872006033132332E3132332E3132332E313233000187210685 018722060350524F565F4E41505F4144560001C65301872306033932303100010101C65901871906 9C01871A0603666F6F0001871B06036261720001010101 What is wrong in this WBXML? Please suggest how to change values of parameters. Abhi | |||
Abhishek Pandey New member Username: Abhishek_pandey Post Number: 2 Registered: 12-2004 |
Hi Gary, One more thing i want to pointed out that in Series 60 document form Nokia WBXML xml is 1.3 but in the specifications for P800 it is 1.2. Is it makes any difference when converting XML to WBXML. Abhi | |||
Gary Chapman Unregistered guest |
Abhi, The MAC block is calculated based on the WBXML (which starts at 020B6A00...) If you go in and change bytes after this then you will need to recalculate the MAC block (the P800 OMA doc has instructions for this). If it's XML Version 1.2 then the WBXML will start with 02, Version 1.3 will be 03, Version 1.4 will be 04 etc. Gary | |||
Abhishek Pandey New member Username: Abhishek_pandey Post Number: 3 Registered: 12-2004 |
Hi Gary, Can you help me to calculate MAC value i.e. step by step. I need this urgently. Thanks, Abhi | |||
AndreR Unregistered guest |
Run HashCalc. Data Format: HexString Data: insert your WBMXL (030B6A....) HMAC: Select Key Format: Text String Key: insert your PIN (1111) Press "Calculate" Take a line from SHA1 for example: baf331ccfc21875498df23b250060b8d47e25286 Convert to Upper Case: BAF331CCFC21875498DF23B250060B8D47E25286 And convert to HEX: 42414633333143434643323138373534393844463233423235303036304238443437453235323836 That's all. Good Luck! | |||
Abhishek Pandey New member Username: Abhishek_pandey Post Number: 15 Registered: 12-2004 |
Hi Gary/Abhishek, Have to got success to set MMS account using OMA CP for P800. If yes can you please send me that XML document. Thanks in advance. Sobhi C | |||
ramakrishna New member Username: Talluritrk Post Number: 5 Registered: 05-2004 |
Hi all, As I observed few mobiles are expecting the MAC value in small letters (Nokia) & few mobiles ( SonyEricsson) are expecting the MAC value in Capital letters, 1. is it client s/w implemetation issue ? 2. What is the standed way in converting the MAC value into Octenets ? Thanks in Advance Ramakrishna | |||
Anonymous |
I have a question... I want to put only the content-type without SEC for not requiring PIN, which will be the headerlen and lenght-quote?? It's my trace: 01 06 3C1F2D ??¿¿¿ I suppose that I will have to replace these parameters. B6 WbXML 030b6a127364702e6f75722e636f6d004e415020310045c656018715068300018707060378797a00 0101c651018715068300018707060348656c6c6f576f726c640001871c0603687474703a2f2f0083 00032f4955542f686f6d65706167652e68746d0001c65201872f0603476174657761792031000187 2006033131312e33312e3232322e343600018721068501872206830c01c653018723060338300001 872406d201010101c65501871106830c01871006ab01870706034f55522047505253000187080603 6f75722e6e6574000187090689010101 Regards, Thanks Ruben. | |||
Anonymous |
Hi Ruben, I tried to use a length of 1, and 4 without any luck ("030601B6" "041F02B6"). If you find out how to post a settings message without a pin, please post it here - I'll do the same. Thanks Arnon | |||
Anonymous |
deleted by admin 797 | |||
steven New member Username: Stevenwireless Post Number: 3 Registered: 04-2006 |
seems pin is necessary, unless you work with carrier, |