This repositories contains the test specifications and test adapter code
to test compliance to ETSI TS 103 479 (V1.1.1: “Emergency Communications (EMTEL); Core elements for network independent access to emergency services”.
to test compliance to ETSI TS 103 479 (Emergency Communications (EMTEL); Core elements for network independent access to emergency services).
## Contact information
Email at cti_support at etsi dot org
@@ -13,9 +13,10 @@ See the attached LICENSE file or visit
https://forge.etsi.org/legal-matters
## Standard links
- ETSI TS 103 650-1, Part 1: Test Purposes - Available soon
- ETSI TS 103 650-2, Part 2: Test Suite - Available soon
- ETSI TS 103 479, Core elements for network independent access to emergency services - Available soon
- ETSI TS 103 650-1, Part 1: Test Purposes V1.2.1 - Available [here](https://www.etsi.org/deliver/etsi_ts/103600_103699/10365001/01.02.01_60/ts_10365001v010201p.pdf)
- ETSI TS 103 650-2, Part 2: Test Suite V1.2.1 - Available [here](https://www.etsi.org/deliver/etsi_ts/103600_103699/10365002/01.02.01_60/ts_10365002v010201p.pdf)
- ETSI TS 103 479 V1.2.1, Core elements for network independent access to emergency services - Available [here](https://www.etsi.org/deliver/etsi_ts/103400_103499/103479/01.02.01_60/ts_103479v010201p.pdf)
- ETSI TS 103 698, Emergency Communications (EMTEL); Lightweight Messaging Protocol for Emergency Service Accessibility (LMPE) - Available [here](https://www.etsi.org/deliver/etsi_ts/103600_103699/103698/01.01.01_60/ts_103698v010101p.pdf)
- Next Generation 112 Long Term Definition, accessible [here](https://eena.org/wp-content/uploads/2018/11/Next-Generation-112-Long-Term-Definition-Standard-For-Emergency-Services.pdf)
## RFC links
@@ -187,17 +188,46 @@ Procedure:
- $HOME/frameworks,
- $HOME/dev
- $HOME/lib
- In $HOME/frameworks, build the following package:
- Eclipse IDE for C/C++ Developers, according the procedure specified [here](https://www.eclipse.org/cdt/)
- TITAN, according the procedure specified [here](https://github.com/eclipse/titan.core)
- Import the TITAN plugin into your Eclipse IDE, according the procedure specified [here](https://github.com/eclipse/titan.core)
- Update your default environment with the content of the script $HOME/dev/TTF009_Ng112/scripts/devenv.bash.ubuntu
- Switch to the next clause (Usage)
@@ -215,34 +245,37 @@ Procedure using Eclipse TITAN:
- Start eclipse using a new workspace, (e.g. with the name workspace_titan)
- Download and follow the steps to install Eclipse plugins for TITAN, accessible [here]{https://www.eclipse.org/downloads/download.php?file=/titan/Eclipse_installationguide.pdf}
- Open the workspace_titan
- Create a new TITAN project (e.g. STF549_Ng112)
<TODO>
- Create a new TITAN project (e.g. TTF009_Ng112)
- Import the .tpd file located at the root level of the project
Procedure in TITAN command line:
- Open several SSH session (PuTTY...)
- Change to the directory ~/dev/STF549_Ng112/src/AtsNg112/objs
- Build the test suite AtsNg112
- Change to the directory ~/dev/TTF009_Ng112/
- Build the test suite you want to exectue (e.g. LIS test suite)
```sh
$ ../bin/ng112_generate_makefile.bash
$ cd ~/dev/TTF009_Ng112/
$ export ATS=AtsLIS
$ make
...
```
- Edit the file ../etc/AtsNg112.cfg
- Edit the file ../etc/AtsLIS/AtsLIS.cfg
- Update the following fields:
- system.httpPort.params
- Caller.SIPP.params
- Ecrf.SIPP.params
- CallTaker.SIPP.params
- CallTalker.SIPP.params
- To run the test suitem, execute the following command:
```sh
$ ../bin/run-all.bash
$ cd ~/dev/TTF009_Ng112/scripts
$ ./run-all.bash
...
```
- The log files are located in ../logs folder. You can edit them using any editor or using the Eclipse TITAN log plugins
- The log files are located in ../logs/AtsLIS folder. You can edit them using any editor or using the Eclipse TITAN log plugins