Messages

One of the best ways I have found in understanding what kind of hardware works in LMCE is by looking at the user pages in the wiki. Just click on phenigma's user setup example link above.

I've looked at your post twice now and realize that maybe you would benefit from the following (which I used sucessfully on my system):

Solution (http://forum.linuxmce.org/index.php?topic=12861.msg92498#msg92498) and this is quoting from that post:

"Apparently the number detection is not yet working...so asterisk thinks it is an anonymous call. In /etc/extensions.conf the second line under globals is set to no

ALLOW_SIP_ANON = no

this kicks any phone call into internal voice message that sounds exactly like a phone provider message informing the dialer that the number is not in service. If you change this to

ALLOW_SIP_ANON = yes

and the do a core restart gracefully inside of asterisk, external phone calls will now be allowed to go in to the system

Of course you are still not "home" yet as the system then tells you that pluto default voice mail does not exist and then just hangs not knowing what to do..."

Not sure if this will help, but I had a similar problem with a CM8738 sound card with both coaxial and tos-link out. I already had a coax cable present so used that. The 1204 scripts that set up the sound card for this particular MD upon every reboot kept placing "plughw:0,1" in /etc/asound.conf. What I needed was asound.conf to read: "plughw:0,2". I didn't figure that out until trying

Code Select Expand

speaker-test -D plughw:0,2. Using aplay -L helped me identify that right device number.

To keep the correct "0,2" in place after a reboot, I had to edit /usr/pluto/template/asound.conf.

I hadn't seen this thread before today. I use mythtv a lot with schedules direct and OTA broadcast. No cable. No satellite. The family loves the speed of fast-forwarding and the pause functionality: pausing, then going frame by frame backward and forward. Great for sports.

I had been playing with 1204 and mythtv, trying to get it to perform well enough. Once I was able to upgrade from mythtv 0.25 to 0.27 (thanks to the examples in http://forum.linuxmce.org/index.php?topic=13581.msg98968#msg98968) and got it to work, I put 1204 back in as main house server controlling everything. I'm still working on each MD to work well enough with mythtv. So, right now, we record a tv show, edit it within mythtv on a desktop, then play it back on a MD using qorbiter as a remote.

One thing I've checked on my own system is whether the voicemail offered by my provider is enabled/disabled (I made that mistake once or twice).

In a terminal, after

Code Select Expand

sudo asterisk -rvvvvv, doing a 'sip show peers' or 'sip show registry'. All your phones should be registered. If not, track down why.

Not sure if you could do this since you reinstalled 1004, but compare 'dialplan show' of the old with the new. I've found asterisk to be a bear when tracking down errors.

Also, check the at home, or away status (go into lmce-admin website ->  Security -> Security status) and how it affects the way your telephones answer/ring (Telecom -> Call routing); on that same page, check: "# of seconds to ring before ivr (0=none)".

A follow-up.

Noticed after rebooting (and after I sent the message above) that the startup scripts rewrote the etc/exports file with the same oddities and now I see the "mount call failed" message again.

Discovered in /etc/network/interfaces an extra "eth0" on the same line as "netmask 255.255.255.0". Don't know how it got there. I wonder if I didn't hit delete enough? Weird.

Rebooted and /etc/exports looked normal. Am able to mount nfs shares from my laptop and the MD finally boots without the nfs problem.

**another follow-up. Restarted to make sure and the /etc/exports file is back to having the same oddities as noted above. I have no idea what is going now. I checked the /etc/network/interfaces file and there were no problems.

After a new install of beta yesterday, I booted up a diskless MD and received the "nfs mount call failed . . . error 13" loop. Decided to try to mount /home from my laptop, but couldn't. So, I checked the core's /etc/exports, and noticed two oddities:
  1) 192.168.80.0 was written as 192.168.80 without the .0
  2) eth0 (the external nic) was listed instead of eth1, which is the internal nic

Changed both of the above, then tried mounting again from both my laptop and the MD. Worked.

Not sure why the exports file was written that way during the install process. And, not sure if changing it the way I did will work for everything on the core.

phenigma's reference to http://forum.linuxmce.org/index.php?topic=8425.msg61787#msg61787 also helped me resolve the "Diskless Setup failed" message I was receiving for all the MDs I was trying. This was a fresh install of beta 8.10.

This was the fix I was looking for (adding a closing quote to the end of the last line in /etc/pluto/bin/files.d/fstab-diskless) in testing beta810. Big thanks. I had tried booting five different MDs and all returned the "failed" message.