Does Nokia MMSEngine for JAVA omits headers?

Does Nokia MMSEngine for JAVA omits headers? SearchSearch
Author Message
Eitan Gur
New member
Username: Eitangur

Post Number: 2
Registered: 01-2005
Posted on Sunday, February 27, 2005 - 05:09 pm:   

Hi

I'm using Nokia's MMSEngine for sending MMS messages. For some reason, I loose headers I put manually in multiparts.
Is this a bug or a feature?

Thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4102
Registered: 10-2002
Posted on Monday, February 28, 2005 - 07:18 pm:   

I'm sorry, but in order to answer your question, I need more detail.

What headers are you talking about?

Through what interface are you submitting messages?

Through what interface are you routing messages externally?
Eitan Gur
New member
Username: Eitangur

Post Number: 3
Registered: 01-2005
Posted on Tuesday, March 01, 2005 - 07:32 am:   

Hi

Thanks for your reply.
I'm using EAIF15 for sending the MMS messages with Nokia MMS Engine. The router is also Nokia's MMSC (I think version 3.1).
The headers I'm talking about are X headers. Specifically I'm trying to send the header X-Name in every BodyPart. I see it in the message before sending, but the received message arrives without them.

Thanks again, hope you could help me.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4126
Registered: 10-2002
Posted on Tuesday, March 01, 2005 - 04:56 pm:   

As long as the message stays in MM1 (or EAIF) format, those headers should be preserved.

So if you submit the message via EAIF, and the message is delivered by NowSMS as a direct delivery MMSC, or routed to another MMSC over MM1 or EAIF, those headers should remain.

But if the message gets converted to MM7 or MM4, we will not convert those headers. We only convert well-known headers when going between these formats.

Can I ask why you need an "X-Name" header ... i.e., What is the purpose of this header?

Also, I would like to see an MMSCDEBUG.LOG that shows your message being submitted so I can make sure that I understand correctly what type of header you are referring to. The easiest way to enable the MMSCDEBUG.LOG is via a checkbox on the "Serial #" page of the configuration dialog.

-bn