Really stuffed with g729 admins please help out

[webgurru]

I have purchased 30 licenses for g729 codec and installed per instruction of Digium. When I try to use g729 codec I receive this error on CLI

"NOTICE[2716]: chan_sip.c:3796 process_sdp: No compatible codecs!"

I contacted Digium support and they replied this

"I am sorry to inform you, but as the directory says, this is unsupported. Asterisk 1.2 is no longer supported software. You need to upgrade to a later version of asterisk. The 1.2 versions of asterisk are no longer maintained by digium. But generally unless you know otherwise(usually for developmental purposes), you should use the i686 version of the codec for 32 bit OS installs."

Earlier I used codec "prescot" recommended by install utility, now I downloaded i686 and installed it. I reloaded codec using command asterisk -rx "reload codec_g729a.so", but still got the same error. There should be a way to use this codec as I was suggested in early questions when I was trying to use VICIDIALNOW first time.

Admins please help me out, I have already deployed system and just waiting for final configuration and start dialling.

Best regards,

[mflorell]

I would suggest upgrading to 1.4.21.2, There are instructions for how to do this in the REQUIRED_APPS.txt file.

Thanks for the note about Digium not supporting G729 on Asterisk 1.2 anymore, that is rather disappointing.

[webgurru]

I would suggest upgrading to 1.4.21.2, There are instructions for how to do this in the REQUIRED_APPS.txt file.

Thanks for the note about Digium not supporting G729 on Asterisk 1.2 anymore, that is rather disappointing.

Thanks Matt, I'll try to update and will let you know with results

Best regards,

[webgurru]

Hi Matt,

I tried to update asterisk. I followed each and every step in the document, but could not install it. All steps goes fine except the last 3.

./configure
make
make install

When I execute ./configure , I receive following error at the end of execution

"configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details."

After this I can't execute last 2 commands.

I did this with 2 installs. The second install was a brand new one. Any help?

Best regards,

[webgurru]

Hi Matt,

I manage to install g729 codec on asterisk 1.2, now I just want to confirm my call is connected using g729 or not. I am really can't decide if you could help me. My account entry in carrier is

type=friend
username=myuser
secret=mypassword
host=myserver
dtmfmode=rfc2833
context=inbound
canreinvite=no
disallow=all
allow=g729
insecure=port,invite

On my SIP phone I am using codec in this sequence

g729
g711 ulaw
g711 alaw

when I make a call my SIP phone shows connected using g711, as this codec is not allowed in my SIP account entry, I am not sure whether it is connected using g729 or g711. If I remove g711 from SIP phone, I can't dial it and CLI says

NOTICE[2636]: chan_sip.c:3796 process_sdp: No compatible codecs!

I am really not sure which codec is being used?

Best regards,

[webgurru]

Further show translation command show this output

Code: Select all

            Translation times between formats (in milliseconds)
           Source Format (Rows) Destination Format(Columns)

         g723   gsm  ulaw  alaw  g726 adpcm  slin  lpc10  g729 speex  ilbc
g723     -       2        2       2      2        2        1       3         7      21     -
gsm      8       -        2        2     2        2        1        3        7      21     -
ulaw     8      2        -        1     2        2         1        3       7       21     -
alaw     8      2        1        -      2        2         1        3       7       21     -
g726     8      2        2        2      -         2         1        3       7       21     -
adpcm  8      2        2        2      2         -         1        3       7       21     -
slin       7      1        1        1     1         1         -        2       6       20     -
lpc10    8     2        2        2     2          2         1       -       7        21     -
g729    8      2        2        2     2         2         1       3        -       21     -
speex  8      2        2        2     2        2         1       3        7        -     -
ilbc        -     -         -         -         -         -         -       -         -        -       -


[gardo]

You need to install the gcc-c++ package. On VicidialNOW you can install it by running" yum install gcc-c++".

Hi Matt,

I tried to update asterisk. I followed each and every step in the document, but could not install it. All steps goes fine except the last 3.

./configure
make
make install

When I execute ./configure , I receive following error at the end of execution

"configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details."

After this I can't execute last 2 commands.

I did this with 2 installs. The second install was a brand new one. Any help?

Best regards,

[webgurru]

Thanks Gardo,

I'll give it a try and let you know with results. Do you gave any idea of my above question as well?

Best regards,

You need to install the gcc-c++ package. On VicidialNOW you can install it by running" yum install gcc-c++".

[webgurru]

Thanks Matt and Gardo,

I could manage to update asterisk, now when I start system, I receive following error

Code: Select all

Notice: Configuration file is /etc/zaptel.conf
line 10: Unable to read Zaptel version information

Zaptel Version: Unknown
Echo Canceller: Unknown
Configuration
====================

Channel map:

0 channels to configure.

Too many tones included
ioctl(ZT_LOADZONE) failed: Invalid argument
line 10: Unable to register tone zone 'us'



Could you please let me know any fix for this?

Best regards,

[gardo]

Please post your /etc/zaptel.conf.

[webgurru]

Hi Gardo,

Code: Select all

# /etc/zaptel.conf:
# Digium/Clone X100P EXAMPLE:
# Here is an example of a configuration where an X100P single FXO card is used
# for zaptel timing and not used for calling:
#
# NOTE: you can get an X100P on ebay for $10-30 that will work with Asterisk

loadzone=us
defaultzone=us
#fxsks=1


Please post your /etc/zaptel.conf.

[webgurru]

@Matt and Gardo,

I don't know if this have any effect on VICIDIALNOW working but I solve the problem using this

I execusted this command "yum -y update" once this command finished then I rebuilt zaptel (make clean ; make ; make install) and everything works fine now. I can dial using SIP phone and campaign. I did this on test system. I want a confirmation if the above command won't make any harm to vicidialnow in any way. Once I'll get go ahead signal from Matt, any Admin or any senior member I'll do it on my main system as well.

Best regards,

Please post your /etc/zaptel.conf.

[gardo]

Running "yum -y update" will update your VicidialNOW system to the latest CentOS updates. The only drawback is that the customized VicidialNOW kernel will be replaced by the stock kernel used by CentOS. You need to make the custom kernel the default by editing "/boot/grub/grub.conf". Other than that it's a good idea to keep your system updated. Let it run for a while and let us know how it goes.

[webgurru]

Thanks Gardo,

I don't know how to make these changes. Following is my grub.conf file, could you please let me know what to change.

Code: Select all

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/cciss/c0d0p2
#          initrd /initrd-version.img
#boot=/dev/cciss/c0d0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm
hiddenmenu
title CentOS (2.6.18-128.1.16.el5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-128.1.16.el5 ro root=LABEL=/
        initrd /initrd-2.6.18-128.1.16.el5.img
title VicidialNOW (2.6.18-92.el5.vnow)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-92.el5.vnow ro root=LABEL=/
        initrd /initrd-2.6.18-92.el5.vnow.img


Best regards,

Running "yum -y update" will update your VicidialNOW system to the latest CentOS updates. The only drawback is that the customized VicidialNOW kernel will be replaced by the stock kernel used by CentOS. You need to make the custom kernel the default by editing "/boot/grub/grub.conf". Other than that it's a good idea to keep your system updated. Let it run for a while and let us know how it goes.

[gardo]

Change this:

default=0

to

default=1