please verify that on the sccp.conf file in the /etc/asterisk you had the correct bind ip addres based on your internal network address and the references on the lines and devices are based on the correct mac address of your phone. Then verify both the SEPDefault7970.cnf.xml file located in the tftpboot directory and also the link based on the mac of your phone that had the correct ip of your core and the correct URLs (authenticationURL and servicesURL.

And finaly did you use VLAN env also on the phone? And how many dhcp server did you have in your env?

I didn't find LinuxMCE version which you use. I installed several Cisco 7970 phones under LMCE 0710 and they worked from the box as phones and Orbiters. Not sure about that but I suppose that the IP of your phone should be something like 192.168.80.2 or so. But your phone has 192.168.80.253, which doesn't belong to IP range for LinuxMCE devices. Maybe this is a problem?

I started getting this error as well on 2 of my 3 cisco 7970 phones. Since it was working on one, I knew that something must have changed on the other two but I didn't know where to look. I logged into the terminal and ran

tail -f /var/log/pluto/DCERouter.log

as I tried to get the orbiter to connect. This gave me the cisco orbitor device number that was trying to log in but not much more.

I then went to Wizard \ Devices \Orbiters in the web admin and found the device number (which is listed next to the description field). Then clicked on advanced and near the bottom of the page found

Remote Phone IP

For some reason I do not understand, it was off by one digit: 192.168.80.14 instead of 192.168.80.13I corrected this field. Saved the page and then did a Wizard \Restart \Quick Reload Router from inside the web admin.

Exiting the orbiter on the phone and then reinitializing it under the Services Menu while the DCERouter.log was running, I no longer got the invalid ip message (who would of thought that it actually was telling you the truth) and saw from the log that the orbiter was actually loading.

My suspicion is that this ip gets coded into that field the first time the phone is loaded and when you change your subnet or for some other reason restart the system after a catastrophe, the DHCP server gives the device a new ip but the old ip is still in that field. Just guessing.

Hope this helps someone who has run into a dead end with this problem.

Ok, where can i get these group ranges? Because i've assigned my spa-3102 and pap2t-na as 192.168.80.30 and 192.168.80.31 respectively (forcing this at webadmin -> phones - mac adress and ip address, which created the entries at /etc/dhcp3/dhcpd.conf, having the devices with static addresses on it's configurations. They are working fine (well, sometimes extensions get busy tone when dialing to them or when calling out nothing happens), but after a complete reboot, works fine again...And as i'm getting a 7091G the next weeks, will be good to know...

I'm not sure what you mean by group ranges for the 7970(1). The template has to have a range based on your cisco phone's mac address which you must convert as per the instructions in the wiki. If by ranges you mean ip addresses, my understanding is that the initialization of the cisco phone is supposed to be pnp and that the dhcp server will assign and (hopefully) remember the correct ip for your phone.

In case pnp doesn't completely finish, as was my case, and the cisco extension fails to register in freepbx (Advanced \Configurations \Phones Setup) you cut to the chase and go to my solution at the end of this thread: