I've fixed this by implementing Raul102801's suggestion above. I modified my named configuration such that my dyndns hostname resolves to 192.168.80.1 from within my internal LMCE network, instead of the public internet IP of the core.

Do you guys consider this a band-aid solution? If not, should I modify the trac ticket (#324) i submitted for this issue and include my solution?

We're all excited for the beta, but I'd caution you not to put dates in the devs mouths. Keep in mind the main developer just started a new job. It is unquestionably more important that he perform well in his new job than that the beta be released by a certain date.

Didn't realize VOIP was so sensitive. I read at some point that linuxmce has a QOS feature to prioritize voice data, but I just did some research on my aging wireless access point and it seems to be missing any such features. Will be interesting to see if there's any improvement using wired LAN only.

The codec my VSP suggests and the codec I'm using is u-law. I understand it's the best (provided you have the bandwidth which I certainly do...or should) and I understand the bitrate is fixed at 64kbps or thereabouts.

I have set [disallow=all] and [allow=u-law] for all extensions and protocols. Asterisk CLI verifies that u-law is being used exclusively.

I am testing as follows:

Call between two internal extensions, one is an iPhone with Siax (IAX) using internal wifi network, the other is a PC with Voiper softphone (IAX). I am listening from the PC via ipod headphones, while my girlfriend talks into the iphone. The call quality is exactly the same tinny sounding quality as I get when I make external calls through my unlimitel IAX trunk.

Does anyone else have this problem? I understand I should be able to get landline quality or better but this is far from that.

I have a couple ACT Homepro lamp modules and I noticed that the brightness level mappings are not ideal. For example, changing from 90% to 100% there is almost no perceptible difference. The same goes for 70% to 90%. There is a big difference in perceived levels below this however.

How can I re-map these intervals so that I have higher resolution? Is this problem likely specific to this model of controller? Can I create a mapping for each individual device or are the mappings global?

I'm experiencing poor (tinny-sounding) VOIP call quality. Internal calls suffer the same problem, so I've ruled out my VSP as the cause. The problem is also independent of softphone client and choice of protocol (IAX/SIP). Any ideas what the culprit could be?

Could this be related to the fact that my home network is completely wireless after the core?

Thanks to donpaul for his work in bringing VPN to linuxmce. I'm excited about streaming video from the core to an external pc or my iphone using this.

I typically get 50kb/s from my core to another consumer quality point of access over the VPN. This is not enough to stream most of video material in my library, from my initial tests. I assume there are ways to compress the video in realtime and stream it at a lower bitrate so that I don't need to create lower quality copies of all my material just for remote viewing.

Where can I learn more about implementing something like this? I read up a bit on mediatomb, and I get the impression it can do this. I'd like to know what I need in the way of a client (on a PC or iphone) and what configuration needs to happen on the two ends.

this is not needed and just coincidence [...] You probably rebooted the core or something like that when replacing the binary.

Hari

Actually I didn't. Before replacing the binary I rebooted, reloaded the router, removed the usb stick, replaced the usb stick, and did a spiritual dance around my CORE about 20 times in just about every possible sequence to no avail. As soon as I replaced the binary it started working instantly.

Return code: 2209/03/09 21:03:5132 (spawning-device)[1;33mDevice requests restart... count=1/50 dev=32[1;00mThu Sep 3 21:03:51 EDT 2009 Restart========== NEW LOG SECTION ==========109/03/09 21:03:5932 (spawning-device)[1;00mStarting... 1[1;00m109/03/09 21:03:5932 (spawning-device)[1;00mFound ./ZWave[1;00m0509/03/09 21:04:00.020[33;1mCreating child 33[0m <0xb794e6c0>0509/03/09 21:04:00.020[33;1mNote: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.020[33;1mNote: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 34[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 39[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 1945 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 1945 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 45[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 46[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 47[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mCreating child 48[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events.[0m <0xb794e6c0>0509/03/09 21:04:00.021[33;1mNote: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR.[0m <0xb794e6c0>0509/03/09 21:04:03.117[33;1mNo callback received: await_callback: -1 timer: 31[0m <0xb794db90>0509/03/09 21:04:03.325[33;1mGot reply to ZW_MEMORY_GET_ID, Home id: 0x00061b58, our node id: 1[0m <0xb794db90>0509/03/09 21:04:03.537[33;1mGot reply to GET_SUC_NODE_ID, node: 1[0m <0xb794db90>0509/03/09 21:04:04.006[33;1mFinished building node list:[0m <0xb794db90>0509/03/09 21:04:04.006[33;1mNode: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945[0m <0xb794db90>0509/03/09 21:04:04.006[33;1mNode: 4 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38[0m <0xb794db90>0509/03/09 21:04:04.006[33;1mNode: 5 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38[0m <0xb794db90>

EDIT: For shits and giggles, I installed the new driver (even though I'm running 810 and read that it was already included in 810). Everything's running fine now as far as I can tell.