Contactez-nous

partie centrale qui "pousse"

1. Retrieve Routing & Billing Information

This set of questions is targeted at TSPs interested in knowing where to route correctly the traffic to INA numbers in Switzerland. It deals with downloading an initial file with all ported numbers, with the daily incremental files and with the general INA routing and billing principles. The targeted TSPs are the charging determination point operators (CDP-TSPs) and have usually ?read-only? capability on the INet-Server INA service.

/

What are the main reference documents?

  • INA Document for Implementation: This document describes operational processes among operators (INA transactions, tariff models, billing via file transfer). It is more focused at TSPs wanting to take in service INA numbers (INA-TSPs). However, some important chapters also concern access providers (CDP-TSPs), notably the process of rated CDR exchange among operators for calls to offline numbers.
  • INA General Set-Ups: general branch agreement of the telecommunication industry how to handle the INA-business. Rules for tariffs, routing, storing of data, etc.. The document is owned by the Headgroup.

Other useful documents:

  • Functional Specifications INA: focused at technical people to understand the INA application (notably the various rules applying to file transfer and GUI requests).
  • Graphical User Interface (GUI) INA - Inet-Server User Manual WEB Client: This document describes the manual user interface and is mainly useful to download some manual reports or to generate some specific files with INA numbers or tariffs. The daily files with the list of INA numbers are also available from this manual interface, but it is highly recommended for the creation of large files (such as extracts of all INA numbers) to use the SSH File Transfer Interface.
What numbers are concerned by INA?

Following types of numbers are included in the INet-Server INA database:

  • Freephone numbers (0800)
  • Shared cost service numbers (084x)
  • Value added numbers (0900, 0901, 0906)
  • Directory service numbers (18xy)
  • Personal numbers (0878)

The INet-Server contains all numbers that have been allocated by OFCOM to a Service Provider and their history.

How to download the information about all INA numbers and tariffs in Switzerland (initial files)?

There are two different types of information required:

  1. Tariff profiles: available in the .ptp (online and offline-a tariff classes) and .ptb files (offline-b tariff classes). Note that .ptb files are not required as the INA-TSPs have to send XDR Files with the cdr information.

  2. INA numbers and their features (among others, tariff class number): available in the .lig files.

1. Tariff profiles:

There are several ways to obtain a file with all tariff classes:

a. Via File Transfer:  LIST_TP request to obtain a .ptp file containing all online and offline-a numbers. You can also use selection criteria (<TARIFF_PROFILE_TYPE>=001) to obtain a result file with only the online tariffs as for offline-a you can rely on the XDR files received from the INA-TSP.

 

b. Via GUI: Go under the menu Tariff Class and select tariff profile online, then click on the button "summary light", then on the button "download ptp file". You can also select the online tariff profiles with the flag "industry standard" if you want to see only these tariffs.

The GUI presentation Tariff profile summary (Summary light) differentiates between

- tariff profiles for which there is a single transaction in the selected range of transaction dates.

- tariff profiles with multiple transactions in the selected range of transaction dates.

The differentiation consists of a bold font for the display of the respective tariff profile in the case of multiple transactions. The differentiation is disabled if there is no specification of the transaction date in the selection parameters for the summary light.

A "Download" button on the GUI screen "List tariff profile Summary Light" produces a file of the current view with the format .ptp or .ptb (depending on the profile type, see section 4.25 List tariff profile), and the user can download this file to his directory.

Print screen 1: How to extract on the GUI the list of all online tariffs

 

2. INA numbers and their features

There are several ways of obtaining the lig files. A TSP can obtain all the information about INA numbers for an initial data load by using the .lig file (INA_List), which contains all numbers taken into service or out-of-service and modifications done on the numbers (tariff changes).  This file can either be ordered via file transfer (cf. SSH File Transfer Detailed Technical Specifications INA) or via GUI (cf. Graphical User Interface (GUI) INA- Inet-Server User Manual WEB Client).


a. Web GUI custom report: Under the menu "INA Number"/Select INA Number, enter an appropriate selection (no selection criteria for getting everything, except the INA Status = SRVIN), then click on the download button at the bottom of the page.
Beware that the amount of data is limited in the GUI by the system parameter MAX_ROWS_GUI, so you will need to either make several selections on number ranges or to use the "allnumbers'" file described below.

