>This is not exactly what I had in mind - (a) as this kind of string >would get translated by kannel to '?<' as ESC will be translated >directly to '?'. (b) the GSM standards _currently_ do define the ESC >sequences as valid. I'm not really worried about current standard >support in phone (as newer phones would surely conform to the current >standards), but more with standard support within Kannel. and my >question is (again) - which do you think is the correct implementation, >Kannel's counting only actual characters, or Siemens M20's counting >every septet ? > >P.S >tests show that some phones just silently ignore the escape sequences >(showing the character after the ESC - the triangle bracket), for >example - the Nokia 33, and some show the intended result - the square >bracket, for example - the Nokia 71. > >Oded Arbel >m-Wise Inc. >[EMAIL PROTECTED] >
What I can tell from EMI usage, the escape sequence stuff is slightly broken. I got customers sending \n in their text (because they've forgotton to replace it with linefeed). In kannel this translates the \ to two characters. The problem here is that it increses the size of the text and this AFTER the message has been split. The result of that is that we will end up with SMS being longer than 160 characters. So while you take a look into this, think about this fact. The final header has to be the number of octets of the SMS after escape sequences have been applied. The escape stuff is something done in the phone and the SMSC never cares about it. For the SMSC its just a stream of bytes. -- Andreas Fink Fink-Consulting ------------------------------------------------------------------ Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com ------------------------------------------------------------------ Something urgent? Try http://www.smsrelay.com/ Nickname afink
