Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - los93sol

Pages: 1 2 [3] 4 5 ... 27
Feature requests & roadmap / Re: Project Natal
« on: November 04, 2010, 09:39:51 pm »
Bumping an old thread since Kinect is finally available.  Some notes that make this thing an absolutely incredible candidate for home automation usage.

1) Price point, $150USD
2) Heat sensing capability
3) True noise cancelling microphone
4) USB
5) Pan/Tilt functionality
6) Laser scanning

Okay, so I picked one up at launch at midnight last night and got it home, I'm extremely impressed with it, and immediately saw the use cases in home automations.  Yes it's closed source, but so was the wiimote and it's now functional on Linux so really only a matter of the right people showing interest in it as a hackable device/toy.  The base itself has pan/tilt functionality built in, there is a laser that scans the room and adjusts the angle of the camera as necessary to track whoever is detected as the player in the room.  (think security)  There is a microphone on board with proper noise cancelling built in, and an on board camera. (think security and phone)  From what I can tell the laser is also being used to determine depth of objects within the room.  From the setup shots, it also appears the device has heat sensing capabilities built in as well, though I have not confirmed this yet.  Last but not least, it is USB.

So what do you guys think?  I see a GSD driver in it's future once things start progressing, seems a very cheap way to get phone and security features added to a room.  $150 is cheap for a launch price when you consider what we'd pay for equipment separately to get the identical you're stealthy, an intruder won't realize it's a security's just a Kinect sensor (they will probably steal it though, but then you just get a nice up close shot of their face)  :)

Installation issues / Re: linuxmce-phonebook-lookup.agi missing.
« on: November 04, 2010, 03:17:41 pm »
Can someone please check this in the latest snapshot and verify that it gets installed now.

Feature requests & roadmap / Re: Asterisk 1.8 Support Google voice.
« on: October 29, 2010, 07:38:27 pm »
Figures lol...was just a few months ago when I was testing and I scrapped it altogether.  In that case...probably it is a good candidate...and an easy project for someone to get their feet wet.

Feature requests & roadmap / Re: Asterisk 1.8 Support Google voice.
« on: October 28, 2010, 07:34:36 pm »
I tested GV, the major issue which resulted in it not being an option for our usage is that DTMF is not passed on incoming calls which prevents callers from accessing the IVR generated by the system.

Developers / What is it?
« on: October 28, 2010, 03:57:18 pm »
I understand that it is the mini versions, but what is it exactly?  Was DCERouter rewritten to be free of the PPL for this version?

Users / Re: Android Touch Orbiter
« on: October 26, 2010, 09:01:46 pm »
RE: Refresh problems after screen orientation may want to try this in your manifest file for the orbiter's activity definition


By default Android will reset your Activity when the screen orientation changes, but setting the above will prevent that from happening.  The other option is to handle this scenario directly in code which you probably don't need to do since I assume the only thing really being reset is your socket connection.

Just a quick tip, hope it helps.


Installation issues / Re: linuxmce-phonebook-lookup.agi missing.
« on: October 25, 2010, 07:35:08 pm »

This was added to svn by me about 4 months ago.  You should have it on your system too, please verify if it is already there and that the permissions match the other linuxmce scripts in that directory.  If they do not match, change them and reboot so they get loaded correctly.  Hope this helps.

From your CLI output the only thing registered is your core's extension 200.  201 and 202 are created but not registered.

For your new problem, I'd do sip show registry to see the status of that trunk.  When you say you tried re-registering your trunk, did you actually delete it from the web admin and re-add it, or did you just edit the settings and save them?  If you just edited then go back and delete the trunk and re-add it and the run sip show registry after a reboot.

We implemented some changes awhile back that requires each device to contain a secret now, I did not have access to every device to actually test the changes, but the effort was made to ensure they were all updated.  It is entirely possible your device is not actually registered, though your MD should be.

Please verify that the extension assigned to the grandstream shows as a registered extension in Asterisk CLI with sip show peers.

Developers / Re: TouchOrbiter - Auto-configuring new orbiter
« on: October 20, 2010, 02:31:30 pm »
Anyone interested in touch orbiter auto-configuration should really follow along with  That's the ticket documenting the development/changes Merkur and I are working to implement which makes it relatively quick and painless to incorporate this feature.

More details to come as things progress, but right now you can get rooms, users, skins, languages, and ui's available to populate selections in your touch orbiter implementation.  You can also poll for the status of orbiter generation with full progress and feedback just like a conventional orbiter would display.

Hopefully others will start jumping on board to help test and develop this.

Developers / Re: TouchOrbiter - Auto-configuring new orbiter
« on: October 18, 2010, 09:17:30 am »
Regarding auto-configuring new orbiter's, Merkur2K and I are working through this at the moment for the Android Orbiter I have been working on.  The implementation is quite simple, there is a PHP script that you post to using your variant of httpclient and it returns JSON back which can be easily parsed to retrieve the database results for rooms, users, skins, ui's, and languages.  You can then monitor the progress of the generation process and display that to your user by whatever means is convenient.  We are still working through creating the device and adding resolutions to the database on demand, but the previously mentioned features are already tested and working in the Android Orbiter.  Note that before using these features you will have to perform a logon to the web admin using appropriate credentials from the user to access the PHP script.  This will all be documented in the wiki when the details are firmed up and it has been fully tested.  Until then, hopefully this is a nice teaser....

Users / Re: Android Touch Orbiter
« on: October 14, 2010, 12:33:34 am »
darrenmason, if you implement onResume() you can reload the settings upon re-entry to the main activity...just a quick tip so you don't have to have people rebooting their phones and all that

Users / Re: Android Touch Orbiter
« on: October 12, 2010, 01:59:00 am »
Darren, I've got a version going as well...implemented some nice features into it already and localized every string in the app and translated to English, Spanish, German, Russian, Italian, Japanese, and French.  I'm working tonight to get some server-side work done to validate the user and create the devices on the core completely dynamically to make it literally just download off the market, follow the quick setup wizard in the app and start using it.  So far the UI is in place for the setup wizard in the app, just need to complete the server-side work and add a few additional features to the app and it's complete.  Orbiter itself is fully functional and quick snappy on my Droid X.

Please stop by the dev channel if you'd like to work together so we aren't ending up with separate efforts for the same task.


Feature requests & roadmap / Re: Use Google Contacts
« on: October 04, 2010, 11:55:54 pm »

Users / Re: Orbiter Phone problem when receiving a call.
« on: September 02, 2010, 06:50:18 pm »
No issues here, who is your provider?  Have you checked the Asterisk CLI to see what's happening?

Pages: 1 2 [3] 4 5 ... 27