The MMS web service offers third-party applications the following features:
- Sending an MMS to an AT&T subscriber number.
- Polling for/setting up notifications for delivery reports.
- Receiving an MMS from the subscriber. [This message is sent to the application short code, so the application short code acts as the MSISDN for the application]
- Polling for received messages.
- Setting up notifications for received messages.
Things to note:
- The attachments to the message should be base 64 encoded.
- The target device should be one supported by AT&T or the messages may not go through.
- The SLA specifications applicable to this service should be taken into consideration.
- This is specific to the Message Notification Service : You may need to change the data type for SENDER ADDRESS in the types XSD to String before generating the code for the notification service to avoid Malformed URI exceptions.
- We had issues encoding attachments to base64 and receiving attachments may have similar issues. The team at AT&T is aware of this and is working on supporting binary encoding.
Refer to the attached developer's guide for more details and code examples.
Note: The code examples provided below use classes that you would need to compile for your application. You will need to download the WSDL (append "?wsdl" to the endpoint URL to download the WSDL) for the relevant service and compile these classes using a library like Apache Axis. Eclipse has a plug-in for Axis which makes things easier.
The code below does the following:
- Starts notifications for multimedia messages
- Fetches received messages
- Stops notifications