In this section we collect all the logs about events that has happened. This type of logs are written once the event has finished and do not represent a live photograph of the state of the service or of the appliance. They are mostly useful for debugging user's issues and to provide support.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | the static logs |
---|
|
...
menu | AnchorName | static_logs_menu |
---|
|
Image Added |
As you can see in
Xref |
---|
AnchorName | static_logs_menu |
---|
|
all these logs are grouped under the "LOGGING" label into the main menu.4.0.1.
...
1 Auditing
The Auditing page can be found under Logging section in the main menushows any change to the configuration performed via web console.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | List of SIP Session Activities |
---|
AnchorName | sip logs |
---|
Audit Events Log List | AnchorName | audit_log |
---|
|
Image Added |
As shown above in
, we can collect several informations:Timestamp: the exact time the event happened.
Note |
---|
Please remember that the timestamp is related to the appliance's time configuration. It's local time which gets reported. |
- Username: the user who performed the change is traced by the username used in the login.
- Change: the type of changes performed.
- Object Type
- Object ID
These informations can be used for security checks as for post-issue analysis.
4.0.1.2
...
Web Sessions
...
In the web sessions it's possible to read the list of all the access made to the web console.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | List of SIP Web Session ActivitiesLogs |
---|
AnchorName | sip logs |
---|
|
Image Removed |
...
|
Image Added |
Just click on the SIP Sessions Web Sessions entry in the 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 you can read that a NETWORK_ERROR has caused the DISCONNECT event for one user. |
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.
Each one has its Details column which explains the exact message provided by the PrivateServer.
CONNECT/DISCONNECT event are bound to a remote address, not directly related to a specific VoIP account. A periodic background task analyses the SIP session logs and, when possible, reconcile them binding these events to a specific account.
Reconciliation is very useful while debugging SIP session for a specific user: clicking on username field will show a filtered list of SIP session events.
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 |
---|
Prefix | figure |
---|
SubtitleText | Registered Account list |
---|
AnchorName | registered account list |
---|
|
Image Removed |
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.
Image Removed
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 |
and you get a list as in figure
Xref |
---|
AnchorName | web_sessions_log |
---|
|
. Fields shown are:- Date Created: this is when the event occurred
- Event Type: there are several type of Events (see specifications below)
- Principal: the username used to log in.
- IP Address: the IP address from which the connection has been performed.
Info |
---|
If the user listed is "anonymousUser" then this is an event triggered by the system. This is specifically true for events like the "SESSION_TIMEOUT". |
Event Types
Here follows a list of all the event types logged in this table:
- SESSION_TIMEOUT : pretty self explanatory
- LOGOUT : The user performed a logout
- SUCCESS_INTERACTIVE / SUCCESS : these two events always come together and indicates a login has successfully performed. The former one points out the login happened through the web interface ("interactive"), the latter is a generic successful login log.
- FAIL_USER_NOT_FOUND : the login used was not found among the users configured.
- FAIL_CREDENTIALS_EXPIRED : the password or the credentials used are set as expired
- FAIL_BAD_CREDENTIALS : wrong password
4.0.1.3 Call Detailed Records
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 the Call Detailed Record in in the main menu. You'll get the "Cdr List" page which includes all the calls recorded.
Subtitle |
---|
Prefix | Figurefigure |
---|
SubtitleText | Call Detailed Record List |
---|
AnchorName | cdr list |
---|
|
Image RemovedImage Added |
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.
- Call route: if the call transited on a trunk this field would shown the trunk's name.
Relevant fields in CDR
The The Disposition is 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
The Hangup Cause describes describes in details what caused the hangup. Possible causes are:
- 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.
The The Call Type identifies identifies the nature of the call. Used with the Call id fields this value is useful to trace down complex calls like three-way calls, conferences or transferred calls. Possible values are:
- 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
The The Call id is is a number that identifies uniquely the call. It can be used to trace a call if it changes its nature (ie becoming a three-way call) or to group all the participants (ie in a conference room).
4.0.5 Data Retention
Info |
---|
|
The "Data Retention" feature has been introduced in the present version. |
...
Info |
---|
It's possible to avoid any call record, as a Privacy option. To enable the "No-CDR" option, you just have to set the CDR Period to "DAY" and the duration to '0' (zero). |
Warning |
---|
The above statement about the CDR Privacy option is true only for the DIRECT calls (which are the calls between two users). Conferences and 3-way calls will be logged as ever, though. |
4.0.1.4 SIP Sessions
The SIP Sessions page show the activities each Account did with the server.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Menu access to the Data RetentionList of SIP Session Activities |
---|
AnchorName | data_retention_menus |
---|
|
Image Removed |
...
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.
...
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.5.1 Setup of Data Retention
You can create a retention policy for some important logs provided by the appliance.
you can read that a NETWORK_ERROR has caused the DISCONNECT event for one user. |
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.
Each one has its Details column which explains the exact message provided by the PrivateServer.
CONNECT/DISCONNECT event are bound to a remote address, not directly related to a specific VoIP account. A periodic background task analyses the SIP session logs and, when possible, reconcile them binding these events to a specific account.
Reconciliation is very useful while debugging SIP session for a specific user: clicking on username field will show a filtered list of SIP session events.
4.0.1.5 App log configuration
As the web interface is made from a Java application in Tomcat, then you can set the logging levels that are going to be written in the catalina.out log file.
Warning |
---|
This is an advanced feature usually useful only for debugging purposes. It's not recommended to change the default settings. |
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Data Retention Policy listSet Logging levels |
---|
AnchorName | dataapp_retentionlog_policy_listconf |
---|
|
Image Removed |
In Image Added |
In order to change a log level you have first to select a component of the appliance from the left drop-down menu (please check the
data_retention_policy_list | is shown the list of the available logs to be stored. What happens when you start the Data Retention on a log is that the system checks all the entries older than the date configured (let's say older than one year from the present day) and move them out the regular logging system to a compressed archive that could be later downloaded.). Then you can set a logging level from the right drop-down menu.When you're done just press the Submit button and the catalina.out log file would change its log level accordingly.
Anchor |
---|
| install_messages |
---|
| install_messages |
---|
|
4.0.1.6 Install messages Info |
---|
|
This log is available starting with the current version of PrivateServer. |
Install messages are one amongst the numerous means for installing PrivateGSM on the customers' mobile device.
What we accomplish sending an Installation message is to help the customer to find out the correct edition of PrivateGSM application (either Professional or Enterprise) and automatically install it.
If you choose to delete the archive, press the last column icon Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Data Retention Policy editorlist of the install messages sent |
---|
AnchorName | datainstall_retention_policy_editor |
---|
|
Image Removed |
Each log entry listed in
Xref |
---|
AnchorName | data_retention_policy_list |
---|
|
has an editor form as the one shown in Xref |
---|
AnchorName | data_retention_policy_editor |
---|
|
. Using the mentioned form you can:- 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: 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.5.2 Retrieve the Data Archives
As said in the previous paragraph (4.0.5.1), there are two left menu entries to manage the Data Retention feature (see Xref |
---|
AnchorName | data_retention_menus |
---|
|
). If you want to access to the stored archives just press the "Archived Data" link.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Data Archive List |
---|
AnchorName | data_archive_list |
---|
|
Image Removed |
The "Data Archive List" is shown in the page body (see
Xref |
---|
AnchorName | data_archive_list |
---|
|
). Each archive row shows its Name, its Creation Timestamp and its Size (all the columns are pretty self explaining).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 |
|
Image Added |
main features of the logs of the install messages are:
- Timestamp: the exact date & time when the message has been sent
- Account: to who the message has been sent to
- Platform: which mobile platform
- Variant: this could be either:
- ZRTP: this is the Professional Edition
- SDES: this is the Enterprise Edition
- Sent: if the message results to be effectively sent or if there were issues in sending it
- Sent by: the User who sent the Install Message.
- Virtual phone number: the number of the mobile device where the text has been sent to
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | details of one install message |
---|
AnchorName | install_msg_detail |
---|
|
Image Added |
Clicking on the Timestamp field it becomes possible to reveal details about each message. You can have an example in
Xref |
---|
AnchorName | install_msg_detail |
---|
|
. Info |
---|
|
Clicking on the Account field brings you straight to the Account's detail. |
The most important one among them is no doubt the Message link. That's because it's possible to use it in order to create a message to be sent by other means. This composed message would have the same validity of any text message sent to deliver an Install Message to the user.
Info |
---|
|
An example of a good use of this field in the day-by-day business is copying it into an email and sent it to the user, asking him to open the email on his mobile and then click on the link inside the email. In this way you has a service manager would have a perfect replacement for the text message as a mean for delivering the Install Message. |
Anchor |
---|
| provisioning_messages |
---|
| provisioning_messages |
---|
|
4.0.1.7 Provisioning messages Info |
---|
|
This log is available starting with the current version of PrivateServer. |
Provisioning messages are basically the mean for delivering the download URI of the provisioned configuration. Long story short: whenever you push an automatic activation by sending the provisioning message you're sending a text message that contains the URI to the user's configuration. Part of this configuration is created by the Provisioning Profile, part of it is taken by the Account configuration. Nevertheless, it's always a configuration file to be downloaded and then installed in your PrivateGSM.
Subtitle |
---|
Prefix | figure |
---|
SubtitleText | Log list of the provisioning messages |
---|
AnchorName | provisioning_messages_logs |
---|
|
Image Added |
Clicking on the Provisioning Messages link brings you to the logs list shown in
Xref |
---|
AnchorName | provisioning_messages_logs |
---|
|
. Here you have all the primary informations about the automatic activation performed:- the User who sent each provisioning message
- the timestamp pointing out when each message has been sent
- the Virtual phone number where the message has been sent to
- the status of the message: either it's been Consumed or not. This means if the customer has ever clicked on the link inside the text message
- the Account to which the message has been sent to
- if the text message has been Sent or not, meaning if any problem arose during the delivery and the text never left the server.
The confirmation pop-up windowdetail of provisioning message | AnchorName |
---|
|
popupareyou_sureImage Removed |
A confirmation is requested (see Image Added |
Clicking on the Timestamp field it becomes possible to reveal details about each message. You can have an example in
popupareyou_sure). If you approve the action then the archive is removed from both the list and the hard disk of the appliance. Warning |
---|
title | Point of no return action! |
---|
|
Please be aware that this action is not undoable! Once confirmed the deletion, the archive is lost forever! |
.
Info |
---|
|
Clicking on the Account field brings you straight to the Account's detail. |
Three are the contents shown in the detail form that are not present in the list above:
- The Message link
- The Token
- The Validity
The most important one among them is no doubt the Message link. That's because it's possible to use it in order to create a message to be sent by other means. This composed message would have the same validity of any text message sent to deliver a provisioning profile to the user.
Info |
---|
|
An example of a good use of this field in the day-by-day business is copying it into an email and sent it to the user, asking him to open the email on his mobile and then click on the link inside the email. In this way you has a service manager would have a perfect replacement for the text message as a mean for delivering the Provisioning Profile. |