| OMA OTA settings without proxy/gateway |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| didster New member Username: Didster Post Number: 1 Registered: 02-2005 |
Hi All, I am trying to use NowSMS to send the UK Orange GPRS internet settings to a Nokia 6600. I have sent these settings from oranges site, and have: GPRS APN: orangeinternet GPRS Username: <blank> GPRS Password: <blank> Proxy: <blank> Proxy port: <blank> The unusual two being the proxy port and IP (BTW, why is this refered to as a "WAP gatweway IP" on NowSMS?). I have tried to leave the wap gateway IP blank from the page, and the settings make it to the phone, but it says it's unable to save them. I have tried entering 0.0.0.0, and that works, but sets the proxy IP to 0.0.0.0 which is obviosuly no good. I have also tried entering "192.168.071.035" which is an IP I found from http://www.filesaveas.com/gprs.html but while that makes it to the phone, it doesn't actually work. So basically, I would like to know if there is there anyway of specifiying "None" for the proxy IP from the OMA OTA settings page? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4097 Registered: 10-2002 |
Hi, Someone else was asking about this in another thread: http://support.nowsms.com/discus/messages/1/8582.html Give the XML that I posted in that thread a try. (Unfortunately I can't test it at present.) -bn | |||
| didster New member Username: Didster Post Number: 2 Registered: 02-2005 |
Hi Bryce, I have tried your suggestions, but with no luck  . The SMSs make it to the phone, but say "failed to save connection settings" (thats for the plain XML suggestion). I tried adding a username+password, but the same occured. The method with the form does get to the phone, and does save, but "Enable Proxys" is still set to yes, with an IP of 0.0.0.0  . This must be posiable, the Nokia settings page manages to correctly send it! I was thinking of trying to intercept this SMS from their page, and decode it to get back to exactly what they are sending. I have a GSM modem which does work with NowSMS both ways. Though it has very odd problems.... It keeps resending the same message over and over and reintialising the modem - its a SE GC79. I can only get it to work at all with the Modem Manager SW running (a suggestion I found from this board). And with this running, NowSMS seems to have some problems. Without the modem manager running, I get CMS ERROR 30 all the time. Anyway, thats another problem. It does work, the incomming SMSs come in, and get saved in SMS-In. They are blank though, and I can't get anything useful from them such as UDHs and Data parts. I tried enabeling the debug log, and I do get something in there, but its just a long number, I can't see what I can do with it. Not only that, it's exactly the same for the three messages that make up the OMA OTA (I assume) message sent from Nokia, so I guess it can't be the decoded data. Is there anything I can switch on in NowSMS to try and get back to what it was Nokia's site has sent? Thanks a lot for your help. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4130 Registered: 10-2002 |
I've done a little investigation on this issue. And I don't know if this is the "preferred, correct" way to do things, but it seems that if you send an old style WAP OTA message to the phone, it will ignore the proxy setting in the OTA message and create a connection profile without a proxy. What's odd is that you still have to include a proxy in the setting that you send out, otherwise the phone complains that the message is not a supported format. I tried this approach on a Nokia 6260 and a Nokia 6600. (I would have liked to also try a 3650, but I can't get it to start up for me. What is it about Nokia Series 60 phones where if they sit idle for an extended period of time, they lock up during startup?) This said, Nokia Series 40 phones seem to ignore the older WAP OTA settings, so I'm not sure what you do with those phones. Intercepting the other settings is a good idea. But it sounds like your modem is having some issues with binary messages. I'd be curious to see the SMSDEBUG.LOG. | |||
| didster New member Username: Didster Post Number: 3 Registered: 02-2005 |
Hi Bryce, Odd isn't it. Well, our aim is to basically provision a small number of handsets for all the different UK operators. Whenever possible, we try to use the old style Nokia/Ericsson (WAP) OTA settings message, simply because as you say the phone is quite happy to accept it without a proxy. Only one UK network is causing us problems, Orange, which doesn't seem to use a proxy, all the rest do. And likewise, only one phone is causing the problem, the 6230, which as you say doesn't accept the WAP OTA messages in favour of OMA ones. At the moment, the intercepting method seems the only way forward. Well, there are a few problems it seems with this modem, some of which may be related to it's inability to correctly process incoming binary SMSs, so I'm going to put some logs up. First off, here is a log of sending a SMS, with the Modem manager software that comes with the modem not running. In this case, the SMS does not go through: ------------------------------------- 08:37:15:281 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 08:37:17:281 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:37:17:281 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:37:17:281 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:37:17:687 [2] TestModemSpeed: Initialised modem at 115200 bps 08:37:17:937 [2] ThreadProcessModem: AT+CPMS? 08:37:18:000 [2] ThreadProcessModem: +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK 08:37:18:000 [2] ThreadProcessModem: AT+CNMI? 08:37:18:078 [2] ThreadProcessModem: OK 08:37:18:078 [2] ThreadProcessModem: AT+CPMS=? 08:37:18:140 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:37:18:140 [2] ThreadProcessModem: Modem initialization complete: COM6: [snip] 08:38:37:437 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:38:37:437 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=XXXXX&Text=Test&InfoCharCounter=&PID=&DCS =&Submit=Submit 08:38:37:437 [5] Debug: 1 recipient entries 08:38:37:437 [5] Debug: +XXXXX 08:38:37:437 [5] ThreadProcessConnection: Request processing complete 08:38:37:890 [2] ThreadProcessModem: Processing 42257B8D.req... 08:38:37:890 [2] ThreadProcessModem: OUT: AT+CMGS=17 08:38:37:953 [2] ThreadProcessModem: IN: > 08:38:37:953 [2] ThreadProcessModem: OUT: 0001000C91447743018363000004E439790E 08:38:38:031 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 30 08:38:38:031 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 30 08:38:39:281 [2] ThreadProcessModem: Processing 42257B8D.req... 08:38:39:281 [2] ThreadProcessModem: OUT: AT+CMGS=17 08:38:39:343 [2] ThreadProcessModem: IN: > 08:38:39:343 [2] ThreadProcessModem: OUT: 0001000C91447743018363000004E439790E 08:38:39:421 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 30 08:38:39:421 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 30 08:38:51:421 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:38:51:421 [2] ThreadProcessModem: After ModemRelease - COM6: 08:38:58:343 [0] main: Shutdown: Closing log files ------------------------------------- Next, we have sending a SMS with the software running. In this case, it does go though, but it never gets deleted from NowSMSs Q directory, and basically keeps sending itself over and over ------------------------------------- 08:40:28:484 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 08:40:30:484 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:40:30:484 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:40:30:484 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:40:30:906 [2] TestModemSpeed: Initialised modem at 115200 bps 08:40:31:156 [2] ThreadProcessModem: AT+CPMS? 08:40:31:218 [2] ThreadProcessModem: +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK 08:40:31:218 [2] ThreadProcessModem: AT+CNMI? 08:40:31:281 [2] ThreadProcessModem: OK 08:40:31:281 [2] ThreadProcessModem: AT+CPMS=? 08:40:31:343 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:40:31:343 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:40:32:718 [2] ModemReceiveMessages: +CME ERROR: 513 08:40:38:718 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:40:38:718 [2] ThreadProcessModem: After ModemRelease - COM6: 08:40:44:734 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:40:44:734 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:40:44:734 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:40:45:140 [2] TestModemSpeed: Initialised modem at 115200 bps 08:40:45:218 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:40:45:390 [2] ThreadProcessModem: AT+CPMS? 08:40:45:468 [2] ThreadProcessModem: +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK 08:40:45:468 [2] ThreadProcessModem: AT+CNMI? 08:40:45:531 [2] ThreadProcessModem: OK 08:40:45:531 [2] ThreadProcessModem: AT+CPMS=? 08:40:45:593 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:40:45:593 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:40:46:265 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:40:46:265 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=XXXXX&Text=dsds&InfoCharCounter=&PID=&DCS =&Submit=Submit 08:40:46:265 [5] Debug: 1 recipient entries 08:40:46:265 [5] Debug: +XXXX 08:40:46:343 [5] ThreadProcessConnection: Request processing complete 08:40:46:359 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:40:46:359 [5] ThreadProcessConnection: Processing request /favicon.ico 08:40:46:359 [5] ThreadProcessConnection: Request processing complete 08:40:46:968 [2] ThreadProcessModem: Processing 42257C0E.req... 08:40:46:968 [2] ThreadProcessModem: OUT: AT+CMGS=17 08:40:47:031 [2] ThreadProcessModem: IN: > 08:40:47:031 [2] ThreadProcessModem: OUT: 0001000C91447743018363000004E439790E 08:40:47:296 [2] ReceiveModemCommand: trying again... 08:40:47:562 [2] ReceiveModemCommand: trying again... 08:40:47:828 [2] ThreadProcessModem: ERROR - Error waiting for response from modem (2) 08:40:47:828 [2] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (2) 08:40:53:906 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:40:53:906 [2] ThreadProcessModem: After ModemRelease - COM6: 08:40:59:906 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:40:59:906 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:40:59:906 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:41:00:312 [2] TestModemSpeed: Initialised modem at 115200 bps 08:41:00:562 [2] ThreadProcessModem: AT+CPMS? 08:41:00:625 [2] ThreadProcessModem: +CPMS: "SM",0,15,"SM",0,15,"SM",0,15 OK 08:41:00:625 [2] ThreadProcessModem: AT+CNMI? 08:41:00:687 [2] ThreadProcessModem: OK 08:41:00:687 [2] ThreadProcessModem: AT+CPMS=? 08:41:00:750 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:41:00:750 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:41:05:750 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:41:05:750 [2] ThreadProcessModem: After ModemRelease - COM6: 08:41:12:484 [0] main: Shutdown: Closing log files ------------------------------------- I did try receiving an SMS without the SW running next, but in this case nothing happens. So I'll skip that and go straight to the receiving an SMS with the modem manager running. This is the provisioning message sent from Nokia for the 6230 on Orange ------------------------------------- 08:46:12:421 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 08:46:14:421 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:46:14:421 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:46:14:421 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:46:14:843 [2] TestModemSpeed: Initialised modem at 115200 bps 08:46:19:921 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:46:19:921 [2] ThreadProcessModem: After ModemRelease - COM6: 08:46:44:921 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:46:44:921 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:46:44:921 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:46:45:328 [2] TestModemSpeed: Initialised modem at 115200 bps 08:46:45:593 [2] ThreadProcessModem: AT+CPMS? 08:46:45:671 [2] ThreadProcessModem: +CPMS: "SM",4,20,"SM",4,20,"SM",4,20 OK 08:46:45:671 [2] ThreadProcessModem: AT+CNMI? 08:46:45:734 [2] ThreadProcessModem: OK 08:46:45:734 [2] ThreadProcessModem: AT+CPMS=? 08:46:45:812 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:46:45:812 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:46:46:140 [2] ReceiveModemCommand: trying again... 08:46:46:390 [2] ModemReceiveMessages: +CMGL: 0,0,18 0791448720003023000886127000000000503010110162000120 08:46:46:390 [2] ModemReceiveMessages: Decoding received message index 0 from message storage ME 08:46:46:390 [2] ModemReceiveMessages: 0791448720003023000886127000000000503010110162000120 08:46:46:390 [2] ModemReceiveMessages: SMSC address len = 7 08:46:46:390 [2] ModemReceiveMessages: SMSC Address = +447802000332 08:46:46:390 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 08:46:46:390 [2] ModemReceiveMessages: Sender address len = 8 08:46:46:390 [2] ModemReceiveMessages: Sender Address = 21070000 08:46:46:390 [2] ModemReceiveMessages: PID = 00 08:46:46:390 [2] ModemReceiveMessages: DCS = 00 08:46:46:390 [2] ModemReceiveMessages: Anticipated user data length = 1 08:46:46:390 [2] ModemReceiveMessages: Message = 08:46:46:390 [2] ModemReceiveMessages: AT+CMGD=0 08:46:46:421 [3] ThreadProcessInboundSMS: Processing 42257D76.in... 08:46:46:468 [2] ModemReceiveMessages: +CME ERROR: 513 08:46:46:531 [2] ModemReceiveMessages: +CME ERROR: 513 08:46:52:531 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:46:52:531 [2] ThreadProcessModem: After ModemRelease - COM6: 08:46:58:562 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:46:58:562 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:46:58:562 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:46:58:984 [2] TestModemSpeed: Initialised modem at 115200 bps 08:46:59:234 [2] ThreadProcessModem: AT+CPMS? 08:46:59:296 [2] ThreadProcessModem: +CPMS: "SM",5,20,"SM",5,20,"SM",5,20 OK 08:46:59:296 [2] ThreadProcessModem: AT+CNMI? 08:46:59:359 [2] ThreadProcessModem: OK 08:46:59:359 [2] ThreadProcessModem: AT+CPMS=? 08:46:59:421 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:46:59:421 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:46:59:562 [2] ModemReceiveMessages: +CME ERROR: 513 08:46:59:828 [2] ReceiveModemCommand: trying again... 08:47:00:093 [2] ReceiveModemCommand: trying again... 08:47:00:187 [2] ModemReceiveMessages: +CMGL: 4,0,20 0791447758100650040C91449771427887000050302080641400014A 08:47:00:187 [2] ModemReceiveMessages: Decoding received message index 4 from message storage SM 08:47:00:187 [2] ModemReceiveMessages: 0791447758100650040C91449771427887000050302080641400014A 08:47:00:187 [2] ModemReceiveMessages: SMSC address len = 7 08:47:00:187 [2] ModemReceiveMessages: SMSC Address = +447785016005 08:47:00:187 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 08:47:00:187 [2] ModemReceiveMessages: Sender address len = 12 08:47:00:187 [2] ModemReceiveMessages: Sender Address = +447917248778 08:47:00:187 [2] ModemReceiveMessages: PID = 00 08:47:00:187 [2] ModemReceiveMessages: DCS = 00 08:47:00:187 [2] ModemReceiveMessages: Anticipated user data length = 1 08:47:00:187 [2] ModemReceiveMessages: Message = J 08:47:00:187 [2] ModemReceiveMessages: AT+CMGD=4 08:47:00:250 [2] ModemReceiveMessages: +CME ERROR: 513 08:47:00:421 [3] ThreadProcessInboundSMS: Processing 42257D77.in... 08:47:06:250 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:47:06:250 [2] ThreadProcessModem: After ModemRelease - COM6: 08:47:12:250 [2] ThreadProcessModem: Before ModemAllocate - COM6: 08:47:12:250 [2] ThreadProcessModem: After ModemAllocate - COM6: - OK 08:47:12:250 [2] ThreadProcessModem: Re-initializing modem: COM6: ... 08:47:12:656 [2] TestModemSpeed: Initialised modem at 115200 bps 08:47:12:906 [2] ThreadProcessModem: AT+CPMS? 08:47:12:968 [2] ThreadProcessModem: +CPMS: "SM",5,20,"SM",5,20,"SM",5,20 OK 08:47:12:968 [2] ThreadProcessModem: AT+CNMI? 08:47:13:031 [2] ThreadProcessModem: OK 08:47:13:031 [2] ThreadProcessModem: AT+CPMS=? 08:47:13:093 [2] ThreadProcessModem: +CPMS: ("SM","BM","SR"),("SM"),("SM") OK 08:47:13:093 [2] ThreadProcessModem: Modem initialization complete: COM6: 08:47:37:125 [2] ThreadProcessModem: Before ModemRelease - COM6: 08:47:37:125 [2] ThreadProcessModem: After ModemRelease - COM6: 08:47:43:437 [0] main: Shutdown: Closing log files ------------------------------------- And here is finally is one of the .SMS files from SMS-In: ------------------------------------- [SMS-IN] ModemName=COM6: Sender=21070000 Data= Binary=0 ------------------------------------- When NowSMS is running and so is Modem manager, as the SMSs come in MM beeps, and if you look in it's own SMS section, you see three blank SMSs in the inbox from 21070000 - the Nokia site. I'm not sure if this entire problem is being caused by having the two pieces of SW running at the same time - but for the like of me I can't get Now to do anything without MM running. Thanks a lot for your help | |||
| didster New member Username: Didster Post Number: 4 Registered: 02-2005 |
Finally... After a lot of monkeying around, I have got the XML I need. This wasn't done in the end using NowSMS, I did it with another S60 phone, then extracted the WBMXML out of the message store and converted it to XML. Here's what it looks like: <wap-provisioningdoc> <characteristic type="NAPDEF"> <parm name="NAPID" value="Orange Internet"></parm> <parm name="BEARER" value="GSM-GPRS"></parm> <parm name="NAME" value="Orange Internet"></parm> <parm name="NAP-ADDRESS" value="orangeinternet"></parm> <parm name="NAP-ADDRTYPE" value="APN"></parm> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"></parm> <parm name="AUTHNAME" value=""></parm> <parm name="AUTHSECRET" value=""></parm> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w2"></parm> <parm name="NAME" value="Orange Internet"></parm> <parm name="TO-NAPID" value="Orange Internet"></parm> <characteristic type="RESOURCE"> <parm name="URI" value="http://orange.multimedia/"> </parm> <parm name="NAME" value="Orange Internet"></parm> <parm name="STARTPAGE" value="http://orange.multimedia/"></parm> </characteristic> </characteristic> </wap-provisioningdoc> That works on the 6230 (Proxys are disabled). Though it works on nothing else For example the motorola V620 which handles OMA messages fine from NowSMS, ignores it. I've tried changing it to short hand (/ rather than </parm>) and it still does the same. Bryce, is there anything that jumps out at you as being incorrect with that above snippit? I'm still intrested in getting the problems with the modem sorted though, if you have any ideas on that? Thanks a lot. | |||
| Martin Higham New member Username: Martin Post Number: 1 Registered: 03-2005 |
I was struggling to get this to work for a number of networks and ended up opting for the easy solution of configuring my wireless village clients to use WSP and the standard GPRS WAP access points. These always include proxy settings. I did run in to an additional probelm with Series 60. Virgin Mobile doesn't use a password with its authentication. Putting in the line <parm name="AUTHSECRET" value=""></parm> when the name is not blank caused my 6670 to reset itself. Leaving the line out works but causes the phone to prompt for the username/password when initiating a connection. This is the exact behaviour that the Virgin or Nokia OTA settings cause too, so it is clearly a known problem. Settings that I have working for the 6670 do not work when provisioned to a 6630 or 6170! This area is a minefield. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4425 Registered: 10-2002 |
Many Nokia phones do not seem to like the empty AUTHNAME and AUTHSECRET parameters. I've had better luck just leaving them out if they are not needed. We're going to modify the behaviour of NowSMS when OMA OTA settings are sent out and no proxy server (WAP gateway) address is configured. The update should be posted within the next week. But to send out settings with an APN only and no proxy/gateway, the template will look something like this: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="Orange Internet"/> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="Orange Internet"/> <parm name="NAPID" value="Orange_Internet_NAPID"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAP-ADDRESS" value="orangeinternet"/> <parm name="NAP-ADDRTYPE" value="APN"/> <parm name="INTERNET"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> </characteristic> </characteristic> </wap-provisioningdoc> Or ... if you also want to include a home page: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="Orange Internet"/> </characteristic> <characteristic type="NAPDEF"> <parm name="NAME" value="Orange Internet"/> <parm name="NAPID" value="Orange_Internet_NAPID"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAP-ADDRESS" value="orangeinternet"/> <parm name="NAP-ADDRTYPE" value="APN"/> <parm name="INTERNET"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w2"/> <parm name="NAME" value="Orange Internet"/> <parm name="TO-NAPID" value="Orange_Internet_NAPID"/> <characteristic type="RESOURCE"> <parm name="NAME" value="Orange Internet"/> <parm name="URI" value="http://orange.multimedia/"/> <parm name="STARTPAGE"/> </characteristic> </characteristic> </wap-provisioningdoc> This is somewhat similar to the example above. But note the following differences: 1.) A bootstrap name is included. Nokia phones ignore this, but other phones use this as the settings name, so it's a good idea to include it. 2.) Instead of <parm ..></parm>, the tags are self-closing ... <parm/>. Both should be treated equivalently by a phone, but you never know. 3.) The AUTHNAME and AUTHSECRET parameters with empty values have been left out. Some Nokia phones reboot themselves when encountering an empty value for these parameters. 4.) In the browser home page definition, "STARTPAGE" should not have a value according to the XML schema. The proper approach is to have a "URI" parm with the the homepage value, and then a separate "STARTPAGE" parm without a value. 5.) "INTERNET" parm added to the "NAPDEF" characteristic. It's somewhat vague what this parameter means, but it sort of implies that the profile is used for general internet connectivity. I'd be interested if anyone has any further feedback on these settings! -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4433 Registered: 10-2002 |
Follow-up ... the NowSMS update that I referenced above, which changes the OMA OTA template when the proxy/gateway field is left blank is now available. It is part of the v5.51b patch, for more details please see http://www.nowsms.com/whatsnew.htm. | |||
| sensuale Unregistered guest |
can ne1 tell me pls if theres another proxy port for the 6230 thanx | |||
