Difference between revisions of "Testing MOR PRO installation"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(96 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<center><big><big><big><b>IMPORTANT! INFORMATION IN THIS TOPIC IS OUTDATED AND NOT USED ANYMORE!</b></big></big></big></center>
==Initial tests==
* MySQL and Asterisk connectivity
* Fax2Email modules
* H323 module
* #mime-construct
* If g723 and g729 codecs are installed
* Connected users
* Autodialer
* Part of GUI
[[MOR Install Testing Manually Old | This can also be done manually]].
==Login to the system==
Go to the GUI: ''http://<my-ip-address>/billing''
Login as: '''admin/admin'''
If you can't connect or are unable to access, reboot the PC where MOR is installed and try again.
==Configuration file==
==Configuration file==


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


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


Restart Apache:
Restart Apache.


If you have Debian:
If you have Debian:
  /etc/init.d/apache2 restart
  /etc/init.d/apache2 restart


Or Centos/Fedora:
If you have Centos/Fedora:
  /etc/init.d/httpd restart
  /etc/init.d/httpd restart


==GUI==
== h323.conf ==


Go to and make sure page is displayed correctly:
Enter server's IP as described here: [[One-way audio or not audio at all]]


* SETUP - Settings - Save changes
* SETTINGS-Users-Devices - create new device/delete device
* SETTINGS - Accounting - Invoices - Generate...
* STATISTICS - Call - Graphs
* SETTINGS - Users - Recordings - Show
* PERSONAL MENU - Calls


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


==Realtime==
==GUI==


In Asterisk CLI:
Go to this page and make sure it is displayed correctly:


realtime mysql status
* SETTINGS - Users - Devices - create new device/delete device


Should show something like:
Register as a new user over GUI (registration from login page). Enter your email address, and after registration, check whether you have received confirmation.


Connected to mor@127.0.0.1, port 3306 with username mor for 4 days, 13 hours, 13 minutes, 29 seconds.
* Google Maps - enter key from this page: [[Get Google Maps key]]
 
<br>


==Activation test==
==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.
Configure softphone with following settings: 101/101 and call any number - let's say 123456789. On the CLI, the normal call process should be visible. If MOR says, "MOR is not authorized to work on this computer", there are problems with the serial.


Or in Asterisk CLI write:
Or in Asterisk CLI write:
Line 47: Line 69:
  module load app_mor.so
  module load app_mor.so


It should say somethign similar:
It should say something similar to:


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


This means everything is ok.
This means everything is okay.


==Codecs==
<br>


In Asterisk CLI:
==VoiceMail==


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


Should show g723 and g729 installed:
==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:


If g723 and g729 lines look like this:
-- 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
....


g723    -  -    -    -        -    -    -    -    -    -    -    -    -
Possible errors:
g729    -  -    -    -        -    -    -    -    -    -    -    -    -


Then - install g723/g729 codecs.
Errno::EACCES (Permission denied - /tmp/mor_cf_xxxx or /var/spool/asterisk/outgoing/mor_cf_xxxx)<br>
A Errno::EXDEV occurred in functions#activate_callback:


==Autodialer==
[[Can't open GUI|Fix it.]]


Enable crontab logs:
----


''/etc/syslog.conf'' uncomment '''cron.*'''
No action on Asterisk CLI - enter correct AMI settings in MOR GUI Settings - AMI Interface


Execute:
==Crontab for Auto-Dialer ==


/etc/init.d/sysklogd restart
Skip this section if you do not have an Auto-Dialer add-on.


Change editor from vi to some usable one:
Check ''/home/mor_ad/mor_ad_cron.log'', you should see something like this:


In file ''/root/.bashrc'' at the end add: '''export EDITOR='mcedit''''
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.
Relogin to root account for this change to take effect.
Successfully connected to database.
 
No campaigns found active this time: 00:01:53
Execute:
  Total campaigns retrieved: 0
 
  crontab -e
 
In the file's end add:
 
*/5 * * * * /home/mor_ad/mor_ad_cron >> /home/mor_ad/mor_ad_cron.log


Make sure you pressed ENTER after this line!!! If you don't it will not work.


<br>


==For multi-server systems==


==Fax2Email==
=== Configure AMI connections ===


In Asterisk CLI:
On Asterisk servers, configure /etc/asterisk/manager.conf to allow the GUI server to connect to Asterisk servers over AMI.


  module show like fax
  [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


It should show:
NOTE: 10.70.10.10 is an '''EXAMPLE''' IP - put the correct one in your system.


CLI> module show like fax
=== Enter Asterisk servers into GUI interface ===
Module                        Description                              Use Count
app_nv_faxdetect.so            NV Fax Detection Application            0
app_rxfax.so                  Trivial FAX Receive Application          0
app_txfax.so                  Trivial FAX Transmit Application        0
3 modules loaded


Go to device's 102 settings and change fax email to yours.
Enter correct settings to allow GUI to manage Asterisk servers over AMI.


Using your softphone dial '''*9901''' - you should get email with test fax attached as PDF.
== Read below only if Asterisk isn't on the same server ==
If Asterisk is running on a different machine, then you need to setup a correct recordings folder. 1 Make sure Apache is running on the Asterisk server; secondly, make sure you have a correct "Recordings_Folder" value. (You have to enter something like this: http://asterisk.server/recordings/ ). Now delete /home/mor/public/recordings symlink from the GUI server. To test, try to open the recordings page in your GUI.


Go to:
===Final steps===


STATISTICS-VARIOUS-FAXES - press on PDF - should open your received fax
If this server has GUI, be sure to change variable ExceptionNotifier.email_prefix = "[CLIENT] " variable to your contacts. For example:


==H323==
ExceptionNotifier.email_prefix = "[Digital Solutions .132] " (where .132 are the last digits of the server's IP address).


In Asterisk CLI:
Afterwards, restart Apache.


module show like h323
So if you have a problem with your GUI, the authors will get noticed instantly.
 
==WEB Callback==


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)
'''Note to engineers:''' Always update the server list with new data.
-- Executing [21233@mor_cb_src:1] NoOp("Local/21233@mor_cb_src-18d8,2", "MOR CB calls src!") in new stack
....
 
==Crontab for Auto-Dialer ==
 
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


==Manager connection==


...
----

Latest revision as of 16:39, 25 March 2011

IMPORTANT! INFORMATION IN THIS TOPIC IS OUTDATED AND NOT USED ANYMORE!


Initial tests

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

This can also be done manually.

Login to the system

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

Login as: admin/admin

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

Configuration file

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

  • Web_URL - enter the 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 a bad value. Enter the real IP by which you access GUI.
  • Recordings_Folder - enter the correct URL where recordings can be reached (they can be on a different server, e.g. http://98.65.43.21/billing/recordings)
  • Add-ons - enable add-ons if you purchased them. Note: enabling add-ons when they are not installed will interfere with your GUI.

Restart Apache.

If you have Debian: 

/etc/init.d/apache2 restart

If you have Centos/Fedora: 

/etc/init.d/httpd restart

h323.conf

Enter server's IP as described here: One-way audio or not audio at all



GUI

Go to this page and make sure it is displayed correctly:

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

Register as a new user over GUI (registration from login page). Enter your email address, and after registration, check whether you have received confirmation.


Activation test

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

Or in Asterisk CLI write: 

module unload app_mor.so
module load app_mor.so

It should say something similar to: 

[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 okay.


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 an Auto-Dialer add-on.

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 the 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 an EXAMPLE IP - put the 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 a different machine, then you need to setup a correct recordings folder. 1 Make sure Apache is running on the Asterisk server; secondly, make sure you have a correct "Recordings_Folder" value. (You have to enter something like this: http://asterisk.server/recordings/ ). Now delete /home/mor/public/recordings symlink from the GUI server. To test, try to open the recordings page in your GUI.

Final steps

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

ExceptionNotifier.email_prefix = "[Digital Solutions .132] " (where .132 are the last digits of the server's IP address).

Afterwards, restart Apache.

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


Note to engineers: Always update the server list with new data.


Retrieved from "https://wiki.kolmisoft.com/index.php?title=Testing_MOR_PRO_installation&oldid=9028"