| Urgent!! MMSC returning M-Send-cnf with status set as "Invalid con... |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Murali Mohan.K |
Hi, I am trying to send M-Send-Req PDU to an MMSC. But it returns M-send-cnf with "Invalid Content; Plz try again" status. I have sent my M-Send-req PDU as follows... 0x8c, 0x80, 0x98, 0x4d, 0x73, 0x67, 0x54, 0x49, 0x44, 0x31, 0x32, 0x33, 0x34, 0x0, 0x8d, 0x90, 0x97, 0x39, 0x31, 0x34, 0x36, 0x36, 0x33, 0x37, 0x32, 0x0, 0x8a, 0x83, 0x8f, 0x81, 0x94, 0x81, 0x86, 0x81, 0x90, 0x81, 0x84, 0xa3, 0x1, 0x1, 0x15, 0x83, 0x77, 0x72, 0x69, 0x74, 0x65, 0x20, 0x79, 0x6f, 0x75, 0x72, 0x20, 0x74, 0x65, 0x78, 0x74, 0x20, 0x68, 0x65, 0x72, 0x65, 0x00 The PDU can be decoded as follows..... 0x8c, 0x80, -- Msg Type M-Send-req 0x98, 0x4d, 0x73, 0x67, 0x54, 0x49, 0x44, 0x31, 0x32, 0x33, 0x34, 0x0, -- TID-- MsgTID1234 0x8d, 0x90, -- MMS Version 1.0 0x97, 0x39, 0x31, 0x34, 0x36, 0x36, 0x33, 0x37, 0x32, 0x0, -- To -- 91466372 0x8a, 0x83, -- Msg Class -- Auto 0x8f, 0x81, -- Priority -- Normal 0x94, 0x81, -- Sender Visibility -- Show 0x86, 0x81, -- Delivery-Report -- No 0x90, 0x81, -- Read Reply -- No 0x84, 0xa3, -- Content-type -- Multipart.Mixed 0x1, -- number of components Component starts ============= 0x1, -- length content-type plus other headers 0x15, -- Length of data 0x83, -- Content Type text/plain 0x77, 0x72, 0x69, 0x74, 0x65, 0x20, 0x79, 0x6f, 0x75, 0x72, 0x20, 0x74, 0x65, 0x78, 0x74, 0x20, 0x68, 0x65, 0x72, 0x65, 0x00 -- Equivalent text is "Write your text here" I am not able to find any problem here... But the MMSC says "Invalid content". Am I missing some header here? like "Accept Charset"... etc... Plz let me know if some changes to be made. Thanx in advance Murali | |||
| Bryce Norwood - NowSMS Support |
Murali, The only issue that jumps out at me is that the phone number in the "To:" field should be suffixed with /TYPE=PLMN. I don't see anything wrong with the content itself. I guess another issue is that the "From:" field is mandatory in an MMS PDU ... even if the "From-value" is "insert-address-token". As this header field is mandatory in the spec, I could see an MMSC rejecting a message because the header is not present. Another related issue would be whether or not the MMSC has the ability to identify you based on how you have made your connection to it. Often, the way this works is that the WAP gateway is integrated into the access server/GGSN so that the WAP gateway can map the IP address that a request comes from to a phone number. The WAP gateway can then inform other servers, such as the MMSC about the identity associated with a request. If the MMSC cannot determine your identity through its normal means, then it might return an unusual error (although I'd expect the error in such a case to be error-sending-address-unresolved). -bn | |||
