Difference between revisions of "Registration Status"
From Kolmisoft Wiki
Jump to navigationJump to search
m |
|||
| Line 2: | Line 2: | ||
This feature was developed to make MOR administrators 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 administrators life easier. With this feature an administrator is able to track SIP device status from GUI and solve problems faster. | ||
<br><br> | <br><br> | ||
==Technical details== | ==Technical details (requirements)== | ||
These requirements must be fulfilled in order this functionality would work correctly: | These requirements must be fulfilled in order this functionality would work correctly: | ||
| Line 14: | Line 14: | ||
<br><br> | <br><br> | ||
==Device list== | ==Device list== | ||
<br><br> | <br><br> | ||
Revision as of 12:47, 17 August 2011
About
This feature was developed to make MOR administrators 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).
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
