I have quite similar problems. I recently did a fresh install with LMCE-1004-20121218182926965. So far it went as usual, linuxfirmware-nonfree had to be installed manually, upon creating an md downloading xmltv took the whole night, but eventually it was all done.
However I did also encounter problems with my files. I have two hdd installed in my core, each around 2tb in size. The first drive holds a 250gb partition for the system and a little swap, the rest is for data.
All the drives were recognizes and taken in with lmce-datastructure. The next day I wanted to watch something stored on the system, but the orbiter showed none. I checked in the webadmin and was astonished to see, that none of the files had been added to the database yet, though updatemedia appeared to be running. So I let the system resynchronize the whole drives and after a while everything reappeared. Unfortunately there are still some issues remaining:
 

• I have a few double entries, where for one movie appears the normal title and the second entry is the filename.
• files do not get automatically added to the database, I always have to either resynchronize the respective directory, or add the files manually
• at least one time the second drive got set offline, where I set it back online and had access after router reload

Anyways, I want to thank you guys, for an outstanding job getting us so far. I wish you a very happy new year!

Hello my friend,
I'm very sorry for not showing up here earlier, but the last days in the office had been very busy to say the least- plus I did a complete reinstall, because Mythtv was getting worse day by day.
Now that those things have been sorted, I tried the latest script from this thread and it worked :-) I now have incoming calls showing the proper callerid. The only thing I haven't tried yet, is making international calls from LMCE.

Thank you for your good job and I wish you a very happy new year!

