Difference between revisions of "Multi Server support"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 14: Line 14:


* '''ID''' - unique identifier of server which should be same as server_id in '''mor.conf'''
* '''ID''' - unique identifier of server which should be same as server_id in '''mor.conf'''
* '''Test''' - press to test connection to the server over AMI


* '''Hostname''' most times is equal to '''Server IP'''
* '''Hostname''' most times is equal to '''Server IP'''

Revision as of 14:42, 6 January 2009

This functionality is available from MOR 0.7

SETTINGS - Billing - Servers

With this system it is possible to manage several Asterisk servers from GUI.

These servers are Asterisk servers which work with calls.

Database and GUI servers are not described here.

  • Gateway - determines if server acts as Gateway for SIP Proxy. This option is available only when Carrier Class addon is enabled. It means that SIP Proxy will use this server to send calls through.
  • Active - determines if server is active - e.g. if MOR should 'talk' to this server in order to update provider/device information. Disabling server does not disables it's use, only the updating of changes from GUI.
  • ID - unique identifier of server which should be same as server_id in mor.conf
  • Test - press to test connection to the server over AMI
  • Hostname most times is equal to Server IP
  • URL - special URL for some third-party software, sometimes for server stats
  • Type and Comment - just for informational purposes
  • Max Call Limit - not used for now
  • AMI Username/AMI Secret - settings to connect to that server over AMI - most important settings in this window! Should match values in servers' /etc/asterisk/manager.conf
  • SSH Username/Password/Port - not used now







Providers

This window shows which Providers are accessible from this Server.

Every Provider can belong to every Server.

It is important to map correct Providers to Correct servers.

This mapping is most important for MOR Carrier Class