Difference between revisions of "FAQ"

From VoIPmonitor.org
Jump to navigation Jump to search
Line 32: Line 32:
 
Go to settings -> System configuration -> Advanced section -> Hide timezone information -> Enable and set to TRUE
 
Go to settings -> System configuration -> Advanced section -> Hide timezone information -> Enable and set to TRUE
  
 +
= Licensing =
 +
== How to know how many license channels do we need? ==
 +
Go to GUI -> Tools -> concurrent calls.
  
 +
== How does having multiple sensors affect the licensing? If I add a 2-3 remote sensors to the system, would they use the same license pool? ==
  
 
+
Central GUI calculates connected channels for the whole database but groups all calls legs as a single call so multiple legs are not counted twice etc.
 
 
  
  

Revision as of 10:18, 17 October 2014

Scalability

How does voipmonitor scale?

Read this: Scaling


How to clean old data and database?

Read this: Data Cleaning

CDR

What is the red small icon in CDR?

Cdrcolumnsredflag.png The red icon in those columns signalize which side sends BYE first.

How to interpret two charts in the cdr detail?

See this: Graph cheat sheet

Supported architectures

What architectures are tested?

x86 32 and 64, ARMv5 - (if you have error with missing "__sync_fetch_and_sub_8" you have to upgrade GCC compiler to version 4.8)

Configuration

Why I do not see sip packets other then port 5060?

Voipmonitor sniffer by default sniffs packets only on port 5060 from or to. If you need to sniff more SIP ports you need to specify it in configuration. Please see this: Sniffer_configuration#sipport

How to disable timezone check

Go to settings -> System configuration -> Advanced section -> Hide timezone information -> Enable and set to TRUE

Licensing

How to know how many license channels do we need?

Go to GUI -> Tools -> concurrent calls.

How does having multiple sensors affect the licensing? If I add a 2-3 remote sensors to the system, would they use the same license pool?

Central GUI calculates connected channels for the whole database but groups all calls legs as a single call so multiple legs are not counted twice etc.
















































.