Kolmisoft Wiki - User contributions [en]

API Configuration

2015-10-07T07:29:42Z

Renatas:

Go to '''SETTINGS –> Setup –> Settings –> API''' tab

[[File:Settings api.png]]

* '''Allow API globally''' – should we enable API globaly? When it is disabled, all settings below are also disabled and not editable.
* '''Allow GET API''' – should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
* '''Allow Resellers to use Admin Tariffs''' – It is possible to let Resellers use Admins Tariffs. With [[MOR API user details update]] Resellers can set Admins Wholesale or Retail Tariffs for their users. With [[MOR API rate get]] they can get Admins Rates. Using [[MOR API tariff rates get]] Resellers can get Admins Tariffs.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''XML API Extension''' – send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you.
* '''Allow API Login Redirect''' – if login is successful the customer will be redirected to MOR billing Main site.
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
* '''Uniquehash''' – admin's unique hash. Reseller can see it by going to '''SETTINGS''' -> '''Registration'''.
'''NOTE''' that MOR does not allow you to enable '''Allow API''' if '''API Secret Key''' is not entered. In such case you will get a message '''Invalid API secret key'''. '''Enter API Secret Key''' in order to fix this.
 

= From Reseller/RSPRO =

Reseller can use API functionality if '''Allow API globally''' in Admins settings is checked.
Reseller has three options in his API Settings (Settings –> API tab):
* '''Allow API''' – turns on API functionality.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
'''NOTE''' that Reseller also must enter '''API Secret Key''' if he want to use API functionality.
 
= See also =

* [[MOR API]]

API Configuration

2015-10-07T07:25:31Z

Renatas:

Go to '''SETTINGS –> Setup –> Settings –> API''' tab

[[File:Settings api.png]]

* '''Allow API globally''' – should we enable API globaly? When it is disabled, all settings below are also disabled and not editable.
* '''Allow GET API''' – should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
* '''Allow Resellers to use Admin Tariffs''' – It is possible to let Resellers use Admins Tariffs. With [[MOR API user details update]] Resellers can set Admins Wholesale or Retail Tariffs for their users. With [[MOR API rate get]] they can get Admins Rates. Using [[MOR API tariff rates get]] Resellers can get Admins Tariffs.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''XML API Extension''' – send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you.
* '''Allow API Login Redirect''' – if login is successful the customer will be redirected to MOR billing Main site.
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
* '''Uniquehash''' – admin's unique hash. Reseller can see it by going to '''SETTINGS''' -> '''Registration'''.
'''NOTE''' that MOR does not allow you to enable '''Allow API''' if '''API Secret Key''' is not entered. In such case you will get a message '''Invalid API secret key'''. '''Enter API Secret Key''' in order to fix this.
 

=From Reseller/RSPRO =

Reseller can use API functionality if '''Allow API globally''' in Admins settings is checked.
Reseller has three options in his API Settings (Settings –> API tab):
* '''Allow API''' – turns on API functionality.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
'''NOTE''' that Reseller also must enter '''API Secret Key''' if he want to use API functionality.
 
= See also =

* [[MOR API]]

API Configuration

2015-10-07T07:06:13Z

Renatas:

Go to '''SETTINGS –> Setup –> Settings –> API''' tab

[[File:Settings api.png]]

* '''Allow API globally''' – should we enable API globally? When it is disabled, all settings below are also disabled and not editable.
* '''Allow GET API''' – should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
* '''Allow Resellers to use Admin Tariffs''' – It is possible to let Resellers use Admins Tariffs. With [[MOR API user details update]] Resellers can set Admins Wholesale or Retail Tariffs for their users. With [[MOR API rate get]] they can get Admins Rates. Using [[MOR API tariff rates get]] Resellers can get Admins Tariffs.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''XML API Extension''' – send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you.
* '''Allow API Login Redirect''' – if login is successful the customer will be redirected to MOR billing Main site.
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
* '''Uniquehash''' – admin's unique hash. Reseller can see it by going to '''SETTINGS''' -> '''Registration'''.
'''NOTE''' that MOR does not allow you to enable '''Allow API''' if '''API Secret Key''' is not entered. In such case you will get a message '''Invalid API secret key'''. '''Enter API Secret Key''' in order to fix this.
 

=From Reseller/RSPRO =

Reseller can use API functionality if '''Allow API globally''' in Admins settings is checked.
Reseller has three options in his API Settings (Settings –> API tab):
* '''Allow API''' – turns on API functionality.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
'''NOTE''' that Reseller also must enter '''API Secret Key''' if he want to use API functionality.
 
= See also =

* [[MOR API]]

API Configuration

2015-10-07T06:52:53Z

Renatas:

Go to '''SETTINGS –> Setup –> Settings –> API''' tab

[[File:Settings api.png]]

* '''Allow API globally''' – should we enable API globaly? When it is disabled, all settings below are also disabled and not editable.
* '''Allow GET API''' – should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
* '''Allow Resellers to use Admin Tariffs''' – It is possible to let Resellers use Admins Tariffs. With [[MOR API user details update]] Resellers can set Admins Wholesale or Retail Tariffs for their users. With [[MOR API rate get]] they can get Admins Rates. Using [[MOR API tariff rates get]] Resellers can get Admins Tariffs.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''XML API Extension''' – send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you.
* '''Allow API Login Redirect''' – if login is successful the customer will be redirected to MOR billing Main site.
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
* '''Uniquehash''' – admin's unique hash. Reseller can see it by going to '''SETTINGS''' -> '''Registration'''.

'''NOTE''' that MOR does not allow you to enable '''Allow API''' if '''API Secret Key''' is not entered. In such case you will get a message '''Invalid API secret key'''. '''Enter API Secret Key''' in order to fix this.
 
=From Reseller/RSPRO =

Reseller can use API functionality if '''Allow API globally''' in Admins settings is checked.

Reseller has three options in his API Settings (Settings –> API tab):
* '''Allow API''' – turns on API functionality.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.

'''NOTE''' that Reseller also must enter '''API Secret Key''' if he want to use API functionality.
 
= See also =

* [[MOR API]]

M4 Sometimes users are blocked automatically

2015-08-21T08:08:05Z

Renatas:

Users are blocked by alert. To check which alert is blocking.
Go to alert list location : http://xxx.xxx.xxx.xxx/billing/alerts/list.
Replace xxx.xxx.xxx.xxx with your servers IP adress).

 

[[File:Example.png]]

 

If this Alert is not needed for you, you can disable or delete it.
You can also check why Users are blocked using Action Log (Reports -> Action Log).

M4 Call Count Bigger That What We Can Process

2015-08-21T07:54:42Z

Renatas:

You can set max concurrent calls to user under which account Termination Points are created (it is

LIME user used as example). You can also set limit (capacity) in each TP, in this case limit will be applied

only to that particular TP.

 

[[File:call limit M2.png]]

 

 

[[File:TP capacity M2.png]]

M4 Sometimes users are blocked automatically

2015-08-21T07:54:10Z

Renatas:

Users are blocked by alert. To check which alert is blocking.
Go to alert list location : http://xxxx.xxxx.xxxx.xxxx/billing/alerts/list.
Replace xxxx.xxxx.xxxx.xxxx with your servers IP adress).

 

[[File:Example.png]]

 

If this Alert is not needed for you, you can disable or delete it.
You can also check why Users are blocked using Action Log (Reports -> Action Log).

File:Call limit M2.png

2015-08-21T07:48:06Z

Renatas: uploaded a new version of "File:Call limit M2.png"

File:TP capacity M2.png

2015-08-21T07:46:46Z

Renatas: uploaded a new version of "File:TP capacity M2.png"

M4 Call Count Bigger That What We Can Process

2015-08-21T07:43:35Z

Renatas:

You can set max concurrent calls to user under which account Termination Points are created (it is

LIME user used as example). You can also set limit (capacity) in each TP, in this case limit will be applied

only to that particular TP.

 

[[File:call limit M2.png]]

 

 

[[File:TP capacity M2.png]]

File:TP capacity M2.png

2015-08-21T07:42:07Z

Renatas:

File:Call limit M2.png

2015-08-21T07:41:16Z

Renatas:

M4 Call Count Bigger That What We Can Process

2015-08-21T07:41:01Z

Renatas: Created page with 'You can set max concurrent calls to user under which account Termination Points are created (it is LIME user used as example). You can also set limit (capacity) in each TP, in t…'

You can set max concurrent calls to user under which account Termination Points are created (it is

LIME user used as example). You can also set limit (capacity) in each TP, in this case limit will be applied

only to that particular TP.

 

[[File:call limit M2.png]]

 

 

[[File:TP capacity M2. png]]

M4 Sometimes users are blocked automatically

2015-08-21T07:34:44Z

Renatas:

Users are blocked by alert. To check which alert is blocking.
Go to alert list location : http://xxxx.xxxx.xxxx.xxxx/billing/alerts/list.
Replace xxxx.xxxx.xxxx.xxxx with your servers IP adress).

 

[[File:Example.png]]

 

If this Alert is not needed for you, you can disable or delete it.
You can also check why Users are blocked using Action Log (Reports -> Action Log).

File:Example.png

2015-08-21T07:32:57Z

Renatas: uploaded a new version of "File:Example.png"

M4 Sometimes users are blocked automatically

2015-08-21T07:31:01Z

Renatas:

Users are blocked by alert. To check which alert is blocking.
Go to alert list location : http://xxxx.xxxx.xxxx.xxxx/billing/alerts/list. (Replace xxxx.xxxx.xxxx.xxxx with your servers IP adress).
[[File:Example.png]]
If this Alert is not needed for you, you can disable or delete it.
You can also check why Users are blocked using Action Log (Reports -> Action Log).

File:Example.png

2015-08-21T07:29:23Z

Renatas:

M4 Sometimes users are blocked automatically

2015-08-21T07:28:22Z

Renatas: Created page with 'Users are blocked by alert. To check which alert is blocking. Go to alert list location : http://xxxx.xxxx.xxxx.xxxx/billing/alerts/list. (Replace xxxx.xxxx.xxxx.xxxx with your …'

Users are blocked by alert. To check which alert is blocking.
Go to alert list location : http://xxxx.xxxx.xxxx.xxxx/billing/alerts/list. (Replace xxxx.xxxx.xxxx.xxxx with your servers IP adress).
[[File:Example.jpg]]
If this Alert is not needed for you, you can disable or delete it.
You can also check why Users are blocked using Action Log (Reports -> Action Log).

M4 Switch Manual

2015-08-21T07:15:08Z

Renatas:

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =
* [[M2 Switch | Introduction]]
* [[M2 Switch Stress Test | Stress Test]]
* [[M2 Roadmap| Roadmap]]
* [[M2 Network Architecture | Network Architecture]]
* [[M2 Supported Codecs | Supported Codecs]]

 

= Configuration =
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Move MOR Database to M2]]

 

= Routing =
* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 tech_prefix_rules | TP Technical Prefix Rules]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Dial Peers | Dial Peers (DP) ]]

 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2 Rates | Rates]]
** [[M2 Rate Notification | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]

 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]

 

= Reporting =
Reports, Stats

* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
 

 

= I Have a Problem =

* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =
* [[M2 User Dashboard | Dashboard]]

 

= Tutorials =
* [[M2 How to make first call | How to make first call]]

M4 Switch Manual

2015-08-21T07:11:31Z

Renatas:

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =
* [[M2 Switch | Introduction]]
* [[M2 Switch Stress Test | Stress Test]]
* [[M2 Roadmap| Roadmap]]
* [[M2 Network Architecture | Network Architecture]]
* [[M2 Supported Codecs | Supported Codecs]]

 

= Configuration =
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Move MOR Database to M2]]

 

= Routing =
* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 tech_prefix_rules | TP Technical Prefix Rules]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Dial Peers | Dial Peers (DP) ]]

 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2 Rates | Rates]]
** [[M2 Rate Notification | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]

 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]

 

= Reporting =
Reports, Stats

* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
 

 

= I Have a Problem =

* [[call count bigger that what we can process]]
* [[sometimes users blocked automatically]]
 

= User Portal =
* [[M2 User Dashboard | Dashboard]]

 

= Tutorials =
* [[M2 How to make first call | How to make first call]]

End IVR Type

2015-08-20T08:51:57Z

Renatas:

=Description=

This option allows to select which End IVR to use for Calling Card Dial-Plan.

[[File:End_ivr_type2.png]]

 
== End IVR #1 ==

This is default IVR.

When call ends or caller presses * to terminate call, he comes into this IVR.

Here he hears message: "Press 1 to dial new destination, press 2 to dial same destination, press 3 to check your balance, press 4 to use new card"

When user presses some button [1,2,3,4,5] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card
5 - Topup a cards balance with another card balance

More information about card topup functionality can be found [[Card TopUp | here]]

'''NOTE:''' This End IVR is dedicated only to Calling Card Dial plan.

In Authorization by PIN/ANI End IVR#1 options are these:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance

 

== End IVR #2 ==

This type of IVR allows to enter new Destination or redial old one by pressing 1#.

User can enter destination and # to dial to it, or he can enter 1# and then system will redial old destination.

 

== End IVR #3 ==

This IVR is just a hangup. E.g. call will end at once using this IVR and no further actions will be possible.

'''NOTE:''' This End IVR is dedicated only to Calling Card Dial plan.

In Authorization by PIN/ANI the End IVR#3 forwards Call to End IVR#1.

 

== End IVR #4 ==

When user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance

 
== End IVR #5 ==

Menu for Resellers mostly which is used to Topup cards for their clients.

When user presses some button [1,2,3,4,5,6,7] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance
5 - Topup a cards balance with another card balance with PIN
6 - Topup a cards balance with another card balance with CLI
7 - Topup a cards balance with another card balance with NUM + PIN

These options are used to increase Calling Card A balance with Calling Card B money:

5 - Topup a cards balance with another card balance with PIN .This option asks you to enter PIN number of card B.

6 - Topup a cards balance with another card balance with CLI.

Is authenticated by caller ID. This option asks you to enter phone number of card B.

7 - Topup a cards balance with another card balance with NUM + PIN.

Is authenticated by top up card number and PIN. This option asks you to

enter card's number and PIN of the card B.

 
== End IVR #6 ==

This End IVR allows the user to topup a card's balance with another card('''Action #5''') by pressing '*' instead of dialing a destination. After toping up the card, the user will be prompted to dial a destination again.
 
