Sirena Travel

Sirena Travel is one of the largest Russian companies providing services on booking and sale of air tickets, seats for cultural and entertainment events, registration of insurance policies, etc. The company operates the first accredited domestic aviation distribution system (ADS) "Sirena Travel", developed in accordance with the recommendations of IATA (International Air Transport Association), which provides agencies with interfaces for booking and sale of tickets, and to airlines - tools for management and control of seat resources.

Online booking via Sirena Travel

In order to book tickets via Sirena Travel online, you need to connect to Websky booking system (Websky system website) (Sirena Travel air tickets sales module).

Description

The Websky booking system supports ticket sales on the agency's website through the global distribution system Sirena Travel (Sirena 2000).

General features

Search and general

Search by nearest dates - conditionally.
Search by nearest airports - allows you to search for flights not only to the airport of the selected city, but also to the airports of neighboring cities; for example, to include in the search results options for flights arriving at Sharjah airport when searching for flights to Dubai. It works automatically if the option is activated on the GDS side of Sirena Travel. If necessary, you must request the GDS to connect to your ClientID. Attention! The list of airports is set on the GDS side of Sirena Travel.
Search by public + private fares.
Search by private fares.
Search by schedule
Maximum number of passengers of all types in the search request - 9
Number of passengers of one type in the request - 9

Booking

Additional operations which include the use of requisites/settings
- Reading fare rules
- Checking availability
- Price actualization
- Types of refundable fares - Public
Operations/requests of the .NET air server
- Flight booking
- Cancellation of booking
- Booking update (synchronization)
- Import of booking by PNR locator
- Receiving booking history from GDS
- Modification of entered booking content
- Adding content
- Content via WS - TCH

Ticketing

From requisites/settings
- Ticketing on the airline's stock
Operations/requests of the .NET aircraft server
- Ticket issuance for all reservations
- GDS processing
- Voiding
- Ticket refund

Connecting to Sirena Travel

To implement its online point of sale, the agency must either have its own agreement with Sirena Travel or be a sub-agent of the agency that already has such an agreement.

In the application for connection of a new ClientID, you must specify the allowed IP addresses of servers:

188.235.129.232
37.200.71.164
95.213.141.253
37.200.70.250
95.213.141.254
37.200.71.162

