Testing MOR PRO installation

Initial tests

Run /usr/src/mor/test.sh to test

• MySQL and Asterisk connectivity
• Fax2Email modules
• H323 module
• #mime-construct
• If g723 and g729 codecs are installed
• Connected users
• Autodialer
• Part of GUI

That can be done manually also.

Login to the system

Go to the GUI: http://<my-ip-address>/billing

And login as: admin/admin

If you can't connect or unable to access, reboot PC where MOR is installed and try again.

Configuration file

Go to /home/mor/config/environment.rb

• Web_URL - enter correct URL where MOR GUI can be reached, e.g. http://23.45.67.89/billing
  • Do not leave 0.0.0.0 - it's bad value, enter real IP by which you access GUI
• Recordings_Folder - enter correct URL where recordings can be reached (they can be on different server, e.g. http://98.65.43.21/billing/recordings)
• Addons - enable addons if you purchased them. Note - enabling them when they are not installed will mess your GUI

Restart Apache:

If you have Debian:

/etc/init.d/apache2 restart

Or Centos/Fedora:

/etc/init.d/httpd restart

GUI

Go to and make sure page is displayed correctly:

• SETTINGS - Users - Devices - create new device/delete device

Register new user over GUI (registration from login page), enter your email and check after registration if you received it

• Google Maps - ivesti rakta is psl: Get Google Maps key

Activation test

Configure softphone with following settings: 101/101 and call any number, let's say 123456789. On the CLI normal call process should be visible. If MOR tells, that "MOR is not authorized to work on this computer" - that means there are problems with serial.

Or in Asterisk CLI write:

module unload app_mor.so
module load app_mor.so

It should say somethign similar:

[Dec 10 08:49:27] NOTICE[19319]: app_mor.c:4050 load_module: MOR PRO is authorized to work on this computer.
Loaded app_mor.so => (MOR Billing Solution v0.5.0.6)

This means everything is ok.

Fax2Email

Go to device's 102 settings (http://YOUR_IP/billing/devices/pdffaxemail_edit/1) and change fax email to yours.

Register your softphone with settings 101/101 (if you can't make sure you opened necessary ports).

Using your softphone dial *9901 - you should get email with test fax attached as PDF.

Go to:

• STATISTICS-VARIOUS-FAXES (http://YOUR_IP/billing/stats/faxes_list/2) - press on PDF - should open your received fax <--- THIS WORKS ONLY FOR NEW INSTALLATIONS!

VoiceMail

Dial *97, you should hear: Comedian Mail Mailbooox... or You haaaave no messages...

WEB Callback

Login as user 101: (101/101)

Go to PERSONAL MENU - Various - Callback and enter any numbers, press Execute. On Asterisk CLI you should see:

-- Attempting call on Local/21233@mor_cb_src/n for 23234@mor_cb_dst:1 (Retry 1)
-- Executing [21233@mor_cb_src:1] NoOp("Local/21233@mor_cb_src-18d8,2", "MOR CB calls src!") in new stack
....

Possible errors:

Errno::EACCES (Permission denied - /tmp/mor_cf_xxxx or /var/spool/asterisk/outgoing/mor_cf_xxxx)

A Errno::EXDEV occurred in functions#activate_callback: 

Fix it.

---

No action on Asterisk CLI - enter correct AMI settings in MOR GUI Settings - AMI Interface

Crontab for Auto-Dialer

Skip this section if you do not have Auto-Dialer addon.

Check /home/mor_ad/mor_ad_cron.log, you should see something like this:

2007-12-07 00:01:53 - Start of MOR Auto-Dialer Cron script.
DB config. Host: localhost, DB name: mor, user: mor, psw: mor, port: 3306.
Successfully connected to database.
No campaigns found active this time: 00:01:53
Total campaigns retrieved: 0

For multi-server systems

Configure AMI connections

On Asterisk servers configure /etc/asterisk/manager.conf to allow GUI server to connect to Asterisk servers over AMI

[mor]
secret = morsecret
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
permit=10.70.10.10/255.255.255.0
read = system,call,log,verbose,command,agent,user,config
write = system,call,log,verbose,command,agent,user,config

NOTE: 10.70.10.10 is EXAMPLE IP - put correct one in your system.

Enter Asterisk servers into GUI interface

Enter correct settings to allow GUI to manage Asterisk servers over AMI

Read below only if asterisk isn't on the same server

If Asterisk is running on different machine, then you need to setup correct recordings folder. 1 Make sure apache is running on Asterisk server, secondly make sure you have correct "Recordings_Folder" value (You have to enter something like this: http://asterisk.server/recordings/ ). Now delete /home/mor/public/recordings symlink from GUI server. To test, try to open recordings page in your GUI.

Final steps

If this server has GUI, make sure change variable ExceptionNotifier.email_prefix = "[CLIENT] " variable to your needs. For example:

ExceptionNotifier.email_prefix = "[Digital Solutions .132] " (where .132 is last digits of server).

So if you will have problem with your GUI, authors will get noticed instantly.

Note to engineers: Always update server list with data.