| Does this look correct (EMS) |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through August 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Omar Marji New member Username: Omarello Post Number: 2 Registered: 07-2004 |
Hello, I am just getting the hang of how to encode and decode EMS messages... my question is does the following look like a correct UDH for an EMS message. 820C8000424547494E3A494D454C4F44590D0A56455253494F4E3A312E300D0A464F524D41543A43 4C415353312E300D0A4D454C4F44593A2A3366336633663323633123643323643323643363317233 66336633663323633323663323663323663366332A342363332363332363332A332361310D0A454E 443A494D454C4F44590D0A Also i have another question does the udhl have to be the exact number of octets. I mean lets say i have 76 octets but in my UDHL it is 78 does it affect the result.. casue i read some examples that had the length not exactly the same as the number of octets.. thanx a lot | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3181 Registered: 10-2002 |
Hi Omar, Without validating the actual data, I'd say the headers look correct. The UDHL is correct, and the length of the information element "0C" is correct. I'm not sure I understand your question about the UDHL ... but basically the receiving client is going to parse UDHL bytes out of the message to interpret as the UDH. If that length is not correct, then the client is likely not to be able to parse it correctly and will report an error regarding the message. (If the UDHL is larger than the actual amount of data, the SMSC might also reject the message.) -bn | |||
