Difference between revisions of "Registration Status"
| Line 1: | Line 1: | ||
=About= | =About= | ||
This feature was developed to make MOR administrator's life easier. With this feature an administrator is able to track SIP device status from GUI and solve problems faster. | This feature was developed to make MOR administrator's life easier. With this feature an administrator is able to track SIP device status from GUI and solve problems faster. | ||
Revision as of 09:19, 30 November 2012
About
This feature was developed to make MOR administrator's life easier. With this feature an administrator is able to track SIP device status from GUI and solve problems faster.
Technical details (requirements)
These requirements must be fulfilled in order this functionality would work correctly:
- Works only with SIP devices.
- Device must try to register or someone should call to that device in order that device status would be visible.
- Device must register to an Asterisk server where it is assigned.
Example:
If a device is assigned to a server A but registers to server B - status will not be shown (devices must register to the server they are assigned to).
Status
OK - Device is registered, all is OK
LAGGED - Device is registered but connection to it is poor
UNREACHABLE - Device tried to register before, but currently it is unreachable
UNKNOWN - means the device state status could not be found. This is NOT an alternative message to the previous UNREACHABLE message.
This status is created when you add a new device and the system does not yet have any data about its registration status.
Unmonitored - Device should not register to server so its status is unmonitored, this device made calls, so server is aware of its existence
NO STATUS - Device never tried to register to Server and Server does not know nothing about this device.
Device list
Device edit
Very technical details
Most probably you will never need these.
These files must exist:
- /usr/local/mor/mor_retrieve_peers
- /etc/cron.d/mor_minute_actions
Logs
If you want to get a lot of logs put DEBUG = 1 in mor.conf
Logs for this feature can be found here:
- /var/log/mor/ami_debug.log
