Clickatell routing error

clickatell routing error

The SendSMS HTTP request may fail either because of wrong credentials, wrong subscription package or blocking HTTP access to Message Media. You may see this indicated in your message report as a 'Routing error'. •. To be able to send to France - Orange, you need to enable your 2.5 credit profile. Text of Clickatell SOAP Changes to DocumentationAdded error code 901 Added message concat maximum of 35 Added Error Code 130 and Message Status 014.

Clickatell routing error - right!

Unable to send SMS using clickatell

Here is a more detail solution to the problem above. I recently had the same problem with Ushahidi 2.1 code. You can download the complete solution at http://tambalamin.com/clickatell-patch-code.zip. All you will need to do is upload the files to the correct path using the path info provided. You will be able to send SMS from Ushahidi using Clickatell easily.


What was changed in Messages.php

Some where between line 282 and 286

//$sms_to = intval($reply_to->message_from);

The above line was replaced with

$sms_to = $reply_to->message_from;


What was changed in Clickatell_API.php

Some where between line 202 and 206

//$comm = sprintf ("%s/sendmsg?session_id=%s&to=%s&from=%s&text=%s&callback=%s&unicode=%s%s",

The above line was replaced with

$comm = sprintf ("%s/sendmsg?session_id=%s&to=%s&from=%s&text=%s&callback=%s&mo=1&unicode=%s%s",


application/controllers/admin/messages.php

plugins/clickatell/libraries/Clickatell_API.php


Testing your clickatel API outside Ushahidi to make sure it works and can send SMS to your number. Copy and paste the below in your URL and replace the text in []


http://api.clickatell.com/http/sendmsg?api_id=[ADD YOUR API ID here]&user=[ADD YOUR USERNAME]&password=[ADD YOUR PASSWORD]&to=[ADD THE NUMBER YOU ARE SENDING TO WITH COUNTRY CODE]&text=[YOUR SMS MESSAGE GOES HERE]&from=[ENTER YOUR CLICKATEL TWO-WAY NUMBER here]&mo=1


You will end up with something like this


http://api.clickatell.com/http/sendmsg?api_id=3355076&user=tlamin&password=xxxx&to=19176234281&text=Testing+Clickatel+outside+Ushahidi&from=15626615847&mo=1


http://api.clickatell.com/http/sendmsg?api_id=3355076&user=tlamin&password=xxxx&to=19176234281&text=0123&from=15626615847&mo=1&unicode=1


You should get something ID: c553c4d9e33b27b29113c6ff06fc0972 in your browser and the message will show up at the destination address. If this does not work, check more



Clickatell SMS: no text message received; delivery failed due to routing error

  1. Last updated
  2. Save as PDF
  • Article Type: General
  • Product: Aleph
  • Product Version: 20

Problem Symptoms:
Trying to configure the ams proxy for provider Clickatell, using the instructions in the document "Configuring SMS from Aleph using provide Clickatell", the institution was added as described, with real account information.
When testing as described in Step 4, the output indicates the request was successful, but no text message is received.
The error report on the Clickatell account page shows that the the Clickatell server received the message, but delivery failed due to a "routing error".
Checking with Clickatell tech support, the URL needs to have a "from=" and "MO=" parameter, which seems to be missing from the aleph ams proxy url. (See example in Additional Information below.)

Cause:
Missing ProviderMo and ProviderFrom parameters

Resolution:
As discussed in http://customercenter/DocumentationCenter/Ex Libris Documentation/Primo/OLH_4_9_1/Technical_Guide/SMS_Messages09.17.4.html , the <ProviderMo> and <ProviderFrom> parameters are required....

*ProviderMo ?€“ Enter 1 (true) to enable two-way messaging for mobile originations.

*ProviderFrom ?€“ Enter the mobile number assigned to the Clickatell account. This parameter is required to allow messages to be sent from your USA long code (which is required to send messages to the USA).
A U.S. number should be preceded by "1". Example: 18472275555.

Additional Information

Sample URL (without the "from=" and "MO=" parameters) from the jboss server log: http://api.clickatell.com/http/sendmsg? user=umichlib_test&password=xxxxxxxxx&api_id=3534155&to=15173920656&text=test


Checking the Message Status

One of the features of the Clickatell SMS Gateway is the ability to check the status of sent SMS/TXT Messages that you have sent from Data Manager.

Important: you can only query the status of messages that have been successfully submitted from Data Manager to the Clickatell SMS Gateway, i.e. those that return an ID number (for example ID: cbe87b795e12d4c46eed5500459a6cee indicates the SMS/TXT Message was successfully submitted, where cbe87b795e12d4c46eed5500459a6cee is the unique ID allocated to your message by Clickatell). The ID number is used to query the status of the message.

 

Querying the Status of an SMS/TXT Message

To query the status of an SMS/TXT Message that you have previously sent to a single Contact from your Data Manager Contacts database:

1. Go to the Data Manager Home Screen.

2. Click the Contacts button.

3. Locate the Contact you sent the SMS/TXT Message you wish to query to and click the Person Icon to the left of their First Name. You will now be viewing the full details for the selected Contact. See the section on Searching the Contacts database for instructions on how to find a Contact.

4. Click the SMS tab - this displays any SMS/TXT Messages previously sent to this Contact:

5. Click this Icon under the SMS tab to the right of the SMS/TXT Message you wish to query to view the SMS/TXT Message. A new Windows showing the details for the SMS/TXT Message will appear as follows:

6. This window shows the details for the SMS/TXT Message, including the sender, recipient, message text and send result. To query the status of the message click the Message Status button. Data Manager will query the Clickatell SMS Gateway for the details of the selected SMS/TXT Message, and a new Window showing the Message Status will appear:

You can use the SMS Message Status Codes field to compare the response to see the status of the selected SMS/TXT Message. Look for the number that follows the word Status in the Sent Message Status field. The Clickatell SMS Gateway will return a response in the Sent Message Status field to a message query in the following format:

ID: number Status: number

For example ID: 006e05805b21c0e9c6461d8f6b20d70b Status: 004 indicates the SMS/TXT Message was received by recipient , where cbe87b795e12d4c46eed5500459a6cee is the unique ID allocated to your message by Clickatell and 004 is the Message Status.

The possible responses from the Clickatell SMS Gateway when checking the Message Status are:

Sent Message Status ((Clickatell SMS Gateway Response)

Description

001

Message unknown - The message ID is incorrect or reporting is delayed

002

Message queued - The message could not be delivered and has been queued for attempted redelivery

003

Delivered to gateway - Delivered to the upstream gateway or network (delivered to the recipient)

004

Received by recipient - Confirmation of receipt on the handset of the recipient

005

Error with message - There was an error with the message, probably caused by the content of the message itself

006

User cancelled message delivery - The message was terminated by an internal mechanism

007  

Error delivering message - An error occurred delivering the message to the handset

008

OK - Message received by gateway

009

Routing error - The routing gateway or network has had an error routing the message

010

Message expired - Message has expired before we were able to deliver it to the upstream gateway. No charge applies

011

Message queued for later delivery -  Message has been queued at the gateway for delivery at a later time (delayed delivery)

012

Out of credit - The message cannot be delivered due to a lack of funds in your account. Please re-purchase credits

In addition to these responses above from the Clickatell SMS Gateway Data Manager can also return an internal error that beings with $$ if there was a problem querying the Message Status of the SMS/TXT Message to the Clickatell SMS Gateway (for example if you were not connected to the Internet or your Internet connection was unavailable):

Sent Message Status(Data Manager Internal Error)

Description

$$-1

User cancelled

$$12002

The request has timed out. (ERROR_INTERNET_TIMEOUT)

$$-4230

The connection timed out

$$-3242

This protocol is not supported (use only http and https)

$$-30776

Authentication error, you need to supply a correct user name and password

$$-92    

Servername part of the url is too long

$$-2110

Path part of the url is too long

Other errors may be returned, specifically errors in the range 300 to 599, which are HTTP Status Codes.

When you have finished querying the Status of your SMS/TXT Message click the green Close button to close the Message Status window then click the green Close button to close the SMS/TXT Message details window and return to the main Contacts database.

TIP: you can also click the Message Status button that is on the screen after you have sent a single SMS/TXT Message and also after you have sent a bulk SMS/TXT Message.

Sometimes your system may display a clickatell routing error message. There can be many reasons for this problem.

Repair your computer now.

  • Step 1: Download and install ASR Pro
  • Step 2: Open the program and click "Scan PC"
  • Step 3: Click "Repair now" to start the repair process
  • Speed up your computer today with this easy and free download.

    I recently upgraded a valid trial account to a paid starter pack, and because I was assigned a long number, attempts to send messages through my HTTP API were unsuccessful, and messages appeared in the message reporting console with the following features:

    Repair your computer now.

    Are you tired of dealing with pesky computer errors? Tired of losing files, or having your system crash without warning? Well, say goodbye to all your worries, because ASR Pro is here to help! This incredible software will quickly and easily identify and repair any Windows issues, so you can get back to work (or play) in no time. Not only that, but by using ASR Pro you'll also be better protected against hardware failure, malware infections and data loss. So why wait? Get ASR Pro today and start enjoying a smooth, error-free computing experience!


    I have verified that the username, my personal password, and my API ID have been entered correctly, and the long amount is consistent with an active API user. I tried the “Valid Sample Code” provided in the API Application Console, still with the same result. Below are some erroneous information identifiers that are applicable to the entire Clickatell team if they are helpful.

    clickatell routing error

    Since it’s still worth something, my test account worked fine and as expected, so I’m pretty sure it’s probably not a user error. In (obvious) percentage terms. I also updated a few weeks ago; I don’t know if there can be a waiting period between the activation of the credit card account and the operation of the service. Many thanks if you consider any help on this.

    When submitting reviews from your account, you must specify the following parameters:

    The MO=1 parameter tells our gateway that the numbers originate from a two-way number with no sender ID, which ensures that many messages are routed along a certain trusted route. The from=two number.parameter type should also be used to ensure successful delivery of messages by anyone with a two-way number.

    Problem with Trying symptoms:
    configure ams proxy for Clickatell provider using the instructions in the “Configure Aleph SMS to Allow Clickatell” state, the configuration was added with account information as described actually. Br>< When tested as described in step 4, the output shows that the request was successful, but no private message was received. Error".
    After checking with Clickatell tech support, the URL should have “from=” and therefore “MO=”, which the parameter seems to have disappeared from the URL of the Aleph-Ams proxy site (see below). example in Other information types below.)

    Resolution:
    As specified by Http://customercenter/DocumentationCenter/Ex in Libris Documentation/Primo/OLH_4_9_1/Technical_Guide/SMS_Messages09.17.4.html, required
    clickatell routing error

    Clickatell SOAP

    SOAP API Specification V 1.2.117May 2012

    SOAP API Specification V 1.2.119 December 2011

    SOAP API Specification v.1.2.1

    1.1. 2. 3. 4. 5. 6. 7.

    Content

    Content ................................................................................................................................................ 0 Change history .................................................................................................................................... 2 Overview ............................................................................................................................................. 2 Introduction .......................................................................................................................................... 3 Getting started ..................................................................................................................................... 3 Submitting SOAP to the gateway ........................................................................................................ 5 Basic commands ................................................................................................................................. 5 7.1 Authentication and session ids ...................................................................................................... 5 7.2 Ping ................................................................................................................................................ 6 7.3 Send a message ............................................................................................................................ 6 7.4 Query a message ........................................................................................................................... 7 8. Message parameters .......................................................................................................................... 8 8.1 Table of parameters ....................................................................................................................... 8 8.2 Message parameters in detail ...................................................................................................... 10 9. Additional Commands ....................................................................................................................... 18 9.1 Delete/Stop message................................................................................................................... 18 9.2 Query balance .............................................................................................................................. 19 9.3 Coverage query ........................................................................................................................... 19 9.4 MMS Push ................................................................................................................................... 20 9.5 WAP push service indication ....................................................................................................... 21 9.6 Get message charge query.......................................................................................................... 22 9.7 Token (voucher) pay .................................................................................................................... 23 10. Batch messaging ............................................................................................................................... 23 10.1 Start batch ............................................................................................................................... 23 10.2 Sending messages to existing batch ....................................................................................... 24 10.3 Quick send to batch ................................................................................................................. 25 10.4 End batch................................................................................................................................. 25 11. Message examples ........................................................................................................................... 26 11.1 Simple examples ..................................................................................................................... 26 11.2 Batch SMS examples .............................................................................................................. 28 12. Appendix A: Error codes ................................................................................................................... 31 13. Appendix B: Message statuses ......................................................................................................... 32 14. Terminology....................................................................................................................................... 33 15. Contact details................................................................................................................................... 35

    Copyright 2000 - 2011 Clickatell. All rights reserved.

    1

    SOAP API Specification v.1.2.1

    2. Change historyApproximately six (6) months of changes are reflected.Visit http://www.clickatell.com/downloads/soap/Clickatell_SOAP.pdf to check for updates to this document

    Version1.2.1 1.2 1.1.9

    Date19 December 2011 12 August 2011 28 February 2010

    SectionAppendix A 8 & Appendix A 12 & 13

    Changes to DocumentationAdded error code 901 Added message concat maximum of 35 Added Error Code 130 and Message Status 014

    3. OverviewThis technical document is intended for developers who wish to use the Clickatell SOAP API for sending messages, and describes the various programming methods and commands used by developers when using this API. SOAP is a protocol for exchanging XML-based messages using HTTP/HTTPS. It uses XML as its message format and is transmitted via HTTP/S. SOAP messages are in the form of a packet and submitted to a SOAP portal for our gateway to pass on To use this API, you need to register at (http://www.clickatell.com/register/?product=1). When you sign up for a SOAP account you will be given a username, password and api_id: keep these at hand. Once you have registered and been activated you will receive 10 free credits with which to test our service. Messages sent with these credits contain a canned (pre-populated) message. You can test the API using these credits, and purchase credits to start sending your own, customised messages. It is recommended that you have an understanding of profiles before reading this document. Information is available at http://www.clickatell.com/help-support/developer-apis/routing-profile-guide. Please note that we request delivery acknowledgement for every message we send although delivery acknowledgement status will only be delivered to you if requested. There are a number of different ways of gaining access to the gateway: SMTP - enabling a server or client generated email to be delivered as an SMS. HTTP / HTTPS - submitting either a POST or GET to the API server. FTP uploading a text file to our FTP Server. XML posting to our gateway using XML over HTTP/S. COM Object for Windows based development. SOAP submit SOAP packets over HTTP/S. SMPP customers requiring a high throughput binary socket connection.

    Copyright 2000 - 2011 Clickatell. All rights reserved.

    2

    SOAP API Specification v.1.2.1In order to reduce testing costs, Clickatell offers a test number range. Messages sent to any number on this prefix will only be charged 1/3 of a credit. Use the number 279991xxxxx (for South Africa) or 1999xxxxxxx (for the U.S.) where xxxxx represents any numeric string. Message statuses will be returned. We will cover the SOAP method in this document. Additional documentation is available for the other methods. Sample code is provided on the site.

    4. IntroductionThe SOAP API uses Web Services Description Language, which is an XML-based language that provides a model for describing Web services. WSDL is often used in combination with SOAP and XML Schema to provide web services over the Internet. A client program connecting to a web service can read the WSDL to determine what functions are available on the server. Any special data types used are embedded in the WSDL file in the form of XML Schema. The client can then use SOAP to actually call one of the functions listed in the WSDL. Note: It is important that the ENTIRE document is read before contacting support. Parameters are case-sensitive. You must use character references for Greek and other extended characters.

    5. Getting startedIn order to use the Clickatell gateway you need a Clickatell account and at least one registered connection (API sub-product instance) between your application and our gateway. Each connection method is known as a sub-product (of our API product). Heres how: Step 1 - register for a Clickatell account If you do not already have a Clickatell Central account, you need to register for one as per below. If you have a Clickatell Central account, proceed to Step 2 for instructions on how to add an API connection to your account. Go to http://www.clickatell.com/products/sms_gateway.php, and choose the appropriate API subproduct (connection method) you wish to use. Click on the registration hyperlink. Select the Account type you would like to use (Local or International) Enter your personal information to complete the registration form Accept Terms & Conditions Click Continue - an email containing an activation link will be sent to the email address you have provided(Local account type registrations will be shown a confirmation pop-up where you need to confirm that you wish to register for a local account type.)

    If y

    Support forum

    Clickatell is not routing the messages sent through Diafaan.

    when I click send, the log says that the gateway sent the message.
    just few seconds after, I get a failed status and the following error message:
    Status: 301: Error: Status error received after the message was accepted by the Clickatell gateway.
    Error: 9: The routing gateway or network has had an error routing the message.
    Message: test3333333333
    =======================================================
    I contacted clickatell about their "error routing" and this is their reply:

    Hi Richard,

    Thank you for contacting Clickatell

    The issue is that you have not specified to use the 2-way number when sending the messages. You will need to specify the following additional parameters in your code:

    mo=1 (this activates 2-way messaging)
    from=XXXX (Specifying your 2-way number as the source address)

    For example:
    https://api.clickatell.com/http/sendmsg?user=XXX&password=XXX&api_id=XXX&mo=1&from=XXX&to=Destinationaddress&text=message+content ;

    If you need any further assistance, please feel free to reply to this email.

    Clickatell SMS: no text message received; delivery failed due to routing error

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Problem Symptoms:
    Trying to configure the ams proxy for provider Clickatell, using the instructions in the document "Configuring SMS from Aleph using provide Clickatell", the institution was added as described, with real account information.
    When testing as described in Step 4, the output indicates the request was successful, but no text message is received, clickatell routing error.
    The error report on the Clickatell account page shows that the the Clickatell server received the message, but delivery failed due to a "routing error".
    Checking with Clickatell tech support, the URL needs to have a "from=" and "MO=" parameter, which seems to be missing from the aleph ams proxy url. (See example in Additional Information below.)

    Cause:
    Missing ProviderMo and ProviderFrom parameters

    Resolution:
    As discussed in http://customercenter/DocumentationCenter/Ex Libris Documentation/Primo/OLH_4_9_1/Technical_Guide/SMS_Messages09.17.4.htmlthe <ProviderMo> and <ProviderFrom> parameters are required.

    *ProviderMo ?€“ Enter 1 (true) to enable two-way messaging for mobile originations.

    *ProviderFrom ?€“ Enter the mobile number assigned to the Clickatell account. This parameter is required to allow messages to be sent from your USA long code (which is required to send messages to clickatell routing error USA).
    A U.S. number should be preceded by "1". Example: 18472275555.

    Additional Information

    Sample URL (without the "from=" and "MO=" parameters) from the jboss server log: http://api.clickatell.com/http/sendmsg? user=umichlib_test&password=xxxxxxxxx&api_id=3534155&to=15173920656&text=test


    server certificate verification error fetchmail Unable to send SMS using clickatell

    Here is a more detail solution to the problem above. I recently had the same problem with Ushahidi 2.1 code. You can download the complete solution at http://tambalamin.com/clickatell-patch-code.zip. All you will need to do is upload the files to the correct path using the path info provided. You will be able to send SMS from Ushahidi using Clickatell easily.


    What clickatell routing error changed in Messages.php

    Some where between line 282 and 286

    //$sms_to = intval($reply_to->message_from);

    The above line was replaced with

    $sms_to = $reply_to->message_from;


    What was clickatell routing error in Clickatell_API.php

    Some where between line 202 and 206

    //$comm = sprintf ("%s/sendmsg?session_id=%s&to=%s&from=%s&text=%s&callback=%s&unicode=%s%s",

    The above line was replaced with

    $comm = sprintf ("%s/sendmsg?session_id=%s&to=%s&from=%s&text=%s&callback=%s&mo=1&unicode=%s%s",


    application/controllers/admin/messages.php

    plugins/clickatell/libraries/Clickatell_API.php


    Testing your clickatel API outside Ushahidi to make sure it works and can send SMS to your number. Copy and paste the below in your URL and replace the text in []


    http://api.clickatell.com/http/sendmsg?api_id=[ADD YOUR API ID here]&user=[ADD YOUR USERNAME]&password=[ADD YOUR PASSWORD]&to=[ADD THE NUMBER YOU ARE SENDING TO WITH COUNTRY CODE]&text=[YOUR SMS MESSAGE GOES HERE]&from=[ENTER YOUR Clickatell routing error TWO-WAY NUMBER here]&mo=1


    You will end up with something like this


    http://api.clickatell.com/http/sendmsg?api_id=3355076&user=tlamin&password=xxxx&to=19176234281&text=Testing+Clickatel+outside+Ushahidi&from=15626615847&mo=1


    http://api.clickatell.com/http/sendmsg?api_id=3355076&user=tlamin&password=xxxx&to=19176234281&text=0123&from=15626615847&mo=1&unicode=1


    You should get something ID: c553c4d9e33b27b29113c6ff06fc0972 in your browser and the message will show up at the destination address. If this does not work, check more



    Clickatell SOAP

    SOAP API Specification V 1.2.117May 2012

    SOAP API Specification V 1.2.119 December 2011

    SOAP API Specification v.1.2.1

    1.1. 2. 3, clickatell routing error. 4. 5. 6, clickatell routing error. 7.

    Content

    Content . 0 Change history . 2 Overview . 2 Introduction . 3 Getting started . 3 Submitting SOAP to the gateway . 5 Basic commands . 5 7.1 Authentication and session ids . 5 7.2 Ping . 6 7.3 Send a message . 6 7.4 Query a message . 7 8. Message parameters . 8 8.1 Table of parameters . 8 8.2 Message parameters in detail . 10 9. Additional Commands . 18 9.1 Delete/Stop message. 18 9.2 Query balance . 19 9.3 Coverage query . 19 9.4 MMS Push . 20 9.5 WAP push service indication . 21 9.6 Get message charge query. 22 9.7 Token (voucher) pay . 23 10. Batch messaging . 23 10.1 Start batch ., clickatell routing error. 23 10.2 Sending messages to existing batch . 24 10.3 Quick send to batch . 25 10.4 End batch. 25 11. Message examples . 26 11.1 Simple examples . 26 11.2 Batch SMS examples . 28 12. Appendix A: Error codes . 31 13. Appendix B: Message statuses . 32 14. Terminology. 33 15. Contact details. 35

    Copyright 2000 - 2011 Clickatell. All rights reserved.

    1

    SOAP API Specification v.1.2.1

    2. Change historyApproximately six (6) months of clickatell routing error are reflected.Visit http://www.clickatell.com/downloads/soap/Clickatell_SOAP.pdf to check for updates to this document

    Version1.2.1 1.2 1.1.9

    Date19 December 2011 12 August 2011 28 February 2010

    SectionAppendix A 8 & Appendix Clickatell routing error 12 & 13

    Changes to DocumentationAdded error code 901 Added message concat maximum of 35 Added Error Code 130 and Message Status 014

    3. OverviewThis technical document is intended for developers who wish to use the Clickatell SOAP API for sending messages, and describes the various programming methods and commands used by developers when using this API. SOAP is a protocol for exchanging XML-based messages using HTTP/HTTPS, clickatell routing error. It uses XML as its message format and is transmitted via HTTP/S. SOAP messages are in the form of a packet and submitted to a SOAP portal for our gateway to pass on To use this Clickatell routing error, you need to register at (http://www.clickatell.com/register/?product=1), clickatell routing error. When you sign up for a SOAP account you will be given a username, password and api_id: keep these at hand. Once you have registered and been activated you will receive 10 free credits with which to test our service. Messages sent with these credits contain a canned (pre-populated) message. You can test the API using these credits, and purchase credits to start sending your own, customised messages. It is recommended that you have an understanding of profiles before reading this document. Information is available at http://www.clickatell.com/help-support/developer-apis/routing-profile-guide. Please note that we request delivery acknowledgement for every message we send although delivery acknowledgement status will only be delivered to you if requested. There are a number of different ways of gaining access to the gateway: SMTP - enabling a server or client generated email to be delivered as an SMS. HTTP / HTTPS - submitting either a POST or GET to the API server. FTP uploading a text file to our FTP Server. XML posting to our gateway using XML over HTTP/S. COM Object clickatell routing error Windows based development. SOAP submit SOAP packets over HTTP/S. SMPP customers requiring a high throughput binary socket connection.

    Copyright 2000 - 2011 Clickatell. All rights reserved.

    2

    SOAP API Specification v.1.2.1In order to reduce testing costs, Clickatell offers a test number range. Messages sent to any number on this prefix will only be charged 1/3 of a credit. Use the number 279991xxxxx (for South Africa) or 1999xxxxxxx (for the U.S.) where xxxxx represents any numeric string, clickatell routing error. Message statuses will be returned. We will cover the SOAP method in this document. Additional documentation is available for the other methods, clickatell routing error. Sample code is provided on the site.

    4. IntroductionThe SOAP API uses Web Services Description Language, which is an XML-based language that provides a model for describing Web services. WSDL is often used in combination with SOAP and XML Schema to provide web services over the Internet. A client program connecting to a web service can read the WSDL to determine what functions are available on the server. Any special data types used are embedded in the WSDL file in the form of XML Schema. The client can then use Clickatell routing error to actually call one of the functions listed in the WSDL. Note: It is important that the ENTIRE document is read before contacting support. Parameters are case-sensitive. You must use character references for Greek and other extended characters.

    5. Getting startedIn order to use the Clickatell gateway you need a Clickatell account and at least one registered connection (API sub-product instance) between your application and our gateway. Each connection method is known as a sub-product (of our API product). Heres how: Step 1 - register for a Clickatell account Clickatell routing error you do not already have a Clickatell Central account, you need to register for one as per below. If you have a Clickatell Central account, proceed to Step 2 for instructions on how to add an API connection to your account. Go to http://www.clickatell.com/products/sms_gateway.php, and choose the appropriate API subproduct (connection method) you wish to use. Click on the registration hyperlink. Select the Account type you would like to use (Local or International) Enter your personal information to complete the registration form Accept Terms & Conditions Click Continue - an email containing an activation link will be sent to the email address you have provided(Local account type registrations will be shown a confirmation pop-up where you clickatell routing error to confirm that you wish to register for a local account type.)

    If y

    API Error codes

    001

    Authentication failed

    Authentication details are incorrect.

    007

    IP lockdown violation

    You have locked down the API instance to a specific IP address but attempted to send from an IP address different to the one you have set.

    You can edit the setting to include your new server’s IP address or remove the IP lockdown completely within Developers’ Central’s API settings.

    100

    Data malformed

    The JSON/XML data submitted is clickatell routing error that the syntax of your request has been formulated clickatell routing error and resubmit.

    101

    Invalid or missing parameters

    One or more parameters are missing or invalid.

    102

    Invalid user data header

    The format of the user data header is incorrect.

    Ensure valid UDH data is being passed to the API.

    105

    Invalid destination address

    The destination address you are attempting to send to is invalid.

    Check that the number of the handset that you are attempting to send a message to clickatell routing error valid. The number should be in an international format, without a ‘ 00’ prefix or leading ‘+’ symbol OR begin with a ‘0’ if the default country prefix is enabled on your API.

    106

    Invalid source address

    The specified sender address is incorrect.

    The address that the message is sent ‘from’ has been specified incorrectly. If you are using a Sender ID as your source address, ensure that it has been registered within your online Developers’ Central account.

    108

    Invalid or missing API ID

    The API ID is either incorrect or has not been included in the API call.

    Include the correct API product ID in your query. You can check the ID that is associated with your API by logging into your Developers’ Central account.

    109

    Missing message ID

    This may refer to either a client message ID or API message ID – for example, when using the ‘stop message’ command.

    113

    Maximum message parts exceeded

    The text component of the message is greater than the permitted 160 characters (70 Unicode characters). View the concatenation page for help in resolving this issue.

    Set concat equal to 1,2,3-N to overcome this by splitting the content across multiple messages. View concatenation information.

    114

    Cannot route message

    This implies that the gateway is not currently routing messages to this network prefix. Please email [email protected] with the mobile number in question.

    116

    Invalid unicode data

    The format of the Unicode data entered is incorrect.

    Ensure that the Unicode format is correct and resubmit your query.

    120

    clientMessageId contains space(s)

    Your specified client message ID contains a space. Space characters in client message IDs are not currently supported.

    The delivery time must be entered in minutes up to a clickatell routing error of 7 days.

    121

    Destination mobile number blocked

    This number is not allowed to receive messages from us and has been put on our blocked list.

    122

    Destination mobile opted out

    The user has opted out and is no longer subscribed to your service.

    123

    Invalid Sender ID

    The sender ID is not valid or has not been approved.

    A sender ID needs to be registered and approved before it can be successfully used in message sending.

    128

    Number delisted

    This number has been delisted and cannot receive our messages.

    130

    Maximum MT limit exceeded until <UNIX TIMESTAMP>

    This error is returned when an account has exceeded the maximum number of MT messages that can be sent daily or monthly. You can send messages again on the date indicated by the UNIX TIMESTAMP.

    160

    HTTP method is not supported on this resource

    An unsupported HTTP method has been performed on the resource. Example: HTTP POST on the Coverage resource.

    The response MUST include a Content-Type header that contains a valid method for the requested resource.

    161

    Resource does not exist

    You are attempting to access a REST API resource that does not exist.

    165

    Invalid or no version header specified

    The expected header that specifies version was either not found or is invalid.

    Before continuing, make sure that the correct version is included in the submitted header, clickatell routing error. The header to use is 

    166

    Invalid accept header specified

    The optional header that specifies acceptable content does not contain an allowed value.

    167

    Invalid or no content-type specified

    The expected header that specifies content-type content was either not found or did not contain an allowed value.

    Before continuing, make sure that an allowed value is included in the submitted content-type header. The allowable content-type header values are ‘application/json’ or application/xml’.

    250

    Destination address is on DNC list – Do not contact receiver

    DNC lookup for the destination address result shows that the receiver should not be contacted.

    Use the “bypass_dnc_check” (this name varies for APIs) request parameter to bypass the DNC check.

    301

    No credit left

    Insufficient credits.

    Log in to your Developers’ Central account and purchase additional credits.

    901

    Internal error – please retry

    An error occurred on our platforms.

    Please retry submitting the message. This should be exceptionally rare.

    Support forum

    Clickatell is not routing the messages sent through Diafaan.

    when I click send, the log says that the gateway sent the message.
    just few seconds after, I get a failed status and the following error message:
    Status: 301: Error: Status error received after the message was accepted by the Clickatell gateway.
    Error: 9: The routing gateway or network has had an error routing the message.
    Message: test3333333333
    =======================================================
    I contacted clickatell about their "error routing" and this is their reply:

    Hi Richard,

    Thank you for contacting Clickatell

    The issue is that you have not specified to use the 2-way number when sending the messages. You will need to specify the following additional parameters in your code:

    mo=1 (this activates 2-way messaging)
    from=XXXX (Specifying your 2-way number as the source address)

    For example:
    https://api.clickatell.com/http/sendmsg?user=XXX&password=XXX&api_id=XXX&mo=1&from=XXX&to=Destinationaddress&text=message+content ;

    If you need any further assistance, please feel free to reply to this email.

    clickatell routing error

    You can watch a thematic video

    2.3.2.3 Packet Tracer - Troubleshooting Static Routes

    0 Comments

    Leave a Comment