There are several kinds of log on PrivateServer and each one is suitable to monitor a different aspect of the service.
- static logs
- Auditing
- Web Sessions
- Call Detail Record
- Sip Sessions
- App log configuration
- Install messages
- Provisioning messages
- live logs
- Registered Accounts
- Sip Trunk status
- log's retention
- Data Retention
- Archived Data
4.0.
...
asfasfafs
4.0.1 SIP Sessions logs
The SIP Sessions page show the activities each Account did with the server.
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
To get this list just click on the SIP Sessions entry in the main menu. The activities are listed by date and they give you a detailed overview of the SIP status for each one. These logs are very useful for debugging the networking issues on the client side.
Tip | ||||
---|---|---|---|---|
In
|
The Event column lists the SIP events:
- CONNECT: PrivateGSM client opened a connection to PrivateServer. This usually means the client has been activated
- REGISTER: The Account has been correctly registered and is now on line
- UNREGISTER: The Account has been correctly unregistered and is now off line
- DISCONNECT: PrivateGSM client closed the connection. This usually means the client has been stopped.
4.0.2 Registered Accounts
If you want a full list of all the Accounts who are on line, then you click on the Registered Accounts entry in the main menu.
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
The list shows all the user actually on line and thus reachable on your PrivateServer. To read more detail about each user just click on its Id.
4.0.3 Web Authorization accesses
You can have a full view of all the access made to the management console.
Just click on the Web Sessions entry in the main menu and you get a list as in figure above. It shows up the detail about the user (principal), the IP address used to connect, the date of each authentication and the outcome (Event Type).
4.0.4 Call Detailed Records
Info | ||
---|---|---|
| ||
In this version the CDR has been completely rearrange to better show the valuable informations |
Despite its name the CDR is a debugging and quality assurance facility. It saves all the calls status, meaning it is very useful to understand is something is going wrong with you Secure Call Service.
To access the CDR you must click on the Call Detailed Record in the main menu. You'll get the "Cdr List" page which includes all the calls recorded.
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
If the table is empty, please place a phone call between the two SIp Accounts. Then come back on this page and check that the call has been correctly registered. The shown fields are:
- Call Date: when the call has been placed
- Caller Number: The virtual phone number used to place the call
- Caller: The caller description, if any
- Caller Group: The caller's group description, if any
- Callee Number: The virtual phone number called
- Callee: The callee description, if any
- Callee Group: The callee's group description, if any
- Total Duration: how long the call lasted. Time elapsed from the moment the "Call Button" is pressed on the caller's client to the one in which the communication is closed at all
- Call Duration: how long the call lasted, just the voice
- Disposition: which result the call had
- Hangup Cause: how long the call lasted
- Call id: a unique number that identifies the call
- Call type: nature of the call performed
Relevant fields in CDR
The Disposition is very important because it tells you the exit code of each call. Possible codes are:
- ANSWERED: the call was taken by the callee
- NO_ANSWER: nobody picked up the phone to answer (mostly this is a time out code)
- BUSY: the callee refused the call
- FAILED: for some reason the call was not able to be placed
- NO_ROUTE_DESTINATION: The callee is not reachable because of network issues.
- NORMAL_CLEARING: Call closed normally.
- USER_BUSY: The user is busy.
- NO_ANSWER: The callee didn't answer and the call was closed for timeout reason.
- CALL_REJECTED: The callee rejected the call, as by pressing the "hold" button.
- BEARERCAPABILITY_NOTAVAIL: The caller and the callee were using different security models that are not compatible.
- NO_USER_RESPONSE: The same as in "NO_ANSWER", but this happens when the call goes out by Trunk.
- CALL: Usual call between two persons
- 3-WAY: Usual call (as above) with an added person during the call
- CONFERENCE: Conference call
- TRANSFER: Usual call that is transferred to a third person
4.0.5 Data Retention
...
title | NEW FEATURE |
---|
...
3.1 Data Retention
The "Data Retention" is the new possibility that EVSS gives you to archive and store away some of the older data for consultation purposes.
...
The first one is used to configure the Retention features, the latter for retrieving the information stored on the hard disk of PrivateServer.
4.0.
...
3.
...
2 Setup of Data Retention
...
Xref | ||
---|---|---|
|
Warning |
---|
The data involved in the process are deleted from the database. |
Info |
---|
If you need to understand the data stored in each Data Type, please refer to the static logs section of the present manual. |
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
Each log entry listed in
Xref | ||
---|---|---|
|
Xref | ||
---|---|---|
|
- enable the Data Retention(Enabled checkbox)
- select the period to be kept on-line (Period Duration)
- choose how many archives you want to keep online (Period/s Online)
Note | ||
---|---|---|
| ||
A new Privacy option is possible from this version on: Privacy option can be setup in order to avoid any Call Record in the appliance. If you set the CDR Period to '0' (zero) then no more CDR logging will be performed for any DIRECT call (calls between two users). Conferences and 3-way calls will be logged as ever, though. |
4.0.
53.
23 Retrieve the Data Archives
Xref | ||
---|---|---|
|
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
The "Data Archive List" is shown in the page body (see
Xref | ||
---|---|---|
|
The last two columns shows two icons: the first one is for downloading the archive, the second one is for deleting it.
Tip |
---|
It's possible to download the archive also by clicking on its name |
If you choose to delete the archive, press the last column icon.
Subtitle | ||||||
---|---|---|---|---|---|---|
| ||||||
A confirmation is requested (see
Xref | ||
---|---|---|
|
Warning | ||
---|---|---|
| ||
Please be aware that this action is not isn't undoable! Once confirmed the deletion, the archive is lost forever! |
4.0.3.4 System's logs
PrivateServer is composed by multiple system applications beside the main Secure Voip Engine and its Web Console and they write down informations in logs. That's why PrivateServer applies one retention policy on these applications' logs as well. We're talking about:
- Tomcat
- Asterisk
That are our main players. Both of them use system locations (specifically directory /var/log) to store their logs. PrivateServer saves only the last week of these files and rotates them on a daily base. Rotate operation implies both deletion for files oder than one week and archiving in .zip format for the most recent ones. All the log files are labelled by timestamp of the rotation.
Navbar |
---|