| What's wrong? |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| newbie Unregistered guest |
now ,i don't understand two question: 1) I POST mms to gw,and can receive the MMS successfully, but i can't get m_send-cnf,while i get the CONNECTREPLY as the following pdu(wsp part), not REPLY! why? 0x02,0x81,0xb5,0x42,0x00,0x15,0x45,0x6e,0x63,0x6f,0x64,0x69,0x6e,0x67,0x2d,0x76, 0x65,0x72,0x73,0x69,0x6f,0x6e,0x00,0x31,0x2e,0x32,0x00, 2)i get mms notication message which begin with 0x8c,0x80,....., but I have a good algorithm to decode it. I mean, I know the meaning of these data,but how should i write a algorithm to decoding it. would you please help me? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 997 Registered: 10-2002 |
1.) Sorry, I don't have enough information about what exactly you are sending to understand. If you don't receive a reply, this is probably an indication that your POST is malformed, and the gateway decided to ignore the malformed packet. 2.) In general, I recommend that you employ an algorithm that does not require specific knowledge of every MMS header (future versions of MMS will add more headers). Each header name can be either an encoded binary value (high bit set, e.g., 0x80), or a text header (value between 0x20 and 0x7F). MMS uses WSP encoding, so conceivably their could be code page shifts in some implementations (see section 8.4.1.1 of the WSP spec), but I would probably just recommend that you punt and consider the message corrupt if you received a code page shift, e.g., value of the header field starts with an octet in the range of 0x00 and 0x1F. Header field values are encoded as per WSP, and section 8.4.1.2 shows how the first octet of the field value can be interpreted. This information allows you to interpret how long the header field value is without understanding the actual content of the header field. | |||
