Cloud9 HTTP/XML/SS7 GSM System API - Function 'inbound_routing

HTTP/XML/SS7 System API V2.3

Email page

Print page

Tuesday, September 07, 2010 01:09:14

Balance Functions

DDI Mapping

CDR Functions

IMSI Control Functions

Inbound Call Functions

MSRN Functions

Outbound Call Functions

Pin Functions

Routing Functions

SMS Functions

USSD Functions

Voicemail Functions

API Function: inbound_routing_status
API Function Application: Query the inbound service assigned to a MSISDN
API Function Request Type: HTTP Request is sent from your server to our server.
API Function Status: Available as standard
API Function Examples: Click Here to view online examples.

The 'inbound_routing_status' function enables you to query how a call will be routed to a particular MSISDN when a inbound call
request is received.

http://api.wire9.com/api.cgi?transaction_id=1000&query=%2B447700000000&request_type=inbound_routing_status
&carrier_id=1&password=test&timestamp=2007-03-08%2023:43:43

IMPORTANT: You must URL Encode your HTTP string. URL Encoding replaces unsafe ASCII characters with "%" followed by their hex equivalent. Safe characters are defined in RFC2396. For example a '+' will become '%2B'

The URL is made up of the following variables:

URL	http://api.wire9.com/api.cgi
TRANSACTION_ID	This variable must be set to a numerical value by your system. The ID is used to track the HTTP request through the Wire9 system. The data returned by our system will contain the ID that you assign. The transaction ID can be assigned a value from 0 – 999999.
QUERY	This variable must contain the MSISDN or IMSI of the subscriber of whom to return a MSRN for. If passing a MSISDN you may use the following formats: 07xxx, 447xxx or +447xxx.
REQUEST_TYPE	This variable must be set to inbound_routing_status. This setting tells our system that you wish to carry out a inbound routing status request.
CARRIER_ID	This variable must contain the carrier ID that has been assigned to you for use with our API. Please contact support@cloud9-mobile.co.uk if you do not have your API carrier ID.
PASSWORD	This variable must contain the password that has been assigned to you for use with our API. Please contact support@cloud9-mobile.co.uk if you do not have your API password.
TIMESTAMP	This variable is set by your system. It should contain a valid date and time in yyyy-mm-dd HH:mm:ss format. This time stamp is used for the API CDR records.

Please Note: All of the above variables are required within the HTTP request string.
The INBOUND_ROUTING_STATUS request will fail if the required variables are not passed in the correct format.

When a valid INBOUND_ROUTING_STATUS request is made the Cloud9 system will return a standard XML (version 1 tree)
which your system must then phase through and pull out the required data:

<?xml version="1.0" ?>

<Wire9_data>

<ROUTING_Response>

<ROUTING>GSM - Handset</ROUTING>

<ROUTING_ID>0</ROUTING_ID>

<IMSI>234180000000000</IMSI>

<MSISDN>+447700000000</MSISDN>

<REQUEST_STATUS>1</STATUS>

<TIME_STAMP>2007-03-08 23:43:43</TIME_STAMP>

<TRANSACTION_ID>1000</TRANSACTION_ID>

</ROUTING_Response>

</Wire9_data>

The XML output is made up like so:

IMSI	This variable contains the IMSI of the subscriber.
MSISDN	This variable will contain the MSISDN of the subscriber.
ROUTING	This variable will contain a text description of what service the inbound MSISDN is assigned to.
ROUTING_ID	This variable will contain the ID which has been assigned to the inbound routing service. 0 = GSM Handset 1 = SIP Client* 2 = IAX Client* 3 = IVR* 4 = Follow Me* 5 = Custom Service* 6 = Text to Speach Engine* 7 = Voicemail Box 8 = Conference Bridge* 9 = System Message (* These services are BETA services and are not available as part of the general Cloud9 offering at present.)
REQUEST_STATUS	Options: 0 = Fail 1 = Success
TIME_STAMP	The returned TIMESTAMP that you passed within the HTTP request string.
TRANSACTION_ID	The transaction ID your system assigned to the GET MSRN request.

If our server is unable to process the request or a system error occurs we will send back a formatted XML
error message like so stating what error occurred within the <Error_Message></Error_Message> tag:

<? xml version="1.0" ?>

<Error>

<Error_Message>Error: Unknown user </Error_Message>
</Error>

ERROR_MESSAGE

This variable will contain information to why the request could not be processed by our system.

Top of page Email page Print page

Last Review 16/08/2008 @ 21:08:20