Such an agreement allows to conclude an additional agreement with CJSC "Sirena Travel" for the use of the software tool "Operational Gateway of the "WS-Gate" booking system" with the number of sessions required by the agency (a session means either a neutral session (TCH) or a session of the airline) to work with one site (the question of working with several sites, namely with subagencies' sites, is solved separately). The text of the additional agreement, which includes the main part, terms of reference, description of regulations, procedures, links to XML documentation, can be found in the agency section at website or obtained from Sirena Travel. Upon completion of the development, the Agency must send to Sirena Travel a request for testing the operation of the Internet sales point and a letter on putting the sessions specified in the contract into production mode.

Upon conclusion of the contract with Sirena Travel, the client is assigned a test ERSP-code and a Client_id.

The important point is that in order to start working, it is required not only to be tested by Sirena Travel, but also to be accredited as an Internet sales point by TCH (the necessary documents can be found in the agency part on the website). At the same time:

the TCH session is certified;
if the credit card payment is not carried out through TCH, the site is accredited with the right to book and sell;
if credit cards are paid through TCH, the site is accredited with the right to book, sell and pay.

Agency accreditation department phone: (495) 660 19 78.

The following requisites are required to connect to the Sirena:

Sirena2000 client ID;
Sirena2000 server IP address;
Sirena2000 server port;
Sirena2000 ERSP code.

IP and ports used in Websky

environment	ip:port	ip:port
GDS (working system)	193.104.87.251:34321	194.84.25.50:34321
GRT (test system)	193.104.87.251:34322	194.84.25.50:34322
GRU (training system)	193.104.87.251:34323	194.84.25.50:34323

Attention! When switching from test mode to production mode, you need to change ports.

Features of working with Sirena Travel

When searching, Sirena returns only published fares.
This supplier does not have the option to choose a complex route. The maximum number of segments according to the documentation is two.
It is possible to enter visa data only from Sirena's terminal. This is due to the fact that the concept of secure flight is not yet implemented in GDS and information about the need to make the notes PNR is displayed only as a message on the reference about the availability of seats.
It is possible that airline changes the value of the tax after booking. In this case Websky will update the price before ticketing.
For the following airlines, taxes РУ and SA are not considered (airlines do not require taxes in the price):
- Tatarstan Airlines, tax SA: 500 rub.
- Rusline airline, tax РУ: 300 rub.
- Siberia Airlines, taxa SU 1000 rub.
- Transaero Airlines, taxa SA 210 rub.
For the "Aeroflot" (SU) airline, the PS tax is not considered.
There is a possible situation when, using the standard pricing in Sirena, not the cheapest fares of the airline in this direction are returned, but the fares that are the route fares, which therefore gives them a higher priority. Route fares mean the fares set for the direction where there are intermediate flight points. When booking such flights, the cheaper fare is returned and the order price is reduced. This is the standard behavior of the booking system, which is not affected by whether the process is carried out directly in terminal mode or through web services.
There may be a situation when Sirena sends response for a number of airlines that there is no flight (route and baggage information). For such cases, there is a check request in Websky system. Before booking, the system sends a reference inquiry to Sirena and receives information whether flights are available from this airline. If available, it requests the flights and displays information about the route and baggage. If not available, there will be no such information in the created booking.
Information on baggage allowance through Sirena's web services is guaranteed to be available by default only after booking. In order for data about your baggage to come at the stage of search and flight update, you need to request the GDS for a particular client_id to enable the option of displaying your baggage in the parameter baggage for requests for price and price_flight, respectively.
The system may give different number of options in response to the request. In any case, it will give the number of options specified in the min_results. But max_results may not be reached if the system's internal limit is triggered. If a constraint is triggered and not all options are given, the answer will indicate "cut".
There is a possible situation when the flights can be viewed in the terminal, but they are not displayed on the site as they are started as charter fares. As a rule, the price of such fares is zero, but not always. There may be a category of passenger - ZRA. It is impossible to get such flights online.
If there is a need to combine subclasses in the flight, it is necessary in the section: "Air tickets" → "GDS connection requisites" - mark the field "Combine subclasses on segments on the route of carriage".

Ticketing in GDS Sirena Travel

Tickets to Sirena Travel are issued after payment acceptance. For each form of payment, the travel agency can set its time for payment by contacting support at [email protected] or by calling +7 (499)724-39-66, add. 155. The default time for all forms of payment is 15 minutes.

In general, 3 parameters affect the possibility of the ticketing:

time limit on the seats;
fare validity period;
setting up the site for this payment form.

For the logic implemented in Websky, the ability of ticketing is influenced by time limit on the seats and period of fare validity. Sirena chooses the lowest of the two values.

The time limit for places can be changed by the airline - in this case the message from the airline comes to queue 10 in Sirena, which should be controlled by the operator.

Attention! If the fare validity period has expired, it is impossible to apply it again within this order. This may be done only by the operator from the Sirena control panel.

Attention! There may be situations when some requests (for example, ticketing, ticketing confirmation) may not be fulfilled if the number of virtual consoles is insufficient, and no response will be received from Sirena. To solve this problem, you need to increase the number of virtual desks.

On the Sirena's side, there are settings - the minimum time to the time limit of PNR and the minimum time allowed for payment (for example, 5 and 5 minutes). During payment, the time for payment is calculated on the basis of these settings, specifically, from the remaining time to the time limit (for example, 7 minutes) is calculated the minimum time to the time limit of payment (5 minutes) and compared to the minimum time allowed for payment, in this case it is 7-5 = 2 < 5. And in case the time is less, the payment can no longer be started. To change this setting, you need to contact the Sirena support team.

New booking statuses in Sirena Travel

unconfirmed_sale - means that the payment has not been confirmed (there were some problems with issuing the ticket). Usually the order is in this status for a very short time. If the order hangs in this status, then most likely there is a malfunction. You should contact the technical support service.
mso - the ticket is not sold, but the receipt of the MSO is printed;
mso - the receipt has been issued.

Sirena Sessions

A session is the work of one remote control of an Internet sales point.

The procedure for connecting additional remotes:

Agency orders additional remotes in Sirena and prescribes them in the contract.
Having received the numbers of the consoles, the agency applies to the TCH with a request to accredit them (samples of applications can be found at the TCH website in the section regulation of the rights of sale of agencies in the CERT.
After the accreditation of the additional remote control, the agency applies to Sirena with a request to open a sale at this remote control, attaching to it the TCH answer about accreditation.

If you look at this process from a technological point of view, adding an Internet sales point (ISP) console means adding a new technological address in the office configuration.

If there are no questions from TCH and Sirena, the process of adding the remote and its accreditation takes 2-3 working days.

According to the information from Sirena, for the average volume of sales, the number of remotes does not exceed 5.

The maximum number of additional consoles (sessions), known at the moment - 10.

Setting up agency charges

Sirena has the mechanism for carrying out agency charges that works in any session. However, its use is only mandatory for TCH e-commerce. To pay via eGo in a BSP session, you can either use the Sirena's charge management mechanism or impose the charge yourself when transferring to eGo for payment. When charging via the Sirena's XML gateway, you can understand whether the charge is applied to this payment option or not (you must comply with the same conditions (BSP, ERSP, form-of-payment...) under which the payment will be made).

eGo — the payment gateway of the processing system.

TCH e-commerce — one of the payment options available through eGo.

Timelimits for Sirena Travel in Websky

Timelimit can be assigned in two ways:

Automatic timelimit (using data from the airline's Time Limit Rules);
With the use of Timelimit data (category 5), i.e. by evaluation.

Immediately after booking, the timelimit is automatically set in accordance with the data of the "Rules of Time Limit Appointment" of the airline. If there is an attribute of time limit assignment for an airline in the system according to the evaluation (according to Fare Rules - Category 5), then, if the ticket is not issued immediately, in order to complete the PNR (request E/I), it is necessary to reinstall the time limit in accordance with the data of Fare Rules. Otherwise, the system gives a response: "INSTALL THE TIMELIMIT ON EVALUATION (TL APPLICATION)".

Attention! The time limit value for orders in Sirena is influenced by Websky settings. The minimum value is taken as a reference.

The Websky timelimit for Sirena is displayed on 2 pages:

Booking confirmation page - here you can see airline's time limit, which comes to Websky when searching with settings taken into account.
On the page with information about the ready order - here you can see the final timelimit which comes from the siren according to Websky settings.

Attention! The final timelimit for an order in Sirena is available only after booking.

Synchronization of orders

You can use the order synchronization module for Sirena Travel supplier. Learn more: Order Synchronization.

Type of itinerary receipt recommended by TCH for Internet sales outlets

The itinerary receipt (Sirena Travel) with Latin elements can be found here: File:Itteng.pdf

The itinerary receipt (Sirena Travel) with Cyrillic elements can be found here: File:Ittrus.pdf

Stocks

This section presents an excerpt from the document: "TECHNOLOGY OF ORDER, DISPLAYING, MARKETING AND CONTROL OF USE OF SPD BLANKS AND ELECTRONIC NAV-TCH Tickets".

1. The procedure for providing the agency and consideration in the TCH application for SPD forms and other forms, as well as quotas for electronic tickets NAV-TCH.

1.1. The Agency under the Standard TCH Agreement with the agency independently determines the need for SPD forms and other forms (hereinafter - forms), as well as quotas for electronic tickets for the upcoming period and submits to the TCH "Application for SPD forms, other forms and quotas for electronic tickets NAV-TCH" (hereinafter - Application), issued in accordance with Annex 1.

1.2 The application is provided by the agency in TCH in advance, taking into account the terms of consideration of the application and the time required to transfer and crediting to the current account of TCH amounts specified in the Notification, in accordance with paragraphs 3.4 and 3.8.1 of this technology.

1.3 The application may be sent to TCH for preliminary consideration by fax, AFTN telegraph channel, e-mail, INFOSED, mail or by hand. In this case, by the time of receipt of forms by a representative of the agency, the original of this application should be provided to the TCH.

1.4. The application is examined in the TCH within 4 working days from the date of its receipt.

1.5. The number of issued forms E61, H61, D61, Z61, 35, 30, M61 and provided quotas of electronic tickets is determined by TCH based on the Application and the terms of the TCH Standard Contract with the agency.

1.6. The number of issued forms of various charges receipts of form K95, forms C98 and forms of labels of the package / party is determined by the TCH, based on the Application. TCH has the right to reduce the number of issued blanks of these forms based on existing stocks.

1.7. The number of issued forms A61, S11, T12, forms of freight bills is determined by the TCH, based on the Application and individual contracts or agreements.

1.8. After consideration of the Application, TCH sends a Notification of the agency about the consideration of the Application (hereinafter - Notification). Notification is sent to the agency by e-mail. 1.8.1 In the case of a positive decision to issue forms, the Notification specifies forms and number of forms, address, terms and conditions of receipt of forms, amounts payable, bank requisites, other conditions of receipt of forms, as well as provided quotas for electronic tickets. 1.8.2 In case of reduction of number of forms issued and quotas of electronic tickets provided and in case of refusal to issue forms and provide quotas of electronic tickets the reason for this or that decision is specified in the Notice. Reasons for refusal in issuing forms and providing quotas of electronic tickets or reduction of the number of issued forms and quotas of electronic tickets can be: failure of the agency to comply with the conditions of the Standard Contract with the TCH, availability of sufficient stock of forms and quotas of electronic tickets at the agency, etc.

1.9. Upon receipt of a Notification with a refusal to issue forms and provide quotas for electronic tickets, the agency eliminates the reasons indicated in the Notification and notifies the TCH about it, after which the Application is re-examined in the TCH in the prescribed manner. 1.10. When providing the agency with e-ticket quotas, TCH places in the CEC information about the quotas of e-ticket provided to the agency. 1.11. If within 10 days after sending the Notification to the agency representative of the agency has not arrived at the TCH to receive forms, the Application is considered to be canceled in the part of the forms. If the agency needs forms for the upcoming period, the agency submits a new application to the TCH.

Receiving flights with transfers at different airports

GDS Sirena Travel allows you to receive flights with transfers at different airports without using a complex route (example: Ekaterinburg - Domodedovo, Moscow; Vnukovo, Moscow - Fergana). The functionality is connected by the Websky system administrator. To enable it, leave a request in the helpdesk.nemo.travel project tracker.

Attention! To connect the new functionality it is necessary to sign an additional agreement between the agent and GDS Sirena Travel GDS.

Sirena Travel's payment gateways

"E-commerce" payment gateway

"E-commerce for Business" solution is a complex of solutions for those who already accept bank cards and want to achieve maximum automation of the payment acceptance process, for whom it is important to get a stably working solution using all possibilities of Internet acquiring.

The specificity of the range of services provided by the company to Internet stores of enterprises offering traditional "travel" content to network users is primarily related to unique technologies based on deep integration with air ticket booking systems - GDS (Sirena Travel, Galileo, Sabre, Amadeus) and partnership with the Transport Clearing House (TCH).

High reliability and security of the system is confirmed by PCI DSS certificate as well as VISA and MasterCard payment systems. In addition to processing bank cards (VISA, MasterCard, JCB), the company performs the routing of payments made with electronic money (Yandex money, Web Money), various payment systems (Rapida, Elexnet, Qiwi) and payments made through the largest payment acceptance networks (Euroset, Svyaznoy).

MPS (EgoPay)

Sirena Travel payment solution (2nd version), allows you to pay not only for TCH, but also BSP tickets. And it supports direct processing in BSP.

The advantages of the second version are the ability to pay for tickets booked in the GDS Galileo, Sabre, Amadeus, as well as hotels and rail transportation.

It is possible to pay with negative charges.

Attention! The discounted amount will not be deducted from the client's account, but the difference must be compensated by the agency when making payments with airline.

Attention! When ordering shop_id on the MPS side, please note that the MPS sets rebook and reprice PNR as the default setting for shop_id. If this setting is enabled for shop_id, then the situation may arise in case if MPS ticketing was carried out, if the order is in attempted status, and the booking in GDS Sirena Travel is live, the MPS adds a time limit of 15 minutes to the current time. It means that the time limit transmitted to Websky will not coincide with the time limit on the MPS side, which may lead to cancellation of the order on the Websky side, and the issuance of the order on the MPS side. We recommend to disable this setting on the MPS side for shop_id.

Attention! When switching the airline from the PC payment form (by default) to Invoice PC, you may encounter problems with the ticketing if the payment was made before the transition. To open the payment form Invoice PC, agent must timely send a request to the TCH.

Payment settings via Sirena Travel payment gateway (2nd version)

Settings for this payment method on the Websky side can be found in Finances → Payment methods → Gateway control → Sirena 2.

Production mode - is responsible for conversion of this payment method into production mode.
Use fiscal payment - when you enable the settings, the payment system transmits the necessary information to form a fiscal check. "" Attention! Make sure that your MPS shop_id has a fiscal payment enabled.
Fiscalization parameters - this option regulates the list of parameters transmitted in the check. If no position is selected, all the positions will be transmitted by default, specifically: air ticket, Aeroexpress, insurance, service package, agency services, service charge and charge for payment.
'Taxes subject to fiscalization - it is necessary to specify tax codes (and VAT rate), which should be transferred when paying as a charge. For example: ZZ-10;XX-18.
Use source from host - when you enable this setting, the tax data is provided by supplier Sirena Travel. Sirena Travel tax data source can only be used for Sirena tickets, Sirena air express and additional airline services received from Sirena Travel. For other suppliers, tax data is provided by either the Websky or MPS system. First of all, we set up the source of Sirena Travel's tax data at MPS and then at Websky.
Send source = ips for selected GDS is the source of tax data for the MPS. The setting allows you to select GDS, for which the VAT rate will be taken from the settings on the MPS side. Services to which this setting applies: airline tickets and additional airline services, i.e. what comes from GDS. First of all, we set up the source of ips tax data in the MPS, and then in Websky.
Login - provided by Sirena Travel employees.
Password - provided by Sirena Travel employees.
BSP Store ID - provided by Sirena Travel employees.
TCH Store ID - provided by Sirena Travel employees.
Prefix to payment code - is consistent with the payment gateway and is used to generate the payment code. Example value: 123
Time until automatic payment cancellation in minutes (recommended 10) - regulates the time limit for payment session.
Override markup for GDS processing (empty - no markup) - markup for payment through GDS processing.
Preferred currency - currency of payment.
Payment Method - payment options available in the payment system.
Text for offline payment methods - message displayed to buyer if offline payment method is chosen (Euroset, QIWI, Rapida).
Payment frame height - specify the value determining the frame height in pixels.
Display frame with payment page on order information page - if enabled, the frame with payment gateway will be displayed on booking form 2.0.
Brief information about the receipt for displaying to the user - here you can add a brief description of the payment method to display it in the Payment Gateway block when choosing a payment method.
Template of receipt for printing - here you can specify the type of receipt for printing.
Use GDS processing - this option is responsible for making payment via GDS processing. (enabled by default)
Transmit source (host) of order - includes transmission of information about GDS to MPS. It is not recommended to enable this option if the GDS, for which this payment method is used, is different from Sirena Travel. If the parameter is turned off, the MPS can't issue an order, the statement will be started by Nemo.
Clearing value for airline tickets - this setting allows you to select the type of settlement system. Available values:
- On the basis of the setting in the requisite
- tch
- bsp
- card
- Empty value
Order execution is performed on the gateway side - prohibits issuing air tickets and additional services on the Websky side, if successful payment is made and services are executed on the payment system side.
Make out check based on Nemo Connect data - When you enable this setting, all data required for making out a fiscal check will be transferred from the Nemo system. This setting is necessary when using the MPS Gateway, the flight is not processed by the Sirens GDS. Attention! To enable this option, the agent must request the MPS to activate shop_on_confirm.

Transactions in the Sirena payment gateway

Interaction with the payment gateway occurs in 3 stages:

creating a transaction;
request for transaction status;
payment confirmation or refund.

BSP and TCH payment options

In this payment gateway, BSP and TCH payment options are possible. The technical difference is that in the TCH payment option, the ticket is automatically issued in the Sirena and Websky does not initiate ticketing, but only receives information about issued tickets. This happens when there is an attempt on Websky side is made to issue a ticket.

Creating a transaction

When a transaction is created, the booking component is determined and a corresponding order description is made. Order description is essential only for air transportation. Also, if the component of the booking is air transportation, it is determined whether the TCH-session of payment (via TCH e-commerce) for this flight is possible and the relevant requisites are used. If a TCH payment is possible but the TCH store ID is not specified, the BSP store ID is used. If there are no key details (BSP Shop Identifier, Login, Password) the request will not be sent and the corresponding error will appear.

Request for transaction status

This request is repeated according to the schedule once in 5 minutes from the moment of transaction creation in Sirena, as well as on the fact of redirecting the user of Sirena to Websky. When creating a transaction, the transaction life time is specified. Accordingly, after this time is expired or upon payment or payment cancellation, the transaction status is recorded in Websky and requests are suspended.

Payment confirmation

A confirmation request is sent by Websky automatically. For air travel - after ticket issuing in Websky. For all other components - either immediately after successful request for transaction status (for direct payment) or after booking (for prepayment). For air travel, in case of an error when sending the request or receiving insufficient data, the request is put in a queue and repeated once a day. For the other components, the request is queued only after receiving an error on the part of Sirena.

Automatic refund upon cancellation of order

To enable automatic refunds, but "not ticketed" orders, enable the option Automatic refunds after order cancellation (Personal Account and MPS only) in Finances → Payment methods → Outdated version → Payment gateways.
This option activates automatic refund when cancelling orders paid through the MPS or on a personal account.

Only the manager or expert of the main agency has access to cancel the paid order. Only under these users you can make an automatic refund when cancelling an order. Other users send a request to cancel the order.

Errors in interacting with GDS/GRS/API Sirena Travel

Errors in interaction with GDS Sirena Travel

Errors with search

Not dependent on suppliers:

"You are not allowed to perform this operation!	This error occurs because of the settings on the Sirena Travel side, if the details used by the agent are not specified for the environment in which the request is sent, or if some operations are not fixed in Sirena Travel for the requisites used.
"The results of the issue do not include Saratov Airlines 6W flights".	Probably a child category passenger has been entered in search criteria. There is a fare rule in 6W airline - if the fare is applied to a passenger with a code RMG, RVG, RBG or AGA (children), certain seats must be booked, which is not implemented through xml gateway.
Error from supplier.. Please retry in 15 seconds	Occurs due to overload of Sirena's servers. Repeat the search later.
Error from supplier.. Internal error	Malfunction on the GDS side (Sirena).

"SIMULTANEOUS CHANGES TO PNR - USE IR TO IGNORE AND RETRIEVE PNR"	PNR is being changed in the same time when working with booking. In this case you need to start the operation again.
"Invalid search request object".	This error occurs when you access an incorrect search result. Possible reasons: incorrect search link; search result may become obsolete.

Errors in booking

"CANNOT PUT TO WAITLIST and CANNOT GET SPACE"	Error means no seats available in the selected subclass.
"IMPOSSIBLE TO READ FLIGHT"	For flights of this airline, the availability of seats and booking is made online. There is no information about the flight in GDS.
"No contacts specified"	No customer contact indicated.
"WAIT LIST FOR FLIGHT IS FORBIDDEN"	Error means that the requested flight was cancelled at the time of booking, such flights cannot be sifted from the search results because the seats are displayed in stock at the time of request.
"Cannot book and price PNR"	Paper form is installed by default, and this airline only allows sale on electronic forms in TCH session. Install the electronic form by default.
"SEGMENT 2 DOESN'T CONNECT WITH PREVIOUS BY TIME"	Incorrect docking time. This error will occur at the time of booking if the connecting time specified in the GDS by the airline is less than the minimum connecting time allowed at a particular airport. For example, for domestic flights to Domodedovo, the minimum connecting time is 90 minutes, for international flights - 100 minutes.
"WRONG DOCUMENT NUMBER"	The document number does not correspond to the specified type of document. The error occurs if you specify the document type P (which is perceived by GDS as a foreign passport) and the 10-digit document number.
"NP DOCUMENT CANNOT BE ISSUED IN RU"	The specified country of issue of the document is inadmissible for the selected type of document. The mistake usually occurs if you specify the document type A (National passport) for the selected Russian citizenship when making a booking.
«Invalid format of element 'doc'»	Occurs when trying to enter the birth certificate number in an incorrect format. The correct format is: 1 or 2 Latin letters, 2 Cyrillic letters, 6 digits without spaces and other characters. Example: IOL123456.
Error from supplier.. Please retry in 15 seconds	Occurs due to overload on Sirena's servers. Repeat the search later.
It is not possible to book one of the flight segments. Try another flight. Cannot reserve seats on flight HY-603	The airline responded with a refusal to provide seats. Generally, an error occurs if there was a synchronization of data on the availability of seats for a given class and flight between the GDS resource and the host of the airline itself. Enabling the RBFL (lowest price re-bookings) option in the booking requisite settings will help to reduce the number of such errors. If errors still occur, you should contact Sirena's technical support with a request to perform manual data synchronization, specifying specific flight numbers, airline, direction, class and time of departure.
Error from supplier.. Sale is not allowed	Occurs due to asynchronization with the inverter center of the a/k or lack of subclass places.

Ticketing errors

"ETC TCH - TICKET STOCK IS NOT SPECIFIED FOR POINT OF SALE".	The flow of electronic tickets of TCH is not assigned for this point of sale (to decide on the allocation of the flow should contact the TCH).
"ERROR: ONE OF SEGMENTS HAS XX_STAT"	One of the segments has the status of cancelled (XX) - the segment could have been cancelled by the airline.
"PNR and surname do not match"	Last name in PNR does not match the last name in the order.
"ONE OF SEGMENTS HAS XX_STAT"	Seats were removed earlier time limit. Apparently, it was done by airline telegram. The order was in the 10th queue, which the cashier of the agency has to look through.
"Too rapid-expired fare. Repeat at 5 minutes"	In order to avoid this error in the settings "GDS Connection Details", the value of the field Time of booking release must match the settings on the Sirena Travel side.
"ETC TCH: ETC TCH - THE STOCK OF TICKETS IS EXHAUSTED FOR POINT OF SALE 92152314 ETC TCH: -02ULE TO THE HEAD OF AGENCY"	Error occurs when issuing tickets at the TCH stock and means that the stock of the ticketing is currently over. The error will disappear after the stock is replenished. To do this, the agent should contact the TCH directly.

Voiding errors

"PNR is occupied by another user (console МОВЦ35 1). Repeat the request later"	At the time of the request, the order was occupied by the technologist at the МОВЦ35, processing telegrams with ET.
"4 Incorrect symmetric key"	An error about an incorrect key rarely occurs. This is due to the hourly replacement of the symmetrical key and the procedure of its exchange. It is possible that the exchange took place at the moment of another request and the second was encrypted with the old key.
"You are not allowed to do this operation"	The ticket was issued through the Sirena Travel desk. In this case it is impossible to void the ticket using the engine.

Errors in exchange

"Error: EVALUATION AND AUTHORISATION AMOUNTS"	This error occurs because the Payment Order number was not specified when booking. It is necessary to specify the invoice number when making a booking.

Features of working with Sirena in Websky

In Websky, the booking form prevents booking errors related to violation of Sirena restrictions on the number of symbols assigned to a passenger's full name:

Maximum number of symbols for last name and surname in the sum is 54.
Maximum number of symbols for surname, name and patronymic in the sum is 53.

Avia+

"Avia+" is a GDS Sirena Travel functionality that provides access to advanced airline content, including billing options received from GDS Sirena Travel and GDS Travelport under one GDS Sirena Travel account (client_id) without additional requests.

The functionality is connected by the Websky system administrator. To enable it, leave a request in the helpdesk.nemo.travel project tracker.

Attention! To connect the new functionality, it is necessary to sign an additional agreement between the agent and PJSC "TCH".

Functionality Supported by Avia+

Search
Getting Fare Rules for flight and booking
Actualization of the flight
Work with branded families
Flight booking
Booking update
Cancellation of booking
Ticketing of bookings
Voiding
Importing bookings
Getting the PNR history
Data addition to the reservation (via SSR)
Modification of data in the reservation (via SSR)
Check out your reservation
Reading the queues
Removing booking from the queue

Features not supported by Avia+

Selection of price available for booking in case of unavailability of the price received during the search.
Creating a flight booking without passport and contact information of the passenger with their subsequent notification.
Modification of passport and contact information of the passenger in the booking
Search by nearest dates
Working with unbranded fare families
Rent a seat for the issued booking (preparation for return)
Split (separation) of a PNR
Airline ancillary services
Autorefunds
Autoexchanges

Useful Links