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.
As you can see in all these logs are grouped under the "LOGGING" label into the main menu.
The Auditing page shows any change to the configuration performed via web console.
As shown above in , we can collect several informations:
Timestamp: the exact time the event happened.
Please remember that the timestamp is related to the appliance's time configuration. It's local time which gets reported. |
These informations can be used for security checks as for post-issue analysis.
In the web sessions it's possible to read the list of all the access made to the web console.
Just click on the Web Sessions entry in the main menu and you get a list as in figure . Fields shown are:
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". |
Here follows a list of all the event types logged in this table:
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.
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:
The Disposition is very important because it tells you the exit code of each call. Possible codes are:
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). |
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. |
The SIP Sessions page show the activities each Account did with the server.
|
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.
In you can read that a NETWORK_ERROR has caused the DISCONNECT event for one user. |
The Event column lists the SIP events:
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.
This is an advanced feature usually useful only for debugging purposes. It's not recommended to change the default settings. |
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 ). 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.
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.
To make the Install messages work fine you have to configure the Application download URL. |
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.
main features of the logs of the install messages are:
Clicking on the Timestamp field it becomes possible to reveal details about each message. You can have an example in .
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.
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. |
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.
Clicking on the Provisioning Messages link brings you to the logs list shown in . Here you have all the primary informations about the automatic activation performed:
Clicking on the Timestamp field it becomes possible to reveal details about each message. You can have an example in .
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 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.
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. |