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 provide support. As you can see in all these logs are grouped under the "LOGGING" label into the main menu. Security EventsSince 14.1 version Security Events has been added to PrivateServer logging. This log category lists every event captured by our Security Information and Event Management (SIEM) interface, which has been introduced in that version. SIEM interface catches and rewrites SIEM style events that are currently managed in underlying event log layers such the one described just after present paragraph. This means that each event listed under this section is also present in a specific on but shown in different format, often raw one. SIEM formatted events are instead all present here. Just clicking on Timestamp you get single event details as shown in . You can tell we're dealing with SIEM formatted log just by reading Details part. Consider that we're talking of a generic SIEM format that can be more refined and adapted for being processed by external systems. PrivateServer can generate events in CEF format, compatible with HP Arcsight product. System EventsSystem Events list shows all events occurred to PrivateServer but not directly intercepted by Web appliance because triggered out of its scope. Examples are:
Clicking on Timestamp part of the log shows you System Event's details as show in . AuditingThe Auditing page shows any change to the configuration performed via web console. As shown above in , we can collect several informations:
These informations can be used for security checks as for post-issue analysis. Web SessionsIn 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:
Event TypesHere follows a list of all the event types logged in this table:
Call Detailed RecordsDespite 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:
Relevant fields in CDRThe Disposition is very important because it tells you the exit code of each call. Possible codes are:
The Hangup Cause describes in details what caused the hangup. Possible causes are:
The Call Type 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:
The Call id 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).
MessagesThe Messages page lists Secure Messages managed by PrivateServer.
The list represent the log of Secure Messages transaction happened, so that it's showed:
Each Secure Message managed by PrivateServer is represented on one single line, as shown in . Secure Message StatusEach Message walks through different statuses, each one representing a milestone towards its delivery:
There are statuses describing issues raised during the delivery, such as:
SIP SessionsThe 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. The Event column lists the SIP events:
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. Install messagesInstall 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. 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 .
Provisioning messagesProvisioning 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 .
Three are the contents shown in the detail form that are not present in the list above:
|