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).
Teldas defines inter-operator processes and technical specifications within industry working groups. 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.
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 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.
Teldas offers to Swiss and Liechtenstein Telecommunication Service Providers the possibility to manage their Number Portability processes.
Moreover, Service Providers wanting to take INA numbers into service can manage their INA numbers and tariffs through the Teldas central database platform.
Another service which is also opened to foreign telecommunication providers or users such as SMS Service Providers and Authorities is the access to our central database to find out where a specific number is in service. This allows for correct routing of communications to swiss ported numbers and INA numbers. For INA, an additional service is the provision of retail billing information.
Our services are exclusively addressed to providers of telecommunication services or public authorities needing access to number routing information and not to end-customers (owners of the telephone numbers or INA numbers).
No proprietary hard- and software is required for users. A test environment is available for the first implementation for new Users, for the testing of new functionalities and for training purpose.
Do you have customers with E.164 Numbers or Service Numbers and you would like to port in & out numbers with other Swiss operators, respectively with other Liechtenstein operators ?
- 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
- 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 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.
- This service is available for Swiss INA numbers (VAS 0900x, freephone 0800x, shared rate 084x, directory services 18xy).
- You can manage the administrative steps of a taking an INA number into service, out-of-service and modifying tariffs on your INA numbers.
- You can create new INA tariffs in case the ones already available don’t suit your service needs
- You can transmit cdr information to the other operators (CDP-TSPs) via a secure protocol (SSH) in case you are using offline tariff profiles
- You can choose the level of automation of your INA process by using your preferred mix among full automation (WS API) or manual interventions via our web-based GUI. Note that some transactions like tariff creations are only available on the manual interface.
- The INA routing service is also included : You can use our dedicated WS API to retrieve periodically information about where to route calls to INA numbers and at what price
- Sign the Teldas User Contract INA (English) / Benutzervertrag INA (German) in addition to the Teldas ONP User contract. Note that integral part of the User Contract INA is the SLA (Appendix 5): This is a multilateral SLA valid among operators being part of the INA 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.
- Obtain a number portability routing number (NPRN) from OFCOM
- Sign the INA contract with Swisscom to delegate the wholesale invoicing of the third party billing of INA call charges (Leistungsbeschreibung Mehrwertdienste) if you don’t want to invoice each operator (CDP-TSP) individually based on bilateral contracts with each operator.
Every INA number gets an individual tariff profile. We distinguish between three types of tariffs:
- online tariff profiles: these need to be supported by all CDP-TSPs in their billing system (no XDR file exchange). Exception: for prepaid calls, only the subset “industry standard” must be supported
- offline-a tariff profiles: these imply that the INA-TSP sends XDR files (call charge records) to the CDP-TSP. Note that the CDP-TSP has the possibility to make the retail billing itself
- offline-b tariff profiles: event-based charges which necessitate XDR file exchange as the CDP-TSP has no way to calculate the price of the call.
You can create your own tariffs (via our manual Web based GUI) or use existing tariffs. For “industry standard” tariffs accessible to prepaid calls, the Headgroup will define them.
INA Number management
OFCOM allocates INA numbers directly to the End-User (Service Provider), who is then free to choose any Telecom Service Provider to take the number into service (within the 180 days until the allocation expires).
On INet, this process is reflected by a first allocation transaction initiated by OFCOM, then any INA-TSP can activate the number (using the alloc_reference_code stored in INet during the alloc step). While the number is active, it is possible for the INA-TSP to modify the tariff & access from abroad information. When the subscriber renounces to the INA number, this is reflected by a termination, followed by a deallocation transaction.
All these steps can be done using the automated WS interface or via our manual web-based GUI.
INA porting: Refer to the number porting process in general, which is the same for INA numbers as for mobile and fix numbers.
- 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 SSH)
- Sign the Teldas User Contract ONP (English) / Benutzervertrag ONP (German)
- 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.
- 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.
- 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.
- Install an SSH client program such as WinSCP and SSH keys (public key to be sent to Teldas) if you are sending traffic to INA offline numbers.
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.
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 will be transferred to you via XDR files (SSH). 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.
For more than 20 years, Teldas has been offering numbering services to operators in Switzerland. You are a company in need of routing communications to the correct carrier in Switzerland? You would like to port numbers from another operator or implement into your network Swiss Service Numbers ? Teldas will provide you with these services.
First founded as an association ("Verein Nummerportabilität") in 1999 by 7 founding members (Swisscom, Orange, diAx, MCI-WorldCom, multilink, Colt, sunrise) to support the introduction of Number Portability in Switzerland in March 2000, it was migrated in April 2003 into a company ("Teldas GmbH"), after the integration of the INA service in September 2001.
The Teldas GmbH shareholders are Salt Mobile SA, Sunrise UPC GmbH and Swisscom (Schweiz) AG.
The Teldas Users are mostly telecommunication service providers established in Switzerland and Liechtenstein. However, our users also include public authorities requiring our data to identify the operator where a number is implemented, foreign operators routing traffic to Switzerland or SMS service providers wanting to optimise the sending of VAS sms to the correct mobile network.
- Joining Fee (CHF 800)
- Annual Fee (CHF 1’300 for ONP, CHF 1’300 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.
- Transaction Fees:
- For ONP portings, the fee is comprised between CHF 0.40 and 1.3 per Work-Order Inport, Outport and Cancel, dependend on the amount of transactions/year.
- For INA, the fee is comprised between CHF 1.5 and 3.0 per transaction on an INA number and per INA number implemented with so-called offline tariffs, depending on the amount of transactions/year.
- For INA, a transaction fee of CHF 150 is also applicable for each tariff creation or modification, as well as for urgent number transactions.
The applicable fees are described in the Appendix 2 of the Teldas user contract.
User contract INA (English)
User contract INA (German)
User Contract ONP (English)
User Contract ONP (German)
ONP Supplementary contract (English)
ONP Zusatzvertrag (German)
- 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.