Ah, yes, the poor man's database, the astdb. That'll work in a pinch, although it doesn't scale well. Then again, for this particular application, scalability is probably not a concern.
The other benefit of using a database is that you can set up permissions that don't require you to give permission to execute core Asterisk commands to the web server. If you're just running it from cron (analyzing the log), I'm sure that works, although it will add latency. If the proximity detector hits a URL that immediately flips a switch in a database, there's only sub-second latency from the trigger to the desired outcome. On Tue, Mar 31, 2015 at 3:13 PM, Curt Lundgren <[email protected]> wrote: > I've been taking a different approach. Issuing 'asterisk -rx "database put > CF <extn> <cell phone>"' sets up call forwarding and 'asterisk -rx "database > del CF <extn>"' removes the forward rule. > > Curt > > On Tue, Mar 31, 2015 at 1:46 PM, John F. Eldredge <[email protected]> > wrote: >> >> It could be that I just need to use a larger geofence for uninterrupted >> results. I was using a radius of 100 meters. >> >> >> >> On March 31, 2015 1:39:59 PM CDT, Chris McQuistion >> <[email protected]> wrote: >>> >>> The iOS Location service seems to be pretty reliable, if a bit slow to >>> respond to location changes. I've been using it with my home automation >>> system for quite a while, to determine when I am within 1 kilometer, 5 >>> kilometers, 10 kilometers, etc. On that system, I do different actions, >>> depending on how far I am from home (changing the thermostat setpoints, >>> mostly.) >>> >>> I have a lot of faith in the iOS location services working, within an >>> acceptable degree of range and within an acceptable timeframe. I don't need >>> pinpoint-accurate location. I just need it to notice when I'm within a >>> half-mile of the office or not. >>> >>> On Tue, Mar 31, 2015 at 1:36 PM, John F. Eldredge <[email protected]> >>> wrote: >>>> >>>> I have had mixed results with cell-tower-based location services. The >>>> problem is that the closer towers will occasionally have all channels in >>>> use, leading your phone to connect to a further-away tower. This causes >>>> your >>>> phone to think your location has changed. Does your phone support >>>> Near-Field >>>> Communications? You could mount a couple of NFC tags in your office, swipe >>>> one of them as you start work, and swipe the other as you are about to go >>>> home. >>>> >>>> >>>> >>>> On March 31, 2015 12:05:34 PM CDT, Chris McQuistion >>>> <[email protected]> wrote: >>>>> >>>>> Some good ideas here (multiple sensors (maybe low-power bluetooth) to >>>>> detect incoming path vs outgoing path) and some not-so-good-ideas >>>>> (implanting sensors inside of my body....) >>>>> >>>>> iOS (and I assume Android as well) have low power background app >>>>> refresh (at least this is what Apple calls it) that you can use for >>>>> geo-location. It isn't actually using GPS, as that would chew up battery >>>>> power. It is a background process that uses info from WiFi networks, cell >>>>> towers, etc, to determine location "passively", so it doesn't chew up a >>>>> lot >>>>> of battery power. >>>>> >>>>> What I got working yesterday was two IFTTT "recipes" to create files in >>>>> Google Docs and Dropbox for each time I enter or exit the Watkins area. >>>>> That part actually works. The next step is doing something with that >>>>> information (from Google Drive or Dropbox) to launch an action on our VoIP >>>>> server. >>>>> >>>>> It still seems kludge-y to me, but I haven't heard a better suggestion >>>>> that less power (and is fully automated.) >>>>> >>>>> Chris >>>>> >>>>> On Tue, Mar 31, 2015 at 6:02 AM, JMJ <[email protected]> wrote: >>>>>> >>>>>> On 03/31/2015 12:54 AM, Tilghman Lesher wrote: >>>>>>> >>>>>>> That's also why I suggested that you place two proximity detectors >>>>>>> along a single path. The order in which they activate then indicates >>>>>>> ingress or egress. >>>>>> >>>>>> >>>>>> And since nobody has mentioned using a Raspberry Pi yet... you could >>>>>> make a proximity detector out of a Raspberry Pi with a camera and/or a >>>>>> USB >>>>>> Bluetooth gadget. >>>>>> >>>>>> If the work schedule is consistent, you could just schedule the PBX to >>>>>> route calls based on the time of day. Yeah, I know... who has a >>>>>> consistent >>>>>> work schedule any more? heh heh -- Tilghman -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
