This gives our customers access to real-time details on product availability, order and delivery information.

Our mobile customers can use the LinxOnline Interaction Gateway for Mobiles for ordering, activation, fault logging and port/churn.

Benefits

• Automates more transactions, boosting productivity and effectiveness;
• Decreases costs by improving operating efficiencies such as eliminating double keying of information;
• Provides secure, reliable access to critical business applications, with 24-hour, seven-day availability.

Technical documents

We've produced a range of technical documentation to help with the development of our customers' LOLIG interfaces, including:

• LOLIG concepts document (PDF, 752kb);
• LOLIG design guidelines (ZIP, 1268kb);
• LOLIG product rules (DOC, 485kb);
• LOLIG staging guide (DOC, 2412kb);
• LOLIG build guide (ZIP, 809kb).

Documents relating to LinxOnline Interaction Gateway for Mobiles development include:

• LinxOnline Interaction Gateway for Mobiles concepts document (PDF, 359kb);
• LinxOnline Interaction Gateway for Mobiles design guidelines (PDF, 1200kb);
• LinxOnline Interaction Gateway for Mobiles staging environment user guide (ZIP, 285kb);
• LinxOnline Interaction Gateway for Mobiles product catalogue (ZIP, 487kb);
• LinxOnline Interaction Gateway for Mobiles build guide (ZIP, 414kb).

Service status

Check the online service status for LOLIG, including scheduled maintenance activities.

Developers' kit

The LOLIG developers' kit contains a set of code libraries and tools that can help in the development of a LOLIG client. This includes:

• how-to guides (ZIP, 66kb), which outline the most common LOLIG orders and can be used as a basis for developing a client LOLIG interface;
• sample code libraries (ZIP, 1996kb), which cover sending SOAP messages to the LOLIG web services and receiving responses in return. Code libraries are provided for the following programming languages:
  • Perl
  • Java
  • C#

Example XML request and response sequences (ZIP, 53kb) have also been developed, and these can be used as a guide to structuring web service requests and expected responses. Each file name contains the name of the web service it represents.
Telstra accepts no responsibility or liability associated with the use of the provided code libraries - they are for example purposes only.