Problems sending binary data

Problems sending binary data SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through March 09, 2004 » Problems sending binary data « Previous || Next »
Author Message
declan magee
New member
Username: Declanmagee

Post Number: 2
Registered: 02-2004
Posted on Friday, February 27, 2004 - 10:33 am:   

Hi , Im trying to send an EMS message of a predefined EMS image.
I am using java to send a http get message.
I have included details from the smslog. I have cut down on the error messages as these seem to be repeats.

any help much appreciated.

?SENDER=07745335117&Data=&PhoneNumber=07966665818&UDH=108100FFFFFFFF800000018000 00018000000183E0080180800801808C6E0180928801809E480180902801808EC601800000018000 00018188678182589401824897018248608182489081824A90818188670180000001800000018000 00018000000180000001800000018000000180000001800000018000000180000001FFFFFFFF&DCS =11&PID=00
10:26:02:106 [4] Debug: 1 recipient entries
10:26:02:106 [4] Debug: 07966665818
10:26:07:341 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
10:26:07:341 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
10:26:08:403 [2] ThreadProcessModem: Processing 4035FB02.req...
10:26:08:403 [2] ThreadProcessModem: OUT: AT+CMGS=138

10:26:08:528 [2] ThreadProcessModem: IN:
10:26:08:528 [2] ThreadProcessModem: OUT: 0041000B817069665618F800118E108100FFFFFFFF80000001800000018000000183E00801808008 01808C6E0180928801809E480180902801808EC60180000001800000018188678182589401824897 018248608182489081824A9081818867018000000180000001800000018000000180000001800000 01800000018000000180000001800000018000
10:26:13:153 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
10:26:13:153 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
10:26:13:215 [2] ThreadProcessModem: Processing 4035FB03.req...
10:26:13:215 [2] ThreadProcessModem: OUT: AT+CMGS=138

10:26:13:340 [2] ThreadProcessModem: IN:
declan magee
New member
Username: Declanmagee

Post Number: 3
Registered: 02-2004
Posted on Monday, March 01, 2004 - 03:17 pm:   

Problem sorted
because the DCS was 11 i.e. seven bit
I needed to place some filler bits to the end of the UDH.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1947
Registered: 10-2002
Posted on Tuesday, March 02, 2004 - 09:34 pm:   

Hi Declan,

I'm glad to hear that you resolved the problem.

While the DCS is suspicious (and is likely a problem) ... my first guess here would have been that the UDH field is not formatted properly.

NowSMS expects the first byte of the UDH to be a byte that indicates the length of the UDH. (This can be a little confusing, but this is consistent with how the UDH is actually represented in the resulting physical message, and consistent with how most reference material describes UDH encoding.)

Also, we have noticed that some GSM modems (particularly phones being used as modems) do not like a message that includes only UDH and nothing after the UDH. When you have a modem like that, you have to add some filler bits. To keep the encoding simple, we usually recommend using a DCS of 8 (Unicode) if you can, and specifying 0020 as the data parameter (a space character).


Login Login / Register Logout Logout Search Last 30 Days Topics Topics