This article assumes that you have direct access to the Sleipner host. If not, contact Support.

In certain areas of the world (especially where there is a risk for clashing callsigns), the ATC or the airline issues a callsign conversion table that translates the IATA Flight Number into a unique callsign instead of just taking the same numeric values from the IATA Flight Number to the Callsign numeric part.

Samples

• No conversion: SK1234 = SAS1234
• With conversion: SK1234 = SAS12NM.

For N-OC to be able to upload the correct ATC Callsign and be able to parse inbound data correctly, the Callsign table in N-OC needs to be populated. This can either be done manually or by uploading a Callsign file.

Callsign File Specification

• The header is always IATA,ICAO.
• The period is usually a season.
• The callsign can be very specific (departure/arrival, frequency) as well as very general. If no frequency is provided, the callsign will be applied with frequency 1234567.
  
  

IATA,ICAO

26MAR17,28OCT17

AB123,ABC123

AB124,ABC124

OR

IATA,ICAO

26MAR17,28OCT17

AB123,ABC123,ARN,,1234567

AB124,ABC124,ARN,CPH,1234567

AB125,ABC125,,CPH,1234 7

AB125,ABC125,,, 34

Note: You need to use space for frequencies not in question.

All previous records for the given flight will initially be erased and replaced by the data in the file, so you need to cover all cases in the file every time you import again.