Difference between revisions of "Registration Status"
m |
|||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 6: | Line 6: | ||
*Works <u>only with SIP</u> devices. | *Works <u>only with SIP</u> devices. | ||
*Device <u>must try to register</u> or <u>someone should call to that device</u> in order that device status | *Device <u>must try to register</u> or <u>someone should call to that device</u> in order for that device status to be visible. | ||
*Device must register to an Asterisk server <u>where it is assigned</u>. | *Device must register to an Asterisk server <u>where it is assigned</u>. | ||
*Qualify must be enabled. | |||
<br><br> | <br><br> | ||
===Example: === | ===Example: === | ||
| Line 15: | Line 16: | ||
<br><br> | <br><br> | ||
==Status== | ==Status== | ||
[[File:bullet_green.png]] '''OK''' - Device is registered | [[File:bullet_green.png]] '''OK''' - Device is registered and Device is responding to Qualify requests. All is OK. | ||
[[File:bullet_yellow.png]] '''LAGGED''' - Device is registered but | [[File:bullet_yellow.png]] '''LAGGED''' - Device is registered and Device is responding to Qualify requests, but response takes longer than it suppose to. It indicates poor connection. | ||
[[File:bullet_red.png]] '''UNREACHABLE''' - Device | [[File:bullet_red.png]] '''UNREACHABLE''' - Device stopped responding to Qualify requests. MOR is still trying to send Qualify requests to Device and expecting response. | ||
[[File:bullet_black.png]] '''UNKNOWN''' - | [[File:bullet_black.png]] '''UNKNOWN''' - Device was UNREACHABLE for more than one hour. MOR stopped trying to reach it by sending Qualify requests. Please refer to [[How_Registration_works_and_fails | this]] page to see how Device gets such status. | ||
[[File:bullet_white.png]] '''Unmonitored''' - | [[File:bullet_white.png]] '''Unmonitored''' - such status is shown when "Qualify" is set to "NO" in Device settings. | ||
'''NO STATUS''' - Device never tried to register to Server and Server does not know | '''NO STATUS''' - Device never tried to register to Server and Server does not know anything about this device status. | ||
<br><br> | <br><br> | ||
| Line 40: | Line 42: | ||
<br><br> | <br><br> | ||
==Very technical details== | ==Very technical details== | ||
'' | ''You will probably never need these.'' | ||
These files must exist: | These files must exist: | ||
| Line 54: | Line 56: | ||
*/var/log/mor/ami_debug.log | */var/log/mor/ami_debug.log | ||
<br><br> | <br><br> | ||
=See also= | =See also= | ||
* [[Device Registration Status is not visible in the system]] | * [[Device Registration Status is not visible in the system]] | ||
* [http://kb.smartvox.co.uk/voip-sip/sip-registration-explained/ SIP Registration Explained] | * [http://kb.smartvox.co.uk/voip-sip/sip-registration-explained/ SIP Registration Explained] | ||
Latest revision as of 09:09, 24 January 2017
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 for this functionality to work correctly:
- Works only with SIP devices.
- Device must try to register or someone should call to that device in order for that device status to be visible.
- Device must register to an Asterisk server where it is assigned.
- Qualify must be enabled.
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 and Device is responding to Qualify requests. All is OK.
LAGGED - Device is registered and Device is responding to Qualify requests, but response takes longer than it suppose to. It indicates poor connection.
UNREACHABLE - Device stopped responding to Qualify requests. MOR is still trying to send Qualify requests to Device and expecting response.
UNKNOWN - Device was UNREACHABLE for more than one hour. MOR stopped trying to reach it by sending Qualify requests. Please refer to this page to see how Device gets such status.
Unmonitored - such status is shown when "Qualify" is set to "NO" in Device settings.
NO STATUS - Device never tried to register to Server and Server does not know anything about this device status.
Device list
Device edit
Very technical details
You will probably 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
