Page 1 of 1

Invalid Sender?

Posted: Thu Aug 26, 2010 2:20 pm
by Trizzunkz
Has anything changed in the SMS API this morning? I have the following in my app log:

Code: Select all

--------------26/08/2010 08:55:34--------------
1|XXXXXXXXXX||13909136|OK<br>
-------------------------------------------
--------------26/08/2010 09:00:10--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 09:02:14--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 09:03:51--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 09:29:32--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 09:30:25--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 09:35:20--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
--------------26/08/2010 13:03:58--------------
0|XXXXXXXXXX|||Invalid sender
-------------------------------------------
(Phone numbers removed for privacy)
Nothing has changed at my end, so I'm wondering if there are any changes/issues at eXetel's end.

Thanks.
Joel.

Re: Invalid Sender?

Posted: Thu Aug 26, 2010 3:00 pm
by William M
We have begun strictly enforcing rules for the "Sender" field already specified within our HTTP API Document.

HTTP API Documentation Section 1.1
The name or number of the SMS sender that will appear on the destination mobile handset. Restricted to 11 alphanumeric characters or 15 numerical characters.

Cheers Will

Re: Invalid Sender?

Posted: Thu Aug 26, 2010 3:57 pm
by Trizzunkz
Was anyone planning on notifying the API users?

Re: Invalid Sender?

Posted: Thu Aug 26, 2010 4:02 pm
by William M
All users have inherently been advised as this was always the case.

Re: Invalid Sender?

Posted: Thu Aug 26, 2010 4:07 pm
by Trizzunkz
Fair enough.
Thanks for your help.