SMS JobSubmit Error

I am trying to send an SMS message using the JobSubmit API, and while it
looks like the request is sent successfully ( I do not get any errors from the web service request), looking at the job status
via the web portal, I see this error:

Error Code: J281
Error: Invalid profile for Managed Email

The Job ID is 95553055 and the XML for the request itself is:

<ns1:JobSubmitRequest>
        <ns1:SubmitId>1350322640</ns1:SubmitId>
        <ns1:Message>
                <ns1:MessageId>1350322640</ns1:MessageId>
                <ns1:JobOptions>
                        <ns1:SmsOptions></ns1:SmsOptions>
                </ns1:JobOptions>
                <ns1:Destinations>
                        <ns1:Sms ref="1350322640">
                                <ns1:Phone>5551231234</ns1:Phone>        [not the phone number I am actually using]
                        </ns1:Sms>
                </ns1:Destinations>
                <ns1:Contents>
                        <ns1:Part>
                                <ns1:Document ref="test_sms">
                                        <ns1:DocType>text</ns1:DocType>
                                        <ns1:DocData format = "text">test message</ns1:DocData>
                                </ns1:Document>
                                <ns1:Treatment>body</ns1:Treatment>
                        </ns1:Part>
                </ns1:Contents>
        </ns1:Message>
</ns1:JobSubmitRequest>

Is this error simply the result of our account not being set up to handle SMS, or is it a problem with the request that we can address on our side?

Find more posts tagged with

Comments

skamens

Yes, this is an account setup issue.

You can resolve it quickly as follows:

Log in to the portal (https://test2.myportal.easylink.com)
Select Jobs->Create/Send Job
On the line that says "Select job type", click "Email".

What should happen is that the portal should prompt you to set up a couple of configuration settings needed for email jobs; this will then resolve the issue with your API-based submission.

The reason this comes up is that the SMS traffic is processed by the Email system, which needs these settings to work properly.

If this doesn't work, we can set up these parameters internally, but I believe this should do the trick.