upgraded to 2.9 and now no calls are getting connected

Hi,
I had a running FreePBX installation with lots of configuration. But it was on an old CentOS system and I decided to move to a Ubuntu server.
I got my new server ready and then installed all Asterisk packages together with FreePBX.
Free PBX 2.9 is installed. Then I took a backup from my old system with Backup &Restore module. I restored that backup to the new one.
New configuration is accepted by the FreePBX and everything seems in place.
However I can't dial out any calls.
I get "exit with zero" errors on the log. But that's all; there is no other log.
How can I analyze this further ? And any solutions ?
thanks.
__________________



Did you restore a backup
Did you restore a backup from a version previous to the 2.9?
yes, I did install a backup
yes, I did install a backup from 2.8.
but what's wrong with that ?
configuration seems to be accepted by the system.
how can I get more logs/debugs ?
Major DB schema changes
Major DB schema changes occurred between the two versions.
If you untar the backup file and run, move it to the tmp directory and run the generate astdb script you probably will have registrations but so much more will have to be fixed. You will find you have a ton of broken destinations.
Both DB's are completely hosed. I tried selectively restoring tables so I did not have to manually recreate 30 IVR's and it took Tony, Bryan and I almost 4 hours to fix the issues. You have to use the migration tool, period. Simply no way around it.
I know it's not the answer you wanted.
what is the migration tool
what is the migration tool ?
I can use it if it's applicable.
btw, IMHO the problem isn't about the configuration because when I had initially installed my previous FreePBX setup (the working one) , I had to make changes to the dialparties.agi script to enable calls.
I just don't remember what was the modification. and as I don'thave any logs, I'm not sure if it's the same problem or not.
If you do a check for
If you do a check for updates on a 2.9 system the "2.10" upgrade too will appear. You can't run it once the dbmigrate scripts have been run.
I can't think of any reason to modify dialparties.agi
from 2.9 to 2.10 ? how will
from 2.9 to 2.10 ?
how will that help me ?
I know about the upgrade module, but that's for upgrading from a previous version to new version.
I now have 2 systems:
1. 2.8.x with a working configuration on CentOS 5
2. 2.9.x with non working configuration on Ubuntu 11.10
how can I migrate my configuration to the Ubuntu system ?
and why do I have no logging on the new system ?
thx.
so ?
so ?
any idea ?
help needed
Hi,
I'm stuck and need help.
I now have 2 systems:
1. 2.8.x with a working configuration on CentOS 5
2. 2.9.x with non working configuration on Ubuntu 11.10
how can I migrate my configuration to the Ubuntu system ?
and why do I have no logging on the new system ?
thx.
help ?
Hi,
I'd appreciate any help please.
Thanks.
?
SkykingOH,
are you not following up ?
I really need help on this. I'm stuck.
Following up on what?
Following up on what?
Upgrade the 2.8 system to match the Ubuntu system.
Use the FreePBX upgrade utility. That's all you have to do.
Keep in mind 2.10 is still beta and the backup module is all new and a work in progress.
If you want follow up and accountability you need to purchase support. This is a community forum.
I don't understand
Hi,
Unfortunately I don't understand:
Do you propose to upgrade the old (CentOS) system to 2.9 version first ?
And then get a backup with "Backup & restore" module ?
and import that to the new 2.9 system ?
isn't it risky to upgrade the old system to the new version ? what if I get the same problems on the functioning old system ?
btw, I know this is a community forum but you made a suggestion and I didn't understand it. That's why I'm trying to ask details...
sorry if I was not polite enough. It's just disturbing that I couldn't make a working system on the new installation with backups from old system.
It's not about being polite.
It's not about being polite. I don't know what to tell you to do.
You are running an unsupported OS for starters.
The migration tool migrates data within the framework. You can't restore from a previous version, period.
The new system does not work because you trashed the DB with the restore and more than likely the AstDB is also in an unrestored state.
If you don't want to try the in place update then install the old version on another computer, restore to that then run the upgrade util. I have had to do that on a VM to migrate users from trixbox's.
Also if your config is not complex you can use the bulk import module, copy the sound files over SCP and then just setup everything else again by hand.
thanks.
now that the new installation is trashed with old version's restore, how can I restore a fresh DB with zero config ?
how can Iremovethe current installation and install old version (2.8) ?
Depends how well you know
Depends how well you know Linux and MySQL.
Essentially just drop asterisk and asteriskcdrdb databases from MySQL tool.
Then remove everything from the doc root /var/www/html/admin
Lastly download the 2.8 tarball, untar it, run the dbcreate scripts and then do a normal install_amp.
If this is overwhelming just go pickup an hour of support and we can do this for you.
thanks
thank you. I did as you suggested (btw, I am using asterisk at home for only 2 sip channels, it's not a commercial setup.)
unfortunately after restoring my backup I have several problems. Please see below.
It seems that I have a wrong password somewhere. But I don't know where. any idea ?
1. on the console I have several of these errors:
2. outgoing trunk is registered to my service provider. extensions are registered but I can't make a call.
3. on GUI, I get "asterisk connection failure"
4. on GUI, I get this error:
5. on GUI, I have brokem modules warning
6. on GUI, I have "Symlink from modules failed" error:
I think.
I think I've solved the password issue by changing my password in /etc/asterisk/manager.conf
but I have the following issue which I couldn't solve:
and my calls are still not connecting.
btw, I still have broken modules. I didn't want to fix them before anyone makes a suggestion about above issues...
ok
OK; I've also solved the symlink issue.
I removed the /etc/asterisk/logger.conf and /etc/asterisk/sip_notify.conf
now I don't have this issue.
also I have manually installed broken modules. now I don't have any errors on the GUI and console.
but my calls are still not connecting.
please help me...
You are not telling us much
You are not telling us much (output of sip show peers, debug info) I have no idea what "calls don't work" means exactly.
What I suspect is the astdb is not restored properly. I mentioned this in the info I provided you two weeks ago.
ok
"calls don't work" means:
- incoming calls (from trunk) are not ringing on my registered peers (extensions)
- extensions can't dial out
- 2 extension can't call each other
so, any basic call scenario fails.
what does "astdb is not restored properly" mean ? how can I fix that ?
what do you mean by "untar the backup file and run" ?
there is nothing in that tarfile to run. I restore it through "backup & restore" module.
where is the "generate astdb" script ?
I'm sorry to disturb you by my noob questions but you are my only hope as noone else tries to help...
btw, "sip show peers" output is exactly as in my working old system. peers are registered. I don't know what "debug info" is. if you tell me how to get that, I'll try...
Nobody tries to help because
Nobody tries to help because you are using an unsupported OS and did not follow advice to not restore between versions.
It should have been to untar the backup to the /tmp directory, then run the /var/lib/asterisk/bin/restoreastdb.php script. You will have to look at the script and see exactly what the argument it is looking for, I think it is the backup sequence number.
As far as Asterisk debug info, how to log, post logs, sip debug has been discussed on every Asterisk forum for years. I quick search of google or reading the Asterisk documentation would help you understand what is going on and what we need to help you.
I also suggested that using our support would get this resolved very quickly.
wait
really ?
Ubuntu is an unsupported OS ?
but I am following the advice. You told me to install the older version (2.8 in my case) and I did it.
But this method didn't help me...
So now you recommend me to untar the backup and run the restoreastdb.php script.
I'll do that...
But I doubt it will help, because I believe that this script is automatically run by the "backup & restore module" when it applies a restore.
you also suggest to get a commercial support. but I told you that this is not a commercial setup. I use it at home as a 2 channel home PBX.
I don't have the money for any commercial support.
p.s: I really doubt, if I had the money for commercial support, that my problem would be solved easily. There is a problem which breaks all calls on the platform. There is no clue of the root cause.
This thing has no meaningful logs...
p.s-2: I still don't see how to get debug info that you're looking for. no google search could answer about this.
Wow, huge statements that
Wow, huge statements that are completely inaccurate:
1 - the astdb restore is run, it just doesn't always work. Do a 'database show' and take a look at what keys are in that DB.
2 - I am sure I could fix it in under 30 minutes as could any member of the support team
3 - CentOS id the only Linux flavor that is supported. Everything is is "you are on your own".
4 - You rolled back your FreePBX to 2.8, did the restore and you still can't register?
5 - No meaningful logs? Have you even looked at Asterisk? SIP transaction logging (sip set debug peer xxx), dialplan logging (verbosity) and debug (core set debug xxx) produce more logging that you could possibly digest.
answers
well, I didn't know that Ubuntu is not supported. sorry...
1. so you recommend doing a restore by running the php script.
2. if you believe that this is an easy problem that can be solved in under 30 minutes, just let me know where to look at. I am using Linux distros for more than 15 years and have decent amount of linux knowledge. if it's so easy, I could fix it by your instructions.
3. next time , I'll consider CentOS. I had thought that Ubuntu is a well known distro and would be supported anyway.
4. I told you in previous posts that I followed your recommendation and installed a fresh 2.8 version. Then I restored the backup through "backup & restore" module.
Calls are still not being connected.
I never said that I am unable to register. My phones at home are registered and the outbound trunk is registered to my service provider sip proxy.
It's just a matter of calls not being connected.
On my previous installation, I had "custom context" module installed. I suspected that and removed it. Still not working...
5. I'll try those debug commands.
You have a ton of Linux
You have a ton of Linux knowledge but you don't know much about Asterisk or FreePBX. We could play 20 questions for hours and I may not stumble upon what you did.
Now you are making me wonder what "calls not being connected means". The log from when a call fails is helpful.
logs and show outpur
hi,
today I tried to get the logs but I see no matter which verbosity is set I don't get any logs except sip.
please see below, maybe you can find something meaningful. I don't...
anyone understands the problem ffrom these logs ?
so, I just wonder...
has anyone understood the problem from these logs ?
clean install
Hi,
As I couldn't make it run with my old configuration, I'm now trying with a clean install.
I installed version 2.9.0 and created 1 extension with my outbound routes and trunks.
Unfortunately outbound call still does not work.
My phone receives a "DECLINED" message from Asterisk and I don't understand why.
I created a new thread for this as it's a new installation:
http://www.freepbx.org/forum/freepbx/installation/failure-with-clean-ins...
giving up
tried everything. including installation of a new system with a very simple configuration.
Asterisk and FreePBX does not send any packets to the trunk.
giving up because this is not working and there is no one else on the forum willing to help. (except SkykingOH whom I'd like to thank although he couldn't show me the correct path)