On Wed, Jun 17, 2009 at 04:09:46PM -0700, Darryl Dunkin wrote:
hardhdlc is for a BRI, use dchan=24 instead to set the d-channel.
hardhdlc is *NOT* BRI-specific.
In ISDN (BRI/PRI) messages on the D channel are encoded in HDLC:
http://en.wikipedia.org/wiki/HDLC
Zaptel originally decoded the
[2009-05-27 02:06:16.294] WARNING[6971] chan_dahdi.c: No D-channels
available! Using Primary channel 24 as D-channel anyway!
[2009-05-27 02:06:16.295] VERBOSE[6971] logger.c: [2009-05-27 02:06:16.295]
== Primary D-Channel on span 1 up
[2009-05-27 02:06:16.301] ERROR[6971] chan_dahdi.c: !! Got a
] On Behalf Of Jim
Dickenson
Sent: Wednesday, June 17, 2009 15:49
To: Asterisk User MailList
Subject: [asterisk-users] What causes this error?
[2009-05-27 02:06:16.294] WARNING[6971] chan_dahdi.c: No D-channels
available! Using Primary channel 24 as D-channel anyway!
[2009-05-27 02:06:16.295] VERBOSE
- Non-Commercial Discussion
asterisk-users@lists.digium.com
Date: Wed, 17 Jun 2009 15:56:31 -0700
To: Asterisk Users Mailing List - Non-Commercial Discussion
asterisk-users@lists.digium.com
Conversation: [asterisk-users] What causes this error?
Subject: Re: [asterisk-users] What causes
: [asterisk-users] What causes this error?
/etc/dahdi/system.conf has this:
loadzone=us
defaultzone=us
#Sangoma A102 port 1 [slot:4 bus:7 span:1] wanpipe1
span=1,0,0,esf,b8zs
bchan=1-23
hardhdlc=24
/etc/wanpipe/wanpipe1.conf has this:
[devices]
wanpipe1 = WAN_AFT_TE1, Comment
[interfaces]
w1g1
On Wednesday 17 June 2009 17:48:37 Jim Dickenson wrote:
[2009-05-27 02:06:16.294] WARNING[6971] chan_dahdi.c: No D-channels
available! Using Primary channel 24 as D-channel anyway!
[2009-05-27 02:06:16.295] VERBOSE[6971] logger.c: [2009-05-27 02:06:16.295]
== Primary D-Channel on span 1 up
Discussion
asterisk-users@lists.digium.com
Conversation: [asterisk-users] What causes this error?
Subject: Re: [asterisk-users] What causes this error?
hardhdlc is for a BRI, use dchan=24 instead to set the d-channel.
-Original Message-
From: asterisk-users-boun...@lists.digium.com
phone1.cfg:
call.callsPerLineKey=1
Raúl Gómez C. wrote:
Michael,
I haven't used nor configured a Polycom phone, but you should check in
/etc/asterisk/sip.conf the call-limit param of the phone's config.
On Thu, Feb 28, 2008 at 12:31 PM, Michael Munger
[EMAIL PROTECTED] wrote:
We
We have an asterisk system and Polycom phones that were provisioned by
someone else. They want to get call waiting to work, but for the life of
me, I cannot figure out why the Polycom is returning a SIP 486 Busy Here
when you call and the person is already on the phone.
I have the feeling
Michael,
I haven't used nor configured a Polycom phone, but you should check in
/etc/asterisk/sip.conf the call-limit param of the phone's config.
On Thu, Feb 28, 2008 at 12:31 PM, Michael Munger
[EMAIL PROTECTED] wrote:
We have an asterisk system and Polycom phones that were provisioned by
I have found several references to this problem, but never a solution. I
have fixed it before, but it was always by accident...
Feb 5 13:27:39 NOTICE[12924]: channel.c:1904 ast_read: Dropping
incompatible voice frame on Local/[EMAIL PROTECTED],2 of
format ulaw since our native format has
Hi
What causes deadlock?
Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for
'0x82acb10', 10 retries!
Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for
'0x8298160', 10 retries!
Here is the portion of the log:
Apr 5 14:02:42 NOTICE[23363] chan_zap.c:
I sometimes get these WARNINGs too.
I would like to know what causes it and how to avoid them too.
Thanks.
Andy
On 4/5/06, Chuck Bunn [EMAIL PROTECTED] wrote:
Hi
What causes deadlock?
Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for
'0x82acb10', 10 retries!
Apr 5
-Original Message-
From: David Brodbeck [mailto:[EMAIL PROTECTED]
I'm running Asterisk HEAD from March 4. I've Googled a bit
but I can't
figure out what causes this error:
app_queue.c:374 in changethread: Can't change device
'**Unknown**' with no
technology!
It doesn't
I'm running Asterisk HEAD from March 4. I've Googled a bit but I can't
figure out what causes this error:
app_queue.c:374 in changethread: Can't change device '**Unknown**' with no
technology!
It doesn't seem to be causing any problems, but I'm curious what causes it.
I did a few Google
15 matches
Mail list logo
