|
After yum update, FOP doesn't display DAHDI trunks 2 Years, 8 Months ago
|
Karma: 0
|
|
Subject line pretty much says it all. I ran a yum update on an Elastix 1.5 box to fix some issues with faxing, and afterward, the FOP no longer displays any Trunks. Any idea what I should check?
|
|
|
|
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 8 Months ago
|
Karma: 8
|
|
I have the same problem.
gamba47
|
|
|
|
There is not place like 127.0.0.1
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 8 Months ago
|
Karma: 0
|
|
I also have the same problem...anyone know how to solve?
|
|
|
|
|
|
|
|
|
|
There is not place like 127.0.0.1
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 8 Months ago
|
Karma: 1
|
|
I have the same issue, the fix suggested in the link did not work for me.
Ron
|
|
|
|
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 8 Months ago
|
Karma: 8
|
|
Thanks ronaldlw for test it.
gamba47
|
|
|
|
There is not place like 127.0.0.1
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 7 Months ago
|
Karma: 1
|
|
any update on this?
Thanks,
Ron
|
|
|
|
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 7 Months ago
|
Karma: 8
|
|
I format my box.
gamba47
|
|
|
|
There is not place like 127.0.0.1
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 7 Months ago
|
Karma: 28
|
|
To fix it, please edit the file retrieve_op_conf_from_mysql.pl under the directory: /var/lib/asterisk/bin
and change the file name zapata-auto.conf or zapata-channels.conf to dahdi-channels.conf
After making this changes, go to the PBX Configuration and edit any think like edit an extension and submit then "Apply configuration changes" then go to the FOP to see the DAHDI trunks
|
|
|
|
|
|
|
Re:After yum update, FOP doesn't display DAHDI trunks 2 Years, 7 Months ago
|
Karma: 1
|
|
thanks saleh, that worked great! Any idea what the deal was with this? I'm going to be MUCH more careful with yum updates from now on! I also had major problems with the module update in freepbx recently. Thankfully this is a pre-production server, or I wouldn't have run ether update without testing first!
Thanks again,
Ron
|
|
|
|
|
|
|