Dahdi - Trunk no audio on out bound

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
I have an Openvox card x400p
wctdm24xxp
seemingly set up OK but on outgoing calls there is no audio … not even a dial tone, incoming is fine….

not sure if the log below is relevant ?

[2011-03-26 14:46:50] WARNING[26006] pbx.c: Context 'ivr-2' tries to include nonexistent context 'ivr-2-custom'
[2011-03-26 14:46:50] WARNING[26006] res_musiconhold.c: chdir() failed: Permission denied
[2011-03-26 14:46:50] NOTICE[26006] app_queue.c: queuerules.conf has not changed since it was last loaded. Not taking any action.
[2011-03-26 14:46:50] WARNING[26006] app_queue.c: Unknown keyword in queue 'default': exten at line 3 of queues.conf
[2011-03-26 14:46:50] NOTICE[26006] chan_iax2.c: Still have a callno...
[2011-03-26 14:46:50] NOTICE[26006] chan_iax2.c: Still have a callno...
[2011-03-26 14:46:50] NOTICE[26006] chan_iax2.c: Still have a callno...
[2011-03-26 14:46:50] NOTICE[26006] chan_iax2.c: Still have a callno...
[2011-03-26 14:46:50] NOTICE[26006] chan_skinny.c: Configuring skinny from skinny.conf
[2011-03-26 14:46:50] NOTICE[26006] pbx_ael.c: Starting AEL load process.
[2011-03-26 14:46:50] NOTICE[26006] pbx_ael.c: AEL load process: parsed config file name '/etc/asterisk/extensions.ael'.

[2011-03-26 14:47:03] ERROR[21896] res_jabber.c: JABBER: encryption failure. possible bad password.
[2011-03-26 14:47:03] ERROR[21896] res_jabber.c: aji_act_hook was called with out a packet
[2011-03-26 14:47:03] WARNING[21896] res_jabber.c: Parsing failure: Hook returned an error.
[2011-03-26 14:47:03] WARNING[21896] res_jabber.c: JABBER: Got hook event.
[2011-03-26 14:47:03] WARNING[21896] res_jabber.c: JABBER: socket read error
[2011-03-26 14:47:05] NOTICE[26021] chan_dahdi.c: Got event 18 (Ring Begin)...
[2011-03-26 14:47:05] WARNING[26021] chan_sip.c: Asked to transmit frame type ulaw, while native formats is 0x8 (alaw) read/write = 0x8 (alaw)/0x8 (alaw)
 

jmullinix

Guru
Joined
Oct 21, 2007
Messages
1,263
Reaction score
7
Most likely, your installation has a trunk g0 in it. I believe that this is installed by default in PIAF. Go ahead and add 4 dahdi trunks and in the identifier field, put the trunk number 1, 2, 3 or 4.

Now set up a dial 9 outbound route with the dial pattern of

9|

and point it to Dahdi trunk 1. When you dial 9, you should hear dial-tone. Repeat this test with Dahdi 2,3 and 4. This will tell you if the TDM card is configured correctly. If you don't hear any dial tone, then post you chan-dahdi.conf file for us to look at.
 
Joined
Oct 5, 2010
Messages
188
Reaction score
38
I believe the default codec provisioned by dahdi is ulaw you will need to override that to use alaw in the UK, I think you can add "A-law override:alaw" to your /etc/asterisk/chan-dahdi.conf file, but then again I don't get many customers from your neighborhood.
 

Alex728

Guru
Joined
Dec 22, 2007
Messages
416
Reaction score
1
Isn't the Openvox 4 channel card usually on wctdm driver? All of mine are..

I don't use DAHDI (still on Zaptel) but if you are making an outbound call the signalling looks a bit odd TBH, you shouldn't be getting a "ring begin" on outbound call. :confused5:

On Zaptel I've always set my codecs at the extension/endpoint level to alaw and its worked fine...

Is the DAHDI channel shown as available and not in alarm?

