WAP Push Support in Series 60 Devices

[yorgens]

It appears that Nokia 60 Series handsets do not support industry specifications for WAP push. Does anyone have any documentation to support how WAP push technically works. I have developed a portal which dispatches an SMS which we get a confirmation from the SMSC, after this the message never arrives in the Service Inbox....???? Any experience out there?

[quyen]

Hello

Exactly what part of the WAP PUSH specifications are you having problems with on the Series60 phone?
Remember that the Nokia 7650 only supports Service Indications, but the Nokia 3650 and N-Gage support both Service Indications and Service Loading.

For WAP PUSH documentation, please refer to the OMA WAP2.0 Technical documents or at the "Browsing/WAP" Documents at Forum.Nokia
look at the following documents (depends on what you are trying to do with your WAP PUSH):
"Nokia GSM WAP Phone Characteristics v1.1"
"Getting Started with WAP Push, v1.02"
"Enhancing the user experience of mobile services with WAP Push"
"WAP Push Info page document 3/5"
"Over The Air Settings Specification, Version 7.0"

BR.
~quyen

[yorgens]

We are having issues with Service Indications when sent to the Nokia 7650, it doesn't work. The same Service Indication when sent to Nokia 3650, SE - T68i etc... works perfectly.

We are sending ServiceIndication's to other phones with no problems, on
the Nokia 7650, however, nothing happens (interference on my PC screen
seems to indicate the message is getting to the phone). In fact if I
send the ServiceIndication to a non-push port the message arrives but is
displayed as an incorrectly formatted text sms.

Im pushing to port 2948 with a minimal wbxml encoded SI:

DEBUG ServiceIndication dumpBytes 140 Dump Of Service
Indication bytes
DEBUG ServiceIndication dumpBytes 141
DEBUG ServiceIndication dumpBytes 155 02 [ Version number -
WBXML version 1.2 ]
DEBUG ServiceIndication dumpBytes 160 05 [ SI 1.0 Public
Identifier ]
DEBUG ServiceIndication dumpBytes 165 6A [ Charset=UTF-8
(MIBEnum 106) ]
DEBUG ServiceIndication dumpBytes 170 00 [ String table length ]
DEBUG ServiceIndication dumpBytes 182 45 [ SI with content ]
DEBUG ServiceIndication dumpBytes 205 C6 [ Indication with
attributes and content ]
DEBUG ServiceIndication dumpBytes 237 07 [ action signal-medium ]
DEBUG ServiceIndication dumpBytes 262 0C [ http:// ]
DEBUG ServiceIndication dumpBytes 222 03 [ STR_I ]
DEBUG ServiceIndication dumpBytes 301 77 [ w ]
DEBUG ServiceIndication dumpBytes 301 61 [ a ]
DEBUG ServiceIndication dumpBytes 301 70 [ p ]
DEBUG ServiceIndication dumpBytes 301 2E [ . ]
DEBUG ServiceIndication dumpBytes 301 79 [ y ]
DEBUG ServiceIndication dumpBytes 301 61 [ a ]
DEBUG ServiceIndication dumpBytes 301 68 [ h ]
DEBUG ServiceIndication dumpBytes 301 6F [ o ]
DEBUG ServiceIndication dumpBytes 301 6F [ o ]
DEBUG ServiceIndication dumpBytes 301 2E [ . ]
DEBUG ServiceIndication dumpBytes 301 63 [ c ]
DEBUG ServiceIndication dumpBytes 301 6F [ o ]
DEBUG ServiceIndication dumpBytes 301 6D [ m ]
DEBUG ServiceIndication dumpBytes 212 00 [ END_I ]
DEBUG ServiceIndication dumpBytes 217 01 [ END ]
DEBUG ServiceIndication dumpBytes 222 03 [ STR_I ]
DEBUG ServiceIndication dumpBytes 301 73 [ s ]
DEBUG ServiceIndication dumpBytes 301 74 [ t ]
DEBUG ServiceIndication dumpBytes 301 65 [ e ]
DEBUG ServiceIndication dumpBytes 301 76 [ v ]
DEBUG ServiceIndication dumpBytes 301 65 [ e ]
DEBUG ServiceIndication dumpBytes 301 37 [ 7 ]
DEBUG ServiceIndication dumpBytes 212 00 [ END_I ]
DEBUG ServiceIndication dumpBytes 217 01 [ END ]
DEBUG ServiceIndication dumpBytes 217 01 [ END ]
DEBUG ServiceIndication dumpBytes 306
DEBUG ServiceIndication dumpBytes 307 End Dump Of Service
Indication bytes

Any help or ideas would be appreciated.

[ravi@purpleace.com]

Which data coding scheme did you use in the TPDU? (GSM 03.38)