| WBXML - 'Untrusted' message? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Sam Unregistered guest |
Hey guys, We're getting the following message on a 6600 when we send a WBXML OTA message: "Message received from untrusted service, continue anyway?" Any ideas? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3270 Registered: 10-2002 |
I haven't seen that on the 6600 (I assume you're referring to a Nokia 6600), but there are some different configuration options in the settings of that phone. And it's been awhile since I've spent much time with the 6600.. Are you sending the message with a USERPIN specified? I believe one of the settings in 6600 wants to have messages signed with a PIN code otherwise they are considered untrusted. There is also another issue where on some phones (but on the 6600 I seem to recall this only affects standard WAP push, not OTA), where they show up as being from an "unknown sender" or a blank sender. With NowSMS v5.50c and later, you can use an INI file setting or variable to set this sender value (the initator):
Note that this Initiator should be in the format of a URL, e.g., http://support.nowsms.com/discus/ (include that trailing backslash!) ... or some phones will get even more confused. -bn | |||
| Anonymous |
Hi All, After recieving the OTA settings, Nokia 6600 is displaying like "Message received from untrusted service, continue anyway?" After that if i am trying to save the settings it is displaying like "Unable to save the settings1" Actually i am sending MMS application settings. Other than MMSC address "in Home page" it is saving the other parameters. <WAP-PROVISIONINGDOC> <CHARACTERISTIC%20TYPE="BOOTSTRAP"> <PARM%20NAME="NAME"%20VALUE="GO"%2F> <%2fCHARACTERISTIC> <CHARACTERISTIC%20TYPE="PXLOGICAL"> <PARM%20NAME="PROXY-ID"%20VALUE="mobile"%2F> <PARM%20NAME="NAME"%20VALUE="GO"%2F> <CHARACTERISTIC%20TYPE="PXPHYSICAL"> <PARM%20NAME="PHYSICAL-PROXY-ID"%20VALUE="mobilem"%2F> <PARM%20NAME="PXADDR"%20VALUE="192.168.1.30"%2F> <PARM%20NAME="PXADDRTYPE"%20VALUE="IPV4"%2F> <PARM%20NAME="TO-NAPID"%20VALUE="NAP1"%2F> <CHARACTERISTIC%20TYPE="PORT"> <PARM%20NAME="PORTNBR"%20VALUE="8080"%2F> <%2fCHARACTERISTIC> <%2fCHARACTERISTIC> <%2fCHARACTERISTIC> <CHARACTERISTIC%20TYPE="NAPDEF"> <PARM%20NAME="NAPID"%20VALUE="NAP1"%2F> <PARM%20NAME="BEARER"%20VALUE="GSM-CSD"%2F> <PARM%20NAME="NAME"%20VALUE="CSD"%2F> <PARM%20NAME="NAP-ADDRESS"%20VALUE="918026686260"%2F> <PARM%20NAME="NAP-ADDRTYPE"%20VALUE="E164"%2F> <CHARACTERISTIC%20TYPE="NAPAUTHINFO"> <PARM%20NAME="AUTHTYPE"%20VALUE="PAP"%2F> <PARM%20NAME="AUTHNAME"%20VALUE="mmsuser"%2F> <PARM%20NAME="AUTHSECRET"%20VALUE="mmsc"%2F> <%2fCHARACTERISTIC> <%2fCHARACTERISTIC> <CHARACTERISTIC%20TYPE="APPLICATION"> <PARM%20NAME="APPID"%20VALUE="w4"%2F> <PARM%20NAME="TO-PROXY"%20VALUE="mobile"%2F> <PARM%20NAME="NAME"%20VALUE="MMSC"%2F> <PARM%20NAME="ADDR"%20VALUE="http://192.168.1.30:8514"%2F> <%2fCHARACTERISTIC> <%2fWAP-PROVISIONINGDOC> HTTP/1.1 Issue : 1. It is unable to recognise the ADDR of the MMS application. 2. Is it complesary to use to the UserPin & MAC headers along with the contnet-type Thanks in Advance | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3457 Registered: 10-2002 |
Well, the first problem here is that NowSMS will not accept the above in upper case. XML is case sensitive, and the OMA docs define these settings in lower case. (I'm actually surprised that we are enforcing this, however.) Also, I'm not sure why "/" characters are escaped as %2F ... and " " (space) characters are escaped as %20. Unless you are sending this as an HTTP GET string rather than as HTTP POST data. Here's a cleaned up version of the XML that you posted above: <wap-provisioningdoc> <characteristic type="BOOTSTRAP"> <parm name="NAME" value="GO"/> </characteristic> <characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="mobile"/> <parm name="NAME" value="GO"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="mobilem"/> <parm name="PXADDR" value="192.168.1.30"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="NAP1"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> </characteristic> <characteristic type="NAPDEF"> <parm name="NAPID" value="NAP1"/> <parm name="BEARER" value="GSM-CSD"/> <parm name="NAME" value="CSD"/> <parm name="NAP-ADDRESS" value="918026686260"/> <parm name="NAP-ADDRTYPE" value="E164"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="mmsuser"/> <parm name="AUTHSECRET" value="mmsc"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w4"/> <parm name="TO-PROXY" value="mobile"/> <parm name="NAME" value="MMSC"/> <parm name="ADDR" value="http://192.168.1.30:8514"/> </characteristic> </wap-provisioningdoc> Cleaning it up, I still can't get a Nokia 6600 to save these settings for MMS usage. But that's actually quite easy to explain why ... the Nokia 6600 (and most other Nokia phones, except the 7650/3650 and perhaps a few others) will not allow you to configure a dial-up profile for MMS usage. It requires GPRS for MMS. There's no technical reason for this (well perhaps there is a technical reason specific to the design of the phone's firmware), but you will see that if you work through the phone's menus it is not possible to create a dial-up profile that can be used for MMS settings. | |||
