Just to answer your side issue:
On Sun, Sep 27, 2009 at 04:05:30PM -0500, Andy Howell wrote:
The only Warning or Error I see is when asterisk first starts a new call.
logger.c: -- Starting simple switch on 'DAHDI/1-1'
[Sep 27 15:55:50] WARNING[4199] chan_dahdi.c: Unable to enable echo
Hi!
I had the same problem...
dahdi_transcode command solved the problem!
CheerS!
Ismael.
On Mon, Sep 28, 2009 at 1:25 AM, Tzafrir Cohen tzafrir.co...@xorcom.comwrote:
Just to answer your side issue:
On Sun, Sep 27, 2009 at 04:05:30PM -0500, Andy Howell wrote:
The only Warning or Error
...@xorcom.com
Subject: Re: [asterisk-users] DAHDI congestion problem
To: asterisk-users@lists.digium.com
Date: Monday, September 28, 2009, 2:25 AM
Just to answer your side issue:
On Sun, Sep 27, 2009 at 04:05:30PM -0500, Andy Howell
wrote:
The only Warning or Error I see is when asterisk
On Mon, Sep 28, 2009 at 04:56:01AM -0700, Landy Landy wrote:
I have a similar problem with DAHDI. If my server gets rebooted, I can't make
any calls until the a call come in from outside. From there I can answer the
call and DAHDI works fine afterwards.
In your case: is the problem reset by
In your case: is the problem reset by restarting asterisk?
'dahdi
resstart'?
The problem does not reset by restarting asterisk.
I've noticed that I can call other sip phones but, when trying to call out, I
get the same (Busy/Congested/Not-Available) congested messege.
On Mon, Sep 28, 2009 at 02:26:29PM +0200, Tzafrir Cohen wrote:
On Mon, Sep 28, 2009 at 04:56:01AM -0700, Landy Landy wrote:
I have a similar problem with DAHDI. If my server gets rebooted, I can't
make any calls until the a call come in from outside. From there I can
answer the call and
: [asterisk-users] DAHDI congestion problem
On Mon, Sep 28, 2009 at 02:26:29PM +0200, Tzafrir Cohen wrote:
On Mon, Sep 28, 2009 at 04:56:01AM -0700, Landy Landy wrote:
I have a similar problem with DAHDI. If my server gets rebooted, I can't
make any calls until the a call come in from outside
On 09/28/2009 01:06 PM, Danny Nicholas wrote:
Funny. The first thing I always do after a reboot is call in from my
cell to make sure things work. But last night I rebooted and immediately
tried dialing out (with a TDM842B) and got:
WARNING[2720]: app_dial.c:1721 dial_exec_full: Unable to
On Mon, Sep 28, 2009 at 04:09:43PM -0500, Shaun Ruffell wrote:
On 09/28/2009 01:06 PM, Danny Nicholas wrote:
Funny. The first thing I always do after a reboot is call in from my
cell to make sure things work. But last night I rebooted and immediately
tried dialing out (with a TDM842B) and
I am unable to dial out over a Wildcard TDM400P. This was working previously,
so must have
messed up the config somehow. I'm running Asterisk 1.6.0.15, with FreePBX
2.5.2.2.
When I dial, I see:
-- Executing [...@macro-dialout-trunk:19] Dial(DAHDI/1-1,
DAHDI/g0/9239220,300,) in
new stack
Andy Howell wrote:
I am unable to dial out over a Wildcard TDM400P. This was working previously,
so must have
messed up the config somehow. I'm running Asterisk 1.6.0.15, with FreePBX
2.5.2.2.
When I dial, I see:
-- Executing [...@macro-dialout-trunk:19] Dial(DAHDI/1-1,
11 matches
Mail list logo
