Final NULL value in .MMS file

Final NULL value in .MMS file SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Final NULL value in .MMS file « Previous || Next »
Author Message
Dan Johnston
Unregistered guest
Posted on Tuesday, June 01, 2004 - 09:32 am:   

While sending an MMS message over WSP protocol. I captured the MMS encapsulation data using Ethereal. I notice that the final value is a NULL value '00'. When I examine the .MMS file on NowSMS server that corresponds to this message. Instead of the final '00', there is a '__' character. With the MMS messaging software I am using, when I recieve this message I can't open it as it is incomplete. However, if I add the NULL '00' value to the .MMS file on NowSMS and recieve it I can open it. Is NowSMS server changing the final NULL into the '__'?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2761
Registered: 10-2002
Posted on Tuesday, June 08, 2004 - 08:27 pm:   

Dan,

I replied to your posting of this on another thread:

http://support.nowsms.com/discus/messages/1/4650.html

But I'll repeat the information here...

There is not a requirement for a final NULL character at the end of an MMS message. So I don't understand what you are referring to.

Perhaps you could upload some Ethereal logs, and one of these message files, and explain what bytes you are looking at or changing. Just put them in a ZIP, and upload the attachment in reply to this posting.

-bn
Dan Johnston
New member
Username: Dan

Post Number: 4
Registered: 04-2004
Posted on Monday, June 14, 2004 - 01:02 am:   

Hello Bruce,
Thanks for replying to my question. I have uploaded a zip file that includes the Ethereal Log that displays the final NULL 00 value. Also in the zip is the .MMS file that does not have the NULL. When I recieve the .MMS file, the message is considered incomplete by the messaging software we use and cannot be opened. Using a binary editor I can add the NULL value to the .MMS file and recieve it and open it no problem. So I am pretty sure the problem is the missing NULL value. Why it is missing and where it goes missing is my problem. If you or anyone else could have a look and let me know what your opinion is I'd be grateful.
application/x-zip-compressedEthereal Log for missing null problem
MissingNullChar.zip (35.3 k)
Dan Johnston
New member
Username: Dan

Post Number: 5
Registered: 04-2004
Posted on Monday, June 14, 2004 - 01:06 am:   

Sorry Bryce. I know your name is Bryce but I know someone here who is named Bruce and got his name in the posting instead of yours. Thanks for your time on this problem.
Dan Johnston
New member
Username: Dan

Post Number: 6
Registered: 04-2004
Posted on Monday, June 14, 2004 - 06:41 am:   

Here is a better log taken of the problem. I don't think the first one is good. Please view this attachment.
application/x-zip-compressedLog of Ethereal showing last NULL and .MMS without
MissingNullChar2.zip (5.3 k)
Dan Johnston
New member
Username: Dan

Post Number: 7
Registered: 04-2004
Posted on Tuesday, June 15, 2004 - 08:20 am:   

In case it has some bearing, I am using NowSMS version 4.20.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2844
Registered: 10-2002
Posted on Tuesday, June 15, 2004 - 08:27 pm:   

Dan,

Ok. This is an odd one. The null is definitely in the content, but it is missing in the MMS file that gets stored on the server.

I did some testing here, and I don't see any problems with a NULL byte at the end of the content of an MMS message.

While the NowSMS version 4.20 could be a problem, I don't think it is, as I don't see any problem reports similar to this. (You can download the v5.50 eval from the web site here, and it will recognise your existing serial number.)

I was talking to one of my colleagues about this, and he had any idea about another possibility of how the NULL might be getting lost between the phone and the MMSC. He's going to follow up with you via e-mail. But if that doesn't point to a solution, let's keep looking.

-bn
Dan Johnston
New member
Username: Dan

Post Number: 8
Registered: 04-2004
Posted on Thursday, June 17, 2004 - 11:46 pm:   

Hello Bruce!
Upgrading from WAP3GX to Now.Wap did the trick. The NULL character is now included in the .MMS files! I thank you and Kent Williams so much for following up with this problem and providing the solution. If either of you ever come to Tokyo, make sure you tell me. I owe you both some imbibements!

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