[asterisk-users] G729 and Dahdi: Inbound forcing ulaw!

[Eric Wieling]

Upgrade to 1.8.7.1  There was a bug fixed recently (I think in 1.8.6, but might have been 1.8.7) which caused Asterisk to sometimes not transcode when it should.  

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of JT
Sent: Wednesday, October 19, 2011 3:45 PM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] G729 and Dahdi: Inbound forcing ulaw!

Happy day to ya list!

I've recently deployed an update on our Asterisk server, taking it from 1.2 up to 1.8.5 - going from zaptel to dahdi.  Excitement levels are high and performance so far is wonderful.

The issue I have is I've purchased several G729 licenses, registered them, installed the module in asterisk (per instructions) and for most calls they work wonderfully.

Inbound calls through the PRI however are forcing ulaw as the codec!  I noticed this as all of my phones are currently set to Disallow:All, Allow:G729,gsm.  (This was the same configuration with Asterisk 1.2/Zaptel).  When an inbound call arrives my logs fill up with:
chan_sip.c: Asked to transmit frame type ulaw, while native formats is 0x100 (g729) read/write = 0x100 (g729)/0x100 (g729)

These did not appear with Asterisk 1.2/Zaptel.  I have reviewed the Dahdi settings and have found nothing relating to the codec being passed or how to force it to use the codecs I've purchased.

Any suggestions on where this might be set for inbound calls?  (Outbound calls, SIP to SIP and SIP to IAX2 to SIP are all using G729 - this only relates to an inbound call from an external land line).