API Function: lu_cdr
API Function Application: Send LU CDR data to your server
API Function Request Type: HTTP Request is sent from Cloud9 to your server.
API Function Status: Requires enablment by Cloud9 before use.
API Function Examples: Click Here to view online examples.


The lu_cdr function enables you to receive location update CDR data to your server. The URL string passed
by our server contains the VLR data of where the subscriber last LU'd.
Our system will pass a URL string like so to your server:

 

http://api.yourdomain.net/lu.asp?request_type=LU_CDR&timestamp=2008-08-14%2012:03:22
&transactionid=10000&cdr_id=123456&carrierid=1&mcc=0&mnc=0
&imsi=234180000000000&msisdn=%2B447700000000&vlr=%2B441283123456&tadig=GBWC9

IMPORTANT: The string we send you will be URL encoded.

 

The URL is made up of the following variables:

 

REQUEST_TYPE

This variable will be set to LU_CDR.

TIMESTAMP

The date and time the HTTP request was created in yyyy-mm-dd HH:mm:ss format. This time stamp is used for the API CDR records.

TRANSACTIONID

This variable will be set to a numerical value by our system. The ID is used to track the HTTP request through the Cloud9 system.

CDR_ID

This variable will contain a unique ID which has been assigned to the CDR.

CARRIERID

This variable will contain the carrier ID that has been assigned to you for use with our API.

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.

IMSI

This variable will contain the IMSI of the subscriber who has made the LU request.

MSISDN

This variable will contain the MSISDN of the subscriber who has made the LU request.

VLR
This variable will contain the VLR of the host network that the subscriber as LU'd onto.

 

When a LU_CDR request is sent to your server your server is required to respond like so:

 

<?xml version="1.0" ?>

<CDR_response>

<cdr_id>123456</cdr_id>

<cdr_status>1</cdr_status>

</<CDR_response>

The XML output is made up like so:

<CDR_RESPONCE>

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

<CDR_ID></CDR_ID>

This variable must contain the CDR ID we passed you within the HTTP post.

<CDR_STATUS></CDR_STATUS>

This variable must contain either 0 or 1 If 0 then this tells our system that the CDR post failed, if 1 then this tells are system the CDR post was successful. By default reply with these field set to 1.

</CDR_RESPONCE>

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

 

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 27/04/2009 @ 17:04:19

Privacy Statement | HTTP/XML System API © 2010 Cloud9 Mobile International Ltd. All Rights Reserved.