Teldas offers a neutral platform for the secure data exchange among Telecommunication Service Providers and for the data storage in the domain of Number Portability (ONP) and Individual Number Allocation (INA).

We offer full flexibility of services with a manual web-based GUI and a a WS API interface. You choose the level of automatisation suitable for the size of your company. No proprietary hard- and software is required. A test environment is available for the testing of the new functionalities or training purpose.

The service is principally focused on Switzerland, but Teldas offers also a porting service for Liechtenstein numbers. The central database contains both Swiss and Liechtenstein portings, but only Swiss Service numbers (INA).

Domains of focus are mostly driven by regulatory topics, but not exclusively. Teldas decisions are not dictated by the Regulator. Teldas defines inter-operator processes and technical specifications within industry working groups.

Teldas counts around hundred users of the platform, ranging from mobile telecommunication providers, fixnet providers, sms service providers, authorities, foreign carriers routing calls to swiss and liechtenstein users.

At the center are the needs of the telecom branch, represented by the operators participating in the different working groups organised by Teldas. The so-called "Headgroup" is the steering committee taking decisions related to the service evolution.

•  

  • We offer porting for geographical and mobile numbers, as well as for so-called INA numbers (0800x, 084x, 0900x, 18xy)
  • You can choose the level of automation of your porting processes by using your preferred mix among full automation (WS API) or manual interventions via our web-based GUI
  • The ONP routing service is also included : You can use our dedicated WS API to retrieve periodically information about where to route calls to swiss and liechtenstein ported numbers

• Obtain a number portability routing number (NPRN) from OFCOM and ensure that your NPRN is registered into the Swisscom Numbering Manual
• Sign the Teldas User Contract ONP (English) / Benutzervertrag ONP (German). Note that an integral part of the User Contract ONP is the SLA (Appendix 5): This is a multilateral SLA valid among operators being part of the ONP process, to ensure that the agreed timing and process is followed by all parties, so that quality of service can be offered to the end customers. SLA penalties are to be charged among operators directly, TELDAS being not involved in the billing process itself. All User contract Appendices can be found under our "Fees" section below.
• Sign the number porting contract with Swisscom which defines the basis for billing of ONP porting fees. The contract is either the standard interconnection contract for voice services (for operators having a physical interconnection with Swisscom) or a specific number porting contract “Leistungsbeschreibung Nummernportierung”.
• If you want to offer Mobile Prepaid Services, you must sign the User Contract SMS and implement the SMS Short Code 499 with our SMS partner. In case you offer Mobile Prepaid or Postpay services, you need also to offer an information service under the SMS Short Code 503.

The process is based on the "one stop shopping" concept, that is the subscriber needs only to contact the new Operator (Recipient) to port his number. However some exceptions can apply for separate contracts (e.g. TV, Carrier Preselection contracts).

•  

  • The Recipient Operator collects from the subscriber a signed PoA (template is defined by Teldas) or for mobile prepaid the subscriber must send a departure SMS to 499
  • The Recipient Operator initiates a work-order in the Porting Application (Inet-Server)
  • The Donor Operator validates the request within the given timeframe (Accept or Reject, with reject reasons defined by Teldas)
  • The order gets synchronized by INet-Server (normally 1 working day before the agreed activation date). At this stage, the order will not be cancelled anymore by the Recipient Operator.
  • The Donor and Recipient Operator modify the routing in their routing system at the agreed activation date/time.
  • The number goes into status ported (handover) normally at latest 2h after the activation date/time, which renders the porting public for all the operators connected to our ported number database. These operators can now adapt the routing to this ported number.

•  

  • All Swiss Service & Directory Numbers (VAS 0900x, freephone 0800x, shared rate 084x, directory services 18xy) are stored in the INet central database along with their tariff
  • With the ONP user contract, you can connect to our central database of ported numbers (called INet-Server) via fully automated processes (WS API) to retrieve call routing information about Swiss and Liechtenstein ported numbers, as well as about Swiss INA numbers.
  • With the INA user contract, you can also retrieve via fully automated processes (WS API) the retail tariff information on INA online numbers, as well as receive periodically for numbers implemented with offline tariffs the .cdr information from the INA Operator (via WS API)

