Bill, As Andreas says, it is indeed the SMPP provider. Is your provider M081L3way? Many months ago, I pointed out to them the incorrect GSM encoding of the @ character on MO messages... and they may not have fixed it yet -- don't take my word for it though, I haven't retested in a while.
Cheers, Ben. On Friday, 2003-08-15 at 03:38:40 AM, Andreas Fink scribbled: *snip* > > 2003-08-14 18:01:03 [8] DEBUG: Octet string at 0x840f038: > 2003-08-14 18:01:03 [8] DEBUG: len: 28 > 2003-08-14 18:01:03 [8] DEBUG: size: 29 > 2003-08-14 18:01:03 [8] DEBUG: immutable: 0 > 2003-08-14 18:01:03 [8] DEBUG: data: 54 68 69 73 20 69 73 20 62 69 > 6c > 6c 27 73 20 74 This is bill's t > 2003-08-14 18:01:03 [8] DEBUG: data: 65 73 74 2e 2e 2e 20 40 20 3f > 20 > 22 est... @ ? " > 2003-08-14 18:01:03 [8] DEBUG: Octet string dump ends. > 2003-08-14 18:01:03 [8] DEBUG: SMPP PDU dump ends. > > this shows what you get on SMPP. > This is supposed to be 00 in SMPP as SMPP transports your data in GSM > character set. > I think your SMPP provider is screwing it up... > Maybe they use a Comverse SMSC (a good default for screwed up > SMSC's...) > > Andreas Fink > Global Networks Switzerland AG > > Tel: +41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 > Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland > Web: http://www.global-networks.ch/ [EMAIL PROTECTED] > > > > -- Benjamin Lee Melbourne, Australia "Always real." http://www.realthought.net/ __________________________________________________________________________ Jealousy is all the fun you think they have.
