Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Subtitle
Prefixfig
SubtitleTextthe static logs menu
AnchorNamestatic_logs_menu

 

...

Image Added

As you can see in 

Xref
AnchorNamestatic_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 menu

Subtitle
Prefixfigure
SubtitleTextList of SIP Session Activities
AnchorNamesip logs
 

4.0.1.2

...

The SIP Sessions page show the activities each Account did with the server. 

Subtitle
Prefixfigure
SubtitleTextList of SIP Session Activities
AnchorNamesip logs

 

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 
Xref
AnchorNamesip logs
 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
Prefixfigure
SubtitleTextRegistered Account list
AnchorNameregistered account list

 

 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

Web Sessions

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  and you get a list as in figure above. It shows up the detail about the user (principal), the IP address used  used to connect, the date of each authentication and the outcome (Event Type).

4.0.4 Call Detailed Records

Info
titleNEW FEATURE

In this version the CDR has been completely rearrange to better show the valuable informations

...

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. 

...

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 The Disposition is  is very important because it tells you the exit code of each call. Possible codes are:

  1. ANSWERED: the call was taken by the callee
  2. NO_ANSWER: nobody picked up the phone to answer (mostly this is a time out code)
  3. BUSY: the callee refused the call
  4. 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:
  1. NO_ROUTE_DESTINATION: The callee is not reachable because of network issues.
  2. NORMAL_CLEARING: Call closed normally.
  3. USER_BUSY: The user is busy.
  4. NO_ANSWER: The callee didn't answer and the call was closed for timeout reason.
  5. CALL_REJECTED: The callee rejected the call, as by pressing the "hold" button.
  6. BEARERCAPABILITY_NOTAVAIL: The caller and the callee were using different security models that are not compatible.
  7. 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:
  1. CALL: Usual call between two persons
  2. 3-WAY: Usual call (as above) with an added person during the call
  3. CONFERENCE: Conference call
  4. 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.1.2 SIP Sessions

The SIP Sessions page show the activities each Account did with the server. 

Subtitle
Prefixfigure
SubtitleTextList of SIP Session Activities
AnchorNamesip logs

 

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 
Xref
AnchorNamesip logs
 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
Prefixfigure
SubtitleTextRegistered Account list
AnchorNameregistered account list

 

 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.5 Data Retention

Info
titleNEW FEATURE

The "Data Retention" feature has been introduced in the present version.

...