I tried it out, but for me its not working...I still get "unkown" as callerid :-(

my cellphone

here you go

I did as you suggested....I attached the log from the call I made...I hope I got it all

Sorry for taking so long to reply...but its a busy time for me right now.
Anyways, I checked Asterisk.log when I called my line from my cellphone and this here is all I could find so far:

05   12/16/12 10:41:22.883      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/204@trusted-43d3;1, callerid  <0xb62feb70>
05   12/16/12 10:41:22.924      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/200@trusted-feff;1, callerid  <0xb62feb70>
05   12/16/12 10:41:22.965      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/201@trusted-1046;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.021      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/206@trusted-0b67;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.062      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/203@trusted-58ba;1, callerid  <0xb62feb70>
05   12/16/12 10:41:23.103      NotifyRing from channel SIP/620-0000000d, callerid <unknown> to channel Local/202@trusted-e373;1, callerid  <0xb62feb70>
05   12/16/12 10:41:25.097      NotifyHangup channel Local/202@trusted-e373;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.107      NotifyHangup channel Local/203@trusted-58ba;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.118      NotifyHangup channel Local/206@trusted-0b67;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.128      NotifyHangup channel Local/201@trusted-1046;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.139      NotifyHangup channel Local/200@trusted-feff;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.149      NotifyHangup channel Local/204@trusted-43d3;1, reason Unknown <0xb62feb70>
01   12/16/12 10:41:25.159      Failed to parse channel SIP/620-0000000d <0xb62feb70>
05   12/16/12 10:41:25.170      NotifyHangup channel SIP/620-0000000d, reason Unknown <0xb62feb70>
05   12/16/12 10:41:25.180      NotifyHangup channel Local/204@trusted-43d3;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.190      NotifyHangup channel Local/202@trusted-e373;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.200      NotifyHangup channel Local/203@trusted-58ba;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.211      NotifyHangup channel Local/200@trusted-feff;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.221      NotifyHangup channel Local/201@trusted-1046;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:25.231      NotifyHangup channel Local/206@trusted-0b67;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:41:55.935      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/204@trusted-bcbf;1, callerid  <0xb62feb70>
05   12/16/12 10:41:55.985      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/200@trusted-61ca;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.026      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/201@trusted-2474;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.067      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/206@trusted-02ba;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.110      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/203@trusted-f083;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.152      NotifyRing from channel SIP/620-0000000e, callerid <unknown> to channel Local/202@trusted-a540;1, callerid  <0xb62feb70>
05   12/16/12 10:41:56.395      Ignoring event because exten is 203 is channel is Local/203@trusted-f083;2 <0xb62feb70>
01   12/16/12 10:41:56.416      Failed to parse channel Local/202@trusted-a540;2 <0xb62feb70>
01   12/16/12 10:41:56.426      Failed to parse channel Local/200@trusted-61ca;2 <0xb62feb70>
01   12/16/12 10:41:56.436      Failed to parse channel Local/201@trusted-2474;2 <0xb62feb70>
01   12/16/12 10:41:56.446      Failed to parse channel Local/206@trusted-02ba;2 <0xb62feb70>
05   12/16/12 10:41:56.467      Ignoring event because exten is 204 is channel is Local/204@trusted-bcbf;2 <0xb62feb70>
05   12/16/12 10:41:56.507      NotifyHangup channel Local/202@trusted-a540;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.518      NotifyHangup channel Local/201@trusted-2474;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.538      NotifyHangup channel Local/206@trusted-02ba;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.548      NotifyHangup channel Local/206@trusted-02ba;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.559      NotifyHangup channel Local/202@trusted-a540;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.579      NotifyHangup channel Local/200@trusted-61ca;1, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.590      NotifyHangup channel Local/201@trusted-2474;2, reason Unknown <0xb62feb70>
05   12/16/12 10:41:56.600      NotifyHangup channel Local/200@trusted-61ca;2, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.129      NotifyHangup channel Local/203@trusted-f083;1, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.139      NotifyHangup channel Local/204@trusted-bcbf;1, reason Unknown <0xb62feb70>
01   12/16/12 10:42:02.150      Failed to parse channel SIP/620-0000000e <0xb62feb70>
05   12/16/12 10:42:02.160      NotifyHangup channel SIP/203-0000000f, reason Normal Clearing <0xb62feb70>
01   12/16/12 10:42:02.170      Failed to parse channel Local/203@trusted-f083;2 <0xb62feb70>
05   12/16/12 10:42:02.180      NotifyHangup channel SIP/204-00000010, reason Normal Clearing <0xb62feb70>
01   12/16/12 10:42:02.190      Failed to parse channel Local/204@trusted-bcbf;2 <0xb62feb70>
05   12/16/12 10:42:02.200      NotifyHangup channel SIP/620-0000000e, reason Unknown <0xb62feb70>
05   12/16/12 10:42:02.211      NotifyHangup channel Local/204@trusted-bcbf;2, reason Normal Clearing <0xb62feb70>
05   12/16/12 10:42:02.221      NotifyHangup channel Local/203@trusted-f083;2, reason Normal Clearing <0xb62feb70>

The interesting part is, that I have another sipphone hooked to the fritzbox parallel to LMCE, but there I get callerid shown, so clearly the box is sending them. Unfortunately I was so far unsuccessful in finding out how it is sending them.

thanks for the help...I will check this, when I find the time and report back

my setup is pretty straight forward:
I have a internetrouter (AVM Fritz!Box) that also receives all incoming calls. I registered asterisk via webadmin as a IP-Phone and thats it.
Since I was unable to make international calls, I hooked up another IP-Phone directly to the box, bypassing lmce- and I can call anywhere in the world and see the incoming phone-number.
The only other thing I did, was the dial-out prefix in lmce is "0".

so, do you think installing from scratch might change things for me?

I noticed l3mce saying that there are only a few open tickets left for 10.04. So I wondered a little, because I remember a ticket for Asterisk for example, where no telephonenumbers show up for incoming calls.
I keep my system up to date, but I still have this issue (aside not being able to call to outside of the coutnry and mythtv constantly crashing) my only standing issue.
So is this fixed and if so, how can I get it to work here?

yes..all my phones are connected as sip-phones. Like I said, I can make national calls, cellphone-calls...no problem..international calls- no dice

so there is definately something wrong with my asterisk. I hooked up a phone directly to my fritzbox and it connects international calls without a problem

done,
please, check this screenshot

It seems like this is not working at present. I have no problem call nationally...but as soon as I want to make an international call, I just can't get a line. I checked the call details and there I can find some of those calls wit "No Answer". Checking my AVM Fritz!Box, where the asterisk is registered as a sipphone- none of those calls show up.
I put a "0" as a dial prefix in the Webadmin, so any international call would have to start with "000". I don't even get a message about a wrong number, so I guess the formatting is okay.
Does anyone have an idea what could cause this?

Cheers
Mario