MSISDN header dramas | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
Author | Message | |||||
cosjav New member Username: Cosjav Post Number: 1 Registered: 12-2005 |
Hi, I have been submitting MM1 messages successfully to the Now SMS/MMS Gateway (trial version 5.51k, also tried 5.51) by setting all the necessary parameters as part of the MMS. Now I am trying to remove the setting of the source MSISDN (sender address) from the MMS and instead submit it as an HTTP header. I have followed the exact instructions as defined in the document: http://www.nowsms.com/tb/TB-NOWSMS-002.htm This is my MMSC.ini file:
Basically, when I try submitting the MMS it does not get forwarded (the MMS notification doesnt get sent) by Now SMS (it is not even logged in the MMSC-<date> log (event log?) file but the MMSCDebug file says: "Message missing content-type header" at the end of the file. But if you have a look at the top of the MMSCDebuf file you can see that the content-type header is set after the X-MSISDN header is set:
Any ideas? I would really appreciate any help. Thanks, cosjav | |||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5294 Registered: 10-2002 |
Hi cosjav, I think the MSISDN header bit is fine, and the "Content-Type:" in the HTTP header is fine. The error is related to the "Content Type" header within the MMS message itself. Here's what appears to be the problem ... I've excerpted the part of the log that shows the header of the MMS message being posted, and highlighted it in blue: : 2D 61 6C 69 76 65 0D 0A 0D 0A 8C 80 8D 90 85 04 -alive : 43 8F E6 53 01 81 97 36 31 34 31 36 31 35 35 35 C S 614161555 : 37 38 2F 54 59 50 45 3D 50 4C 4D 4E 00 96 54 68 78/TYPE=PLMN Th : 69 73 20 69 73 20 61 20 6E 69 63 65 20 6D 65 73 is is a nice mes : 73 61 67 65 21 21 00 86 80 94 81 90 81 8A 80 8F sage!! : 80 84 A3 02 04 2E 03 83 81 83 48 65 6C 6C 6F 2C . Hello, 8C 80 - message type = m-send-req 8D 90 - MMS Version 1.0 85 04 43 8F E6 53 - date/time stamp 01 81 - invalid data ??? 97 ... - to header This invalid data is throwing off the MMS header parsing, so we don't see the "to" header, or other headers that follow, including the "content-type" header. Therefore, the message is being rejected as being corrupt. Do you have control over the code that is generating this MM1 message content? -bn | |||||
cosjav New member Username: Cosjav Post Number: 2 Registered: 12-2005 |
Thank you for your speedy response! I do have access to the code that is generating this MM1 message content and I am looking into this now. I will post back here once I get a result. Thanks, cosjav |