Kolmisoft Wiki - User contributions [en]

Setting up https secure connection

2015-05-07T06:25:40Z

Mantas svelnys:

= Installing SSL =
For an SSL encrypted web server you will need a few things. Depending on your install you may or may not have OpenSSL and mod_ssl, Apache's interface to OpenSSL.

yum -y install mod_ssl openssl

Generate private key
openssl genrsa -out ca.key 2048

Generate CSR
openssl req -new -key ca.key -out ca.csr

Generate Self Signed Key
openssl x509 -req -days 365 -in ca.csr -signkey ca.key -out ca.crt

Move the files to the correct locations
mv ca.crt /etc/pki/tls/certs
mv ca.key /etc/pki/tls/private/ca.key
mv ca.csr /etc/pki/tls/private/ca.csr

Then we need to update the Apache SSL configuration file ( /etc/httpd/conf.d/ssl.conf ). Change the paths to match where the Key file is stored. If you've used the method above it will be.

SSLCertificateFile /etc/pki/tls/certs/ca.crt

Then set the correct path for the Certificate Key File a few lines below. If you've followed the instructions above it is:
SSLCertificateKeyFile /etc/pki/tls/private/ca.key

Quit and save the file and then restart Apache
/etc/init.d/httpd restart

Source: http://shapeshed.com/journal/setting_up_mod_ssl_on_apache_centos_52/

Troubleshooting:

If you cannot access GUI, try following commands:
chown apache.apache /var/log/httpd
service httpd restart

== Allow only https ==
If you would like your users to be automatically redirected to secure connection (https), add the line to /etc/httpd/conf.d/mor.conf so it would look like:

<VirtualHost *:80>
DocumentRoot /var/www/html
<Directory /var/www/html>
Allow from all
</Directory>
RailsBaseURI /billing
<Directory /var/www/html/billing>
Options -MultiViews
</Directory>
RailsEnv production
Redirect permanent / https://www.example.com/ #Add this one. Put your hostname instead of www.example.com
</VirtualHost>

 

== Important notes ==
* When you disable http access and allow https only - please make sure that you change URL in various crontabs used by mor and located in /etc/cron.d/*
 

== ERROR: When directory structure is visible ==

That means incorrect configuration in /etc/httpd/conf.d/ssl.conf

Make sure your file looks like this:

<pre>
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443

##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##

# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout 300

# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
SSLMutex default

# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the
# SSL library. The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names. NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host, inherited from global configuration
DocumentRoot "/var/www/html/billing" #ADD THIS
#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on

# SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect. Disable SSLv2 access by default:
SSLProtocol all -SSLv2

# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/localhost.crt

# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file. Keep in mind that if
# you've both a RSA and a DSA private key you can configure
# both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key

# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt

# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10

# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
SSLOptions +StdEnvVars
</Directory>

# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0

# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

DocumentRoot /var/www/html #ADD THIS
<Directory /var/www/html> #ADD THIS
Allow from all #ADD THIS
</Directory> #ADD THIS
RailsBaseURI /billing #ADD THIS
<Directory /var/www/html/billing> #ADD THIS
Options -MultiViews #ADD THIS
</Directory> #ADD THIS
ServerName my.domain.com #ADD THIS
RedirectMatch permanent ^/$ https://my.domain.com/billing/callc/login #ADD THIS change my.domain.com to proper domain

</VirtualHost>

</pre>

If you are implementing SSL into MOR please remove m2.conf file

rm -rf /etc/httpd/conf.d/m2.conf

Restart Apache after changing this file.

I have a problem with GUI

2015-05-01T10:04:38Z

Mantas svelnys:

What problem do you have?

* [[Access Denied]]
* [[GUI does not open]]
* [[GUI opens very slowly]]
* [[Time in GUI is displayed incorrectly]]
* [[Global_Settings | How to remove Kolmisoft branding from MOR]]
* [[Accountant cannot see assigned permission objects]]
* [[I have a problem with Google Maps]]
* [[I want to hide "I want to" help links]]
* [[I cannot see Menu]]
* [[MOR_integration|I want to integrate MOR]]
* [[I see Apache test on Start page]]
* [[I see "Don't be so smart" error message on some pages]]
* [[Custom_Reseller_Login_page_LOGO|Where can I find reseller's website address?]]
* [[Reseller's LOGO changes after GUI update]]
* [[Can I have a hostname for MOR]]
* [[GUI update blocks user]]
* [[GUI time zone]]
* [[Bad group name apache FAILED]]
* [[Internal Error]]
* [[How to change admin's password]]
* [[Global_Settings | I want to display more information on the start page]]
* [[I have to wait to login again after 3 unsuccesful tries]]
* [[I have changed User password and still able to connect]]
* [[Webphone is not shown]]
 
= See also =
* [[Main_Page#GUI_2 | GUI Problems]]

I have a problem with GUI

2015-05-01T10:04:18Z

Mantas svelnys:

What problem do you have?

* [[Access Denied]]
* [[GUI does not open]]
* [[GUI opens very slowly]]
* [[Time in GUI is displayed incorrectly]]
* [[Global_Settings | How to remove Kolmisoft branding from MOR]]
* [[Accountant cannot see assigned permission objects]]
* [[I have a problem with Google Maps]]
* [[I want to hide "I want to" help links]]
* [[I cannot see Menu]]
* [[MOR_integration|I want to integrate MOR]]
* [[I see Apache test on Start page]]
* [[I see "Don't be so smart" error message on some pages]]
* [[Custom_Reseller_Login_page_LOGO|Where can I find reseller's website address?]]
* [[Reseller's LOGO changes after GUI update]]
* [[Can I have a hostname for MOR]]
* [[GUI update blocks user]]
* [[GUI time zone]]
* [[Bad group name apache FAILED]]
* [[Internal Error]]
* [[How to change admin's password]]
* [[Global_Settings | I want to display more information on the start page]]
* [[I have to wait to login again after 3 unsuccesful tries]]
* [[I have changed User password and he still able to connect]]
* [[Webphone is not shown]]
 
= See also =
* [[Main_Page#GUI_2 | GUI Problems]]

I have changed User password and still able to connect

2015-05-01T10:03:44Z

Mantas svelnys: Created page with 'New password will become valid when user re-login to the system. Until then connection data is store in browsers cache and server. If you want to force user to enter new passwor…'

New password will become valid when user re-login to the system. Until then connection data is store in browsers cache and server.

If you want to force user to enter new password you should clear sessions from server.

In order to do that:

1. Connect to server via SSH

2. Enter commands:

rm -rf /dev/shm/sessions/*
service httpd restart

After that your customer will be kicked-out from GUI and will need to enter password.

I have a problem with GUI

2015-05-01T10:00:54Z

Mantas svelnys:

Transfers with MOR

2015-04-17T10:15:14Z

Mantas svelnys:

Transfers by default are not available in MOR because Asterisk cannot guarantee correct CDRs with Transfers.

In other words - it is possible to dial for free using Transfers with Asterisk (MOR).

----

If you really want transfers and do not care about possible loss, here is the way to enable them:

In file /etc/asterisk/sip.conf

change line

allowtransfer = no

to

allowtransfer = yes

Then in file /etc/asterisk/mor.conf add line (starting from MOR X6):

transfer_billing_enabled = 1

And reload Asterisk.
'''Use it at your own risk!'''

Different phones may have different transfer implementations therefore transfer billing depends on how phones initiate transfer. Only authenticated users can transfer calls.

These are tested scenarios with transfers (tested with ATTENDED and BLIND transfers on MOR X6). 

'''Scenario #1'''

''Prefix 370, rate 0.1''

Local user A calls outside number (prefix 370) and after 30 seconds user A transfers call to local user B. User B talks for another 20 seconds and hangs up. User A will be billed for 50 seconds (30 seconds before transfer and 20 seconds after transfer).

User price = (50*0.1)/60 = 0.0833

'''Scenario #2'''

''Prefix 370, rate 0.1''
''Prefix 371, rate 0.3''

Local user A calls outside number (prefix 370) and after 30 seconds user A transfers call to another outside number (prefix 371). After 40 seconds call ends. User A will be billed for 110 seconds (70 seconds to prefix 370 (30 seconds before transfer and 40 seconds after transfer) and 40 seconds to prefix 371).

User price = (70*0.1)/60 + (40*0.3)/60 = 0.3167

'''Scenario #3'''

''Prefix 370, rate 0.1''

Local user A calls local user B and after 30 seconds user A transfers call to outside number (prefix 370). User B talks for another 20 seconds. User A will be billed for 20 seconds.

User price = (20*0.1)/60 = 0.0333

'''Scenario #4 (BLIND transfers only)'''

''Prefix 370, rate 0.1''

Local user A calls local user B and after 30 seconds user B transfers call to outside number (prefix 370). User A talks for another 20 seconds. User A will be billed for 20 seconds.

User price = (20*0.1)/60 = 0.0333

'''Scenario #5 (ATTENDED transfers only)'''

''Prefix 370, rate 0.1''

Local user A calls local user B and after 30 seconds user B transfers call to outside number (prefix 370). User A talks for another 20 seconds. User B will be billed for 20 seconds.

User price = (20*0.1)/60 = 0.0333

'''Limitations'''

Call can be transfered only one time.

Update MOR GUI

2015-04-02T10:33:27Z

Mantas svelnys: /* How to update the GUI? */

=What is MOR GUI Update?=
MOR GUI update is a procedure to update your graphical user interface (GUI) to the newest version.
=Why should I update my GUI?=
Some features are being implemented after official version release, so if you find, that you lack some feature documented in wiki - you should update your GUI to receive that feature.

Please check for important changes [[Important_changes | here]]. It could be that you will need some changes on configuration after update.

'''P.S. Use the procedure that matches your version, otherwise it might break your system. To update to a newer version - please contact the Kolmisoft team'''

=How to determine what GUI version I have?=
Please run this command to determine your current MOR GUI version:
 
svn info /home/mor | grep URL | awk -F"/" '{print $NF}'
You will get a similar output:
[root@localhost ~]# svn info /home/mor | grep URL | awk -F"/" '{print $NF}'
9

 

=What else should I know?=
MOR GUI and MOR core versions '''must match'''. Always update your GUI according to core version. MOR core version can be determined by running this command:
 
asterisk -rx "mor show status" | grep Version
You will get a similar output:
[root@localhost ~]# asterisk -rx "mor show status" | grep Version
Version: '''9.1.22'''

In this example we have MOR with version 9 core. So to update GUI you should follow the GUI update guide for version 9
 
=How to update the GUI?=

 
----
 

== MOR 8 update ==

To update '''[[MOR 8 documentation | MOR 8]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/0.8/hard_fix.sh

 
----
 

== MOR 9 update ==

To upgrade '''[[MOR 9 documentation | MOR 9]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/9/fix.sh

 
----
 

== MOR 10 update ==

To update '''[[MOR 10 documentation | MOR 10]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/10/fix.sh

== MOR 11 update ==

To update '''[[MOR_11 | MOR 11]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/11/fix.sh

== MOR 12 update ==

To update '''[[MOR_12 | MOR 12]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/12.126/fix.sh

== MOR X3 update ==

To update '''[[MOR_X3 | MOR X3]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/12/fix.sh

== MOR X4 update ==

To update '''[[MOR_X4 | MOR X4]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/upgrade/x4/fix.sh

== MOR X5 update ==

To update '''[[MOR_X5 | MOR X5]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/x5/update.sh

== MOR X6 update ==

To update '''[[MOR_X6 | MOR X6]]''' GUI run such commands over SSH as root:

rm -fr /usr/src/mor
svn co http://svn.kolmisoft.com/mor/install_script/trunk/ /usr/src/mor
/usr/src/mor/x6/update.sh

Recommended hardware

2015-03-17T11:14:26Z

Mantas svelnys: /* Specifications */

== Specifications ==

Main principle - as powerful as possible. For single server solution we recommend:

{| border="1" cellpadding="5" cellspacing="0"
| '''Component''' || '''Minimum requirement''' || '''Recommended''' || [[File:check.png]] ''' We provide as Hosted Solution''' || '''Comment'''
|-
| CPU || Quad Xeon/Intel Core i5+ || any higher CPU || [[File:check.png]] Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz ||
|-
| RAM || 4 Gb || 16 GB or more || [[File:check.png]] 32 GB ||
|-
| HDD || 100 Gb || 100 Gb or more, SDD (Solid State Drives), [http://en.wikipedia.org/wiki/RAID#RAID_1 RAID Type 1] || [[File:check.png]] 2 x 120 GB SSD RAID 1 || all space must be assigned to / partition; ext3 file system
|-
| OS || [[Centos_installation | Linux Centos 6]] || x86_64 || [[File:check.png]] Centos 6.6 ||
|-
| Brand|| Any || Intel, DELL, HP, Fujitsu || [[File:check.png]] Intel ||
|}

It is required to have clean server without any additional packets installed.

Default Centos kernel is required.
 

== Requirements for multi-server deployment ==

'''Asterisk server:''' same requirements as above, except SSD would not increase performance so it is not needed and 4 GB of RAM is sufficient. CPU is most important component here. If Proxy solution is in use, Asterisks cannot be under NAT, it must have Public IP for SIP and RTP traffic.

'''Database server:''' same requirements as above and SSD is highly recommended here. SSD is must if system has more than one Asterisk server. There should be 100GB or more space as database grows fast on high traffic. Fast data storage device and CPU are most important here. If more than one Database server is in use, UPS (Uninterruptible Power Supply) devices must be used for these servers, otherwise power outage would cause broken replication.

'''GUI server:''' same requirements as above, except SSD would not increase performance a lot. HDD with more space is recommended here.

'''Proxy server:''' same requirements as above, except 4 GB of RAM and 40 GB on HDD will be enough here. SSD would not increase performance. Proxy server cannot be under NAT, it must have Public IP for SIP traffic.

'''Redundant servers:''' there are no special requirements on server hardware if server is part of redundant system. However, there are requirements for network to which servers are connected:

* Both servers should be within same subnet.
* Both servers should be able to ''broadcast'' packets to UDP 694 port.
* Both servers should be able to receive packets broadcasted by other server.
* There should be Virtual IP reserved in Subnet.
* Both servers should be able to work with that Virtual IP (only one server at same time).

If any of requirements above are not met, in some cases it is possible to adapt different network configurations or services (like "IP Failover"). However, management/configuration/development of third party software (like special scripts) needed to adapt special solution should be performed by servers owner.

 

== Virtualization ==

MOR system was tested and working on following Virtualization technologies:
* VMware
* VirtualBox

 

== FAQ ==

* Do you have the provision of STUN and TURN servers on your end?

No, we do not provide STUN servers. MOR should receive Public IPs on SIP headers. NAT traversal should be done on customer's side.

 

= See also =

* [[How fast MOR can perform]]
* [[Stress Test 2012-03-05]]

Watch active calls/channels in Asterisk server from CLI

2015-03-05T07:11:03Z

Mantas svelnys: /* Watch active channels */

===Watch number of active channels===

watch "asterisk -vvvvvrx 'core show channels' | grep channels"

===Watch number of active calls===

watch "asterisk -vvvvvrx 'core show channels' | grep calls"

===Watch active channels===

watch "asterisk -vvvvvrx 'core show channels verbose'"

===Watch active channels in Asterisk 1.8===

watch "asterisk -vvvvvrx 'core show channels verbose'"

Watch active calls/channels in Asterisk server from CLI

2015-03-05T07:10:51Z

Mantas svelnys: /* Watch number of active calls */

===Watch number of active channels===

watch "asterisk -vvvvvrx 'core show channels' | grep channels"

===Watch number of active calls===

watch "asterisk -vvvvvrx 'core show channels' | grep calls"

===Watch active channels===

watch "asterisk -vvvvvrx 'show channels verbose'"

===Watch active channels in Asterisk 1.8===

watch "asterisk -vvvvvrx 'core show channels verbose'"

Watch active calls/channels in Asterisk server from CLI

2015-03-05T07:10:21Z

Mantas svelnys: /* Watch number of active channels */

===Watch number of active channels===

watch "asterisk -vvvvvrx 'core show channels' | grep channels"

===Watch number of active calls===

watch "asterisk -vvvvvrx 'show channels' | grep calls"

===Watch active channels===

watch "asterisk -vvvvvrx 'show channels verbose'"

===Watch active channels in Asterisk 1.8===

watch "asterisk -vvvvvrx 'core show channels verbose'"

How to access MySQL database via WEB

2015-02-23T11:35:28Z

Mantas svelnys:

Since MOR v0.7 phpmyadmin directory is restricted from web access.

To access MySQL database via WEB you need to do:
Login via ssh to your MOR GUI server and execute:
cat /root/phpMyAdminPassword
And you must see something like this:
Login and Password from phpMyAdmin system: admin YOURPASSWORD
Now go to http://'''IP ADDRESS OF YOUR WEB SERVER'''/mordbadmin (for example http://123.123.123.123/mordbadmin)
and enter correct details which you have got from /root/phpMyAdminPassword file.

Then login using your regular details from mysql. (Mostly 'mor/mor' or just 'root' without password will help you to access phpmyadmin web page where you can manage your databases).

'''Be very careful when changing something in database, its good idea to make whole database backup before making any changes.'''

BETTER IF YOU DO NOT CHANGE ANYTHING IN DB AT ALL!

A real world example how to obtain phpmyadmin password from system:

[[Image:ppp.png]]

M4 Directions

2015-01-13T15:23:50Z

Mantas svelnys: Created page with 'Can be foun in: MAINTENANCE -> Directions -> Groups Very similar to MOR: http://wiki.kolmisoft.com/index.php/Directions_and_Destinations'

Can be foun in:

MAINTENANCE -> Directions -> Groups

Very similar to MOR:

http://wiki.kolmisoft.com/index.php/Directions_and_Destinations

M4 Switch Manual

2015-01-13T14:56:23Z

Mantas svelnys: /* Maintenance */

= 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]]
* [[m2.conf]]

 

= Routing =
* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Termination Points | Termination Points (TP) ]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Dial Peers | Dial Peers (DP) ]]

 

