- Forums
- >
- API Platform
- >
- HTTP 500 Internal Server Error on MMS
- Thread RSS
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Favorite
- Subscribe
HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
08.10.2012 11:13 AM
My code is python. No ATT sample, so I downloaded python lib from OneAPI, which is for GSMA v1. I updated so it works with both GSMA v2 and ATT Restful. SMS v2 works fine, either as GSMA or ATT. MMS gives back an HTTP error 500, 'Internal Server Error', for both GSMA and ATT. I tried using no attachments or simple text attachements in the MIME, no difference. I verified that my dev account is set for MMS, and scope is 'MMS,SMS,SPEECH' for the access token. I'm using 'https://api.att.com/rest/mms/2/messaging/outbox'
Any idea what is wrong?
Mime looks like this:
MIME-Version: 1.0
--===============1352573029==
Content-Type: application/x-www-form-urlencoded
MIME-Version: 1.0
Content-Disposition: form-data; name="root-fields"
Address=tel%3A9725551212&Subject=Hello+Max+-+MMS+F
--===============1352573029==--
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
08.14.2012 12:39 PM
Hello,
Are you still seeing this problem? I tested and it seems to be working.
Cheers,
--brett
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
08.15.2012 11:51 AM
still same problem, thanks
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
08.15.2012 01:56 PM
Hello,
So, the MMS API is a little finicky. You need to structure the message as shown in the examples here: https://devconnect-api.att.com/docs/mms-v2/send-mm
I noticed your message was different than the examples. I realize that yours is still MIME, but the MMS API is strict on exactly how the MIME parts are structured.
Can you try the request again but with how the examples have it structured?
Thanks,
--brett
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
08.28.2012 06:23 AM
I will try again, but have other tasks to do before I get back to it. I am puzzled that MIME built by the OneAPI/GSMA Python framework (which was for v1) doesn't work with either the ATT or the GSMA v2.
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
10.09.2012 02:18 PM
The API example, the ATT example code and the OneAPI/GSMA python MIME code are all a little different; there was no way to tell what server was picky about. After a lot of trial and error, I got to a 201 Normal Response.
I am now seeing in the resource url an error I don't understand. The oauth accesstoken works for SMS, and the scope for it was 'SMS,MMS,SPEECH'. Do you know what this means and what needs to be changed?
{"RequestError": {
"PolicyException": {
"MessageId": "POL0001",
"Text": "Invalid value for part %1" ,
"Variables" : "accesstoken" }
}}
Re: HTTP 500 Internal Server Error on MMS
- Mark as New
- Favorite
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Flag as Inappropriate
10.18.2012 12:53 PM
Hello,
It means that the value of the access token is incorrect. Are you passing the access token in the HTTP header as such:
Authorization: Bearer YOUR_ACCESS_TOKEN
Cheers,
--brett
-
-
- of 1
-
-
