problem to send Service Loading push message over 8310

[alinesimon]

Hi

I'm implementing push wap 1.2 over nokia 8310 ant 6310.
I have problems with loading service (SL).
I sent a SL message but the 8310 and 6310 don't react.

A structure if sms for push message is : WDP |WSP |WBXML
This a push message SL that i sent for 8310 and 6310 :
<sl
href="http://wap.wapfr.net"
action="execute-high">
</sl>

I sent message via GSM/SMS over 2948 port in connectionless mode.
This is the binary encoding message.
0605040B8423F0000601B001066A008509037761702E776
17066722E6E6574000601

1)Why it's not run for 8310 and 6310 this message?
Have I forgotten WSP headers?This binarny message is ok?
What exactly the structure of SL message. Can you give me
the WSP headers with their respective value ,please.
2)Can you give me a specifications of structure in order to understand.
3) Can you give me a example in binary represented a SL message, please.
4)I sent a CO message. I have trouble to understand what the mobile 8310 or 6310 have to run.
When I sent a CO message, the phone says "Parametres services recus" translated "Received Services Parameters".
It's normal?
If I select "Options" menu, an other "menu" display and ask me to record this message, or display or erase.
If I select "record", I see wap parameters...????

It's normal?
This is a CO message that I sent.
<co>
<invalidate-service uri="http://wap.wapfr.net"></invalidate-service>
</co>

This is a binary encoding CO message :
0605040B8423F0000601B201076A00458706037761702E77617066722E6E6574000101.

This encoding is ok?Can you checking please it's good and can you give informations about CO message structure,please.
Thanks for your help.
charly

[futhark]

This is all wrong !

>>0605040B8423F0000601B001066A008509037761702E776
>>17066722E6E6574000601

06 = length
05 = NBS ports
04 = port length
0B84 = listener port
23F0 = sending port
00 = concat messages ??
06 = ??
01 = ??
B0 = ??
01 = ??
06 = ??
6A = ??
.. 008509037761702E776

please specify why you code the SMS and the WBXML as you do, it seems
to me that it makes no sense ...


Also, the 6310 does not support service loading, only service indication.

regards,
f.

please clarify why you encode the SMS as you do ?

[futhark]

This is all wrong !

>>0605040B8423F0000601B001066A008509037761702E776
>>17066722E6E6574000601

06 = length
05 = NBS ports
04 = port length
0B84 = listener port
23F0 = sending port
00 = concat messages ??
06 = ??
01 = ??
B0 = ??
01 = ??
06 = ??
6A = ??
.. 008509037761702E776

please specify why you code the SMS and the WBXML as you do, it seems
to me that it makes no sense ...


Also, the 6310 does not support service loading, only service indication.

regards,
f.

please clarify why you encode the SMS as you do ?

[sweekeat]

futhark, I'm afraid your analysis is all wrong too :P

06 specifies the UDH length, so after the NBS ports, it should be the actual UD payload already, NOT concatenated msg header. As for whether the payload makes sense, that's another story...

06 = length
05 = NBS ports
04 = port length
0B84 = listener port
23F0 = sending port
--- UDH ENDS HERE ---
00 = concat messages ??
06 = ??
01 = ??
B0 = ??
01 = ??
06 = ??
6A = ??
.. 008509037761702E776