= Billing =

* [[Code Decks]]
* [[M2 Tariffs| Tariffs]]
* [[M2 Rates | Rates]]
* [[M2 Rate Notification | Rate Notifications]]

 

= 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 =
* [[M2 Access Levels | Access Levels]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
* [[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]]

 

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

 

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

LCR

2015-01-08T16:54:26Z

Mantas svelnys: /* Usage */

=Description=

LCR (Least Cost Routing) is a set of Providers that should be used to send a call when trying to dial any destination - for example, by the cheapest rate.

The correct name for such a function is a Routing Table, because the function supports other ways of routing, not just finding the cheapest route.

By default LCR supports fail-over. That is, if one provider fails, the next one is dialed. This is completely invisible for the caller and lets you increase the chances of the user reaching his destination. If one Provider is not capable of delivering a call, the system will try to use the remaining [[How_to_add_Provider_to_LCR | Providers]].
 
==Fail-over explanation==
With such configuration:

[[image:lcr_fo_case1.png]]

System will do following:

* system tries to use "Kolmisoft PREMIUM";

* if above fails, system tries to use "Kolmisoft STANDARD";

* end.
 
With such configuration:

[[image:lcr_fo_case2.png]]

System will do following:
* system tries to use "Kolmisoft PREMIUM";

* end.
 
With such configuration:

[[image:lcr_fo_case3.png]]

System will do following:
* system tries to use "Kolmisoft PREMIUM";

* if above fails, system tries to use "Kolmisoft STANDARD";

* if above fails, system tries to use provider "112" even if its rate is higher than User rate;

* end.
 
=Usage=

Go to '''SETTINGS –> Billing –> LCR'''
 
[[File:lcr_path.png]]
 
Here you can see the list off all LCRs
 
[[File:lcr_main.png]]
 
* Name – name of LCR.
* Order – type of routing mode.
* Providers – quantity of providers in LCR. Click on it to [[How_to_add_Provider_to_LCR | Add Providers to LCR]]
* [[Call_routing_per_destination_basis | By destination]]
* Usage Details – the list of Users and Card Groups where this LCR is used.
* [[LCR make tariff | Make Tariff from LCR Providers to CSV]] – feature that gets you a CSV with the MIN/MAX prices selected from the list of Providers in LCR. Click on the [[Image:excel.png]] icon and the download should start automatically. (De-activated provider will be taken into CSV. "by Destination" will not be taken into CSV)
* LCR copy – press on icon to make LCR copy.
 
Press [[Image:icon_add.png]]'''New LCR''' to create LCR.
 
===Supported routing modes===

* [[Call Routing by price|By Price]] - cheapest first (Least Cost Routing).
* [[Call Routing by priority (Manual LCR) | By priority]].
* [[Routing by Percent| By percent]] or Weight-based routing.

The user has one base LCR, so that all his calls are routed by some preset rule.

It is possible to route different destinations for a User using [[Call routing per destination basis]].
 
==LCR Time Periods==

Sometimes there is such demand to change LCR for some time period. This functionality gives you an ability to do that. Go to LCRs list and press [[image:icon_edit.png]] icon. Here time periods can be set.
 
[[File:lcr_time_periods.png]]
 
Time period defines the exact time period LCR will be active. There is a limit of five periods in one LCR. Rest of the time will be used main LCR.
===Examples===
# Select '''Date''' from 1 of January to 28 of February and choose '''Hour : Minute''' from 09:00 to 18:59. Selected LCR will be used from 1 of January till 28 of February at time from 09:00 till 18:59.
# Select just '''Hour : Minute''' from 19:00 to 08:59 and selected LCR will be used every day at time from 19:00 till 08:59.
# Select '''Weekday''' from Monday to Friday and choose '''Hour : Minute''' from 13:00 to 15:59. Selected LCR will be used every week from Monday till Friday at time from 13:00 till 15:59.
 

==Copying LCRs between resellers==

Sometimes you need to make a LCR which takes quite a long time to make. If you have made a similar one before you can just copy it and change appropriate details.

Go to '''SETTINGS''' -> '''Billing''' -> '''LCR''' -> '''Copy LCR'''
 
[[File:lcr_copy_path.png]]
 
You will see this window:
 
[[File:lcr_copy.png]]
 
Choose ''Original LCR reseller'' and ''Cloned LCR reseller'' and click ''Clone'' button.

Please note that LCR will not be allowed to copy if reseller B is not allowed to use Providers which are used by Reseller A.
 

=See also=

* [[LCR Logic]]
* [[How to add Provider to LCR]]
* [[Call Routing by price]]
* [[Call Routing by priority (Manual LCR) | Call Routing by priority ]]
* [[Routing by Percent | Call Routing by percent]] or Weight-based routing
* [[Call routing per destination basis]]
* [[LCR/Tariff change based on call prefix]]
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[LCR_make_tariff|Make Tariff from LCR Providers to CSV]]

Get Google Maps key

2014-12-30T10:56:07Z

Mantas svelnys:

[[Image:gmaps.jpg|right|400px]]
'''!!!OUTDATED!!!'''

