2 1.see Smart Messaging 2.0 for info, what the DMCP is
4 2.I didn't have success in changing menus via cable (without sending SMS).
5 Here is example foogle funtion. You will see only "Nokia service update failed"
6 ------------------------------------
7 int foogle(char *argv[])
9 GSM_NetworkInfo NetworkInfo;
12 char buffer[100]= { 0x0c, 0x01,
13 0x06, /* User Data Header Length */
14 0x05, /* IEI: application port addressing scheme, 16 bit address */
15 0x04, /* IEDL (IED length ?) */
16 0x15, /* destination address: high byte */
17 0x84, /* destination address: low byte */
18 0x00, /* originator address: high byte */
19 0x00}; /* originator address: low byte */
23 /* Initialise the code for the GSM interface. */
85 for (i=0;i<MSGLEN;i++) {
86 fprintf(stdout,_("%c"),buffer[i]);
89 Protocol->SendMessage(MSGLEN, 0x12, buffer);
90 GSM->GetNetworkInfo(&NetworkInfo); //need to make something
97 -----------------------------------
98 3.to change via SMS - read parts of email sent by Martin Lucina [mato@kotelna.sk]
99 -----------------------------------
101 1. First of all, use the OPER (Operator) services rather than the Nokia
102 services. There's probably no reason why you couldn't use either but
103 there may be extra hooks in the phone firmware regarding Nokia
104 services that I don't know about.
106 2. Make sure that "Operator access number 1" and "Operator access number
107 2" are set correctly in the services menu. The former should be set
108 to the SMS centre the messages you send are going to come from
109 (important, send yourself a test message and check it's details, some
110 operators set the sending SMSC number to one different from the one
111 you originally sent the message to). The latter should be the number
112 of the MS you are sending the SMS from.
114 3. Don't send the messages as binary NBS messsages using the UDH. I
115 haven't been able to get this method to work and besides, the //SCK
116 compatibility header works just fine.
118 Also, while I haven't seen this, it's possible that if you send a
119 message in binary format, the destination MS will reply in binary
120 format. This makes the reply useless if you are sending from another
121 NBS-aware phone, since the NBS router will most likely silently
122 discard it (or try to forward it to the phones TTML/DMCP server,
123 which won't help either).
125 If you send the messages as text, the replies I've seen also come
126 back as text so you can retrieve them from the phone in the normal
129 One caveat I've noticed with sending NBS messages using the //SCK
130 compatibility header is that the NBS grammar in the Nokia SM spec
131 version 2 contradicts the grammar in the original Intel NBS spec. Nokia
132 says you can using either a newline or space as the delimiter after
133 "//SCK", it turns out that you _must_ use a space (as stated in the
134 Intel spec). Of course you can still stick a newline in afterwards.
136 I have attached a test file that will add two menu items that send SMS
137 messages to your services menu. I send this to the phone using
139 $ sendsms +6421XXXXXX < addsms
146 Martin Lucina http://www.kotelna.sk/mato/ Wellington, New Zealand
147 I've always been mad I know I've been mad like the most of us are
148 Pretty hard to explain why you're a madman even if you're not mad