Headgroup Meeting AnneCatherine Christen Managing Director Teldas 29

Agenda 1. Meeting Minutes (23. 11. 2018) To approve 2. INet ongoing Projects (https:

Project Web Service § ff TSPs to participate to UAT !!! TSPs can start

Change requests Following change requests have been recommended by the Working Group and already

Project Web GUI § ff TSPs to participate to Workshops and Po. C !!!

Liechtenstein § In February 2019, Teldas adapted the INet-Server to be able to take

Projects 2019: Content ID Domain Description Estimated Effort PR 10788 ONP Timeout A notification

Projects 2019 proposed rollout § § § 04. 06. 2019 – Delivery of detailed

Mass porting fees § Appendix 2, definition of the porting transaction fee --> Add

INA bilateral contracts § § What contract is necessary for a TSP sending traffic

ONP Document for Implementation § § Po. A templates harmonization: see proposed layouts in

Any other Business § Industry standard tariffs: § AI 1017: Today, the interoperability obligation

Slides: 18

Download presentation

Headgroup Meeting Anne-Catherine Christen Managing Director Teldas 29. 03. 2019 Confidential and Proprietary Any use of this material without specific permission of Teldas Gmb. H is strictly prohibited

Agenda 1. Meeting Minutes (23. 11. 2018) To approve 2. INet ongoing Projects (https: //www. teldas. ch/projects/inet-server-releases. html) Information • Web Service Project: planning / status + 5 change requests supported by the WG Web • GUI Project: planning / status • Liechtenstein Status 3. INet Release 2019 Decide about content and planning • It is proposed to have a small INet-Release in 2019, with no impacts on the operators' SSH interface (SSH tests are however required to check that the impacts are null). 4. ONP User Contract Decision about Appendix 2 and 5. 2 • Decision on Mass porting fees 5. INA User contracts Decide if new Appendix 5. 2 • We face now cases of smaller TSPs having implemented INA 0800/084 x numbers without having signed the Swisscom Transit Service Contract. Currently no clauses are integrated in the Teldas INA contract to handle this case. In the ONP contract, we have a special mention of bilateral charges among operators in case no bilateral contract exists (Annex 5 part 2). Should we also define such a case for INA? Decision on Wholesale charging among TSPs (AI 1081) 6. ONP Document for Implementation Decide about implementation date and validate document • Po. A Process, Po. A template • Routing Change at acti_time 7. AOB & Action Items • Presentation OFCOM: European Electronic Communications Code (EECC)DIRECTIVE (EU) 2018/1972 effects on CH-numbering • Increase the amount of INA industry standard tariffs drastically? Impose obligation of Routing of Prepay calls to online numbers ? (AI 1017 WG) • See list of open actions from previous meeting

Project Web Service § ff TSPs to participate to UAT !!! TSPs can start using WS

Change requests Following change requests have been recommended by the Working Group and already validated by the Teldas members: § § § Notification module improvement Get reject reasons Get all ported numbers Get system and connection parameters Security improvement Change requests are planned for the next sprint implementation on staging

Project Web GUI § ff TSPs to participate to Workshops and Po. C !!!

Liechtenstein § In February 2019, Teldas adapted the INet-Server to be able to take on board the Liechtenstein portings. In this view, a new ONP contract Version 9. 0 has been published. It contains notably some new “country” clauses: Ø 3. 2. 1. 2. Porting is only done on national level between TSPs of the same country. TSPs operating numbers from different countries must obtain and use a separate NPRN for each country. Ø 3. 2. 1. 4. When a number has been successfully ported within the network, the TSP INet-Server informs all TSPs having signed a User contract with Teldas in the form of a "Broadcast" Message and enters the ported number in the central directory of ported numbers held within the TSP INet-Database. At any time Users are thereby provided with access to an up-to -date directory of all ported numbers in Switzerland Liechtenstein § Note that all operators having signed the ONP Contract in a previous version don’t need for the time being to sign the new contract. Other adaptations will be brought in the contract once the Web Service interface is available in production. § New “country” rules have been added in the INet Application, so that Liechtenstein operators can use the Swiss porting database to perform their own portings. The features are available on INet since 12 th February (Version 4. 11. 1) and the Liechtenstein operators are planning to launch their porting service in the coming months. § E. 164. Numbering resources used by Liechtenstein are starting with the prefix 015, NPRNs with 97 xxx. These will be present in the ported number database (. lpn files and. tsp files) as soon as LI operators launch the porting service.

Projects 2019: Content ID Domain Description Estimated Effort PR 10788 ONP Timeout A notification not sent to onp. failure. info mailbox low PR 10791 ONP Correct Partial porting selection results for READ WO medium PR 10822 ONP Wrong use of error message 581 at INIT: it must be split into 2 messages (Donor must be currently operating TSP / Con_type DDI-PSTN/ISDN issue) medium PR 10823 ONP MAX_DAYS_SHIFT_ACTI_SYNC to remove as not used low PR 10824 ONP Do I have to react ? Issue in DB on the date format, function doesn’t provide correct results on SSH low PR 10826 ONP INA numbers of some TSP not displayable low CR 1282 ONP Business validation for reject reason 11 (new error message when departure status = confirmed) low CR 1287 ONP Business validation for accept (new error message if acti_date filled when wish_date <> empty). low CR 1288 ONP Automatic cancel of WO if no Represent after x days medium CR 1289 CR 1290 ONP New error message for INIT if subscriber name/surname is not filled for con_type PSTN/ISDN, Mobile, DDI, INA (currently WO goes into init with these mandatory fields empty) New error message for SYNC: for the sync the tariffclass is disregarded when con_type <> INA. Should we also add an error message "field must be left empty if con_type <> INA" ? low CR 1291 ONP Country flag to be added in the ported number list for WS (impacts on SSH should be transparent but need to be tested, that’s why it should be done within Inet-Release) medium Ø The content of the release is the recommandation of the Working Group Ø TSP to make some regression tests to ensure SSH is not impacted §Medium > 2 wd and <7 wd §Low <= 2 wd

Projects 2019 proposed rollout § § § 04. 06. 2019 – Delivery of detailed specifications 02. 07. 2019 - Deployment on STAGING, for UAT 03. 07. 2019 -20. 08. 2019: UAT Working Group members to test as of Begin August 2019 Important to ensure that SSH is not impacted !!! 26. 08. 2019 - Deployment on TEST 09. 2019 - Deployment on PROD (this is not a non-working day, the proposition is to do it after 6 pm)

Mass porting fees § Appendix 2, definition of the porting transaction fee --> Add „Exception: For a mass porting transaction, each line in the mass migration file is defined as „porting transaction“, with a minimum and maximum total price for the mass porting transaction comprised between CHF 2'000 and CHF 8‘ 000“ ? § Appendix 5, part 2, chapter 2. 3. 3 --> Add „For mass portings, the porting fee is defined per line contained in the mass porting file, with a maximal amount of CHF 8‘ 000“ ? Note that this might also need to be taken over in the Swisscom interconnection contract.

INA bilateral contracts § § What contract is necessary for a TSP sending traffic to Swisscom INA numbers? What contract is necessary for a TSP sending traffic to other TSP's INA numbers? What contract is necessary for a TSP taking into service INA-numbers? AI 1081 § Currently we have 2 operators having implemented 0800 and 084 x numbers and not signed the Swisscom Wholesale Billing Contract Ø How can other TSPs get the interconnection fee for the oigination of 0800 calls ? Ø How can the INA-TSP get the retail share for the 084 x calls ?

ONP Document for Implementation § § Po. A templates harmonization: see proposed layouts in 3 languages Po. A templates entry into force: 1. 1. 2020 at latest see under AI 1057 Legal sentence related to «partial porting» Legal sentence related to «early termination fees» § Routing issue: Donor Operator doesn’t always change the routing correctly at acti_time WG proposes to add precision related to the routing and to aim at modifying the routing at exactly the acti_time, in order to avoid interruption of service TSPs should verify routing is correctly set by the Donor and inform Teldas of any issues Teldas will notify the concerned TSPs but it is then the responsibility of the Recipient Operator to charge SLA penalties, in order to improve service level for the subscriber See under AI 1086

Any other Business § Industry standard tariffs: § AI 1017: Today, the interoperability obligation for Prepay customers is to be able to reach all INA numbers with industry standard tariffs (85 numbers). As 96% of INA numbers are implemented with online tariffs, it would be very helpful if the Mobile Prepay Operators could route the traffic generally to all numbers with online tariffs (not only with industry-standard). § Salt confirms that this is not possible for them (inflexible system). § Swisscom already provides access § Sunrise also confirms that currently not possible for them. Proposition would be to increase drastically the amount of industry standard tariffs (add the flag on most of the 366 online tariffs). Or INA-TSPs to send list of a certain amount of much used INA tariffs (amount to be defined) § Proposed non-working days 2020: for INet-Releases and maintenances § 25. 03. 2020 - 4 work orders open § 10. 06. 2020 - 3 work orders open § 18. 11. 2020 - no work orders § Open Actions from last meeting: § AI 1051: the WG proposes to close the issue, because of data protection issues and Sunrise cannot impose SMS service to its MVNOs § AI 1058: to be closed, see ONP Document for Implementation (agenda point 6) § AI 1079: bank licence requirements (Felix to provide more information) § AI 1081: see agenda point 5