Very strange, just rename chan_datacard.so in /usr/lib/asterisk/modules has no effect and in vain.
What I am doing now to make it work is to:
1. add a line "noload chan_datacard.so" in modules.conf under /etc/asterisk directory.
2. (This is an important step) rename datacard.conf to datacard.disabled.conf under /etc/asterisk directory.
3. chan_datacard.so in /usr/lib/asterisk/modules remained intact.
Glad to advise that our judgement is correct. After re-compiling chan_datacard, it can now be recognized by latest Asterisk 1.8.4 without the need to disable any modules and config files .
I think that this also becomes our upgrading routine whenever new Asterisk release or CentOS, or Kernal update is made.
I used wget method before. This time, I choose the 1st one from branch exactly like what you have been doing as below.
#get branch
svn co http://svn.asterisk.org/svn/asterisk/branches/1.8 asterisk-1.8
cd asterisk-1.8
./configure
#this is ony for format MP3 - SVN required
contrib/scripts/get_mp3_source.sh
contrib/scripts/get_ilbc_source.sh
make menuselect
make
make install
In fact, the system has been set up properly and I don't have problem now including iLBC codec. I think I have used the right method to compile this Asterisk 1.8.4 release with GUI 2.0 that I long for.
The only difference is that I use the SVN instead of wget in this update.
The original problem might be possibly arise from the transition of wget to SVN with which I have to do "make config" once again to let Asterisk read the code from the right place.
Anyway, thanks for your great help, CK.
One thing that I want to point out is that the suggested http address to access GUI that appear in CLI after installation is WRONG. It shows http://localhost:8088/asterisk/static/config/index.html (this is only valid for Asterisk 1.4). The correct address should read http://localhost:8088/static/config/index.html. I think this is one of the many reasons why some other people cannot enter into the GUI from browser.
As you said, there is still problem to access via IE.
I have been using APL to handle all Asterisk configuration and operation for long time. It is no easy task to do the integration. I have to examine line by line, word by word to ensure all settings are function as before. As you know, the naming rules are quite different with GUI and I'm considering whether I should do it all from scratch. But it takes time......
That is why I appreciate what Elastix is doing in its own ways, steps and schedule to integrate the latest Asterisk. They won't upgrade too fast to follow Digium's release. All the Elastix versions are a bit 慢半拍 so that they can have enough time to test by themselves first before rolling out. As you may also aware, Elastix just releases its Asterisk 1.8 which is almost half-year slower than Digium's debut.
發表於 2011-5-17 16:24
| 
