Remotely Monitor Off-Hook Status?

<< < (2/3) > >>

Ostracus:
Had something similar. That's why a 202 can come in handy in if one line's off-hook, the other will still ring.

PhiDeck:
Quote from: infin8loop on January 17, 2015, 02:48:02 pm

If you are up to running a syslog, Off-Hook and On-Hook messages are written to the syslog.

I posted a perl syslog sample that could be modified to look for the Off-Hook and On-Hook message
here http://www.obitalk.com/forum/index.php?topic=185.msg9107#msg9107

The mechanics of what would be done with the messages makes my head hurt a bit. I'd probably take a low-tech approach and maintain a hook-status.txt file with a single line containing the last know status and date/time (updated from the syslog message).  Then I'd have another process running continuously that contained a timer loop that popped, say, every 10 minutes to track the status contained in the hook-status.txt file. If it was in Off-Hook too long, one might assume someone forgot to hang up the phone and send out an email to a caregiver. You could probably get fancy and monitor call termination messages in the syslog as well.

I run a free papertrailapp.com syslog on my one of my obi110's and it contains:

Jan 17 16:14:28 obi1 logger: [SLIC]:Slic#0 OFF HOOK   
Jan 17 16:14:53 obi1 logger: [SLIC]:Slic#0 ONHOOK

from a test call I made.

Best wishes as you help someone deal with the insidious disease of Alzheimer's.

Thank you.  I am leaning toward a syslog solution, pending determining the granularity of control of what gets logged.  I would host the syslog server on a Raspberry Pi, which would also process the log, sending appropriate emails to my cell phone provider's email-to-SMS gateway.

The RPi could also cycle power to the cordless phones' base-station, although more often the patient is using the corded phones (bigger and fewer buttons).

PhiDeck:
Quote from: infin8loop on January 17, 2015, 03:15:15 pm

Hook status of an Obi110 can be retrieved on the local page:

http://local-ip-address-of-obi/PI_FXS_1_Stats.xml

The above address could be posted by a script and the results retrieved and parsed by the script.

This might be a good use for a Raspberry Pi. 


Agreed.  And I already have a RPi, so could test concept before buying another dedicated one.
Leaning toward the RPi hosting and processing the OBi syslog, though.

PhiDeck:
Quote from: Ostracus on January 17, 2015, 06:35:36 pm

Had something similar. That's why a 202 can come in handy in if one line's off-hook, the other will still ring.

Seems like a good solution for the non-cognitively-impaired, particularly if they have 2-line phones.

Not clear on the applicability to an Alzheimer's patient, though.  Having to follow the ring to answer a separate dedicated phone on the second line may be asking too much.  As well as then having to identify the off-hook phone and hang it up.

I'll be happy if I can call the retired neighbor who is almost always home, who can cross the street and hang up the phone for the patient.  Have two back-up neighbors if primary is out.

PhiDeck:
Thanks to all who replied.  On the basis of the info provided, and what I've discerned from on-line documentation, I ordered an OBi110, which'll arrive tomorrow.

Once I experiment, decide on a preferred approach, and implement and deploy the chosen solution, I'll report back here for closure.

Navigation

[0] Message Index

[#] Next page

[*] Previous page