Recommended for one-off downloads.

 

b. Web GUI for periodically created standard reports: In the banner area of the INA home page you will find buttons for downloading various types of files. The available files are only the most recent standard reports for the .ptp / .ptb files and for .lig files (containing only the daily increments). For the .lig file, you can also find a file called "allnumbers...." which is generated once per week and contains all INA numbers at the file date. Note that it also contains INA numbers that are not in service (see INA_Status field definitions)


c. File transfer custom report (SSH access): Submit a uil file with a suitable request (LIST_INA command), then download the result later. You will find the result file under your Login directory. Note that the system parameter MAX_ROWS_FTP restricts the maximum amount of records that can be downloaded in one single report. Therefore, it is recommended to use the already available file "allnumbers..." under your lig subdirectory and generate a file with the selection criteria for the remaining days (selection criteria on the transaction date).

 
d. File transfer for periodically created standard reports: In the lig (or ptp) subdirectory of your SSH login directory you have access to the most recent standard reports.

Recommended for automated operation.

Print screen 2: How to extract on the GUI the list of all INA Numbers in service

How do I get incremental files with INA numbers and tariffs in Switzerland?

Incremental files with INA numbers are generated on the INet-Server every 2 hours and are called .lig files (if a number is taken into service on 08:44, the number will appear in the .lig file of 10:00). For proper routing and billing to INA numbers, it is important to use these files to update the List of INA number on a periodic basis. Note that in the lig files are also contained numbers that are not yet in service (for example status "allocated"): it is thus important to filter out only the numbers that are in status "in service".

Incremental files with the tariff classes are generated on the INet-Server every day (at 16:00) and are called .ptp (online & offline-a) and .ptb (offline b) files.

It is strongly recommended to use automated processes for this task, see the download of files via SSH, as per SSH File Transfer Detailed Technical Specifications INA, chapter 2.1 for general overview of SSH Server and chapter 2.2.1.3.10 & 12, commands INA_LIST and LIST_TP.

Automatically generated .lig files are available in the subdirectory lig and stay in this folder for 7 days (after which they are transferred to the Archive Directory). Note that a .lig file with all INA numbers is also generated once per week, so that at any time you can rebuild the INA number status.

Automatically generated .ptp & .ptb files are available in the subdirectory ptp and stay in this folder for 3 days (after which they are transferred to the Archive Directory).

Automatically generated .lig, .ptp and .ptb files can also be downloaded manually from the GUI Banner (see Graphical User Interface (GUI) INA- Inet-Server User Manual WEB Client).

What if I incur a loss of data in INA files ? Can I generate the delta of INA numbers in Switzerland or should I download a whole initial file again ?

Incremental files can be generated manually using the INA Number screen on the GUI with precise selection criteria on the activation dates / times or using the File Transfer interface with the function INA_LIST.

Can I get the history of INA numbers ? and tariffs ?

Lig, ptp and ptb files always contain the full history of all operations done of the INA number. When you generate a customized file, there is a "history" parameter allowing you to apply also your selection criteria to history data.

Example: Let's assume that INA number X was originally associated with tariff class 12111. In 2006 the number was modified such that it was associated with tariff class 12222. In 2008 the number was modified again and became associated with tariff class 12333, which is now the current association.

You select INA numbers and specify the tariff class 12222 as a selection criterion. If you say "HISTORY=no", then your results will not include INA number X (because today it is no longer associated with 12222). If you say "HISTORY=yes", then you results will include INA number X (because it was associated with 12222 from 2006 to 2007).

How can I determine if a number is in service or not?

You have to look at the <INA_STATUS> field of the .lig file: a number is in service when its status is "016="SRVIN".

001="ALLNO" (not allocated), 002="ALLOC" (allocated by OFCOM), 004="ALLEX" (allocation expired, number not taken into service during 180 days), 008="SRVAN" (in service announced), 016="SRVIN" (in service), 032="SRVTO" (temporary out of service), 064="TERAN" (termination announced), 128= "F_MOD" (modification announcement)

 

Note: <INA_STATUS> = 128 identifies always records for future modifications, whereas all other <INA_STATUS> are history records. If records (1..n) for future modifications exists they are always listed directly after the main and before the history records.

