TIMESTAMP

This variable will contain a time stamp of when the inbound call was received by our network. The date and time will be in yyyy-mm-dd HH:mm:ss format.

IMSI

This variable will contain the IMSI of the subscriber who is to receive the inbound call.

TRANSACTIONID

This variable will contain a numerical ID as assigned by our network for the call authentication request.

CARRIERID

The carrier ID that has been assigned to you for use with our API.

MSISDN

This variable will contain the MSISDN of the subscriber who is to receive the inbound call.

MCC

This variable will contain (if the data is available) the MCC country code of where the subscriber is located. For example 234 for the UK.

MNC

This variable will contain (if the data is available) the MNC operator code (The network name that the subscriber is logged onto). For example 18 for the Cloud9 Network.

TADIG

This variable will contain (if the data is available) the TADIG network code (The network identifier of the network that the subscriber is logged onto). For example GBWC9 for the Cloud9 Network.

REQUEST_TYPE

This variable will contain the API HTTP request type. For Inbound Call authorisation this will be AUTH_CALL_INBOUND

CALLORIGIN

The CLI of the calling party. We will pass the CLI as received from the foreign network so for a UK number you may see 01xxx, 441xxx or +441xxx. If the CLI is withheld then this field will be padded out with 11 zero’s.

USER_BALANCE *

The amount of credit available to the user in £ and pence format (or $, cents or €, cents depending on the subscribers currency setings)
* If your system is holding the user balance then this variable can be ignored as it will be set to 0.00

IOT

If the user is in an IOT chargeable country then this variable will be set to 1 else this variable will be set to 0

IOT_CHARGE

If the user is in an IOT chargeable country then this variable will contain the IOT charge per minute that Cloud9 will change for the call. This charge is for IOT ONLY and doesn't include Cloud9's call termination charges. The charge is in UK Sterling in £0.00 format. Please add your markup to this charge when charging your users.

MSRN

The returned MSRN for the subscriber. The MSRN will be in full international format prefixed with a '+' sign (e.g. +447xxx for the UK). If the subscriber is off line this field will contain the value ‘OFFLINE’

DDI_MAP

If the call arived at Cloud9 via a mapped DDI, this varibale will contain the mapped DDI value.

POLO

The amount of POLO you will receive per second for this call. The amount will be in your default currency.

<MTC_response>

The <MTC_response tag> is required so our system can detect your server’s XML reply.

<TRANSACTION_ID ></TRANSACTION_ID>

The transaction_id tag must contain the transaction ID we passed you within the HTTP request. In the above example this would be 1002.

<REQUEST_STATUS ></ REQUEST_STATUS>

The request status tag must contain either a 0 (zero) or 1 (one). 0 = Failure 1 = Success If set to 0 then our system will route the call the VM or a message announcement.

<ROUTE_TO></ROUTE_TO>

This field must be populated with the destination number you wish to route to. If you wish to route to the assigned MSRN then please populate this field with the MSRN that is passed in the request URL string. Please note that all destination numbers must be in international format prefixed with a '+'.

<TIMER></TIMER>*

The amount of duration in MINUTES that the call is allowed to stay open for. This field will only be used if YOU are holding the user balance, otherwise Cloud9 will control the call timer.

</MTC_response>

The </MTC_response> tag is required so our system can detect your server’s XML reply.

ERROR_MESSAGE

This variable needs to contain information to why the request could not be processed.