•  

  • Sign the Teldas User Contract ONP (English) / Benutzervertrag ONP (German). All User contract Appendices can be found under our "Fees" section below.
  • Sign the Teldas User Contract INA (English) / Benutzervertrag INA (German) if you need not only to know the network where an INA number is in service, but also the tariff applicable for the calling customer. All User contract Appendices can be found under our "Fees" section below.
  • Sign the ONP Supplementary contract (English) / ONP Zusatzvertrag (German) if you plan to use our porting information for online database applications offered to Third Parties. Note that this contract needs to be signed in addition to the ONP standard contract above.
  • Obtain a CDP-Id from Teldas if you send traffic to INA numbers, so that your traffic is recognized for billing purpose. Note that this Id must be ordered at minimum 30 days before you use it in your call routing.

Routing information for swiss ported numbers and INA numbers:

The Number Portability Routing Number (NPRN) is used in the call signaling as prefix in the Called Party Number to route correctly the traffic to the Recipient network, respectively for INA numbers to the INA-TSP. Note that the NPRN cannot be modified by any transit network, only by the "NPRN owner" himself.

The NPRN information of each ported number and INA number is available through a dedicated WS API.

Routing information for liechtenstein ported numbers:

The Liechstenstein ported numbers are also available in our database, but they have been modified to fit into the INet-required format: a fictive prefix 015 has been added to each number/number range instead of the Liechtenstein country code +423. Example: 015 2366488 stands for +423 236 6488

Billing information for INA numbers:

As a CDP-TSP, you are not only responsible to add the correct routing number (NPRN) of the INA TSP to the dialled INA number but also to add your CDP-ID (charging determination point ID) in front of the dialled INA number.  Teldas will give you a CDP-ID at activation of the service. The cdp-id is used to determine to which operator the INA-TSP must send the wholesale invoice for the incoming INA traffic. The INA-TSP can also block some incoming traffic if originating for example from abroad.

For INA numbers in service with an online tariff, you will be required to use our dedicated WS API to obtain the tariffing information to bill your retail customers.

For offline tariffs, the billing information in the form of CDRs will be transferred to you via a dedicated WS API. A Rated CDR is generated for each call with Offline a tariff or each event per call with Offline B tariff and contains all necessary data to invoice the customer: who has called when, whom (service number), how long and at what costs. The Rated CDR substitutes the calculation of the bill by the CDP-TSP because it contains the calculated costs according to the concerned tariff parameters.

• Joining Fee (CHF 800 + 8.1%VAT)
• Annual Fee (CHF 1’300 + 8.1% VAT for ONP, CHF 1’300 + 8.1% VAT for INA). Note that if you need to sign the ONP supplementary contract, the annual fee is at the higher rate of CHF 8'000 + 8.1% VAT.
• Transaction Fees:
  • For ONP portings, the fee is CHF 0.30 (+ 8.1% VAT) per transaction (Work-Order Inport, Outport and Cancel). As of 1.1.2025: CHF 0.25
  • For INA, the fee is CHF 5 (+ 8.1%+ VAT) per transaction on an INA number and per INA number implemented with so-called offline tariffs.
  • For INA, a transaction fee of CHF 150 (+8.1% VAT) is also applicable for each tariff creation, as well as CHF 100 for urgent number transactions.

The applicable fees are described in the Appendix 2 of the Teldas user contract.

User contract - Appendix 2 (English)
Benutzervertrag - Anhang 2 (German)
ONP Supplementary contract (English)
ONP Zusatzvertrag (German)

Below the available ONP and INA User contracts and their Appendices:

• User contract ONP
• User contract INA
• User contract - Appendix 1 The Users Particulars (to be filled in)
• User contract - Appendix 2 Service Fees
• User contract - Appendix 3 Support
• User contract - Appendix 4 Technical interfaces and Documentation
• User contract - Appendix 5 Multilateral ONP SLA and portability charges
• User contract - Appendix 6 Multilateral INA SLA
• User contract - Appendix 7 Commissionned data processing
• User contract . Appendix 8 Abbreviations and definitions

• SLA penalties in case the defined ONP and INA processes are not followed as per Appendix 5 of the Teldas user contract.
• For each ONP work-order, porting fees are to be paid by the Recipient TSP to the Donor TSPs according to the porting type and the porting time (business hours or outside business hours). The porting fees defined in Swisscom Interconnection Contract are applicable. Note that for “mass portings” transactions, the porting fee must be agreed with the Donor Operator on a bilateral basis.

Price Manual Swisscom