apparently DAHDI does now check for -48V on the line (to the point where earlier versions choked on the Openreach line test and locked out the channel!) whereas Zaptel would happily dial out into an unconnected copper pair

try also using Zapbarge to monitor the relevant Zap channel and checking what audio is actually going through, and/ or if you have a 340 test set or other test phone with high impedance monitor, listen to the line at the BT socket or any other convenient places..
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
calls come in fine…
an inbound call on the Dahdi Trunk is fine but outgoing you can see the call go out, but no sound….
the phone rings you can pick it up (so I can ring my mobile for instance from the Dahadi trunk) but no sound….
so sound in bound not outbound.
also UK caller ID not working …
Thanks...
 

blanchae

Guru
Joined
Mar 12, 2008
Messages
1,910
Reaction score
9
I believe the default codec provisioned by dahdi is ulaw you will need to override that to use alaw in the UK, I think you can add "A-law override:alaw" to your /etc/asterisk/chan-dahdi.conf file, but then again I don't get many customers from your neighborhood.

This is your problem. You are using the wrong codec G.711 ulaw (North America only) and you should be using g.711 alaw (Europe and England). In your trunk config, allow=alaw
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
Thanks..


; Copied from DAHDI Module of FreePBX

[general]

#include chan_dahdi_general.conf

[channels]

; include dahdi groups defined by DAHDI module of FreePBX
#include chan_dahdi_groups.conf

include chan_dahdi_additional.conf
cidsignalling=v23
cidstart=polarity
usecallerid=yes
ukcallerid=yes
answeronpolarityswitch=yes
sendcalleridafter=1
echocancel=yes
echocancelwhenbridged=no

context=from-dahdi
callwaitingcallerid=yes
callerid=asreceived
hidecallerid=no
group=
channel => 1
 

blanchae

Guru
Joined
Mar 12, 2008
Messages
1,910
Reaction score
9
This line is wrong:

include chan_dahdi_additional.conf

It is a directive and requires a "#" sign in front. A # is not a comment symbol. The correct line should be:

#include chan_dahdi_additional.conf
 
Joined
Oct 5, 2010
Messages
188
Reaction score
38
I myself don't use the dahdi module in freepbx, I remove it an manually config, or use scripts supplied by the card vendor for PIAF. That module seemed to cause me more problems more than solutions, maybe it's different for people using cards direct from digium...
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
where do I do that ?
I already have alaw set in the dahdi module…
That must write to a text file…, obviously it is not writing properly….
 

blanchae

Guru
Joined
Mar 12, 2008
Messages
1,910
Reaction score
9
You should manually configure /etc/asterisk/chan_dahdi.conf to include the chan_dahdi_additional.conf. This file contains your extension settings. If it is not included, your extensions won't work properly.
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
I have done,
however I do not seem to have a chan_dahdi_additional.conf on my system… or I can't see it in config edit...
 

blanchae

Guru
Joined
Mar 12, 2008
Messages
1,910
Reaction score
9
from the Asterisk CLI>" dahdi restart" then "dahdi show channels"
 

blanchae

Guru
Joined
Mar 12, 2008
Messages
1,910
Reaction score
9
Show us the contents of:

/etc/dahdi/system.conf
/etc/asterisk/chan_dahdi.conf
/etc/asterisk/chan_dahdi_general.conf
/etc/asterisk/chan_dahdi_groups.conf

also from the Linux command prompt:

grep chan_dahdi.c /var/log/asterisk/full
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
tel*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-dahdi default In Service
 

womble1

Guru
Joined
Oct 19, 2008
Messages
632
Reaction score
6
Resolved this worked… Thanks...

This is your problem. You are using the wrong codec G.711 ulaw (North America only) and you should be using g.711 alaw (Europe and England). In your trunk config, allow=alaw
nope this did not work, it's already set to this….
 

Members online

Forum statistics

Threads
25,812
Messages
167,763
Members
19,240
Latest member
nikko
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top