Once the call is terminated, the user will hear the same menu options as with End IVR #1:

When the user presses some button [1,2,3,4,5] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card
5 - Topup a cards balance with another card

 

== End IVR #7 ==

This End IVR allows the user to control whether his calling card is authorized by pin/number or automatically by CallerID number. This is useful when users want to temporarily disable automatic authorization for security reasons.

Note: Pinless dialing should be enabled in dial plan.

When the user presses some button [1,2,3,4] he will be able to do such actions:

1 - Save CallerID number
2 - Clear saved CallerID number
3 - Can dial same old destination (redial)
4 - Can enter new destination

 

== End IVR #8 ==

This End IVR allows to clear saved CallerID number and change card.

When the user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Clear saved CallerID number
4 - Can enter new PIN to use new Card

 

== End IVR #9 ==

End IVR #9 is very similar to End IVR #5. The difference between End IVR #9 and End IVR #5 is that End IVR #9 allows to play custom sound files in card topup.

Custom files are these:

cc_enter_pin_to_topup.wav - played when user is asked to enter pin of a card to which balance should be added.
cc_enter_pin_to_take_topup.wav - played when user is asked to enter pin of a card from which balance should be deducted to primary card.

these files should be prerecorded and uploaded to /var/lib/asterisk/sounds/mor/ivr_voices/en (if language is not english, then instead of "en" there should be directory "ru" or any other language).