The <INA status> = 001 concerns numbers that have once been taken into service and went back to OFCOM, free for new allocation.

Reference document: Functional Specifications INA.

With which program should I open the .lig files, .ptb, .ptb.... files ?

First, the files should be extracted using Notepad++ and then pasted into Excel, so that the different fields are shown correctly in different columns. Attached a template for the lig file.

Excel template for .lig file (.xls)

What is required to be able to retrieve automatically the available .lig, .ptp, .ptb files ?

The transmission of files to/from TSP-INet is based on a secure protocol (SSH) which requires cryptographic keys installed on both the sending and the receiving computer. Therefore, if you wish to send files directly from your PC, you need: an SSH client program and SSH keys.

These are things for which your local IT organization is responsible.

Also consider that file transfers are controlled by sequence numbers. If you send files from your PC, your sequence may interfere with other transfer sequences of your company.

What are the NPRN and CDP-Ids used for ?

The NPRN stands for Number Portability Routing Number and can be found in the .lig file to identify the network where the INA number is implemented.

The NPRN is allocated by the Regulator (OFCOM / BAKOM) and is always under the format 98xxx. On the INet-Server, the NPRN is used also to identify the User Account.

The NPRN is used in the call signaling information to route correctly the traffic. More details on the technical process can be found in the documents "INA Technical Framework and Principles".

Note that an official NPRN is only necessary for TSPs wanting to participate in the Portability Process as a Recipient (port in numbers) or take INA numbers into service. All other TSPs can request a dummy NPRN from Teldas as User Account Identifier. These dummy NPRN are under the format 99xxx and they cannot be used to port-in some numbers (read-only accounts).

The CDP-Id stands for Charging Determination Point and is used to identify the operator where the INA-TSP has to charge the wholesale traffic fee. It is the address included in the Called Party Number for the INA-TSP to recognise the selected carrier network for invoicing purposes. Practically, this would be one of the Carrier Selection Codes (CSC) allocated by the regulator to every TSP (or Teldas can allocate a dummy in the format 103xy).

There are different types of CDP-Ids, depending on the traffic origin:

 

  • CDPn-ID is the National CDP-Id for the calls generated in Switzerland and including MOCs generated by non-Swiss roamers in Switzerland.
  • CDPi-ID is the International CDP-Id for calls generated outside Switzerland and MOC generated by Swiss roamers outside Switzerland.
  • CDPp-ID is the CDP-ID of mobile operators for the access to the directory service numbers 18xx from pre-paid customers as an alternative to the parameter “calling party category” of the signalling system #7. Always format 102xx for CDPp-IDs (allocated by the Head Group).

 

 

Where can I find the name of the Service Provider of a certain number ?

