Docs for all releases
Page History
...
This section describes shell tools required for management of the system at the very system level. All these tools are shipped with the VCS JeraSoft Billing distributive. You need to use SSH or direct access to the server in order to run any of these tools. Please notice that most of given tools require root access and show inline help when run without arguments.
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Attention To free our clients from confusion while trying to indicate a path to VCS JeraSoft Billing system, we introduce the <VCS_PATH> variable that differs depending on VCS the JeraSoft Billing version:
The example is as follows: |
...
- Before installation of the VCS JeraSoft Billing to check minimal hardware and software requirements. At this stage you may download the tool separately from the VCSJeraSoft Billing.
- After installation of the VCS JeraSoft Billing to check security recommendations. Usually you need to tune your firewall settings according to the VCS JeraSoft Billing First Steps.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Attention The tool checks only minimal requirements. Real hardware requirements highly depend on your traffic and deployment model. |
...
The tool is used for managing the VCS JeraSoft Billing Services. It allows to correctly start, stop, get status of the VCS JeraSoft Billing Services as RADIUS Server, SIP Server, Calculator, etc.
...
The tool should be run under root or vcs user. Service manager takes 2 arguments:
Argument | Description |
---|---|
<service-name> | Short name of the service. Run the tool without arguments to get list of the services at your system. |
<action> | Action to perform, one of the following:
|
Additionally you may pass next options:
Option | Description |
---|---|
--path=<path> | Specify the |
JeraSoft Billing location. Only if different from <VCS_PATH> | |
--user=<user> | Specify user the |
JeraSoft Billing runs under. Only if different from "vcs". |
For your convenience there are some examples below:
...
This command may require additional options:
Option | Description | Default |
---|---|---|
--ip=<ip> | IP Address of the Master server | none |
--ssh-port=<port> | SSH Port at the master server | 22 |
--data=<path> | PostgreSQL data path on master system | autodetect |
--vcs-path=<path> | Path to the |
JeraSoft Billing on Slave | <VCS_PATH> |
Master: Add new Slave
The command is run on the Master and used for:
...
This command may require additional options:
Option | Description | Default |
---|---|---|
--ip=<ip> | IP Address of the Slave server | none |
--ssh-port=<port> | SSH Port at the slave server | 22 |
--username=<login> | Login to the slave server | jerasupport |
--data=<path> | PostgreSQL data path on slave system | same as master |
--vcs-path=<path> | Path to the |
JeraSoft Billing on Slave | <VCS_PATH> | |
--role=<role> | Role of the secondary system. Could be [redundancy or reporting] | redundancy |
Slave: Promote to Master
The command is run on the Slave and used to promote current Slave to Master.
...