uppal/cgrates
1
0
Fork 1
mirror of https://github.com/cgrates/cgrates.git synced 2026-02-11 18:16:24 +05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #126 from foehn/master

Browse Source 
Fix account command in the docs
This commit is contained in:
Dan Christian Bogos
2015-07-29 11:19:10 +03:00
parent 4d7c49dba3 88679ef858
commit 13d77363f5
1 changed files with 17 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
docs/tut_cgrates_usage.rst
View File

@@ -4,9 +4,11 @@
Loading **CGRateS** Tariff Plans
--------------------------------
Before proceeding to this step, you should have **CGRateS** installed and started with custom configuration, depending on the tutorial you have followed.
Before proceeding to this step, you should have **CGRateS** installed and
started with custom configuration, depending on the tutorial you have followed.
For our tutorial we load again prepared data out of shared folder, containing following rules:
For our tutorial we load again prepared data out of shared folder, containing
following rules:
- Create the necessary timings (always, asap, peak, offpeak).
- Configure 3 destinations (1002, 1003 and 10 used as catch all rule).
@@ -68,11 +70,11 @@ To verify that all actions successfully performed, we use following *cgr-console
::
cgr-console 'account Tenant="cgrates.org" Account="1001"'
cgr-console 'account Tenant="cgrates.org" Account="1002"'
cgr-console 'account Tenant="cgrates.org" Account="1003"'
cgr-console 'account Tenant="cgrates.org" Account="1004"'
cgr-console 'account Tenant="cgrates.org" Account="1005"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1001"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1002"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1003"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1004"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1005"]'
- Query call costs so we can see our calls will have expected costs (final cost will result as sum of *ConnectFee* and *Cost* fields):
@@ -108,7 +110,7 @@ Check that 1001 balance is properly deducted, during the call, and moreover cons
::
cgr-console 'account Tenant="cgrates.org" Account="1001"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1001"]'
1002 -> 1001
@@ -120,7 +122,7 @@ To check that we had debits we use again console command, this time not during t
::
cgr-console 'account Tenant="cgrates.org" Account="1002"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1002"]'
1003 -> 1001
@@ -132,7 +134,7 @@ To check that there are no debits during or by the end of the call, but when the
::
cgr-console 'account Tenant="cgrates.org" Account="1003"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1003"]'
1004 -> 1001
@@ -150,8 +152,8 @@ Check that 1001 balance is properly debitted, during the call, and moreover cons
::
cgr-console 'account Tenant="cgrates.org" Account="1006"'
cgr-console 'account Tenant="cgrates.org" Account="1001"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1006"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1001"]'
1007 -> 1002
@@ -163,8 +165,8 @@ Check that call can proceed even if 1007 has no units left into his own balances
::
cgr-console 'account Tenant="cgrates.org" Account="1007"'
cgr-console 'account Tenant="cgrates.org" Account="1001"'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1007"]'
cgr-console 'accounts Tenant="cgrates.org" AccountIds=["1001"]'
CDR Exporting
@@ -192,4 +194,4 @@ To verify this mechanism simply add some random units into one account's balance
cgr-console 'balance_set Tenant="cgrates.org" Account="1001" Direction="*out" Value=101'
tail -f /var/log/syslog -n 20
On the CDRs side we will be able to integrate CdrStats monitors as part of our Fraud Detection system (eg: the increase of average cost for 1001 and 1002 accounts will signal us abnormalities, hence we will be notified via syslog).
On the CDRs side we will be able to integrate CdrStats monitors as part of our Fraud Detection system (eg: the increase of average cost for 1001 and 1002 accounts will signal us abnormalities, hence we will be notified via syslog).