OFCOM publishes a list of INA numbers with the Number Holder (link: https://www.eofcom.admin.ch/eofcom/public/searchEofcom_e164.do). The Number Holder is not necessarily identical to the Service Provider. The Number Holder / Service Provider must then go to a Telecom Service Provider (INA-TSP) to implement the number. On the INet-Server, only the INA-TSP can be found.

What are the routing principles to INA numbers?

The direct routing principle applies to Value Added Services (VAS) and Directory services numbers allocated by OFCOM to the number owner according to the Individual Number Allocation (INA) rules. Routing from the originating network to the Recipient necessitates the adding of the NPRN in front of the called number.

The NPRN for each INA Number can be found in the INet-Server central database (.lig files).

The originating TSP must add its CDP-ID in front of the dialled INA number, i.e. the CDPn-ID (national) or the CDPi-ID (international) or CDPp-ID (prepay). This information is used for wholesale billing purpose among operators.

What are the general billing principles for INA numbers ?

Every INA number gets its individual tariff profile according charging types:

  • On-line charging, tariff class available on the INet-Server (.ptp files / tariff classes from 10'000 to 19'999);

    On-line Tariff permits the calculation of the call fees during the call or at the end of the call, in relation to the call duration. The On-line tariff model permits tariff changes dependent on day and time but not on call duration with the exception of a start interval.


    The CDP-TSP must be able to calculate the bills according to the tariffs stored on the INet-Server. The transfer of rated CDRs (XDR file) cannot be used.


    Industry Standard tariffs, which are a subset of the On-line tariffs and will be defined by the Head Group: accessible for Pre-paid and payphone, AOC recommended.
  • Off-line charging type A, tariff class available on the INet-Server (.ptp files/ tariff classes from 1 to 9'999);

    Off-line Tariff Type A permits the calculation of the call fees during the call or at the end of the call (as On-line Tariff) in relation to the call duration. The tariff model contains a larger range of tariffs than those used for On-line Tariff and permits tariff changes during the call dependent on the call duration. The CDP-TSP is not obliged to rate this tariff type but can rely on the xdr files sent by the INA-TSP.
  • Off-line charging type B, tariff class not available on the INet-Server (.ptb files/ tariff classes from 20'000 to 29'999), charging based on rated CDRs of the INA-TSP. The exchange of the rated CDRs will be done by file transfer over the INet-Server in a specified file format.

    The call fee is not related solely to time but also depends on call or transaction related events, e.g. the calling party may use post-dialling and press digit "1" to make a donation of CHF10, digit "2" for to make a donation of CHF20, etc. This requires the INA-TSP and/or Content Provider to carry out a post-call processing when the call has been completed.


    The Off-line Type B TC will be available on the INet-Server with applicable event-dependent tariffs. As solely the content provider can identify these events, rated CDRs must be transferred

For online tariffs, the originating TSPs must update their billing systems with the correct price per INA number.

Calls to offline tariff profiles request the exchange of billing data (rated CDR) between the INA-TSPs and the CDP-TSPs. The INA Document for Implementation describes the processes to exchange rated CDR (XDR file transfer) via the TSP INet-Server. If the CDP-TSP decides to rate the calls to INA numbers with offline-a tariffs himself, then it must inform the INA-TSP via its "download flag" that he can change manually to "no" on the INet-Server.

The money flow from the customer to the INA number holder is following:

(click here to see the picture)

The CDP-ID is the basis for the wholesale billing among operators. All CDP-TSPs sending traffic to INA numbers must ensure that their CDP-Id is correctly announced to our Helpdesk to be stored in the TSP Profile and showing in the TSP-Info.

 

The description and the distinction between Online- and Offline tariff profiles are done in the documents "INA Technical Framework and Principles" and "INA General Set-Ups".

Which tariffs apply for End Customers?

Definition of retail prices:

  • The INA -TSP determines the tariff in all cases for all users of every CDP-TSP.
  • The INet-Server tariffs are the published retail tariffs including VAT.
  • The CDP-TSP may grant its customers (service users) a discount on calls to Shared Rate Services and Personal Numbers. This discount concerns only the CDP-TSP tariff share and must be published.
  • Mobile operators and Payphone can charge an "air fee" for calls to value added numbers, which must clearly be announced in their end customer price plans.

 

Definition of terms:

  • Retail billing is the responsibility of the CDP-TSP and is invoiced towards the end-user. The invoiced amount is based on the retail tariffs, which are published on the INet-Server.
  • Billing share is mutually agreed between the CDP-TSP and the INA-TSP as a percentage of the retail tariff. The billing share compensates the CDP-TSP for the billing service and risk. The billing share is also intending to cover the costs of customer complaint handling and fraud management.
  • Wholesale tariff parameters per service number can be multilateral as well as bilateral, the access to the stored bilateral parameters on the INet-Server is restricted to those parties directly concerned.

Reference Document is the INA General Set-Ups.

Description of the different available files (.uil, .aic, .lig, .ptb... )

In the document SSH File Transfer Detailed Technical Specifications INA you find descriptions of the following download files (and more):

  • lig: Information about INA numbers (through INA_LIST)
  • ptp: Tariff data for profiles of the types online and offline-A (LIST_TP)
  • ptb: Tariff data for profiles of the type offline-B (LIST_TP)
  • dlf: Download flags (LIST_DOFL)
  • tlb: Text library data for offline-B event billing
  • oos: Out-of-service information for INA numbers (OSRVO_READ)
  • uil: request for an upload file by a TSP
  • rdy: every uploaded file must be confirmed with an .rdy file.
  • aic: once the rdy for an uploaded file has been received, INet sends an acknowledgment file on processed transactions (Inet places the file in the archive directory)
  • ixx: file that returns an error code in the extension
  • cst: log entries for CDR files (information about existing files of types cdr, cok, cxx, etc.) (READ_CDR_LOG)
  • pws: list of wholesale parameters (LIST_WOPA)
  • tsp & tsn: files containing important TSP parameters (NPRN, CDP-ID, services subscribed, etc)
Is it possible to get the information about changes in INA numbers and tariffs in advance ?

You can see future modifications on a number by looking at the <INA_STATUS> field of the .lig file: before a number is in service (status "016="SRVIN"), it goes through the status 008="SRVAN". The same before a number goes back to the status "02=ALLOC", it goes through the status 064="TERAN" (termination announced).

This occurs always at least 1 business day before the activation date/time. Exception: Urgent transactions can be initiated by the INA-TSP without this delay.

For new tariffs or tariff modifications, the rule is that these must be announced 10 calendar days in advance. When entering new tariffs or updating existing ones, the TSP must supply a Valid-From date. This date must be far enough in the future. This tariff information is then published in ptp/ptb files immediately, so other TSPs know in advance about it.

The exception being "industry standard tariffs", which are only being modified or created twice per year, following a decision of the Headgroup.

Also, you can use the status F_MOD, which announces that there will be a future status for a transaction. As soon as the F_MOD date has arrived, the records will be rewritten. The F_MOD record becomes the current one (with a state other than F_MOD), and the previously current record becomes history.

What is the difference between periodically generated .lig files and customized .lig files ?

TSP-INet creates 2 kinds of lig files:

1) Automatically created (periodic) lig files for everybody.
These files are named 00000_......lig and are located in the lig subdirectory.

You don't need to acknowledge the download of a periodic lig file. Although you see them in a subdirectory of your login directory, they are in fact not your own files, but they are shared among all INA participants. This is why you don't have a write permission.

2) lig files created just for you. They are created when you send an INA_LIST command in a uil file. With the INA_LIST, you specify your individual selection parameters for INA numbers to be included in the resulting lig file.
These files are named 99929.......lig and are placed in your login directory (the same location where you would place your uil).

You should acknowledge the download of a 99929... lig file, because this way you let TSP-INet know that the lig file is no longer needed and can be removed.

How can I download the cdr for calls to numbers with offline tariff ?

TSP-INet does not evaluate the content of XDR files, but only forwards them from one TSP to another. The receiving TSP will have to validate the content and report invalid data.

First of all the TSP Inet server never send file to a provider. The provider has to download the files from the server, followed by a confirmation message. The file will be stay on the server as long no confirmation message has been received on the server (as long as the limit defined by system parameter Auto_File_Removal_After_Months is not reached).


The INA part of the TSP-INet server is responsible to transfer files from the home directory of a INA TSP to an other CDP TSP. Therefore for the TSP the mechanism of downloading and uploading files is the same like the standard file transfer. The difference is that the CDP TSP has to acknowledge the downloaded .cdr file with a .cok or .cno empty file. After one of these files were uploaded the TSP INet-Server will erase the .cdr file and pass through the .cno or .cok file to the INA TSP. The INA TSP has to download this .cno or .cok file and acknowledge these files with an empty .rdy file.

If the CDP TSP detects an error after processing the .cdr file, a .cxx file is sent back to the INA TSP with the error description inside.

  • The INA -TSP must upload Rated CDRs to the INet-Server at least once per calendar day between 00:01 and 11:59, for all completed calls
  • The CDP-TSP must download Rated CDRs from the INet-Server at least once per calendar day between 12:00 and 23:59.
  • Rated CDRs are required for all calls to Non-Online tariffs. Exception for offline-a tariffs: if the CDP-TSP has changed its download flag to "no", no XDR files are to be sent to him. By default, the TSP accounts are set-up with the download flag = yes for all offline tariffs.

The process is described in more details in the INA Document for Implementation and in the SSH File Transfer Detailed Technical Specifications INA.

 

The format of the XDR file follows the standardized TAP2+ format. The description of the content of the XDR file can be found in the  Document "INA Technical Framework and Principles".

 

Download of XDR files is not possible via the GUI. Via the GUI, it is only possible to check what files are available to download: A "Download" button on the GUI screen "READ_CDR List" produces a file of the current view with the format .cst and the user can download this file to his directory. Example: 99997_998_20000809500001.cst.

The .cst answers the question: Which cdr/cok/cxx... files have I received and how big are they?

2. Manage INA Numbers (INA-TSP functions)

This set of questions is focused on TSPs who are taking in service INA numbers in their network. These INA-TSPs can manage their INA numbers on the INet-Server, taking numbers in service/out of service, modifying the number?s characteristics (tariff profile, etc.).

/

What are the main reference documents?
  • INA Document for Implementation: This document describes operational processes among operators (INA transactions, tariff models, billing via file transfer). It is focused at TSPs wanting to take in service INA numbers (INA-TSPs).
  • INA General Set-Ups: general branch agreement of the telecommunication industry how to handle the INA-business. Rules for tariffs, routing, storing of data, etc.. The document is owned by the Headgroup.

Other useful documents:

  • Functional Specifications INA: focused at technical people to understand the INA application (notably the various rules applying to file transfer and GUI requests).
  • Graphical User Interface (GUI) INA - Inet-Server User Manual WEB Client: This document describes the manual user interface and describes the various INA number and INA tariff transactions that can be done.
  • TSP Info on INet: used for INA wholesale billing purpose, contains the NPRN, CDPid, Carrier Filtering options of all operators sending traffic to INA numbers. Operators sending traffic to INA numbers must ensure their TSP information is up to date in INet. Operators have 30 days to update their wholesale billing systems with the new parameters. Possible to subscribe at the Helpdesk to e-mail notifications informing of changes to the CDP-Ids.
What are the different steps for a number to be activated on the INet-Server?

From the 1st of September 2001 a Customer requesting to implement an INA number for its own use has to request an INA number at OFCOM. OFCOM delivers an allocation decision (Zuteilungsverfüg) to the customer (=INA number owner) who is then free to take the number into service at any INA -TSP. The activation must be done within 180 days after the allocation.

The INA number owner selects a TSP (the INA-TSP) to take the INA number into service within the given 180 days. Moreover the INA number owner negotiates with the INA-TSP the tariff profiles for the INA number.

The INA-TSP announces the taking into service of the INA number within its network to all other TSP at least 1 working day before the activation of the number through the INet-Server (alloc reference code from OFCOM is required to take into service a number). Together with the INA number the selected tariff class and the permission for access from abroad is to be announced.

At any time, the INA-TSP can change some of the attributes (e.g the tariff) of its INA number.

The INA Number owner can change its TSP by using the ONP processes. The Recipient operator needs then to send a Port-In request to the INA-TSP where the number is currently in service. This is done via the ONP Service and is not part of the INA Service.

Reference document: INA Document for Implementation.

What is the alloc reference code needed for?

This code [ALLOC_REF_CODE] is assigned to each INA number by OFCOM and is needed if a TSP wants to take into service a number in the INet-Server. OFCOM sends notably all INA numbers and their respective allocation reference code into the INet-Server when a number is being assigned by them to a Number Owner.

Once an INA number is ported to another operator, this code is still needed as the new operator needs it for any transaction done on the number (change of tariff, etc.). The INA Owner must thus ensure that it transmits this code to its new operator.

The ref code has to be unique i.e. no other identical ref code may be in the database. Once the ref code is assigned by OFCOM, it can only be changed (to a new one) by OFCOM by issuing the "ALLOCATION" process again. The INA TSP is also allowed to modify the code via the MODIFICATION process.

Are all INA numbers accessible in Switzerland ?
  • For prepay and payphone, the access to INA numbers must be granted only for industry standard tariffs.
  • The INA-TSP may limit access for marketing or technical reasons e.g. the PRS can be blocked against access from abroad or inbound roamers as invoicing is impossible.
  • The INA-TSP recognizes traffic from abroad through the CDPi Id (national traffic has always a CDPn ID for national or CDPp Id for Prepay).

Reference document INA General Set-ups.

3. High level overview of the GUI, SSH interface and processes for INA

/

Overview of the main INA process flow among involved parties
  • Allocation/De-allocation, process initiator OFCOM (alloc reference code sent to INet-Server by OFCOM)
  • Activation, process initiator  INA-TSP
  • Modification of data related to the INA number, process initiator INA-TSP
  • Change of the operational status of the INA number, process initiator INA-TSP
  • Out of service order, process initiator OFCOM (when for example the number owner has breached some of his obligations)
  • Termination, process initiator INA-TSP
  • Audit as a data query of INA no in operation, process initiator OFCOM

Screenshot

Overview of the main menus of the INA GUI

The INA Web GUI is good for manual requests and manual INA transactions only. There is no way to automate recurrent requests for .lig or .ptp files via this interface.

The top menu bar permits to download the last periodically generated files (.lig, .ptp, .ptb, .dlf, tsp).

The main menus are:

  • INA Numbers: permits to query the features of INA numbers and their history (customized .lig files)
  • Tariff Class:

    •  permits to query tariffs and obtain customized .ptp and .ptb files (various selection criteria possible)
    • tariff handling functions for INA-TSPs : tariff creation & modification, switching class creation & modification

  • Other: download flag files, CDR log (to read the CDRs), Text library, Reporting, Wholesale parameter

 

Screenshot

SSH Interface (Automatic File Transfer)

Reference document is the SSH File Transfer Detailed Technical Specifications INA.

The functionality that is available using the web interface is also available in the form of batch job processing using automatic file transfer. This is the way to proceed in order to be able to automate the process for file download. Logic can be defined via a script in order to exchange files in the appropriate sequence to query data information and retrieve files. Exchanges are possible using ssh, scp and sftp only.

 

There is a subdirectory lig in the user's SSH login directory (/ina<TSP_ID>/lig). In this subdirectory can be found all the periodical lig files.

For the tariff files .ptp and .ptb, these can be found in the SSH login directory (/ina<TSP_ID>/ptp).

Generation of customized files: It is also possible to generate a customized file, via an .upl extension.

The usual logic to retrieve files consists in uploading a request file with the .upl extension. The file is then processed and downloaded to the TSP server. Once download is completed, TSP must upload a .rdy file to confirm successful download. When this has been done the TSP-INet Server archives the file and an .aic file is sent. All processed up- and downloaded files are moved in to the directory ina<TSP_ID>/archive.

Standard file transfer processing (see the SSH INA Document):

The TSP INet-Server will check for uploaded files and .rdy files 24 hours per day with a repeat rate of

REPEAT_RATE (cron job) minutes. This repeat rate is configurable and currently set to 10 minutes.

Files that have been moved to the archive will stay there for some days, after which they are compressed (see document "Archiving Rules Inet").

moves them to another archive medium.

  • File upload : Every uploaded file (.uil file) must be confirmed with an .rdy file. Note that the .uil file contains commands for listing INA Numbers, performing status changes, etc. (see below file downloads).

  • File download: following downloads are possible:

    • list of requested INA-Numbers (INA_LIST): .lig files containing INA numbers
    • list of requested out of service orders (OSRVO_READ)
    • list of CDR log entries (READ_CDR_LOG). This function starts-up the read process for XDR-filenames. The function searches in the XDR's for information of interest to the TSP
    • list of tariff profiles (LIST_TP): .ptp and .ptb files
    • list of download flags (LIST_DOFL)
    • list of wholesale parameters (LIST_WOPA)
    • .aic file with acknowledgements on processed transactions.
    • .ixx file that returns an error code in the extension.
    • for .cdr and .cxx files

 

cdr processing:

The INA part of the TSP-INet server is responsible to transfer files from the home directory of a INA TSP to an other CDP TSP. Therefore for the TSP the mechanism of downloading and uploading files is the same like the standard file transfer. The difference is that the CDP TSP has to acknowledge the downloaded .cdr file with a .cok or .cno empty file. After one of these files were uploaded the TSP INet-Server will erase the .cdr file and pass through the .cno or .cok file to the INA TSP. The INA TSP has to download this .cno or .cok file and acknowledge these files with an empty .rdy file.

If the CDP TSP detects an error after processing the .cdr file, a .cxx file is sent back to the INA TSP with the error description inside.

The format of the XDR file follows the standardized TAP2+ format.