sorry, but since release is aproaching, I'd like to bump this one as it would be convenient if those contributions could get into LMCE's database.
Anyone from developers willing to help ?
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
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.
I agree I wish I could find something with the functionality of both wrapped into one.
I could run both. Using LinuxMCE soley for the media content/ cams / pbx and Misterhouse mainly for x-10 / weather / etc.
The CN700 / Via based MB is the problem. There may be a workaround coming but many people have had problems getting the VIA stuff to cooperate with Linux past basic computing. I got most of the way with a CX700 and then both the video and audio drivers weren't working. Looking deeper there was a tedious process to build both with no indication on the via boards that it would actually work. I decided to wait since I know the developers are looking at the Via platform and they will make something with a higher chance of working.
Once you build/install Openchrome then then CN700/CX700/CLE266 boards work fine in our experience with LMCE.
There is an advanced interface for Asterisk that gives to good access for setting these things up. Advanced-configuration-phone setup-settings-add trunk (if you don't already have one) . You probably won't need the IAX stuff. You would go into Trunks and add the section after general before extensions to it. There are others much more expert in Asterisk that I am but starting from that and looking at the existing settings got me on the air. Getting a Grandstream 488 working with it to connect my existing phones was more of an adventure I will post if anyone is interested. With much trial and error I even got my Nokia e-70 to work with it.
I can't offer you much help, although I can see no reason why it shouldn't work if you can somehow tell it a different device ID and core IP.
The core will generate an Orbiter interface for a particular device ID that will only work with that Core, so if you do that on each core then as long as you can tell it the Core IP (Which you can) and the device ID (which is the bit I can't remember) then there should be no reason why it shouldn't work.
Is this what you have tried?
On a side note, how have you set up your two cores? Different subnets using different hubs/switches? Is one of them still acting as a gateway? Is DHCP still running on both?Yeap, but I don't see how DHCP would influence my tests, cause I set them to existing ip and ID.
I assume you are running both as an evaluation to see which to proceed with, is this correct?