Unable to send MMS. Gateway sends 0x40 (Bad request) error

Unable to send MMS. Gateway sends 0x40 (Bad request) error SearchSearch
Author Message
Murali Mohan.K
Unregistered guest
Posted on Monday, July 19, 2004 - 10:50 am:   

Hi Bryce,

I am trying to send an MMS through a service provider supporting MMS. But the gateway is sending 0x40 (Bad request) error. What could be the possible reason for this? With the same service provider I was able to send MMS from my application a few weeks back.

Even I checked the packets I am sending through Ethereal. All packets look correct.
Another interesting thing is, I am able to receive an MMS, but only sending fails.

I believe, the problem should not be because of a malformed M-Send-req PDU sent from my App. If there is any problem with MMS PDU, I should get M-Send-Cnf with some error status.
I believe the problem must be the way WSP Post request my App is sending.

Plz let me know if you have any idea about this.

Thanks in advance,
Murali
Murali Mohan.K
Unregistered guest
Posted on Monday, July 19, 2004 - 11:02 am:   

Hi Bryce,

For more clarity, I am attaching the ethereal dump also.

application/octet-streamEthereal dump
ethereal_16.dump (1.5 k)
Ravikanth Bollapragada
New member
Username: Ravikanth_b99

Post Number: 17
Registered: 03-2004
Posted on Monday, July 19, 2004 - 11:45 am:   

Hi Murali,

It seems to me like.. if we try to send MMS to an email address, some network providers are treating it, as a bad request (status code: 400). I too experienced the same problem with O2-Viag from Germany.

Try sending the same MMS to a normal MMS enabled mobile phone, you should be getting OK-Success result.

Anyway, I could not give you any solution here, but just sharing my experience and wanted to know, what happens if you send the same to a mobile phone, rather to an email address.

Thanks,
Ravikanth Bollapragada
http://www.bollapragada.com/ravikanth.htm
Murali Mohan.K
Unregistered guest
Posted on Monday, July 19, 2004 - 03:18 pm:   

Hi Ravikanth,

It does not seem to be the problem because of Email address. I tried sending it to even a MMS enabled phone number but with the same result.

Moreover I dont see any reason why an MMSC says Bad request if it cannot handle email address. It must use M-Send-Cnf to indicate that the message not accepted and can also pass the reason as a string in X-Mms-Response-Text.

I would like to know with which service provider you faced such a problem.

Thanx for sharing your problem

Murali
Ravikanth Bollapragada
New member
Username: Ravikanth_b99

Post Number: 18
Registered: 03-2004
Posted on Monday, July 19, 2004 - 04:26 pm:   

Hi Murali,

Thank you for your comment !
Please have a look at the attachement, which shows the full transaction for sending mms to an email address.

text/plainO2 Viag - Germany - MMS Send Failure
mmstrans02error.txt (24.8 k)


Thanks,
Ravikanth Bollapragada
http://www.bollapragada.com/ravikanth.htm
Murali Mohan. K
Unregistered guest
Posted on Tuesday, July 20, 2004 - 01:20 pm:   

Hi Bryce,

The problem seems to be with the MMS message. M-Send-Req PDU did not have From field which is mandatory. So the MMSC sent Bad request. The message was formed from Nokia toolkit which does not save the message with From field, unless we check the From field.

I am able to send the message by inserting "Insert Address Token" field for From filed.

But I did not understand why MMSC says bad request when there is a problem with MMS message. It can instead send M-Send-Cnf with some error status.
I hope you can throw some light on this matter.

Thanx in advance
Murali
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3193
Registered: 10-2002
Posted on Friday, July 30, 2004 - 11:38 pm:   

Hi Murali,

I'm glad to see that you were able to figure the problem out. It is a good idea to always double check and verify that every field in a particular PDU type that is marked as "Required" is generated by your client.

It is ridculous to have to insert a from header that basically says "I need the MMSC to insert my address please". That is why many MMSCs will accept the message ... because they know that they have to insert the sender address anyway (and wouldn't trust it if it were supplied by the client).

Returning an HTTP response of "400 Bad Request" is an odd way of handling this, but I've seen others in similar situations (such as from address inserted) return "403 Unauthorised".

-bn