Also, End IVR #9 skips topup intro message.

When user presses some button [1,2,3,4,5,6,7] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance
5 - Topup a cards balance with another card balance with PIN
6 - Topup a cards balance with another card balance with CLI
7 - Topup a cards balance with another card balance with NUM + PIN

 

== End IVR #10 ==

End IVR #10 is the same as IVR #1 except it does not allow to topup calling cards.

When user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card

 

= See also =

* [[Authorization_by_ANI#End_IVR|End IVRs for Authorization by ANI dial plan]]

End IVR Type

2015-08-20T08:50:11Z

Renatas:

=Description=

This option allows to select which End IVR to use for Calling Card Dial-Plan.

[[File:End_ivr_type2.png]]

 
== End IVR #1 ==

This is default IVR.

When call ends or caller presses * to terminate call, he comes into this IVR.

Here he hears message: "Press 1 to dial new destination, press 2 to dial same destination, press 3 to check your balance, press 4 to use new card"

When user presses some button [1,2,3,4,5] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card
5 - Topup a cards balance with another card balance

More information about card topup functionality can be found [[Card TopUp | here]]

'''NOTE:''' This End IVR is dedicated only to Calling Card Dial plan.

In Authorization by PIN/ANI End IVR#1 options are these:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance

 

== End IVR #2 ==

This type of IVR allows to enter new Destination or redial old one by pressing 1#.

User can enter destination and # to dial to it, or he can enter 1# and then system will redial old destination.

 

== End IVR #3 ==

This IVR is just a hangup. E.g. call will end at once using this IVR and no further actions will be possible.

'''NOTE:''' This End IVR is dedicated only to Calling Card Dial plan.

In Authorization by PIN/ANI the End IVR#3 forwards Call to End IVR#1.

 

== End IVR #4 ==

When user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance

 
== End IVR #5 ==

Menu for Resellers mostly which is used to Topup cards for their clients.

When user presses some button [1,2,3,4,5,6,7] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance
5 - Topup a cards balance with another card balance with PIN
6 - Topup a cards balance with another card balance with CLI
7 - Topup a cards balance with another card balance with NUM + PIN

These options are used to increase Calling Card A balance with Calling Card B money:
5 - Topup a cards balance with another card balance with PIN .This option asks you to enter PIN number of card B.
6 - Topup a cards balance with another card balance with CLI. Is authenticated by caller ID. This option asks you to enter phone number of card B.
7 - Topup a cards balance with another card balance with NUM + PIN. Is authenticated by top up card number and PIN. This option asks you to enter card's number and PIN of the card B.

 
== End IVR #6 ==

This End IVR allows the user to topup a card's balance with another card('''Action #5''') by pressing '*' instead of dialing a destination. After toping up the card, the user will be prompted to dial a destination again.
 
Once the call is terminated, the user will hear the same menu options as with End IVR #1:

When the user presses some button [1,2,3,4,5] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card
5 - Topup a cards balance with another card

 

== End IVR #7 ==

This End IVR allows the user to control whether his calling card is authorized by pin/number or automatically by CallerID number. This is useful when users want to temporarily disable automatic authorization for security reasons.

Note: Pinless dialing should be enabled in dial plan.

When the user presses some button [1,2,3,4] he will be able to do such actions:

1 - Save CallerID number
2 - Clear saved CallerID number
3 - Can dial same old destination (redial)
4 - Can enter new destination

 

== End IVR #8 ==

This End IVR allows to clear saved CallerID number and change card.

When the user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Clear saved CallerID number
4 - Can enter new PIN to use new Card

 

== End IVR #9 ==

End IVR #9 is very similar to End IVR #5. The difference between End IVR #9 and End IVR #5 is that End IVR #9 allows to play custom sound files in card topup.

Custom files are these:

cc_enter_pin_to_topup.wav - played when user is asked to enter pin of a card to which balance should be added.
cc_enter_pin_to_take_topup.wav - played when user is asked to enter pin of a card from which balance should be deducted to primary card.

these files should be prerecorded and uploaded to /var/lib/asterisk/sounds/mor/ivr_voices/en (if language is not english, then instead of "en" there should be directory "ru" or any other language).

Also, End IVR #9 skips topup intro message.

When user presses some button [1,2,3,4,5,6,7] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can enter new PIN to use new Card
4 - Topup a cards balance with another card balance
5 - Topup a cards balance with another card balance with PIN
6 - Topup a cards balance with another card balance with CLI
7 - Topup a cards balance with another card balance with NUM + PIN

 

== End IVR #10 ==

End IVR #10 is the same as IVR #1 except it does not allow to topup calling cards.

When user presses some button [1,2,3,4] he will be able to do such actions:

1 - Can enter new destination
2 - Can dial same old destination (redial)
3 - Can hear his balance
4 - Can enter new PIN to use new Card

 

= See also =

* [[Authorization_by_ANI#End_IVR|End IVRs for Authorization by ANI dial plan]]