System parameters can be found under the INet-Server system status (on the menu bar). These parameters are useful notably to find out how many days are set for performing a certain action before a timeout occurs or other system specific values.
If you would like to propose a change of value of a system parameter, you should raise your request using the online Change Request form. The Headgroup will then decide whether to accept the proposed change or not.
For changes to system parameters of the Test Environment, an E-Mail to the Helpdesk is sufficient.
Notice: It only concerns users who work with the INet GUI. For those who only work with the INet File Transfer interface, pgp is not required !
You receive the CLSN List (code list for the access to INet GUI) from Inet-Server with pgp encryption. Without installing pgp on your computer, you will thus receive e-mails you cannot read with the CLSN list. It concerns the e-mails sent to your EVENT Mailbox.
All other automatically generated e-mails from INet are being sent "pgp signed" but not encrypted.
E-Mails sent to the Helpdesk must be sent without pgp encryption. The Helpdesk will also respond to your queries via normal e-mail (encryption only concerns the automatically generated e-mails from INet).
How to install .pgp on Microsoft Outlook?
There are several softwares available on the market to install pgp on your Microsoft Outlook. Here a list of some of the en/decryption softwares (Teldas doesn't impose a specific one, you are free to choose any one suitable to you):
GPG4Win is an OpenSource free software, hereafter a small practical guidance how to install pgp on your Outlook mail client, using GPG4Win. In order to read GPG-encrypted messages with your Outlook mail client, proceed as follows:
1. Download Gpg4win from gpg4win.org
2. Stop Outlook
3. Install Gpg4win. Select the following options:
- Kleopatra (Certificate management utility)
- GPA (Gnu Privacy Assistant)
- GpgOL (Outlook add-on)
- GpgEX (Extensions for Windows Explorer)
In addition, it is recommended to also select the documentation options.
4. Start Outlook. At first sight, there is no difference. But in the Tools pulldown menu, you will find a new entry GnuPG Certificate Management. Click on it.
5. The certificate management utility Kleopatra opens. In the pulldown menu File click on New Certificate for creating a new key pair.
6. You have a choice of creating a personal OpenPGP key pair or a personal X.509 certificate. You can choose either option. Let's assume you choose a personal OpenPGP key pair.
7. Enter tsp98xxx as your name. tsp98xxx is meant to be the account which has been created for you on TSP-INet for file transfer access.
You cannot use any other name here.
8. Also enter your TSP-INet EVENT mailbox (if unsure, the Helpdesk can inform you which one has been defined in the INet-Server for you).
9. Enter in the comment field your company and/or your personal name.
10. Next you are asked for a passphrase. This is used for protecting access to your private key. You will have to enter it whenever you receive a new encrypted message. You may choose not to use a passphrase. In this case you must make sure that no unauthorized person has access to your mail client and to your Gpg4win installation.
11. When asked for next steps, just proceed without selecting any of the presented options and finish.
12. When your key pair is ready, it is shown to you in the Kleopatra console in the tab My Certificates. Click on it, then open the File pulldown menu and select Export Certificate. Export your public key to a file named tsp98xxx.asc (where tsp98xxx corresponds to the name used for creating the key). Mail the file to the Helpdesk.
13. Import the TSP-INet public key. There is a button Import Certificates on the Kleopatra console. Select a file containing the TSP-INet public PGP key (id: 56583190, finger: 3630 AA33 E201 021E 2845 7054 E201 37E0 5658 3190, generated on 2014-07-17). You can download it from one of your favorite public key servers (such as http://keyserver.ubuntu.com) . It is also available on the TSP-INet web GUI (click on Download Documents on the ONP or INA homepage) or accessible under your SSH home directory on the file transfer interface (under the "misc / other" directory).
14.The imported key appears now also in the Kleopatra console, most likely in the tab Other Certificates. Click on it, then open the pulldown menu Certificates and select Change Trust Status. The higher the trust status you select, the easier it will be to read encrypted messages from TSP-INet.
How to install .pgp on Thunderbird?
1. Go into the complementary modules and install the extension "enigmail".
You will then see on your Thunderbird menu bar a new menu "open pgp"
2. Go under www.gnupg.org and install "gnupg"
3. Using the configuration assistant on Thunderbird, you can generate
your private and public keys.
Note that you should enter tsp98xxx as your name. tsp98xxx is meant to be the account which has been created for you on TSP-INet for file transfer access. You cannot use any other name here.
Also enter your TSP-INet EVENT Mailbox. Enter in the comment field your company and/or your personal name.
This is used for protecting access to your private key. You will have to enter it whenever you receive a new encrypted message. You may choose not to use a passphrase. In this case you must make sure that no unauthorized person has access to your mail client and to your Gpg4win installation.
It is recommended to save the "revocation certificate" on a separate disk. It is also recommended not to configure pgp for all your outgoing messages, so that you can chose for each message whether you want to send it encrypted or not. Regarding the passphrase:This is used for protecting access to your private key. You will have to enter it whenever you receive a new encrypted message. You may choose not to use a passphrase. In this case you must make sure that no unauthorized person has access to your mail client and to your Gnupg installation.It is recommended to save your private key on your computer. You will now see in the menu bar an icon "pgp - openpgp" which permits to encrypt or sign e-mails.
4. Send your public key to the Helpdesk per e-mail (when writing an e-mail: in the top menu bar, go under OpenPGP and chose "attach mypublic key").
5. Download the Inet public key (id: 56583190, finger: 3630 AA33 E201 021E 2845 7054 E201 37E0 5658 3190, generated on 2014-07-17). You can download it from one of your favorite public key servers (such as http://keyserver.ubuntu.com) or either from the GUI (menu "Download documents") or by file transfer from the "misc / other" directory. You need to copy it and save it on your computer.
6. Now you are ready to receive encrypted e-mails from the INet-Server.Each time you receive such an e-mail, you will be asked to enter yourprivate passphrase so that it appears decrypted on your screen.
If you want to download periodic files from the INet-Server, you need to use SSH. Periodic files are generated for portability (e.g. the .lpn files with all ported numbers) and for INA (e.g. the .lig files with all the INA transactions).
If you are only using the INet-Server to enter portability orders or INA transactions via the Internet Browser (General User Interface-GUI), SSH is not required.
For security reasons, the file transfer interface of TSP-INet supports only encrypted connections based on the SSH (Secure SHell) and PKI (Public Key Infrastructure) standards. More information on them is available from resources such as http://kimmo.suominen.com/docs/ssh/ or http://msdn.microsoft.com/en-us/library/aa387460(VS.85).aspx . Important facts for the TSP:
The test environment can be used by all Users for training purpose or for testing of their interface to the INet-Server. You must be aware that the same test environment is used when new releases of the Inet-Server are to be put in production and therefore it can reflect a different environment than the productive environment. You should always check about the roll-out plans of new INet-Server releases, which you will find under Projects / Inet-Server.
You can access to the test environment under the link https://testsrv.numberportability.ch.
You can get up to 4 TSP accounts on the test environment: the main TSP account has the same NPRN as in production. If you want to test the porting process as Donor/Recipient, you need at least one additional NPRN (format 8XXXX, where XXXX is the same as your main TSP account). This allows you to play the Donor and Recipient roles and go through a whole porting transaction.Other accounts in the format 7XXXX and 6XXXX are possible in case you need to play the OFCOM role (allocate/deallocate INA numbers) or the NRH role (for example with return to NRH porting transactions).
The database on testsrv is not related in any way to the production, not for number porting, nor for system parameters and nor for user account information. Therefore, if you need details about your user accounts or if you need to set a password for an interactive login, please contact the Helpdesk and refer to the test environment chapter of the General User Manual (GUM) for the INet-Server.
Please refer to the document "Archiving Rules INet" in the document section.
The deletion of files is part of the INet clean-up policy as explained in the Archiving rules INet document (chapter "Clean-up TSP's own files on SSH Directories").
The various e-mail boxes that you need to open depend on your business model. You can use the same E-Mail address for all the mailboxes or different ones if you want different teams to receive them.
If different E-Mail addresses, we recommend following structure: onp.supervisorNPRNXX@user.ch, ina.eventNPRNXX@user.ch (e.g. firstname.lastname@example.org).
For more information, please refer to the relevant Mailbox chapter of the General User Manual (GUM) for the INet-Server.
Here the list of the different E-Mail Boxes which can be activated:
Onp.broadcast / ina.broadcast: By default, nothing is defined. As it reflects the information contained in the .lpn files (for ONP) and in the .lig files (for INA) and implies an important amount of e-mails, we strongly advise NOT to activate this mailbox. Exception: broadcast for tariff class modifications can be of interest.
Onp.download / ina.download: E-Mail notification when reports are ready for download.
Onp.event / ina.event: new CLSN lists & for ONP also the status changes of a Work-Order. Note that Status changes can be ordered specifically (refer to chapter "set-up status change e-mails" of the General User Manual (GUM) for the INet-Server), by default only the status changes related to timeouts and cancels by the system will be received (reaction then required!).
Onp.failure / ina.failure: for the management of timeouts (when reaction is required from you) when you are active party in the transaction.
Onp.failureinfo: to inform about timeouts of your work-orders when the other TSP must react.
Onp.poa: to send scan of PoA among operators (manually generated e-mails).
Onp.reminder: by default, nothing is defined. You can set up reminders for every type of action required and define the exact times when these need to be received (to ensure you have enough time to perform the action). For more details, please refer to the chapter "Set-up reminders" of the General User Manual (GUM) for the Inet-Server.
Onp.supervisor / ina.supervisor: to receive important messages from the Helpdesk, e.g. escalation messages in case of INet-Server breakdowns.
Onp.tspmod / ina.tspmod: notification of changes in the TSP user list (.tsp files).
ina.wopa: wholesale parameter e-mails for the billing share.
ina.osrvo: out of service orders.
vta.event: VTA file receipt and non-delivery notifications
We recommend that you activate at least the "supervisor" mailbox and in case you use the interactive logins on the INet-Server also the "event" mailbox. You will receive important messages on these mailboxes.
In case you are an active party in INA and ONP transactions (you are taking into service INA numbers or porting numbers), you should also activate the "failure" mailbox.
One of the Supevisors of your company need to require a new user account to the Helpdesk using the appropriate "User Privilege Table", see chapter "Set-Up Info for TSP users" of the General User Manual (GUM) for the Inet-Server.
To login on the INet-Server (https//www.numberportability.ch), you will require a User Id, password and CLSN code. The CLSN list is sent to the "event" mailbox (please refer to the question "What are the E-Mail accounts that I need to open to receive appropriate reminders & notifications ?"). Note that the CLSN list is always sent .pgp encrypted, please refer to the question "How should I install .pgp and why is it needed?".
Some information on the TELDAS Homepage (https//www.teldas.ch) is user protected. To obtain a user account, please fill in the appropriate registration form.
The User Login is only provided to persons from companies having signed a user contract with Teldas. A User Login permits to view technical documents related to the INet-Server as well as some useful contacts (for example our Helpdesk contact).
Powerusers are allowed to open Change Requests, Problem Reports and IT Breakdowns on the Teldas homepage. Once such a report is published on the Homepage, it initiates the appropriate actions from our Helpdesk or from the other TSPs.
Usually, powerusers are persons from your company active in the ONP / INA / VTA domain. These persons filter the company's internal questions before publishing a PR/CR/IT Breakdown on the Teldas Homepage.
The NPRN stands for Number Portability Routing Number and is used to identify the Operator where to terminate traffic.
The NPRN is also used as INet-Server account identification. It can either be an NPRN allocated by OFCOM (98xxx) or a dummy allocated by TELDAS (99xxx). You need to require an NPRN from OFCOM in case you want to port in numbers or in case you want to have INA numbers implemented in your network. Else a dummy NPRN is sufficient and will give you read only facilities on the INet-Server to query the database or download files.
The CDP_ID is used for wholesale billing purpose to identify the originating network for calls to INA numbers, in order for the INA-TSP to send an invoice for the received calls.It must be included by the originating network in the signalling information for calls to INA numbers.
Swissom as Owner of the INA Allocation Table will update the Table with the appropriate information. For national originating calls, the CDP_IDn is used, for international originating calls the CDP_IDi and for prepay originating calls the CDP_IDp. Note that interested TSPs can subscribe under "My Profile" to e-mail notification / RSS feeds to be informed of updates of this Table.
The CDP_ID is also used on the INet-Server as Mailbox for the Downloading of XDR Files and VTA Files.
The CDP-ID is either allocated by OFCOM as Carrier Selection Code (107xy or 108xy) or else, if the Operator doesn't make Carrier Selection, by TELDAS as dummy (103xy for CDP_IDn and CDP_IDi or 102xy for CDP_IDp). Note that for VTA File exchange, the Operator cannot use a dummy CDP-ID as it must always be related to the Operators'Carrier Selection Code.