You need a Google maps key to use the Google maps plugin.
* Go to [http://code.google.com/apis/maps/signup.html Google].
* Write your site in the text box below. Note that http://1.2.3.4 differs from http://yoursite.com, so enter the hostname that you will use to access your site.
* Press "Generate API key" and Google will give you your key.
* Insert this key in '''SETTINGS –> Setup –> Settings –> Google Maps –> Key'''.
* Click '''Save changes'''.

----
'''See also:'''
* [[Configuration from GUI#Google_Maps | Google Maps Configuration]]
* [[Google Maps integration]]

M4 Routing Logic

2014-12-22T08:40:59Z

Mantas svelnys:

[[File:m2_logical_structure.png|700px]]

# Based on "Routing Group - Dial Peer" priority we order Dial Peers (DP) (if priorities match - we select random)
## Next (by priority) DP is used only when previous has Stop Hunting unchecked
# Based on "Origination Point Routing Algorithm" (example provided bellow) we order Termination Points (TP) in selected Dial Peer by:
## LCR - routing is based only by price (TP tarrifs). If TP price matches - we order by "Dial Peers TP Priority" (if priorities match - we select random)
## Weight - routing is based only by weight number. Lower number has greater priority. If TP weight or price matches - we order by "Dial Peers TP Priority" (if priorities match - we select random)
## Percent - routing is based only by percents. If zero is entered calls will not go through. Let say prov1 has 90% and prov2 has 10% (only two providers in routing group). So in ideal conditions prov1 has 9/10 and prov2 has 1/10 probability to terminate the call.

[[File:M2_Routing_by_LCR_WG_PC.png]]

M4 Routing Logic

2014-12-22T08:40:30Z

Mantas svelnys:

M4 Routing Logic

2014-12-22T08:39:13Z

Mantas svelnys:

[[File:m2_logical_structure.png|700px]]

# Based on "Routing Group - Dial Peer" priority we order Dial Peers (DP) (if priorities match - we select random)
## Next (by priority) DP is used only when previous has Stop Hunting unchecked
# Based on "Origination Point Routing Algorithm" (example provided bellow) we order Termination Points (TP) in selected Dial Peer by:
## LCR - routing is based only by price (TP tarrifs). If TP price matches - we order by "Dial Peers TP Priority" (if priorities match - we select random)
## Weight - routing is based only (price does not matter) by weight number. Lower number has greater priority. If TP weight or price matches - we order by "Dial Peers TP Priority" (if priorities match - we select random)
## Percent - routing is based only (price does not matter) by percents. If zero is entered calls will not go throug. Let say prov1 has 90% and prov2 has 10% (only two providers in routing group). So in ideal conditions prov1 has 9/10 and prov2 has 1/10 probability to terminate the call. If TP percent matches - Termination Points will be ordered by probability described by percent values.

[[File:M2_Routing_by_LCR_WG_PC.png]]

M4 Routing Logic

2014-12-22T08:33:34Z

Mantas svelnys:

[[File:m2_logical_structure.png|700px]]

# Based on "Routing Group - Dial Peer" priority we order Dial Peers (DP) (if priorities match - we select random)
## Next (by priority) DP is used only when previous has Stop Hunting unchecked
# Based on "Origination Point Routing Algorithm" (example provided bellow) we order Termination Points (TP) in selected Dial Peer by:
## LCR - routing is based only by price (TP tarrifs).
## Weight - routing is based only (price does not matter) by weight number. Lower number has greater priority. If TP weight or price matches - we order by "Dial Peers TP Priority" (if priorities match - we select random)
## Percent - routing is based only (price does not matter) by percents. If zero is entered calls will not go throug. Let say prov1 has 90% and prov2 has 10% (only two providers in routing group). So in ideal conditions prov1 has 9/10 and prov2 has 1/10 probability to terminate the call. If TP percent matches - Termination Points will be ordered by probability described by percent values.

[[File:M2_Routing_by_LCR_WG_PC.png]]

File:M2 Routing by LCR WG PC.png

2014-12-22T08:17:10Z

Mantas svelnys:

Ports which should be opened

2014-12-19T13:27:10Z

Mantas svelnys:

For server some ports should be opened '''or forwarded''' to M2/MOR server:

* TCP 80 - for GUI/HTTP
* TCP 22 - for SSH connection
* TCP 25/465 - for SMTP / SMTP over SSL (TLS)
* UDP 694 - for Heartbeat.
* TCP 3306 - for MySQL replication
* TCP 3690 - for SVN connections
* UDP 4569 - for IAX2 connection
* UDP 5060 to 5070, 10000-20000 - for SIP connection
* TCP/UDP 123 - Network Time Protocol
* TCP/UDP 1720 - for H.323 Protocol
* TCP/UDP 5038 - for Asterisk manager interface
* TCP/UDP 10050 - for Zabbix monitoring
* UDP 4000 - 4999 for T.38 support
* TCP/UDP 443 - For HTTPS (if used)
You can test which TCP ports are opened using nmap tool:

nmap -vv -P0 your MOR server's IP address

https://www.virtualizationhero.com/docs/manuals/linux/RHL-9-Manual/security-guide/s1-server-ports.html

=== iptables config ===

For Asterisk server:

iptables -A INPUT -p tcp --dport ssh -j ACCEPT
iptables -A INPUT -p tcp --dport 5038 -j ACCEPT
iptables -A INPUT -p udp --dport 5038 -j ACCEPT
iptables -A INPUT -p udp --dport 4569 -j ACCEPT
iptables -A INPUT -p udp --dport 1720 -j ACCEPT
iptables -A INPUT -p udp --dport 5060:5070 -j ACCEPT
iptables -A INPUT -p udp --dport 10000:20000 -j ACCEPT
iptables -A INPUT -p udp --dport 4000:4999 -j ACCEPT
iptables -A INPUT -j DROP

Heartbeat configuration

2014-11-07T06:40:50Z

Mantas svelnys: /* Possible problems */

'''What is High availability?'''

High availability is a system design protocol and associated implementation that ensures a certain absolute degree of operational continuity during a given measurement period.

Lets say you have two servers 'A' and 'B' with MOR installed, MySQL is running replication between them. By default all trafic comming to server 'A' is monitored by server 'B', so when server 'A' fails, server 'B' stands in its position by given time.

So allmost no data is lost, and your users will be happy with your services.

[[File:Hearbeat_example.jpg]]

'''What is Heartbeat?'''

Heartbeat is software which implements these monitoring and availability features for your servers. It must be carrefully installed, configured and tested on both servers to ensure correct producing of services.

'''What do you need to know before starting'''

Please review once more the provided above scheme. It represents a typical Linux Heartbeat configuration. Before starting you have to be aware of 4 main points:

1. All public IP addresses have to be on same subnet. 
2. [http://en.wikipedia.org/wiki/Virtual_IP_address Virtual IP] has to be free (not assigned to any device on the network) and the last octet of the address (in this case .4 is the last octet) has to be the highest in the configuration. Server A and B have to be on "lower" IP, in this case .2 and .3 (the last octet). 
3. Never use servers when they are off-line as it will ruin the MySQL replication. 
4. After heartbeat configuration has been made, do not change the addressing scheme or the host-names of the servers. 

'''Installation'''

Hearbeat 2.99 has been full tested on Centos 5.2 only, there is no guarantee that it will work on older versions or distros.

Download mor install scripts from svn. in both servers.

Run /usr/src/mor/sh_scripts/install_heartbeat.sh in both servers

Script will:

* download special file, then yum automaticaly install correct heartbeat files for your system.
* install pacemaker, its future only.
* configure /etc/ha.d/authkeys so you don't need to change anything here
* configure /etc/ha.d/ha.cf file, but you still need adjust it by hand (how? later on this page).
* configure /etc/ha.d/haresources file, but you still need to change few bits there, also, later on this page.
* add 2 lines to /etc/hosts, but just for testing purporses only, so you will have to change ips here.

'''ATTENTION''': if you installed Heartbeat manually, please make sure that you have '''same version of Heartbeat on both servers'''. You will probably need same Centos version on both servers to do that.

'''Configuration'''

'''Before going further, you need to setup hostname of both servers. Make sure master will have node01 and slave node02. (uname -n) must return correct words.'''

Make sure to remove all services which are related to Heartbeat from the runlevels:

chkconfig --list

If you want to remove some service (for example asterisk):

chkconfig --del asterisk

Edit /etc/sysconfig/network to change your hostname. Then reboot your machine.

First configure master (node01):

Open /etc/hosts and you will see something like this:

203.0.113.2 node01 #change to correct IP
203.0.113.3 node02 #change to correct IP here aswell

Change ip of node01 of master machine, which "accept all incoming traffic by default".

And change ip to slave, witch will "accept all data, if master will die"

Open /etc/ha.d/ha.cf and change:

Deadtime higher or lower setting. Deadtime means how many seconds have to pass before take over job from master.

Remember, this should be lower on on "lightly" loaded machines, and higher and "highly" loaded machines.

Deadtime 10 is more than enough. (Default is 5)

Make sure you add 2 network interfaces for heartbeat broadcasts.

The bcast directive is used to configure which interfaces Heartbeat sends UDP broadcast traffic on.

For example 'bcast eth0 eth1'.

The udpport directive is used to configure which port is used for these broadcast communications if the
udpport directive is specified before the bcast directive, otherwise the default port will be used.

Now open /etc/ha.d/haresources (be sure to leave only the lines given below):

node01 203.0.113.4 asterisk # just for testing, remember this ip can't be used in your network!!!

Or

node01 IPaddr::192.168.0.142/24/eth0:0 httpd # just for testing, remember this ip can't be used in your network!!! # if eth0:0 does not appear

So, first of all:

Assuming node01 is master and node02 is slave, by default all traffic is going to node01.

You need to choose IP (for Virtual IP) from your network and never use it, otherwise this will lead to unexpected results.

node01 203.0.113.4 asterisk, "if master is dead, slave (node02) will restart asterisk and start to accept traffic comming from 203.0.113.4"

Now copy all configuration to slave (node02).

shell@node01:/$ scp -r /etc/ha.d/ root@node02:/etc/

Start heartbeat on both servers by running /etc/init.d/heartbeat start. If everything will be ok, you will see something like this:

Starting High-Availability services:

2008/12/18_18:13:22 INFO: Resource is stopped

[ OK ]

Do not forget to remove Asterisk from system startup, because it needs to be started by Heartbeat:
chkconfig asterisk off
on both servers.

'''Testing'''

Now run iptraf on both machines, from another machine start pinging your binded IP address (in this example we speak about 203.0.113.4).

Check for masters iptraf window, you will see incoming ICMP data, slave have to be quiet.

[[Image:heartbeat1.png]]

Now kill master (for example: ifconfig eth0 down or issue a reboot), after short period of time (on this example 5 seconds) on slave you will see incoming ICMP packets.

To bring master to work again, first of all you have to configure network on master and start heartbeat. After 20~ seconds master have to start doing his job again.

Now go to GUI and change your default asterisk server IP (Settings -> Servers), change from 127.0.0.1 to virtual IP address. If your GUI is unable connect to them, make sure both asterisk servers allow connections from your GUI server. (file: /etc/asterisk/manager.conf)

= sip.conf =

In file '''/etc/asterisk/sip.conf''' enter correct IP for value '''bindaddr''', correct IP = IP to which your devices are registering. E.g. Virtual IP.

Do same changes for bindaddr in iax.conf, h323.conf and manager.conf

[[How to restart Asterisk server|Restart Asterisk]]

Make this on both servers.

= mor.conf =

On slave server go to '''/etc/asterisk/mor.conf''' and set '''server_id = 2''' (default is 1)

= Possible problems =

Look at the picture:
 
[[File:Heartbeat_broadcast.jpg]]
 
In this example HeartBeat in bcast directive has only one interface configured on both servers: eth1

This can lead to problems if the link eth1 <----> eth1 between the servers fails (broken cable, switch, NIC, etc)

'''You must specify at least 2 interfaces in bcast directive'''

The bcast directive is used to configure which interfaces Heartbeat sends UDP broadcast traffic on.

An example of bcast directive:
bcast eth0 eth1
 

== Virtual interface does not appear ==

Check /var/log/heartbeat.log

If you can see something like:

...
ResourceManager(default)[6106]: 2012/12/07_11:33:51 info: Running /etc/ha.d/resource.d/IPaddr 123.123.123.123 start
IPaddr(IPaddr_123.123.123.123)[6197]: 2012/12/07_11:33:51 ERROR: /usr/lib64/heartbeat/findif failed [rc=1].
/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_123.123.123.123)[6183]: 2012/12/07_11:33:51 ERROR: Generic error
...

Please add subnet mask and interface to /etc/ha.d/haresources like this:

node01 123.123.123.123/27/em1 asterisk

 

== Virtual interface appears on both nodes ==

Check if servers can send packets through port UDP 694 to each other ('''both directions'''). Firewalls may block that port.

Check if /etc/ha.d/haresources has properly defined "node01" (or relevant hostname) on '''both servers'''.

 

== There is more than one HA cluster in the same subnet ==

We can suspect that there is another HA cluster runing if in /var/log/heartbeat.log we see such output:

Nov 06 13:25:28 node01 heartbeat: [9200]: WARN: Invalid authentication type [3] in message!
Nov 06 13:25:28 node01 heartbeat: [9200]: WARN: string2msg_ll: node [cpc2] failed authentication

So we need to change port in /etc/ha.d/ha.cf like this:

logfile /var/log/heartbeat.log
logfacility local0
keepalive 2
deadtime 5 # depends on load, so be careful!
initdead 20 # start time
udpport 496 # UDPPORT SHOULD COME IN FRONT OF BCAST LINE OTHERWISE PORT WON'T BE CHANGED
bcast eth0
auto_failback on
node node01
node node02

== Heartbeat service does not start ==

There is was bug with resource-agents-3.9.2-21.el6_4.8.x86_64 package.

Make sure that packets "heartbeat" and "resource-agents" are up to date.

Command to update:

yum install heartbeat resource-agents

More details:
http://bugs.centos.org/view.php?id=6727

= See also =

[[High availability (Heartbeat clustering)]]

http://www.linux-ha.org/wiki/Haresources

Summary

2014-10-10T07:46:00Z

Mantas svelnys:

'''No longer available till X5: [[There is no "Summary" in MOR X5]]'''

----

=Description=

These statistics provide brief information about Terminators and Originators.
 
=Usage=

Go to '''STATISTICS –> Calls –> Summary'''
 
[[Image:summary_path.png]]
 
Here it is possible to see brief information about Terminators and Originators:
 
[[Image:summary.png]]
 
'''Terminators''' table
* [[Terminators | Terminator]] – name of Terminator.
* Total Calls – quantity of selected period calls made through all Providers which belongs to Terminator.

* Terminator Price – sum of provider_price in selected period calls made through all Providers which belongs to Terminator.

'''Originators''' table
* Originator – name of User.
* Total Calls – quantity of selected period calls.

* Originator Price – sum of (user_price + did_inc_price).

* Originator Price with Tax – sum of (user_price + did_inc_price) with User Tax.
 

=See also=

* [[Terminators]]
* [[User Details]]

There is no "Summary" in MOR X5

2014-10-06T11:47:19Z

Mantas svelnys: Created page with 'We have removed Summary because it was dublication of Aggregates. To get the same information as it was in MOR X4 Sumarry you should use following settings: [[File:Like summ…'

We have removed Summary because it was dublication of Aggregates.

To get the same information as it was in MOR X4 Sumarry you should use following settings:

[[File:Like summary x5 aggregates.png]]

This is how it been in X4:

[[File:X4 old sumarry.png]]

File:Like summary x5 aggregates.png

2014-10-06T11:45:38Z

Mantas svelnys:

File:X4 old sumarry.png

2014-10-06T11:44:25Z

Mantas svelnys:

I have a problem with Statistics

2014-10-06T11:40:45Z

Mantas svelnys:

* [[Where can I find Simultaneous Calls statistic | Where can I find Simultaneous Calls statistics]]
* [[Where can I find hardware and network statistic | Where can I find hardware and network statistics]]
* [[Number of calls in Aggregate do not match with number of calls in Graphs]]
* [[I cannot see calls in Calls by Source]]
* [[Calls in invoice and last calls/country stats do not match]]
* [[There is no "Summary" in MOR X5]]

M4 Dial Peers

2014-08-04T15:15:27Z

Mantas svelnys:

=Description=

Dial Peer is a logical routing entity (group of [[M2 Termination Points | Termination Points]] with predefined rules) which allows to control how calls should be routed.

It consists of several rules and includes [[M2 Termination Points | Termination Points]] over which calls should be routed.

Dial Peers are grouped together into [[M2 Routing Groups | Routing Groups]] which then are assigned to [[M2 Origination Points | Origination Points]].

In order to temporary remove a Dial Peer it can be set as inactive so it won't be used in determining a call's route.

 

= Routing by Destination/Number B =

[[Image:M2_dp_destination_by_tariff.png]]

Destination by Regexp - describes which destinations should be allowed 
Destination by Tariff - describes which destinations should be allowed for selected Tariff and matched by Destinations Mask (which is equivalent to SQL LIKE function) 
Destination deny regexp - describes which destinations should be denied

 

= Routing by Source/CallerID/Number A=

Source regexp - describes which Source/CallerID/Number A should be allowed 
Source deny regexp - which should be denied

 

= Assigning Termination Points =
Routing > Dial Peers > pressing on button in TP List column
 
[[File:M2_assigned_termination_points.png]]
 
Termination Point can be assigned to Dial Peer by pressing on ASSIGN TERMINATION POINT button (1), selecting Termination Point from Termination Points drop down list (2), setting Percent (3), Weight (4) and pressing ASSIGN button (5). 
Active column show if Termination Point is active. Termination Point status can be changed in Termination Points edit page. 
Pressing on Termination Points name (7) redirect to Termination Points edit page. 
Pressing on Percent (8) allows it to be updated (to save it just press anywhere else). 
Pressing on Weight (9) works just like pressing on Percent. 
REMOVE button (10) removes Dial Peers relationship with Termination Point (not the Termination Point)

= Percent and Weight logic =

'''2 providers in TP list has weight = 1 and percent = 100'''

1/2 possibility to call with one or another

'''First provider weight is 1 and percent equal to 100% and the second ones weight is also one but percent is 50%'''

In this case first provider get 2 calls while second provider gets 1 call.

If weight is 1 and percent value is equal (all has 10%, 20% or 100%) calls will be divided randomly but evenly to all providers in list.

= See also=
* [[M2 Regexp Examples|Regexp Examples]]

IVR system

2014-05-01T10:27:59Z

Mantas svelnys: /* See also */

[[Image:ivr_example.png|right|500px]]This system makes it possible to configure advanced IVR ('''Interactive Voice Response''') systems.

This functionality can be used by system owner (admin) and [[Reseller_Pro_Addon|Resellers PRO]].

IVRs and IVR Time Periods are located in '''ADDONS -> PBX functions -> IVR''' and Voices can be found at '''SETTINGS''' -> '''Setup''' -> '''Voices'''
 
== Definitions ==

* '''Voices''' – a set of audio files, such as male/female recordings, that together form a "voice" for the same IVR.
* '''Time Periods''' – a start date/time and end date/time that describe a time period.
* '''IVR''' – a set of IVR blocks.
** '''Blocks''' – a part of IVR in which the caller can take some action (press a button-extension, listen to a recording, etc). Basically block in IVR is "set of rules".
** '''Extensions''' – possible button presses (0-9, *, # and some other special cases).
** '''Actions''' – what action the system should take when a new Block is reached.

 
== Setup logic ==

* Create Voice
** Record and upload the necessary sound files to Voice.
* Create Time Period(s).
* Create IVR.
** Create and configure Block(s).
* Create the IVR Dial Plan.
* Assign this IVR Dial Plan to a DID.
* Call this DID to test it.

 
== Voices ==

'''SETTINGS''' -> '''Setup''' -> '''Voices'''

Here it is possible to create several Voices. A Voice consists of a set of sound files. Usually all the sound files in one Voice are recorded by one person to keep the sound consistent.

Multiple operations can be performed with Voices:

* View a detailed list of the system Voices.
* Add a new sound Voice.
* View the sounds that have files in different Voices.
* Upload new sound files for Voices.
* Delete Voices and voice files from the system.

You cannot remove sounds that are currently used.

 
== Time Periods ==

Go to '''ADDONS -> PBX functions -> IVR''' –> Time Periods'''
 
[[File:ivr_time_perionds_path.png]]
 
Here you will see Time Periods list. Click [[Image:icon_add.png]]'''New Time Period''' to create new period or click on [[image:icon_edit.png]] icon to edit old one to set time periods.
 
[[File:ivr_time_perionds.png]]
 
Time period defines the exact time period IVR will be active. There is a limit of three periods in [[IVR Dial Plan]]. There is a fourth period, but it only consists of all the remaining time that is not covered by the previous three periods.
 
===Examples===
# Select '''Date''' from 1 of January to 28 of February and choose '''Hour : Minute''' from 09:00 to 18:59. Action will be active from 1 of January till 28 of February at time from 09:00 till 18:59.
# Select just '''Hour : Minute''' from 19:00 to 08:59 and action will be active every day at time from 19:00 till 08:59.
# Select '''Weekday''' from Monday to Friday and choose '''Hour : Minute''' from 13:00 to 15:59. Action will be active every week from Monday till Friday at time from 13:00 till 15:59.
 

== IVR Structure ==

* '''IVR''' – consists of a set of IVR blocks.
** '''Blocks''' – part of IVR in which a caller can take some action (press a button-extension, listen to a recording, etc).
** '''Extensions''' – possible button presses (0-9, *, # and some other special cases).
** '''Actions''' – what action the system should take when an extension is activated.

The main part of IVR is '''Blocks'''. The whole of IVR is a set of Blocks. A Block can be considered as a part of IVR logic where a caller can take some action.

'''Extension''' is what the user does – presses a button (0-9, *, #), waits (Timeout), or presses any non-described extension – which can be described as an Invalid Extension. We explain this in detail later.

'''Actions''' are actions which will be activated when the caller comes to a Block.

 
=== Example ===

For example, here is a simple IVR:
* A caller calls a DID and IVR answers with a recording: "Thank you for calling SOME COMPANY. For sales press 1, for management press 2, to speak to a consultant please hold or press 3."

Here we have only one block: the user listens to the recording and can take some Action -> press some button (Extension) or wait (Wait is also Extension but is special - it is called Timeout).

If the user presses something different than 1, 2 or 3, the message will be played again. This is called an Invalid Extension, or (i) for short.

To summarize, we have the following situation:

* 1 Block.
* Extensions: 1, 2, 3, t (timeout), i (invalid).
* Actions: call to sales, call to management, call to a consultant, play recording again.

This example is to illustrate the main IVR building parts. We will show how they operate together to build a working IVR.

 
== Extensions ==

Extensions are button presses on the dialpad: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, * and # and two special extensions:

* t - means "timeout", when no extension is pressed in a determined time period.
* i - means "invalid". This extension becomes active when a caller presses some extensions that are not described in the IVR block configuration.

The 'i' (invalid) extension in the previous example could be triggered when buttons 4, 5, 6, 7, 8, 9, 0, *, # are pressed, because only 1, 2 and 3 are described.

 
== Actions ==

An Action is some (yes...) action which is executed when a new Block is reached.

Possible Actions:

* Playback – plays a sound file.
* Delay – delays execution by some seconds.
* Change Voice – changes IVR Voice.
* Hangup – finishes the call.
* Transfer to – transfers the call to:
** Another IVR
** DID
** Device
** Block
** Extension - in an opened text field you can enter anything.
* Debug – text message to Asterisk CLI which helps debugging.
* Set Accountcode - sets ownership for the call to some other user.
* Set CallerID (Number) - Sets incoming call to IVR, callerID number to any desired value. Usage example can be found [[How_to_request_Authentication_by_PIN_when_call_comes_from_Banned_CallerID | here]]
* Random Play
[[File:Ivr_play_random.png]]
 
This action plays a random sound file from the selected '''IVR Voice''' file group.

== Timeouts ==

=== Timeout digits ===

The maximum amount of time permitted between digits when the
user is typing in an extension. When this timeout expires
after the user has started to type in an extension, the
extension will be considered complete, and will be
interpreted. Note that if an extension typed in is valid,
it will not have to timeout to be tested, so typically at
the expiry of this timeout, the extension will be considered
invalid (and thus control would be passed to the 'i'
extension, or if none exists the call would be
terminated). The default timeout (in MOR IVR) is 3 seconds.

 
=== Timeout Response===

The maximum amount of time permitted after falling through a
series of priorities for a channel in which the user may
begin typing an extension. If the user does not begin typing an
extension in this amount of time, control will pass to the
't' extension if one exists, or if none exists, the call would be
terminated. Once the user begins to type an extension, Asterisk
will wait for digit timeout to be reached, and response timeout has
no effect. The default timeout (in MOR IVR) is 10 seconds.

 

== Deleting IVR ==

* If an IVR is not assigned to any Dial Plan, you can delete the IVR by clicking the [[Image:icon_delete.png]] icon near an IVR in the IVR menu.
* If the IVR is assigned to a Dial Plan, you need to unassign the IVR from the Dial Plan to be able to delete it.

 
== Setup Hints/Tips ==

* If you want to play a sound file, make sure you have set the correct Voice. By default, Voice = 'en'. If you have uploaded a sound file for a different Voice, select it before playing your Sound File:

[[Image:ivr_select_voice_before_playback.png]]

 
== Limitations ==

* Currently it is not possible to record calls for a device which is accessed from IVR. For example, if calls go like this: IVR -> Device, and device has option to record calls for this device, these calls will not be recorded.

 
=See also=
* [[IVR for Calling Cards]]
* [[IVR Greeting for DID]]
* [[Dial Local]]
* [[I have a problem with IVR]]
* [[Sound files]]
** [[MOR IVR Samples]]
*[[IVR setup example]]

*[[Random Play IVR Campaign]]

MOR API rate get

2014-03-24T11:29:47Z

Mantas svelnys: /* Parametres */

=Description=
[[MOR API]] rate_get feature enables you to check rate over http.
 
=Configuration=

Go to '''SETTINGS –> Setup –> Settings'''
 
[[File:settings_path.png]]
 
In API tab ensure that MOR API is enabled and check '''Allow devices to check rate over HTTP''' option :
 
[[File:Settings_various_rate_over_http.png]]
 
=Usage=

* From '''MOR X4''' call: '''/api/rate_get'''
* For Backwards-compatibility old name 'rate' is also usable. Call: '''/api/rate'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres===

* u - username for authentication. Required.
* username – username of user whose rates you want to see.
* prefix – prefix number of destination you want to see.
* [[MOR API hash construction | hash]] - SHA1 hash constructed using '''params''' and '''API_Secret_Key''' ([[MOR API hash construction | More described in Constructing hash]]). '''Required''' (if setting '''Disable hash checking''' is not checked).
'''NOTE:''' Don't use full number in API request. Use correct prefix only, because this method don't do prefix search, its only shows actual price for the exact prefix.
 

===Request===

HTML POST: http://<SERVER_IP>/billing/api/rate_get?u=admin&username=USERNAME&prefix=PREFIX&hash=HASH

Example:

http://127.0.0.1/billing/api/rate?u=admin&username=admin&prefix=370&hash=47fc73b6d374bd0a85e3984c1e1623451681569c
 

===Returns===

'''Success'''

Result is returned in format: rate#destination#prefix

<?xml version="1.0" encoding="UTF-8"?>
<page>
<rate>0.987#Lithuania#370</rate>
</page>

'''NOTE.''' MOR API rate method shows rate, which is applied to User. If rate by prefix is not found in [[Custom Rates]], it will be taken from Tariff assigned to User.
 
----
'''Errors'''

* User do not have rates for selected destination:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>Rate was not found</error>
</page>

* User with selected username does not exist:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>User was not found</error>
</page>

* '''Allow devices to check rate over HTTP''' option in [[MOR_API_rate_get#Configuration | API Settings]] is not set:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>Feature disabled</error>
</page>

* API is not allowed:

<?xml version="1.0" encoding="UTF-8"?>
<status>
<error>API Requests are disabled</error>
</status>

 

=See Also=

* [[MOR API]]

MOR API rate get

2014-03-24T11:28:47Z

Mantas svelnys: /* Request */

=Description=
[[MOR API]] rate_get feature enables you to check rate over http.
 
=Configuration=

Go to '''SETTINGS –> Setup –> Settings'''
 
[[File:settings_path.png]]
 
In API tab ensure that MOR API is enabled and check '''Allow devices to check rate over HTTP''' option :
 
[[File:Settings_various_rate_over_http.png]]
 
=Usage=

* From '''MOR X4''' call: '''/api/rate_get'''
* For Backwards-compatibility old name 'rate' is also usable. Call: '''/api/rate'''
* Methods: POST, GET(if allowed, not recomended)
 
===Parametres===

* username – username of user whose rates you want to see.
* prefix – prefix number of destination you want to see.
* [[MOR API hash construction | hash]] - SHA1 hash constructed using '''params''' and '''API_Secret_Key''' ([[MOR API hash construction | More described in Constructing hash]]). '''Required''' (if setting '''Disable hash checking''' is not checked).
'''NOTE:''' Don't use full number in API request. Use correct prefix only, because this method don't do prefix search, its only shows actual price for the exact prefix.
 
===Request===

HTML POST: http://<SERVER_IP>/billing/api/rate_get?u=admin&username=USERNAME&prefix=PREFIX&hash=HASH

Example:

http://127.0.0.1/billing/api/rate?u=admin&username=admin&prefix=370&hash=47fc73b6d374bd0a85e3984c1e1623451681569c
 

===Returns===

'''Success'''

Result is returned in format: rate#destination#prefix

<?xml version="1.0" encoding="UTF-8"?>
<page>
<rate>0.987#Lithuania#370</rate>
</page>

'''NOTE.''' MOR API rate method shows rate, which is applied to User. If rate by prefix is not found in [[Custom Rates]], it will be taken from Tariff assigned to User.
 
----
'''Errors'''

* User do not have rates for selected destination:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>Rate was not found</error>
</page>

* User with selected username does not exist:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>User was not found</error>
</page>

* '''Allow devices to check rate over HTTP''' option in [[MOR_API_rate_get#Configuration | API Settings]] is not set:

<?xml version="1.0" encoding="UTF-8"?>
<page>
<error>Feature disabled</error>
</page>

* API is not allowed:

<?xml version="1.0" encoding="UTF-8"?>
<status>
<error>API Requests are disabled</error>
</status>

 

=See Also=

* [[MOR API]]

File:Lcr fo case2.png

2014-03-22T12:09:41Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case2.png"

File:Lcr fo case3.png

2014-03-22T11:49:54Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case3.png"

File:Lcr fo case2.png

2014-03-22T11:45:50Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case2.png"

File:Lcr fo case2.png

2014-03-22T11:44:41Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case2.png"

File:Lcr fo case1.png

2014-03-22T11:44:17Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case1.png"

File:Lcr fo case1.png

2014-03-22T11:41:36Z

Mantas svelnys: uploaded a new version of "File:Lcr fo case1.png"

Automatic Backups do not work

2014-03-05T09:31:40Z

Mantas svelnys:

= Cronjob =

Automatic backups are run by cronjob which should reside in '''/etc/cron.d/mor_hourly_actions'''

Inside this file you will see:

0 * * * * root wget -o /dev/null -O /dev/null http://127.0.0.1/billing/callc/hourly_actions

To test if it really works execute such lines in bash:

cd /tmp
wget http://127.0.0.1/billing/callc/hourly_actions

You should get such output:

--07:39:07-- http://127.0.0.1/billing/callc/hourly_actions
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://127.0.0.1/billing/backups/backups_hourly_cronjob [following]
--07:39:07-- http://127.0.0.1/billing/backups/backups_hourly_cronjob
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1 [text/html]
Saving to: `backups_hourly_cronjob'
100%[===========================================================================================================================>] 1 --.-K/s in 0s
07:39:07 (274 KB/s) - '''`backups_hourly_cronjob' saved''' [1/1]

If you do not get such output that means Apache is misconfigured and you need to make sure that your Apache is accessible as 127.0.0.1 from this local MOR server.

In /tmp/mor_debug.txt should be such lines:

2010-03-19 10:00:01 - Make backups at: 10 h
Making auto backup

If they are, '''login as apache user''' and try to execute such command in bash:

/usr/local/mor/make_backup.sh 20100319090451 /usr/local/mor/backups -c

Check if backup is made.

If not, do:

chmod 777 -R /usr/local/mor/backups

 
= Backup is not visible in GUI =

Backup is made, file is present, but does not appear in GUI.

 
= SSL is used in the server =

In such case you should change mor_hourly cron configuration file like this:

'''0 * * * * root wget -o /dev/null -O /dev/null https://your.domain.name/billing/callc/hourly_actions --no-check-certificate'''

If you do not have FQDN then put your server IP adress instead of your.domain.name

File is located in:

''' vi /etc/cron.d/mor_hourly_actions '''

 
= See also =
* [[I have a problem with Backups]]
* [[Backup system]]

Recommended hardware

2014-02-12T07:51:51Z

Mantas svelnys:

Main principle - as powerful as possible.

For 1 server solution:
{| border="1" cellpadding="5" cellspacing="0"
| '''Component''' || '''Minimum requirement''' || '''Recommended''' || [[File:check.png]] ''' We provide as Hosted Solution''' || '''Comment'''
|-
| CPU || Quad Xeon/Intel Core i5+ || any higher CPU || [[File:check.png]] Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz ||
|-
| RAM || 4 Gb || 16 GB or more || [[File:check.png]] 32 GB ||
|-
| HDD || 100 Gb || 100 Gb or more, SDD (Solid State Drives), [http://en.wikipedia.org/wiki/RAID#RAID_1 RAID Type 1] || [[File:check.png]] 2 x 120 GB SSD RAID 1 || all space must be assigned to / partition
|-
| OS || [[Centos_installation | Centos 6]] || x86_64 || [[File:check.png]] Centos 6.2 ||
|-
| Brand|| Any || Intel, DELL, HP, Fujitsu || [[File:check.png]] Intel ||
|}

* [[Centos installation | Centos installation instructions]]

Such server can handle up to 500 concurrent calls if:

* SIP protocol is used
* There's no call transcoding
* GUI, IVR, Recordings and other extra services are not in use
* CPS is low (<5).

We also recommend to have clean server without any additional packets installed.
 
For many servers solution:

'''Asterisk server:''' same requirements as above, except SSD would not increase performance so it is not needed and 4 GB of RAM is sufficient. CPU is most important component here. If Proxy solution is in use, Asterisks cannot be under NAT, it must have Public IP for SIP and RTP traffic.

'''Database server:''' same requirements as above and SSD is highly recommended here. There should be 100GB or more space as database grows fast on high traffic. Fast data storage device and CPU are most important here. If more than one Database server is in use, UPS (Uninterruptible Power Supply) devices must be used for these servers, otherwise power outage would cause broken replication.

'''GUI server:''' same requirements as above, except SSD would not increase performance a lot. HDD with more space is recommended here.

'''Proxy server:''' same requirements as above, except 4 GB of RAM and 40 GB on HDD will be enough here. SSD would not increase performance. Proxy server cannot be under NAT, it must have Public IP for SIP traffic.

'''Redundant servers:''' there are no special requirements on server hardware if server is part of redundant system. However, there are requirements for network to which servers are connected:

* Both servers should be within same subnet.
* Both servers should be able to ''broadcast'' packets to UDP 694 port.
* Both servers should be able to receive packets broadcasted by other server.
* There should be Virtual IP reserved in Subnet.
* Both servers should be able to work with that Virtual IP (only one server at same time).

If any of requirements above are not met, in some cases it is possible to adapt different network configurations or services (like "IP Failover"). However, management/configuration/development of third party software (like special scripts) needed to adapt special solution should be performed by servers owner.

 
= See also =

* [[How fast MOR can perform]]
* [[Stress Test 2012-03-05]]

Recordings Addon

2014-02-04T07:44:56Z

Mantas svelnys: /* Delete recordings after sending it via e-mail */

=Description=

Recordings functionality can be used to record selected users' calls for Monitoring purpose.
 
== Functionality ==

Recording Addon provides this functionality:

* Record User Calls.
* Send a Recording to email.
* Limit space Users' space for Recordings.
* Record Calls without User knowledge.
* Let Users manage their Recordings (send to email/listen/download/delete).
* Convert recordings from WAV to MP3 format and store them on an external server, to ease the load on the main server.

NOTE: Resellers is able to have the same functions as an administrator if '''Allow to use recording functionality''' option is checked by Admin in resellers settings.
 
=== Limitations ===

* Currently it is not possible to record Calls for a Device that is accessed from IVR. If a call goes like this: IVR -> Device, and the device has the option to record calls for this device, these calls will not be recorded.

* Recordings will not be saved on the server if there will be left less then 10% of free space. Such recordings will be sent directly to the Email (if email is specified in GUI Interface) and will be completely removed from the server.
 

=== Sound file format ===

Recordings are saved into mp3 format. 1mb can save around 4min of recordings.
 
=Configuration=

In order to use Recording, you have to set up which Users' Calls you want to record.

Go to '''ADDONS –> Recordings –> Users''' and you will see this window:
 
[[Image:recordings1.png]]
 

Here you can check the '''Forced record calls for this User''' field for the Users you want to record. By checking '''Allow to use recording functionality''' option you can authorize the User to use the Recordings Addon functionality.Click '''Update''' at the bottom for the changes to take effect.

If you leave '''Server space (Mb)''' 0 - there will be no limitations in data usage (HDD will fill up after some time).

If you want to view/listen/download/delete recorded Calls go to '''ADDONS –> Recordings'''. You will see something like this:
 
[[Image:recordings2.png]]
 
'''NOTE''' Recordings are NOT available in Calls between 2 SIP Devices in MOR.
 
== Record not answered calls ==

In order to enable this functionality few changes a needed: 

1) Edit /etc/asterisk/mor.conf 

vi /etc/asterisk/mor.conf

and set '''record_not_answered_calls =''' '''1''' 

This option record_not_answered_calls - save audio to the file while the channel is not answered (not bridged), default 0 (by default records only answered calls).
 

2) Option Show Recordings with zero billsec should be enabled in GUI. 

To enable it go to '''SETTINGS –> Setup –> Visual''' and check option '''Show recordings with zero billsec'''. 
 
[[Image:recordingams.png]]
 
Now system records not answered calls for all users which are using recording functionality. 

Recordings are located in '''ADDONS –> Recordings.''' 

In recording list you will be able to see recordings without duration. 

Such calls were not answered but recorded.
 
[[Image:recordingams2.png]]
 
==Advanced options==

Manage settings for recordings upload to external server go to '''ADDONS –> Recordings –> Settings'''
 
[[File:recordings_settings_path.png]]
 
you will reach settings page
 
[[File:recordings_addon_settings.png]]
 
* Use external Server - should system send recordings to external server?
* Recordings server - details such as IP/Port/Login where port is SSH default port 22 and Login is default root.

'''P.S. SSH keys must be configured without password in order scp command could transfer the recordings to other server. It this functionality is not enabled - the recordings are stored in local server'''
 
== Administrator functionality ==

'''ADDONS –> Recordings'''
 
[[File:Recordings_Addons_Recordings_List.png]]
 
Here the System administrator can see all recordings. He can search Recordings by:

* Period.
* Source (CallerID).
* Destination (Dialed number).
* User.
* Device.

With each recording, it is possible to:

* Check its details.
* Check Call details.
* Add comment to it.
* Listen to it.
* Download it.
* Delete it.

Admin can decide:

* Whether or not the user can use Recording Addon functionality (set to record calls, send recordings to email, etc).
* Which user calls should always be recorded (without user knowledge).
 
'''SETTINGS –> Users –> Edit (on selected user)'''

The Recordings section has the following options:

* Allow to use recording functionality - can this user use the Recording addon functionality?
* Forced record calls for this User - record calls for this user (all devices) without user knowledge.
* Server space - how much HDD space to reserve for recordings of this user.
* Send deleted recordings to this email. If HDD space is used, the recording will be deleted and sent to this email. If this email is empty, the recording will be sent to the default user email.
 
'''Device –> Edit window'''

The following options are available for Device:

* '''Record calls for this Device''' - record calls for this Device (without user knowledge). If this option is enabled, recordings must be deleted manually.
* '''Show Recordings to the User for this Device''' - allows User to see such recordings
* '''Send Recording to Email''' - when recording is completed, send to it email.
* '''Recordings Email''' - send to this email address.
* '''Keep Recordings on Server after sent to Email''' - should the recording be left on the server after being sent to email?
 
[[File:device_recordings_settings.png]]
 

== Recordings bulk management ==

This feature allows an administrator to quickly delete Recordings for selected period or selected Device
 
==== Who can use this functionality? ====

* This feature is only available for MOR administrator
 
==== How to use this functionality ====
Go to '''ADDONS –> Recordings'''
 
[[File:Recordings_menu_path.png]]
 
Click on [[image:icon_edit.png]] '''Bulk management''' link.
 
[[File:Recordings_bulk_management.png]]
 
Here you can check an option to delete by device or by date, select device/date and click '''Delete'''.
 
[[File:Recordings_bulk_management_confirm.png]]
 
Confirm that you really want to delete recordings of selected period/device.
 

= User settings =

The Administrator must authorize the user to use the Recording Addon functionality before User can use its functions. This can be done by checking '''Allow to use recording functionality''' in the User Edit window.
 
'''PERSONAL MENU –> Details'''

* Server space - shows used/reserved HDD space for recordings.
* Email for deleted Recordings - to which email recordings should be sent if there is not enough space for them.
 
'''PERSONAL MENU –> Details –> Devices –> Edit'''

* Record calls for this Device - user can set to record calls for this device or not.
* Send Recording to Email - should recording be sent to email?
* Recordings Email - the email address email to which recordings should be sent.
* Keep Recordings on Server after sent to Email - should recordings be left on the server after being sent to email?
 
'''PERSONAL MENU –> Calls –> Recordings'''

On this page, the User can manage his recordings.
 
= Guides =

== Setup user so he could see his recorded calls ==

1. As admin, go to '''User Edit''' settings [[Image:icon_edit.png]] and check '''Allow to use recording functionality'''. User will be able to use Recording addon functionality.

2. Log in as this User and in '''PERSONAL MENU –> Details –> Devices''', click [[Image:icon_edit.png]] for Device and in the Recordings section check '''Record calls for this Device: YES.'''

3. Now the user will be able to see his calls in '''PERSONAL MENU –> Call –> Recordings'''.
 

== Delete recordings after sending it via e-mail ==

1. As admin, go to '''User Edit''' settings [[Image:icon_edit.png]] and check '''Allow to use recording functionality'''. User will be able to use Recording addon functionality. Do not check '''Forced record calls for this User''' because it this way recordings will '''NOT''' be deleted.

2. Log in as this User and in '''PERSONAL MENU –> Personal Details –> Devices''', click [[Image:icon_edit.png]] for Device and in the Recordings section check '''Keep Recordings on Server after sent to Email: NO.'''

3. Now recordings will be deleted immediately after they will be sent via e-mail.
 

=See also=

* [[MOR Addons]]

Recordings Addon

2014-02-04T07:42:03Z

Mantas svelnys: /* Setup user so he could see his recorded calls */

=Description=

Recordings functionality can be used to record selected users' calls for Monitoring purpose.
 
== Functionality ==

Recording Addon provides this functionality:

* Record User Calls.
* Send a Recording to email.
* Limit space Users' space for Recordings.
* Record Calls without User knowledge.
* Let Users manage their Recordings (send to email/listen/download/delete).
* Convert recordings from WAV to MP3 format and store them on an external server, to ease the load on the main server.

NOTE: Resellers is able to have the same functions as an administrator if '''Allow to use recording functionality''' option is checked by Admin in resellers settings.
 
=== Limitations ===

* Currently it is not possible to record Calls for a Device that is accessed from IVR. If a call goes like this: IVR -> Device, and the device has the option to record calls for this device, these calls will not be recorded.

* Recordings will not be saved on the server if there will be left less then 10% of free space. Such recordings will be sent directly to the Email (if email is specified in GUI Interface) and will be completely removed from the server.
 

=== Sound file format ===

Recordings are saved into mp3 format. 1mb can save around 4min of recordings.
 
=Configuration=

In order to use Recording, you have to set up which Users' Calls you want to record.

Go to '''ADDONS –> Recordings –> Users''' and you will see this window:
 
[[Image:recordings1.png]]
 

Here you can check the '''Forced record calls for this User''' field for the Users you want to record. By checking '''Allow to use recording functionality''' option you can authorize the User to use the Recordings Addon functionality.Click '''Update''' at the bottom for the changes to take effect.

If you leave '''Server space (Mb)''' 0 - there will be no limitations in data usage (HDD will fill up after some time).

If you want to view/listen/download/delete recorded Calls go to '''ADDONS –> Recordings'''. You will see something like this:
 
[[Image:recordings2.png]]
 
'''NOTE''' Recordings are NOT available in Calls between 2 SIP Devices in MOR.
 
== Record not answered calls ==

In order to enable this functionality few changes a needed: 

1) Edit /etc/asterisk/mor.conf 

vi /etc/asterisk/mor.conf

and set '''record_not_answered_calls =''' '''1''' 

This option record_not_answered_calls - save audio to the file while the channel is not answered (not bridged), default 0 (by default records only answered calls).
 

2) Option Show Recordings with zero billsec should be enabled in GUI. 

To enable it go to '''SETTINGS –> Setup –> Visual''' and check option '''Show recordings with zero billsec'''. 
 
[[Image:recordingams.png]]
 
Now system records not answered calls for all users which are using recording functionality. 

Recordings are located in '''ADDONS –> Recordings.''' 

In recording list you will be able to see recordings without duration. 

Such calls were not answered but recorded.
 
[[Image:recordingams2.png]]
 
==Advanced options==

Manage settings for recordings upload to external server go to '''ADDONS –> Recordings –> Settings'''
 
[[File:recordings_settings_path.png]]
 
you will reach settings page
 
[[File:recordings_addon_settings.png]]
 
* Use external Server - should system send recordings to external server?
* Recordings server - details such as IP/Port/Login where port is SSH default port 22 and Login is default root.

'''P.S. SSH keys must be configured without password in order scp command could transfer the recordings to other server. It this functionality is not enabled - the recordings are stored in local server'''
 
== Administrator functionality ==

'''ADDONS –> Recordings'''
 
[[File:Recordings_Addons_Recordings_List.png]]
 
Here the System administrator can see all recordings. He can search Recordings by:

* Period.
* Source (CallerID).
* Destination (Dialed number).
* User.
* Device.

With each recording, it is possible to:

* Check its details.
* Check Call details.
* Add comment to it.
* Listen to it.
* Download it.
* Delete it.

Admin can decide:

* Whether or not the user can use Recording Addon functionality (set to record calls, send recordings to email, etc).
* Which user calls should always be recorded (without user knowledge).
 
'''SETTINGS –> Users –> Edit (on selected user)'''

The Recordings section has the following options:

* Allow to use recording functionality - can this user use the Recording addon functionality?
* Forced record calls for this User - record calls for this user (all devices) without user knowledge.
* Server space - how much HDD space to reserve for recordings of this user.
* Send deleted recordings to this email. If HDD space is used, the recording will be deleted and sent to this email. If this email is empty, the recording will be sent to the default user email.
 
'''Device –> Edit window'''

The following options are available for Device:

* '''Record calls for this Device''' - record calls for this Device (without user knowledge). If this option is enabled, recordings must be deleted manually.
* '''Show Recordings to the User for this Device''' - allows User to see such recordings
* '''Send Recording to Email''' - when recording is completed, send to it email.
* '''Recordings Email''' - send to this email address.
* '''Keep Recordings on Server after sent to Email''' - should the recording be left on the server after being sent to email?
 
[[File:device_recordings_settings.png]]
 

== Recordings bulk management ==

This feature allows an administrator to quickly delete Recordings for selected period or selected Device
 
==== Who can use this functionality? ====

* This feature is only available for MOR administrator
 
==== How to use this functionality ====
Go to '''ADDONS –> Recordings'''
 
[[File:Recordings_menu_path.png]]
 
Click on [[image:icon_edit.png]] '''Bulk management''' link.
 
[[File:Recordings_bulk_management.png]]
 
Here you can check an option to delete by device or by date, select device/date and click '''Delete'''.
 
[[File:Recordings_bulk_management_confirm.png]]
 
Confirm that you really want to delete recordings of selected period/device.
 

= User settings =

The Administrator must authorize the user to use the Recording Addon functionality before User can use its functions. This can be done by checking '''Allow to use recording functionality''' in the User Edit window.
 
'''PERSONAL MENU –> Details'''

* Server space - shows used/reserved HDD space for recordings.
* Email for deleted Recordings - to which email recordings should be sent if there is not enough space for them.
 
'''PERSONAL MENU –> Details –> Devices –> Edit'''

* Record calls for this Device - user can set to record calls for this device or not.
* Send Recording to Email - should recording be sent to email?
* Recordings Email - the email address email to which recordings should be sent.
* Keep Recordings on Server after sent to Email - should recordings be left on the server after being sent to email?
 
'''PERSONAL MENU –> Calls –> Recordings'''

On this page, the User can manage his recordings.
 
= Guides =

== Setup user so he could see his recorded calls ==

1. As admin, go to '''User Edit''' settings [[Image:icon_edit.png]] and check '''Allow to use recording functionality'''. User will be able to use Recording addon functionality.

2. Log in as this User and in '''PERSONAL MENU –> Details –> Devices''', click [[Image:icon_edit.png]] for Device and in the Recordings section check '''Record calls for this Device: YES.'''

3. Now the user will be able to see his calls in '''PERSONAL MENU –> Call –> Recordings'''.
 

== Delete recordings after sending it via e-mail ==

1. As admin, go to '''User Edit''' settings [[Image:icon_edit.png]] and check '''Allow to use recording functionality'''. User will be able to use Recording addon functionality.

2. Log in as this User and in '''PERSONAL MENU –> Personal Details –> Devices''', click [[Image:icon_edit.png]] for Device and in the Recordings section check '''Keep Recordings on Server after sent to Email: NO.'''

3. Now recordings will be deleted immediately after they will be sent via e-mail.
 

=See also=

* [[MOR Addons]]

Heartbeat configuration

2014-01-22T16:14:11Z

Mantas svelnys:

'''What is High availability?'''

High availability is a system design protocol and associated implementation that ensures a certain absolute degree of operational continuity during a given measurement period.

Lets say you have two servers 'A' and 'B' with MOR installed, MySQL is running replication between them. By default all trafic comming to server 'A' is monitored by server 'B', so when server 'A' fails, server 'B' stands in its position by given time.

So allmost no data is lost, and your users will be happy with your services.

[[File:Hearbeat_example.jpg]]

'''What is Heartbeat?'''

Heartbeat is software which implements these monitoring and availability features for your servers. It must be carrefully installed, configured and tested on both servers to ensure correct producing of services.

'''What do you need to know before starting'''

Please review once more the provided above scheme. It represents a typical Linux Heartbeat configuration. Before starting you have to be aware of 4 main points:

1. All public IP addresses have to be on same subnet. 
2. [http://en.wikipedia.org/wiki/Virtual_IP_address Virtual IP] has to be free (not assigned to any device on the network) and the last octet of the address (in this case .4 is the last octet) has to be the highest in the configuration. Server A and B have to be on "lower" IP, in this case .2 and .3 (the last octet). 
3. Never use servers when they are off-line as it will ruin the MySQL replication. 
4. After heartbeat configuration has been made, do not change the addressing scheme or the host-names of the servers. 

'''Installation'''

Hearbeat 2.99 has been full tested on Centos 5.2 only, there is no guarantee that it will work on older versions or distros.

Download mor install scripts from svn. in both servers.

Run /usr/src/mor/sh_scripts/install_heartbeat.sh in both servers

Script will:

* download special file, then yum automaticaly install correct heartbeat files for your system.
* install pacemaker, its future only.
* configure /etc/ha.d/authkeys so you don't need to change anything here
* configure /etc/ha.d/ha.cf file, but you still need adjust it by hand (how? later on this page).
* configure /etc/ha.d/haresources file, but you still need to change few bits there, also, later on this page.
* add 2 lines to /etc/hosts, but just for testing purporses only, so you will have to change ips here.

'''ATTENTION''': if you installed Heartbeat manually, please make sure that you have '''same version of Heartbeat on both servers'''. You will probably need same Centos version on both servers to do that.

'''Configuration'''

'''Before going further, you need to setup hostname of both servers. Make sure master will have node01 and slave node02. (uname -n) must return correct words.'''

Make sure to remove all services which are related to Heartbeat from the runlevels:

chkconfig --list

If you want to remove some service (for example asterisk):

chkconfig --del asterisk

Edit /etc/sysconfig/network to change your hostname. Then reboot your machine.

First configure master (node01):

Open /etc/hosts and you will see something like this:

203.0.113.2 node01 #change to correct IP
203.0.113.3 node02 #change to correct IP here aswell

Change ip of node01 of master machine, which "accept all incoming traffic by default".

And change ip to slave, witch will "accept all data, if master will die"

Open /etc/ha.d/ha.cf and change:

Deadtime higher or lower setting. Deadtime means how many seconds have to pass before take over job from master.

Remember, this should be lower on on "lightly" loaded machines, and higher and "highly" loaded machines.

Deadtime 10 is more than enough. (Default is 5)

Make sure you add 2 network interfaces for heartbeat broadcasts.

The bcast directive is used to configure which interfaces Heartbeat sends UDP broadcast traffic on.

For example 'bcast eth0 eth1'.

The udpport directive is used to configure which port is used for these broadcast communications if the
udpport directive is specified before the bcast directive, otherwise the default port will be used.

Now open /etc/ha.d/haresources (be sure to leave only the lines given below):

node01 203.0.113.4 asterisk # just for testing, remember this ip can't be used in your network!!!

Or

node01 IPaddr::192.168.0.142/24/eth0:0 httpd # just for testing, remember this ip can't be used in your network!!! # if eth0:0 does not appear

So, first of all:

Assuming node01 is master and node02 is slave, by default all traffic is going to node01.

You need to choose IP (for Virtual IP) from your network and never use it, otherwise this will lead to unexpected results.

node01 203.0.113.4 asterisk, "if master is dead, slave (node02) will restart asterisk and start to accept traffic comming from 203.0.113.4"

Now copy all configuration to slave (node02).

shell@node01:/$ scp -r /etc/ha.d/ root@node02:/etc/

Start heartbeat on both servers by running /etc/init.d/heartbeat start. If everything will be ok, you will see something like this:

Starting High-Availability services:

2008/12/18_18:13:22 INFO: Resource is stopped

[ OK ]

Do not forget to remove Asterisk from system startup, because it needs to be started by Heartbeat:
chkconfig asterisk off
on both servers.

'''Testing'''

Now run iptraf on both machines, from another machine start pinging your binded IP address (in this example we speak about 203.0.113.4).

Check for masters iptraf window, you will see incoming ICMP data, slave have to be quiet.

[[Image:heartbeat1.png]]

Now kill master (for example: ifconfig eth0 down or issue a reboot), after short period of time (on this example 5 seconds) on slave you will see incoming ICMP packets.

To bring master to work again, first of all you have to configure network on master and start heartbeat. After 20~ seconds master have to start doing his job again.

Now go to GUI and change your default asterisk server IP (Settings -> Servers), change from 127.0.0.1 to virtual IP address. If your GUI is unable connect to them, make sure both asterisk servers allow connections from your GUI server. (file: /etc/asterisk/manager.conf)

= sip.conf =

In file '''/etc/asterisk/sip.conf''' enter correct IP for value '''bindaddr''', correct IP = IP to which your devices are registering. E.g. Virtual IP.

Do same changes for bindaddr in iax.conf, h323.conf and manager.conf

[[How to restart Asterisk server|Restart Asterisk]]

Make this on both servers.

= mor.conf =

On slave server go to '''/etc/asterisk/mor.conf''' and set '''server_id = 2''' (default is 1)

= Possible problems =

Look at the picture:
 
[[File:Heartbeat_broadcast.jpg]]
 
In this example HeartBeat in bcast directive has only one interface configured on both servers: eth1

This can lead to problems if the link eth1 <----> eth1 between the servers fails (broken cable, switch, NIC, etc)

'''You must specify at least 2 interfaces in bcast directive'''

The bcast directive is used to configure which interfaces Heartbeat sends UDP broadcast traffic on.

An example of bcast directive:
bcast eth0 eth1
 

== Virtual interface does not appear ==

Check /var/log/heartbeat.log

If you can see something like:

...
ResourceManager(default)[6106]: 2012/12/07_11:33:51 info: Running /etc/ha.d/resource.d/IPaddr 123.123.123.123 start
IPaddr(IPaddr_123.123.123.123)[6197]: 2012/12/07_11:33:51 ERROR: /usr/lib64/heartbeat/findif failed [rc=1].
/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_123.123.123.123)[6183]: 2012/12/07_11:33:51 ERROR: Generic error
...

Please add subnet mask and interface to /etc/ha.d/haresources like this:

node01 123.123.123.123/27/em1 asterisk

 

== Heartbeat service does not start ==

There is known bug with resource-agents-3.9.2-21.el6_4.8.x86_64 package.

Solution:

rpm -el --nodeps resource-agents-3.9.2-21.el6_4.8.x86_64
yum install -y resource-agents-3.9.2-21.el6_4.3.x86_64

More details:
http://bugs.centos.org/view.php?id=6727

= See also =

[[High availability (Heartbeat clustering)]]

http://www.linux-ha.org/wiki/Haresources

Digits sound files

2014-01-16T07:16:42Z

Mantas svelnys: /* Necessary files */

=== Necessary files ===

<table border=1>
<tr><th>File name</th><th>What it says</th></tr>
<tr> <td> 0 </td> <td> Zero </td></tr>
<tr> <td> 10 </td> <td> Ten </td></tr>
<tr> <td> 11 </td> <td> Eleven </td></tr>
<tr> <td> 12 </td> <td> Twelve </td></tr>
<tr> <td> 13 </td> <td> Thirteen </td></tr>
<tr> <td> 14 </td> <td> Fourteen </td></tr>
<tr> <td> 15 </td> <td> Fifteen </td></tr>
<tr> <td> 16 </td> <td> Sixteen </td></tr>
<tr> <td> 17 </td> <td> Seventeen </td></tr>
<tr> <td> 18 </td> <td> Eighteen </td></tr>
<tr> <td> 19 </td> <td> Nineteen </td></tr>
<tr> <td> 1 </td> <td> One </td></tr>
<tr> <td> 20 </td> <td> Twenty </td></tr>
<tr> <td> 2 </td> <td> Two </td></tr>
<tr> <td> 30 </td> <td> Thirty </td></tr>
<tr> <td> 3 </td> <td> Three </td></tr>
<tr> <td> 40 </td> <td> Forty </td></tr>
<tr> <td> 4 </td> <td> Four </td></tr>
<tr> <td> 50 </td> <td> Fifty </td></tr>
<tr> <td> 5 </td> <td> Five </td></tr>
<tr> <td> 60 </td> <td> Sixty </td></tr>
<tr> <td> 6 </td> <td> Six </td></tr>
<tr> <td> 70 </td> <td> Seventy </td></tr>
<tr> <td> 7 </td> <td> Seven </td></tr>
<tr> <td> 80 </td> <td> Eighty </td></tr>
<tr> <td> 8 </td> <td> Eight </td></tr>
<tr> <td> 90 </td> <td> Ninety </td></tr>
<tr> <td> 9 </td> <td> Nine </td></tr>
<tr> <td> a-m </td> <td> A M </td></tr>
<tr> <td> at </td> <td> At </td></tr>
<tr> <td> billion </td> <td> Billion </td></tr>
<tr> <td> day-0 </td> <td> Sunday </td></tr>
<tr> <td> day-1 </td> <td> Monday </td></tr>
<tr> <td> day-2 </td> <td> Tuesday </td></tr>
<tr> <td> day-3 </td> <td> Wednesday </td></tr>
<tr> <td> day-4 </td> <td> Thursday </td></tr>
<tr> <td> day-5 </td> <td> Friday </td></tr>
<tr> <td> day-6 </td> <td> Saturday </td></tr>
<tr> <td> dollars </td> <td> Dollars </td></tr>
<tr> <td> h-10 </td> <td> Tenth </td></tr>
<tr> <td> h-11 </td> <td> Eleventh </td></tr>
<tr> <td> h-12 </td> <td> Twelfth </td></tr>

<tr> <td> h-13 </td> <td> Thirteenth </td></tr>
<tr> <td> h-14 </td> <td> Fourteenth </td></tr>
<tr> <td> h-15 </td> <td> Fifteenth </td></tr>
<tr> <td> h-16 </td> <td> Sixteenth </td></tr>
<tr> <td> h-17 </td> <td> Seventeenth </td></tr>
<tr> <td> h-18 </td> <td> Eighteenth </td></tr>
<tr> <td> h-19 </td> <td> Nineteenth </td></tr>
<tr> <td> h-1 </td> <td> First </td></tr>
<tr> <td> h-20</td> <td> Twentieth </td></tr>
<tr> <td> h-2 </td> <td> Second </td></tr>
<tr> <td> h-30 </td> <td> Thirtieth </td></tr>
<tr> <td> h-3 </td> <td> Third </td></tr>
<tr> <td> h-40 </td> <td> Fortieth </td></tr>
<tr> <td> h-4 </td> <td> Fourth </td></tr>
<tr> <td> h-50 </td> <td> Fiftieth </td></tr>
<tr> <td> h-5 </td> <td> Fifth </td></tr>
<tr> <td> h-60 </td> <td> Sixtieth </td></tr>
<tr> <td> h-6 </td> <td> Sixth </td></tr>
<tr> <td> h-70 </td> <td> Seventieth </td></tr>
<tr> <td> h-7 </td> <td> Seventh </td></tr>
<tr> <td> h-80 </td> <td> Eightieth </td></tr>
<tr> <td> h-8</td> <td> Eighth </td></tr>
<tr> <td> h-90 </td> <td> Ninetieth </td></tr>
<tr> <td> h-9 </td> <td> Ninth </td></tr>
<tr> <td> h-billion </td> <td> Billionth </td></tr>
<tr> <td> h-hundred </td> <td> Hundredth </td></tr>
<tr> <td> h-million </td> <td> Millionth </td></tr>
<tr> <td> h-thousand </td> <td> Thousandth </td></tr>
<tr> <td> hundred </td> <td> Hundred </td></tr>
<tr> <td> million </td> <td> Million </td></tr>
<tr> <td> minus </td> <td> Minus </td></tr>
<tr> <td> mon-0 </td> <td> January </td></tr>
<tr> <td> mon-10 </td> <td> November </td></tr>
<tr> <td> mon-11 </td> <td> December </td></tr>
<tr> <td> mon-1 </td> <td> February </td></tr>
<tr> <td> mon-2 </td> <td> March </td></tr>
<tr> <td> mon-3 </td> <td> April </td></tr>
<tr> <td> mon-4 </td> <td> May </td></tr>
<tr> <td> mon-5 </td> <td> June </td></tr>
<tr> <td> mon-6 </td> <td> July </td></tr>
<tr> <td> mon-7 </td> <td> August </td></tr>
<tr> <td> mon-8 </td> <td> September </td></tr>

<tr> <td> mon-9 </td> <td> October </td></tr>
<tr> <td> oclock </td> <td> O'Clock </td></tr>
<tr> <td> oh </td> <td> Oh </td></tr>
<tr> <td> p-m </td> <td> P M </td></tr>
<tr> <td> pound </td> <td> Pound </td></tr>
<tr> <td> star </td> <td> Star </td></tr>
<tr> <td> thousand </td> <td> Thousand </td></tr>
<tr> <td> today </td> <td> Today </td></tr>
<tr> <td> tomorrow </td> <td> Tomorrow </td></tr>
<tr> <td> yesterday </td> <td> Yesterday </td></tr>
</table>

Digits sound files

2014-01-16T07:15:41Z

Mantas svelnys: /* Necessary files */

=== Necessary files ===

<table border=1>
<tr><th>File name</th><th>What it says</th></tr>
<tr> <td> 0.gsm </td> <td> Zero </td></tr>
<tr> <td> 10.gsm </td> <td> Ten </td></tr>
<tr> <td> 11.gsm </td> <td> Eleven </td></tr>
<tr> <td> 12.gsm </td> <td> Twelve </td></tr>
<tr> <td> 13.gsm </td> <td> Thirteen </td></tr>
<tr> <td> 14.gsm </td> <td> Fourteen </td></tr>
<tr> <td> 15.gsm </td> <td> Fifteen </td></tr>
<tr> <td> 16.gsm </td> <td> Sixteen </td></tr>
<tr> <td> 17.gsm </td> <td> Seventeen </td></tr>
<tr> <td> 18.gsm </td> <td> Eighteen </td></tr>
<tr> <td> 19.gsm </td> <td> Nineteen </td></tr>
<tr> <td> 1.gsm </td> <td> One </td></tr>
<tr> <td> 20.gsm </td> <td> Twenty </td></tr>
<tr> <td> 2.gsm </td> <td> Two </td></tr>
<tr> <td> 30.gsm </td> <td> Thirty </td></tr>
<tr> <td> 3.gsm </td> <td> Three </td></tr>
<tr> <td> 40.gsm </td> <td> Forty </td></tr>
<tr> <td> 4.gsm </td> <td> Four </td></tr>
<tr> <td> 50.gsm </td> <td> Fifty </td></tr>
<tr> <td> 5.gsm </td> <td> Five </td></tr>
<tr> <td> 60.gsm </td> <td> Sixty </td></tr>
<tr> <td> 6.gsm </td> <td> Six </td></tr>
<tr> <td> 70.gsm </td> <td> Seventy </td></tr>
<tr> <td> 7.gsm </td> <td> Seven </td></tr>
<tr> <td> 80.gsm </td> <td> Eighty </td></tr>
<tr> <td> 8.gsm </td> <td> Eight </td></tr>
<tr> <td> 90.gsm </td> <td> Ninety </td></tr>
<tr> <td> 9.gsm </td> <td> Nine </td></tr>
<tr> <td> a-m.gsm </td> <td> A M </td></tr>
<tr> <td> at.gsm </td> <td> At </td></tr>
<tr> <td> billion.gsm </td> <td> Billion </td></tr>
<tr> <td> day-0.gsm </td> <td> Sunday </td></tr>
<tr> <td> day-1.gsm </td> <td> Monday </td></tr>
<tr> <td> day-2.gsm </td> <td> Tuesday </td></tr>
<tr> <td> day-3.gsm </td> <td> Wednesday </td></tr>
<tr> <td> day-4.gsm </td> <td> Thursday </td></tr>
<tr> <td> day-5.gsm </td> <td> Friday </td></tr>
<tr> <td> day-6.gsm </td> <td> Saturday </td></tr>
<tr> <td> dollars.gsm </td> <td> Dollars </td></tr>
<tr> <td> h-10.gsm </td> <td> Tenth </td></tr>
<tr> <td> h-11.gsm </td> <td> Eleventh </td></tr>
<tr> <td> h-12.gsm </td> <td> Twelfth </td></tr>

<tr> <td> h-13.gsm </td> <td> Thirteenth </td></tr>
<tr> <td> h-14.gsm </td> <td> Fourteenth </td></tr>
<tr> <td> h-15.gsm </td> <td> Fifteenth </td></tr>
<tr> <td> h-16.gsm </td> <td> Sixteenth </td></tr>
<tr> <td> h-17.gsm </td> <td> Seventeenth </td></tr>
<tr> <td> h-18.gsm </td> <td> Eighteenth </td></tr>
<tr> <td> h-19.gsm </td> <td> Nineteenth </td></tr>
<tr> <td> h-1.gsm </td> <td> First </td></tr>
<tr> <td> h-20.gsm</td> <td> Twentieth </td></tr>
<tr> <td> h-2.gsm </td> <td> Second </td></tr>
<tr> <td> h-30.gsm </td> <td> Thirtieth </td></tr>
<tr> <td> h-3.gsm </td> <td> Third </td></tr>
<tr> <td> h-40.gsm </td> <td> Fortieth </td></tr>
<tr> <td> h-4.gsm </td> <td> Fourth </td></tr>
<tr> <td> h-50.gsm </td> <td> Fiftieth </td></tr>
<tr> <td> h-5.gsm </td> <td> Fifth </td></tr>
<tr> <td> h-60.gsm </td> <td> Sixtieth </td></tr>
<tr> <td> h-6.gsm </td> <td> Sixth </td></tr>
<tr> <td> h-70.gsm </td> <td> Seventieth </td></tr>
<tr> <td> h-7.gsm </td> <td> Seventh </td></tr>
<tr> <td> h-80.gsm </td> <td> Eightieth </td></tr>
<tr> <td> h-8.gsm</td> <td> Eighth </td></tr>
<tr> <td> h-90.gsm </td> <td> Ninetieth </td></tr>
<tr> <td> h-9.gsm </td> <td> Ninth </td></tr>
<tr> <td> h-billion.gsm </td> <td> Billionth </td></tr>
<tr> <td> h-hundred.gsm </td> <td> Hundredth </td></tr>
<tr> <td> h-million.gsm </td> <td> Millionth </td></tr>
<tr> <td> h-thousand.gsm </td> <td> Thousandth </td></tr>
<tr> <td> hundred.gsm </td> <td> Hundred </td></tr>
<tr> <td> million.gsm </td> <td> Million </td></tr>
<tr> <td> minus.gsm </td> <td> Minus </td></tr>
<tr> <td> mon-0.gsm </td> <td> January </td></tr>
<tr> <td> mon-10.gsm </td> <td> November </td></tr>
<tr> <td> mon-11.gsm </td> <td> December </td></tr>
<tr> <td> mon-1.gsm </td> <td> February </td></tr>
<tr> <td> mon-2.gsm </td> <td> March </td></tr>
<tr> <td> mon-3.gsm </td> <td> April </td></tr>
<tr> <td> mon-4.gsm </td> <td> May </td></tr>
<tr> <td> mon-5.gsm </td> <td> June </td></tr>
<tr> <td> mon-6.gsm </td> <td> July </td></tr>
<tr> <td> mon-7.gsm </td> <td> August </td></tr>
<tr> <td> mon-8.gsm </td> <td> September </td></tr>

<tr> <td> mon-9.gsm </td> <td> October </td></tr>
<tr> <td> oclock.gsm </td> <td> O'Clock </td></tr>
<tr> <td> oh.gsm </td> <td> Oh </td></tr>
<tr> <td> p-m.gsm </td> <td> P M </td></tr>
<tr> <td> pound.gsm </td> <td> Pound </td></tr>
<tr> <td> star.gsm </td> <td> Star </td></tr>
<tr> <td> thousand.gsm </td> <td> Thousand </td></tr>
<tr> <td> today.gsm </td> <td> Today </td></tr>
<tr> <td> tomorrow.gsm </td> <td> Tomorrow </td></tr>
<tr> <td> yesterday.gsm </td> <td> Yesterday </td></tr>
</table>

Digits sound files

2014-01-16T07:14:08Z

Mantas svelnys: /* Necessary files */

=== Necessary files ===

<table border=1>
<tr><th>File name</th><th>What it says</th></tr>
<tr> <td> 0.gsm </td> <td> Zero </td></tr>
<tr> <td> 10.gsm </td> <td> Ten </td></tr>
<tr> <td> 11.gsm </td> <td> Eleven </td></tr>
<tr> <td> 12.gsm </td> <td> Twelve </td></tr>
<tr> <td> 13.gsm </td> <td> Thirteen </td></tr>
<tr> <td> 14.gsm </td> <td> Fourteen </td></tr>
<tr> <td> 15.gsm </td> <td> Fifteen </td></tr>
<tr> <td> 16.gsm </td> <td> Sixteen </td></tr>
<tr> <td> 17.gsm </td> <td> Seventeen </td></tr>
<tr> <td> 18.gsm </td> <td> Eighteen </td></tr>
<tr> <td> 19.gsm </td> <td> Nineteen </td></tr>
<tr> <td> 1.gsm </td> <td> One </td></tr>
<tr> <td> 20.gsm </td> <td> Twenty </td></tr>
<tr> <td> 2.gsm </td> <td> Two </td></tr>
<tr> <td> 30.gsm </td> <td> Thirty </td></tr>
<tr> <td> 3.gsm </td> <td> Three </td></tr>
<tr> <td> 40.gsm </td> <td> Forty </td></tr>
<tr> <td> 4.gsm </td> <td> Four </td></tr>
<tr> <td> 50.gsm </td> <td> Fifty </td></tr>
<tr> <td> 5.gsm </td> <td> Five </td></tr>
<tr> <td> 60.gsm </td> <td> Sixty </td></tr>
<tr> <td> 6.gsm </td> <td> Six </td></tr>
<tr> <td> 70.gsm </td> <td> Seventy </td></tr>
<tr> <td> 7.gsm </td> <td> Seven </td></tr>
<tr> <td> 80.gsm </td> <td> Eighty </td></tr>
<tr> <td> 8.gsm </td> <td> Eight </td></tr>
<tr> <td> 90.gsm </td> <td> Ninety </td></tr>
<tr> <td> 9.gsm </td> <td> Nine </td></tr>
<tr> <td> a-m.gsm </td> <td> A M </td></tr>
<tr> <td> at.gsm </td> <td> At </td></tr>
<tr> <td> billion.gsm </td> <td> Billion </td></tr>
<tr> <td> day-0.gsm </td> <td> Sunday </td></tr>
<tr> <td> day-1.gsm </td> <td> Monday </td></tr>
<tr> <td> day-2.gsm </td> <td> Tuesday </td></tr>
<tr> <td> day-3.gsm </td> <td> Wednesday </td></tr>
<tr> <td> day-4.gsm </td> <td> Thursday </td></tr>
<tr> <td> day-5.gsm </td> <td> Friday </td></tr>
<tr> <td> day-6.gsm </td> <td> Saturday </td></tr>
<tr> <td> dollars.gsm </td> <td> Dollars </td></tr>
<tr> <td> h-10.gsm </td> <td> Tenth </td></tr>
<tr> <td> h-11.gsm </td> <td> Eleventh </td></tr>
<tr> <td> h-12.gsm </td> <td> Twelfth </td></tr>

<tr> <td> h-13.gsm </td> <td> Thirteenth </td></tr>
<tr> <td> h-14.gsm </td> <td> Fourteenth </td></tr>
<tr> <td> h-15.gsm </td> <td> Fifteenth </td></tr>
<tr> <td> h-16.gsm </td> <td> Sixteenth </td></tr>
<tr> <td> h-17.gsm </td> <td> Seventeenth </td></tr>
<tr> <td> h-18.gsm </td> <td> Eighteenth </td></tr>
<tr> <td> h-19.gsm </td> <td> Nineteenth </td></tr>
<tr> <td> h-1.gsm </td> <td> First </td></tr>
<tr> <td> h-20.gsm</td> <td> Twentieth </td></tr>
<tr> <td> h-2.gsm </td> <td> Second </td></tr>
<tr> <td> h-30.gsm </td> <td> Thirtieth </td></tr>
<tr> <td> h-3.gsm </td> <td> Third </td></tr>
<tr> <td> h-40.gsm </td> <td> Fortieth </td></tr>
<tr> <td> h-4.gsm </td> <td> Fourth </td></tr>
<tr> <td> h-50.gsm </td> <td> Fiftieth </td></tr>
<tr> <td> h-5.gsm </td> Fifth <td> </td></tr>
<tr> <td> h-60.gsm </td> <td> Sixtieth </td></tr>
<tr> <td> h-6.gsm </td> <td> Sixth </td></tr>
<tr> <td> h-70.gsm </td> <td> Seventieth </td></tr>
<tr> <td> h-7.gsm </td> <td> Seventh </td></tr>
<tr> <td> h-80.gsm </td> <td> Eightieth </td></tr>
<tr> <td> h-8.gsm</td> <td> Eighth </td></tr>
<tr> <td> h-90.gsm </td> <td> Ninetieth </td></tr>
<tr> <td> h-9.gsm </td> <td> Ninth </td></tr>
<tr> <td> h-billion.gsm </td> <td> Billionth </td></tr>
<tr> <td> h-hundred.gsm </td> <td> Hundredth </td></tr>
<tr> <td> h-million.gsm </td> <td> Millionth </td></tr>
<tr> <td> h-thousand.gsm </td> <td> Thousandth </td></tr>
<tr> <td> hundred.gsm </td> <td> Hundred </td></tr>
<tr> <td> million.gsm </td> <td> Million </td></tr>
<tr> <td> minus.gsm </td> <td> Minus </td></tr>
<tr> <td> mon-0.gsm </td> <td> January </td></tr>
<tr> <td> mon-10.gsm </td> <td> November </td></tr>
<tr> <td> mon-11.gsm </td> <td> December </td></tr>
<tr> <td> mon-1.gsm </td> <td> February </td></tr>
<tr> <td> mon-2.gsm </td> <td> March </td></tr>
<tr> <td> mon-3.gsm </td> <td> April </td></tr>
<tr> <td> mon-4.gsm </td> <td> May </td></tr>
<tr> <td> mon-5.gsm </td> <td> June </td></tr>
<tr> <td> mon-6.gsm </td> <td> July </td></tr>
<tr> <td> mon-7.gsm </td> <td> August </td></tr>
<tr> <td> mon-8.gsm </td> <td> September </td></tr>

<tr> <td> mon-9.gsm </td> <td> October </td></tr>
<tr> <td> oclock.gsm </td> <td> O'Clock </td></tr>
<tr> <td> oh.gsm </td> <td> Oh </td></tr>
<tr> <td> p-m.gsm </td> <td> P M </td></tr>
<tr> <td> pound.gsm </td> <td> Pound </td></tr>
<tr> <td> star.gsm </td> <td> Star </td></tr>
<tr> <td> thousand.gsm </td> <td> Thousand </td></tr>
<tr> <td> today.gsm </td> <td> Today </td></tr>
<tr> <td> tomorrow.gsm </td> <td> Tomorrow </td></tr>
<tr> <td> yesterday.gsm </td> <td> Yesterday </td></tr>
</table>

Digits sound files

2014-01-16T06:04:33Z

Mantas svelnys: /* Necessary files */

=== Necessary files ===

<table border=1>
<tr><th>File name</th><th>What it says</th></tr>
<tr> <td> 0.gsm </td> <td> ...and... </td></tr>
<tr> <td> 10.gsm </td> <td> Authorization failed. </td></tr>
<tr> <td> 11.gsm </td> <td> Your balance is empty. </td></tr>
<tr> <td> 12.gsm </td> <td> The number is busy. </td></tr>
<tr> <td> 13.gsm </td> <td> Press one to enter new number. Press two to redial same number. Press three to check your balance. Press four to use new card. Press five to increase your calling card balance by using another card. </td></tr>
<tr> <td> 14.gsm </td> <td> Card expired. </td></tr>
<tr> <td> 15.gsm </td> <td> Card is empty. </td></tr>
<tr> <td> 16.gsm </td> <td> Card is not sold yet. </td></tr>
<tr> <td> 17.gsm </td> <td> Card not found. </td></tr>
<tr> <td> 18.gsm </td> <td> Dialing previous number... </td></tr>
<tr> <td> 19.gsm </td> <td> Please enter your card number: </td></tr>
<tr> <td> 1.gsm </td> <td> Please enter your card and pin number: </td></tr>
<tr> <td> 20.gsm </td> <td> Please enter your pin number: </td></tr>
<tr> <td> 2.gsm </td> <td> Goodbye. </td></tr>
<tr> <td> 30.gsm </td> <td> Please enter your callerID number </td></tr>
<tr> <td> 3.gsm </td> <td> You have entered nothing. </td></tr>
<tr> <td> 40.gsm </td> <td> Please enter the number you wish to call followed by the hash (#) key. If making an international call include the international code. </td></tr>
<tr> <td> 4.gsm </td> <td> The number is unreachable. </td></tr>
<tr> <td> 50.gsm </td> <td> Please enter your PIN number. </td></tr>
<tr> <td> 5.gsm </td> <td> Please enter voucher number. </td></tr>
<tr> <td> 60.gsm </td> <td> ...cents. </td></tr>
<tr> <td> 6.gsm </td> <td> ...euros... </td></tr>
<tr> <td> 70.gsm </td> <td> ...euro... </td></tr>
<tr> <td> 7.gsm </td> <td> ...pence. </td></tr>
<tr> <td> 80.gsm </td> <td> ...pounds... </td></tr>
<tr> <td> 8.gsm </td> <td> ...pound... </td></tr>
<tr> <td> 90.gsm </td> <td> ...hour... </td></tr>
<tr> <td> 9.gsm </td> <td> ...hours... </td></tr>
<tr> <td> a-m.gsm </td> <td> You have... </td></tr>
<tr> <td> at.gsm </td> <td> Your balance was increased by... </td></tr>
<tr> <td> billion.gsm </td> <td> minus... </td></tr>
<tr> <td> day-0.gsm (says: sunday) </td> <td> ...minute </td></tr>
<tr> <td> day-1.gsm (says: monday) </td> <td> ...minutes </td></tr>
<tr> <td> day-2.gsm (says: tuesday) </td> <td> Press one to enter new destination. Press two to redial same destination. Press three to check your balance. </td></tr>
<tr> <td> day-3.gsm </td> <td> ...seconds. </td></tr>
<tr> <td> day-4.gsm </td> <td> ...unlimited minutes. </td></tr>
<tr> <td> day-5.gsm </td> <td> ...cents. </td></tr>
<tr> <td> day-6.gsm </td> <td> ...dollars... </td></tr>
<tr> <td> dollars.gsm </td> <td> ...dollar... </td></tr>
<tr> <td> h-10.gsm (says: 10th) </td> <td> Voucher not found. </td></tr>
<tr> <td> h-11.gsm </td> <td> Thank you. </td></tr>
<tr> <td> h-12.gsm </td> <td> Your balance was increased by... </td></tr>

<tr> <td> h-13.gsm </td> <td> ...and... </td></tr>
<tr> <td> h-14.gsm </td> <td> Authorization failed. </td></tr>
<tr> <td> h-15.gsm </td> <td> Your balance is empty. </td></tr>
<tr> <td> h-16.gsm </td> <td> The number is busy. </td></tr>
<tr> <td> h-17.gsm </td> <td> Press one to enter new number. Press two to redial same number. Press three to check your balance. Press four to use new card. Press five to increase your calling card balance by using another card. </td></tr>
<tr> <td> h-18.gsm </td> <td> Card expired. </td></tr>
<tr> <td> h-19.gsm </td> <td> Card is empty. </td></tr>
<tr> <td> h-1.gsm (says: 1st) </td> <td> Card is not sold yet. </td></tr>
<tr> <td> h-20.gsm</td> <td> Card not found. </td></tr>
<tr> <td> h-2.gsm </td> <td> Dialing previous number... </td></tr>
<tr> <td> h-30.gsm </td> <td> Please enter your card number: </td></tr>
<tr> <td> h-3.gsm </td> <td> Please enter your card and pin number: </td></tr>
<tr> <td> h-40.gsm </td> <td> Please enter your pin number: </td></tr>
<tr> <td> h-4.gsm </td> <td> Goodbye. </td></tr>
<tr> <td> h-50.gsm </td> <td> Please enter your callerID number </td></tr>
<tr> <td> h-5.gsm </td> <td> You have entered nothing. </td></tr>
<tr> <td> h-60.gsm </td> <td> Please enter the number you wish to call followed by the hash (#) key. If making an international call include the international code. </td></tr>
<tr> <td> h-6.gsm </td> <td> The number is unreachable. </td></tr>
<tr> <td> h-70.gsm </td> <td> Please enter your PIN number. </td></tr>
<tr> <td> h-7.gsm </td> <td> Please enter voucher number. </td></tr>
<tr> <td> h-80.gsm </td> <td> ...cents. </td></tr>
<tr> <td> h-8.gsm</td> <td> ...euros... </td></tr>
<tr> <td> h-90.gsm </td> <td> ...euro... </td></tr>
<tr> <td> h-9.gsm </td> <td> ...pence. </td></tr>
<tr> <td> h-billion.gsm </td> <td> ...pounds... </td></tr>
<tr> <td> h-hundred.gsm (says: 100th) </td> <td> ...pound... </td></tr>
<tr> <td> h-million.gsm </td> <td> ...hour... </td></tr>
<tr> <td> h-thousand.gsm </td> <td> ...hours... </td></tr>
<tr> <td> hundred.gsm </td> <td> You have... </td></tr>
<tr> <td> million.gsm </td> <td> Your balance was increased by... </td></tr>
<tr> <td> minus.gsm </td> <td> minus... </td></tr>
<tr> <td> mon-0.gsm (says: January) (says: sunday) </td> <td> ...minute </td></tr>
<tr> <td> mon-10.gsm </td> <td> ...minutes </td></tr>
<tr> <td> mon-11.gsm </td> <td> Press one to enter new destination. Press two to redial same destination. Press three to check your balance. </td></tr>
<tr> <td> mon-1.gsm </td> <td> ...seconds. </td></tr>
<tr> <td> mon-2.gsm </td> <td> ...unlimited minutes. </td></tr>
<tr> <td> mon-3.gsm </td> <td> ...cents. </td></tr>
<tr> <td> mon-4.gsm </td> <td> ...dollars... </td></tr>
<tr> <td> mon-5.gsm </td> <td> ...dollar... </td></tr>
<tr> <td> mon-6.gsm </td> <td> Voucher not found. </td></tr>
<tr> <td> mon-7.gsm </td> <td> Thank you. </td></tr>
<tr> <td> mon-8.gsm </td> <td> Your balance was increased by... </td></tr>

<tr> <td> mon-9.gsm </td> <td> ...and... </td></tr>
<tr> <td> oclock.gsm </td> <td> Authorization failed. </td></tr>
<tr> <td> oh.gsm </td> <td> Your balance is empty. </td></tr>
<tr> <td> p-m.gsm </td> <td> The number is busy. </td></tr>
<tr> <td> pound.gsm </td> <td> Press one to enter new number. Press two to redial same number. Press three to check your balance. Press four to use new card. Press five to increase your calling card balance by using another card. </td></tr>
<tr> <td> star.gsm </td> <td> Card expired. </td></tr>
<tr> <td> thousand.gsm </td> <td> Card is empty. </td></tr>
<tr> <td> today.gsm </td> <td> Card is not sold yet. </td></tr>
<tr> <td> tomorrow.gsm </td> <td> Card not found. </td></tr>
<tr> <td> yesterday.gsm </td> <td> Dialing previous number... </td></tr>
</table>

Digits sound files

2014-01-15T17:59:49Z

Mantas svelnys: Created page with '=== Necessary files === <table border=1> <tr><th>File name</th><th>What it says</th></tr> <tr> <td> 0.gsm </td> <td> ...and... </td></tr> <tr> <td> 10.gsm </td> <td> Authoriza…'

Sound files

2014-01-15T17:42:58Z

Mantas svelnys: /* Necessary files */

=Description=

[[File:all_flags.png|right|100px]]Sound files used by MOR are located in /var/lib/asterisk/sounds/mor.

To see sound files go to '''SETTINGS''' -> '''Billing''' -> '''DIDs''' -> '''IVR''' -> '''Voices''' and click the ''Sound files'' link:

[[File:Ivr soundfiles.png]]

 
== Currently supported languages ==

* English
* Spanish
* Russian
* French
* Brazilian-Portuguese
* Italian
* German
* Hebrew

* Chinese (partly)
* Vietnamese (partly)

Listen to the voices in: [[MOR IVR Samples]]

 

==Add another language==

 
=== Necessary files ===

<table border=1>
<tr><th>File name</th><th>What it says</th></tr>
<tr> <td> and </td> <td> ...and... </td></tr>
<tr> <td> auth_failed</td> <td> Authorization failed. </td></tr>
<tr> <td> balance_empty</td> <td> Your balance is empty. </td></tr>
<tr> <td>cc_busy</td> <td> The number is busy. </td></tr>
<tr> <td> cc_callingcard_choices</td> <td> Press one to enter new number. Press two to redial same number. Press three to check your balance. Press four to use new card. Press five to increase your calling card balance by using another card. </td></tr>
<tr> <td> cc_card_expired</td> <td> Card expired. </td></tr>
<tr> <td> cc_card_is_empty</td> <td> Card is empty. </td></tr>
<tr> <td> cc_card_is_not_sold_yet</td> <td> Card is not sold yet. </td></tr>
<tr> <td> cc_card_not_found</td> <td> Card not found. </td></tr>
<tr> <td> cc_dialing_previous_number</td> <td> Dialing previous number... </td></tr>
<tr> <td> cc_enter_card_number</td> <td> Please enter your card number: </td></tr>
<tr> <td> cc_enter_card_number_pin</td> <td> Please enter your card and pin number: </td></tr>
<tr> <td> cc_enter_pin</td> <td> Please enter your pin number: </td></tr>
<tr> <td> cc_goodbye</td> <td> Goodbye. </td></tr>
<tr> <td> cc_please_enter_callerid_number</td> <td> Please enter your callerID number </td></tr>
<tr> <td> cc_you_have_entered_nothing</td> <td> You have entered nothing. </td></tr>
<tr> <td> cc_please_enter_number</td> <td> Please enter the number you wish to call followed by the hash (#) key. If making an international call include the international code. </td></tr>
<tr> <td> cc_unreachable</td> <td> The number is unreachable. </td></tr>
<tr> <td> enter_pin</td> <td> Please enter your PIN number. </td></tr>
<tr> <td> enter_voucher_number</td> <td> Please enter voucher number. </td></tr>
<tr> <td> EUR_cents</td> <td> ...cents. </td></tr>
<tr> <td> EUR_many</td> <td> ...euros... </td></tr>
<tr> <td> EUR_one</td> <td> ...euro... </td></tr>
<tr> <td> GBP_cents</td> <td> ...pence. </td></tr>
<tr> <td> GBP_many</td> <td> ...pounds... </td></tr>
<tr> <td> GBP_one</td> <td> ...pound... </td></tr>
<tr> <td> hour</td> <td> ...hour... </td></tr>
<tr> <td> hours</td> <td> ...hours... </td></tr>
<tr> <td> you_have</td> <td> You have... </td></tr>
<tr> <td> your_balance_was_increased_by</td> <td> Your balance was increased by... </td></tr>
<tr> <td> minus</td> <td> minus... </td></tr>
<tr> <td> minute</td> <td> ...minute </td></tr>
<tr> <td> minutes</td> <td> ...minutes </td></tr>
<tr> <td> mor_callingcard_choices</td> <td> Press one to enter new destination. Press two to redial same destination. Press three to check your balance. </td></tr>
<tr> <td> seconds</td> <td> ...seconds. </td></tr>
<tr> <td> unlimited_minutes</td> <td> ...unlimited minutes. </td></tr>
<tr> <td> USD_cents</td> <td> ...cents. </td></tr>
<tr> <td> USD_many</td> <td> ...dollars... </td></tr>
<tr> <td>USD_one</td> <td> ...dollar... </td></tr>
<tr> <td>voucher_not_found </td> <td> Voucher not found. </td></tr>
<tr> <td>thank_you </td> <td> Thank you. </td></tr>
<tr> <td> your_balance_was_increased_by </td> <td> Your balance was increased by... </td></tr>
</table>

 
+ all digit files for your language.

* [[Digits sound files]]

Example files: http://www.kolmisoft.com/packets/mor9_sounds.tgz

 

=== Translation/recording ===

* Translate and record a sound file to your language (example: French ('''fr''')).

 

=== Converting ===

In order to have Asteriskplay files, they should be converted to Bit rate: 16-bit, Sample rate: 8000Hz, MONO.

This can be done using the [[Convert WAV file to Asterisk playable format | sox command]]:

/usr/bin/sox file1.wav -r 8000 -c 1 -s -w file2.wav resample -ql

... and putting them into /var/lib/asterisk/sounds/mor/ivr_voices/'''fr'''.

Also, the script /usr/src/mor/sh_scripts/convert2astwav.sh can be used to convert many files at once. Just execute it in the folder with .wav files.

 
==== Errors ====

These errors means that a sound file is not Asterisk compatible:

[Dec 22 03:00:46] WARNING[20516]: format_wav.c:148 check_header: '''Not in mono 2'''
[Dec 22 03:00:46] WARNING[20516]: file.c:322 '''fn_wrapper: Unable to open format wav'''

 

=== Digits ===

Let's say you need digit sounds recorded in French ('''fr''').

Put all digit recordings into /var/lib/asterisk/sounds/digits/'''fr'''.

[[List of sound files for digits]]

 

== Setting language ==

* In DID settings, set language = '''fr'''.

If you want to set your default language for the whole system, not only for DIDs, then in sip.conf/iax2.conf/etc (they are in /etc/asterisk) set:

language = fr

'''Where fr is JUST AN EXAMPLE, CHANGE fr TO THE APPROPRIATE LANGUAGE!!!'''

Reload Asterisk.

 
== Currency ==

For example, let's take Georgian currency GEL ([http://en.wikipedia.org/wiki/Georgian_lari Georgian lari]).

You will need these sound files:

* GEL_cents (meaning 1/100 of main currency, "cents" for USD/EUR, "tetri" for Georgian GEL)
* GEL_many (meaning many of main currency, "dollars" for USD, "euros" for EUR, "lari"? for Georgian GEL)
* GEL_one (meaning 1 of main currency, "dollar" for USD, "euro" for EUR, "lari" for Georgian GEL)

They should be placed into /var/lib/asterisk/sounds/mor/ivr_voices/X.

Where X means your language.

 

== Remove a default sound file from MOR logic ==

Just set the appropriate sound file to contain silence.

 
== Remove/Change sound files ==

Files are stored in /var/lib/asterisk/sounds/mor/ivr_voices/.

Change the necessary sound file if you want to.

Make sure it is in Asterisk compatible format.

I want to hear Tell balance and Tell time voice prompts

2013-12-12T09:03:13Z

Mantas svelnys:

You need to enable '''Tell time''' and '''Tell balanc'''e options in user [[Device settings]], so that users would be able to hear these voice prompts.

Media control[http://wiki.kolmisoft.com/index.php/Device_settings#Network_Related] parameter "can reinvite" should be set to no.