| No. | Checklist item | Command | Expected result | Recommendations
for achieving the
expected result |
|---|
Testing the started services |
|---|
| 1 | Checking the started telephony services:- ecss-mycelium
- ecss-core
- ecss-ds
- ecss-pa-sip
- ecss-mediator
| sudo systemctl list-units --all |\
grep -E "ecss-core|myc|ecss-ds|sip|mediator" |\
awk '{print $1, $3"("$4")"}' |\
jq -R 'split(" ")|{servise:.[0], status:.[1]}' |
| Copy all strings of the command in their entirety |
| {
"servise": "ecss-core.service",
"status": "active(running)"
}
{
"servise": "ecss-ds.service",
"status": "active(running)"
}
{
"servise": "ecss-mediator.service",
"status": "active(running)"
}
{
"servise": "ecss-mycelium.service",
"status": "active(running)"
}
{
"servise": "ecss-pa-sip.service",
"status": "active(running)"
} |
| Make sure all services from the list are active (running) |
| Start the service which status is: inactive (dead), or different from active (running) |
| 2 | Checking the started service for processing voice/video traffic: | sudo systemctl list-units --all |\
grep "ecss-media-server.service" |\
awk '{print $1, $3"("$4")"}' |\
jq -R 'split(" ")|{servise:.[0], status:.[1]}' |
| Copy all strings of the command in their entirety |
| {
"servise": "ecss-media-server.service",
"status": "active(running)"
}
|
| Make sure the ecss-media-server is active(running) |
| Start the ecss-media-server.service service if its status is different from: active(running)
|
| 3 | Checking the started restfs* services(The services are responsible for storing and providing call recording files and automated message files)
| sudo systemctl list-units --all | tr -d '●' |\
grep -E "restfs" | grep -E "card|core|unit|timer|writer" |\
grep -v "checker" |\
awk '{print $1,$3 "("$4")"}' |\
jq -R 'split(" ")|{servise:.[0], status:.[1]}' |
| Copy all strings of the command in their entirety |
| {
"servise": "ecss-restfs-card.service",
"status": "active(exited)"
}
{
"servise": "ecss-restfs-core.service",
"status": "active(exited)"
}
{
"servise": "ecss-restfs-unit-conf.service",
"status": "active(exited)"
}
{
"servise": "ecss-restfs-unit.service",
"status": "active(running)"
}
{
"servise": "ecss-restfs-writer.service",
"status": "active(running)"
}
{
"servise": "ecss-restfs-cleaner.timer",
"status": "active(waiting)"
}
{
"servise": "ecss-restfs-crawler.timer",
"status": "active(waiting)"
}
|
Make sure all services from the list are active. active(exited) – is a normal status for: active(waiting) – is a normal status for: |
| Start the services the status of which starts with inactive
|
| 4 | Checking web services:- ecss-web-conf
- ecss-teleconference-ui
- ecss-cc-ui
| sudo systemctl list-units --all |\
grep -E "ecss-web|teleconf|cc-ui" |\
awk '{print $1,$3 "("$4")"}' |\
jq -R 'split(" ")|{servise:.[0], status:.[1]}' |
| Copy all strings of the command in their entirety |
| {
"servise": "ecss-cc-ui-api.service",
"status": "active(running)"
}
{
"servise": "ecss-cc-ui.service",
"status": "active(exited)"
}
{
"servise": "ecss-teleconference-ui-api.service",
"status": "active(running)"
}
{
"servise": "ecss-teleconference-ui.service",
"status": "active(exited)"
}
{
"servise": "ecss-web-conf.service",
"status": "active(running)"
}
{
"servise": "ecss-web-socket.service",
"status": "active(running)"
} |
Make sure all services from the list are active. active(exited) – is a normal status for: |
| Start the services the status of which starts with inactive |
| 5 | Checking system services connected to ECSS-10 | sudo systemctl list-units -all | grep dnsmasq |\
awk '{print $1,$3 "("$4")"}' |\
jq -R 'split(" ")|{service:.[0],status:.[1]}' |
| Copy all strings of the command in their entirety |
| {
"service": "dnsmasq.service",
"status": "active(running)"
} |
Make sure that the dnsmasq service is active(running). |
| Запустить сервис в случае, если его статус inactive |
| # Generated by NetworkManager
search eltex.loc
nameserver 127.0.0.1 |
Make sure that 127.0.0.1 address is specified in the nameserver; your root domain can be specified in the search. |
| Change nameserver address to 127.0.0.1 |
| 7 | Checking the ECSS-10 database status |
|
|
|
Checking the services launched inside the ECSS-10 |
|---|
| 1 | Checking the connection to the management console (CoCon):The following steps are performed without exiting CoCon. | ssh admin@localhost -p 8023 |
| admin@localhost's password:
admin@[mycelium1@ecss1#ECSS-ID]:/ |
Make sure you are logged in to CoCon and that your ECSS-ID is listed in the invitation line. |
| Contact technical support |
| 2 | Viewing the nodes connected to the ECSS-10 cluster | | Nodes:
core1@ecss1 ds1@ecss1 md1@ecss1 mycelium1@ecss1 sip1@ecss1
All services are started |
Make sure that your system has exactly the same list of nodes running in the ECSS-10 cluster. |
| Start a service that is not running on your system but is listed here |
| 3 | Viewing the MSRs connected to the ECSS-10 cluster | system/media/resource/list short
|
| Active media resource selected list specific:
┌─────────────┬───────────┬─────────────┬───────────┬────────────┐
│ Node │ MSR │ MSR │ Cc-status │ Cc-uptime │
│ │ │ version │ │ │
├─────────────┼───────────┼─────────────┼───────────┼────────────┤
│ core1@ecss1 │ msr.ecss1 │ 3.14.15.243 │ connected │ 9 22:21:44 │
└─────────────┴───────────┴─────────────┴───────────┴────────────┘ |
Test that the Cc-status for the MSR named msr.ecss1 is connected. On your system, the MSR name may differ from the one specified in this article. |
| Check that the following configuration files are correct: - /etc/ecss/ecss-media-server/config.xml
- /etc/ecss/ecss-media-server/conf.d/default.xml
|
| 4 | Viewing the status of the restfs storage | | ┌────────────┬──────────────────────────────┬─────────┐
│Cluster name│ Peer │ Status │
├────────────┼──────────────────────────────┼─────────┤
│default │http://system.restfs.ecss:9990│connected│
└────────────┴──────────────────────────────┴─────────┘
Succesfull |
Make sure that default restfs has the connected status. |
| Contact technical support |
| 5 | Viewing the available auto-informer files | | Type Name Size
directory domain 4K
directory system 4K
directory template 4K
file cleaner.json 1.03K |
Make sure the command output includes the following required names: - domain
- system
- template
- cleaner.json
Other files and directories may also be present, but only the four listed above are required. |
| Contact technical support |
| 6 | Viewing the active commercial license | cluster/storage/ds1/licence/list-licence |
| ┌──┬───────────────────┬────────────┬──────┬──────────────────────┬────────────────────┬──────────┐
│Id│Creation date(UTC) │ SSW ID │Active│ Description │Expiration date(UTC)│Time left │
├──┼───────────────────┼────────────┼──────┼──────────────────────┼────────────────────┼──────────┤
│1 │05.08.2025 13:50:00│ECSS-Test │* │Eltex-SC test │05.08.2026 13:50:00 │83d 6h 36m│
│0 │ │ECSS DEFAULT│ │Default licence │ │ │
└──┴───────────────────┴────────────┴──────┴──────────────────────┴────────────────────┴──────────┘ |
Make sure that the command output includes a license with an ID other than 0, and that this row contains an "*" in the Active column. There may be multiple licenses, but only one can be active (the Active column will contain an “*”) – the one with the highest value in the ID column. |
|
|
Testing the functionality of the ECSS-10 telephony |
| 1 | Testing the playback of auto-attendant files to the calling subscriber using the "My Number" service as an example | On the station subscriber’s phone, dial the feature code: *123. | The caller should hear their own phone number through the handset or speaker |
|
|---|
| 2 | Testing intra-station calls |
|
|---|
Testing the routing of a direct call from one station subscriber to another (A → B). | On the phone of station subscriber “A,” dial the phone number of station subscriber “B.” | - Test that the connection is established correctly.
- Test that voice traffic is transmitted correctly between the two subscribers.
- Test that the caller’s number and name are displayed on Subscriber B’s phone.
- Test that Subscriber B’s name is displayed on Subscriber A’s phone.
|
|
Testing a return call from one station subscriber to another (B → A) | On Subscriber B’s telephone, dial the phone number of the other station subscriber, Subscriber A. |
| 3 | Testing calls to local numbers 
|
|
|---|
Testing a direct call between a station subscriber and a local number (Trunk call) (А → Bloc) | On the station subscriber’s telephone, dial a seven-digit local telephone number that does not belong to this PBX. | - Test that the connection is established correctly.
- Test that voice traffic is transmitted correctly between the two subscribers.
- Test that the calling number is correctly displayed on phone B.
|
|
Testing a return call between a station subscriber and a local number (trunk call) (Bloc → A) | Make a call from a local number to the station subscriber’s number using the subscriber’s local number |
| 4 | Testing long-distance and mobile calls
|
|
|---|
Testing a direct call between a station subscriber and a long-distance number (trunk call) (A → Bld/mob) | On the station subscriber’s phone, dial the phone number in long-distance format (11 digits) | - Test that the connection is established correctly.
- Test that voice traffic is transmitted correctly between the two subscribers.
- Test that the calling number is correctly displayed on phone B.
|
|
Testing a return call between a station subscriber and a long-distance number (trunk call) (Bld/mob→ A) | Make a call from a long-distance or mobile number to the station subscriber’s number using their local area code |
| 5 | Testing correct call forwarding (CFU/CFNR/CFT/CFB) |
|
|---|
Testing call forwarding to the station subscriber A → B → Csub | On subscriber “B,” set up any of the available types of call forwarding to subscriber “C” via the station’s web interface or via a feature code. Make a call from subscriber “A” to subscriber “B.” | - Test that the connection between ‘A’ and “C” is established correctly.
- Test that voice traffic is transmitted correctly between the two subscribers.
- Test that the calling number is correctly displayed on phone “C.”
- Test that the number “C” is correctly displayed on phone “A.”
|
|
Testing the correctness of call forwarding to a mobile number A → B → Cmob | On subscriber “B,” set up any of the available types of call forwarding to mobile number “C” via the station’s web interface or via a feature code. Make a call from subscriber “A” to subscriber “B.” |
|
Testing the correctness of call forwarding to a mobile number for an incoming call from a mobile/local number Ald/mob → B → Cmob | On subscriber “B,” set up any of the available types of call forwarding to mobile number “C” via the station’s web interface or via a feature code. Make a call from mobile number “A” to subscriber “B” using their local number. | - Test that the connection between "A" and "C" is established correctly.
- Test that voice traffic is transmitted correctly between the two subscribers.
- Test that the calling number is displayed correctly on the “C” phone.
|
|
| 6 | Testing a conference call setup (add-on) |
|
|---|
Test the correct setup of a three-way conference call A → B A → C A + B + C | Subscriber “A” (provided they have the following services: add-on, ctr, chold) should initiate a conference call with subscribers ‘B’ and “C.” | - Ensure that the connection between “A,” “B,” and “C” is established correctly.
- Test that voice media traffic is correctly routed between the three subscribers.
|
|
7+ | Checking other used services |
|
|---|
| Test the functionality of all services and integrations used by your company, such as: - email2fax
- fax2email
- IVR
- Teleconferencing
- CallCenter
- Autodialer
and others |
|
|
|
|---|