Displaying 20 results from an estimated 5000 matches similar to: "ISDN Timer T309"
2009 Mar 16
3
Asterisk 1.6 ReceiveFAX problem
hi,all
i have just set up asterisk 1.6.0.7 rc1 with spandsp 0.0.5 pre4 to ReceiveFAX, link to a E1 (DE410P) using dahdi
this can receive the fax from E1 successfully, but i see many error message in the log like this:
[Mar 16 09:24:38] ERROR[23540] channel.c: ast_read() called with no recorded file descriptor.
when i receive a 5 pages fax, i will see this error message over 200 lines.....
it
2011 Jan 11
1
Issue with Red Alarm with DAhDi
Hi!
I have an analog line connected to my asterisk and when I try to answer a call I get this
-- Starting simple switch on 'DAHDI/7-1' -- Executing [s at from-pstn:1] Answer("DAHDI/7-1", "") in new stack -- Executing [s at from-pstn:2] Playback("DAHDI/7-1", "vm-intro") in new stack -- <DAHDI/7-1> Playing 'vm-intro' (language
2016 Jan 05
3
Detected alarm on channel 3: Red Alarm
Hi everyone!
I have a Digium Card TDM410
But, it appear for me this massege
chan_dahdi.c:8061 handle_alarms: Detected alarm on channel 3: Red Alarm
But my line is ok!
But sometimes it back
sig_analog.c:3807 analog_handle_init_event: Alarm cleared on channel 2
But it again back to red alarm.
What can be happen?
My lines is all ok! But when I put on Digium Card TDM410 is very inconsistent
2012 Jul 24
5
DAHDI problems
Is a normal functionality?
when I do
#dahdi_cfg -vvvvvv
In my Asterisk console shows this....
[Jul 24 13:39:08] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got
event: HDLC Abort (6) on Primary D-channel of span 1
If I do this a lot of times...then
[Jul 24 13:39:20] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got
event: HDLC Abort (6) on Primary D-channel of span 1
[Jul 24
2016 Jan 05
2
Detected alarm on channel 3: Red Alarm
Humm, if I put a filter in this lines, maybe back?
2016-01-05 12:36 GMT-02:00, Ryan, Travis <RyanT at oscarwinski.com>:
>
>> -----Original Message-----
>> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-
>> bounces at lists.digium.com] On Behalf Of Vitor Mazuco
>> Sent: Tuesday, January 05, 2016 9:21 AM
>> To: Asterisk Users Mailing
2009 May 26
3
Silly (??) question about chan_dahdi
Hi,
these are my first steps with DAHDI and I finally managed to get
asterisk to load chan_dahdi (after I found out, that I need libpri).
But how do I tell chan_dahdi on which isdn numbers it should react? I
haven't found a parameter like "incomingmsn" for chan_capi in the
documentation.
Thanks for your help,
Stefan
2012 Nov 15
1
Detected alarm on channel 5: Red Alarm
Dear,
i using this scenario.
jitsi---> asterisk---->EPABX------> Local Telephone
when i am calling from jitsi to no 88 its giving this message and getting
busy tone.
== Using SIP RTP CoS mark 5
-- Executing [88 at myphones:1] Dial("SIP/sandeep-00000004",
"DAHDI/g0/88,20,rt") in new stack
-- Called g0/88
[Nov 15 09:53:54] WARNING[3169]: chan_dahdi.c:7536
2009 Apr 29
2
Something wrong with DAHDI signalling according to the CLI
I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO
modules.
When I plug one PSTN-line into a FXO-port I am able to receive calls on
this line and I can also make calls from an internal SIP-phone to the
external PSTN-network.
Still I am bothered about something that appears on the CLI when I do a
reload chan_dahdi.so :
asterisk*CLI> reload chan_dahdi.so
-- Reloading module
2012 May 09
5
Belgian BRI (euroisdn): what to use for a B410P
Hi,
I'm experiencing difficulties to get a B410P running with Asterisk
10.3.1 and DAHDI 2.6.1.
Am I supposed to use DAHDI for this card and ISDN BRI for my country
(Belgium)?
thx,
BC
2011 Mar 18
7
One PRI card with 2 (or more) Telcos
Hi list!
We currently have a PRI gateway composed by a box with two Digium quad-span
PRI cards (a TE420 and a ).
One of the cards is filled with TELCO1, while the other has first two slots
filled with TELCO2, and 3rd slot with TELCO3.
I am currently having (timer ?) issues on TELCO3 (span 7)
D-Chan (202 as determined by dahdi_genconf ) is constantly failing causing
on-going calls to terminate.
2010 Mar 26
1
problem with polarity reverse
Hi,
I have a problem with polarity reverse on answer
I use asterisk 1.4.30 linux kernel version 2.6.27 dahdi version 2.2.1 and analog card is Sangoma a400 with fxo ports
this is my config
[trunkgroups]
2012 Nov 02
1
Unable to create channel of type 'DAHDI' (cause 17 - User busy)
Hi,
I have 6 Red FXO with TDM2400p in my PC. I have install asterisk and dahdi
driver.
Scenario is
jitsi-----> asterisk server-----> analog PBX ----> landline phone
I configured this scenario as follow
in chan_dahdi.conf file
; General options
[channels]
usecallerid=yes
hidecallerid=no
callwaiting=yes
threewaycalling=yes
transfer=yes
2010 Sep 15
1
One way audio when overlapdial is set to yes
Hi Group,
I am currently facing a dead end and any help will be much appreciated.
I have an a104d installed in an asterisk box, two of which is configured on ISDN
pri. One is facing pstn and the other one is facing a hipath 300e Siemens. I am
getting one way audio when a local on the hipath tries to make a pstn call but
no issue on incoming calls from pstn going to the hipath locals.
local
2010 Jul 06
2
Dahdi - alarm which clears itself - Should I care ?
Hi,
When reading logs, I can see a couple of lines such as :
full.6:[Jun 30 15:53:26] NOTICE[6599] chan_dahdi.c: PRI got event: Alarm (4)
on Primary D-channel of span 1
full.6:[Jun 30 15:53:32] NOTICE[6599] chan_dahdi.c: PRI got event: No more
alarm (5) on Primary D-channel of span 1
full.6:[Jun 30 15:53:32] NOTICE[6607] chan_dahdi.c: Alarm cleared on channel
1
full.6:[Jun 30 15:53:32]
2009 Apr 27
4
[UK SPECIFIC] DAHDI and a OpenVox Card
Hi,
Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. When running asterisk -rvvvv I see the port pick
2010 Sep 29
1
Weird Behavior with DAHDI
Hello,
I'm experiencing some weird problems on my server:
- 1) The following messages are filling up my logs:
[Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 140 as D-channel anyway!
[Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No
D-channels available! Using Primary channel 171 as D-channel anyway!
2008 Oct 10
3
Got event 17 (Polarity Reversal)...
Can anyone tell me what this message means?
Got event 17 (Polarity Reversal)...
I'm running DAHDI 2.0 with a TDM401 card. Asterisk version 1.6.0.
It appears that I get this Polarity Reversal each time an inbound call
hangs up. This results in another ring, but no one is there. It appears
as an unknown caller, but I believe its a phantom.
Thanks,
Jim
[Oct 10 12:47:54] NOTICE[6669]:
2014 Jan 20
1
ISDN Cause Code 47 Errors
We fairly recently switched service providers for our 4 PRI circuits. Since
that time, we started to notice some failed inbound calls. These calls
terminate with an ISDN cause code 47 'resource unavailble'. Most of the
time I see this error on the first or second channel on the second span in
a trunk group (This is the providers trunk group for hunting, not an
Asterisk trunk group). All
2010 May 31
1
Suddenly "HDLC Bad FCS (8)" errors on ISDN-PRI, changed nothing
Hi fellow asterisk users,
I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel
module) an approx. 100 snom320. The whole installation is running
without issues since 5 months.
Without having changed anything on the asterisk server for at least 2
months, i noticed "clicking sounds" at external calls over the PRI.
Asterisk constantly throws the following messages:
...
2009 Jan 28
1
E1 conection to a Cisco2600
Hi
I am trying to connect asterisk with a Cisco GW 2600 with E1 pri using a
Digium, Inc. Wildcard TE210P dual-span T1/E1/J1 card 3.3V (rev 02),
Errors:
[Jan 28 17:32:33] VERBOSE[6182] logger.c: == Primary D-Channel on span 1
up
[Jan 28 17:32:33] WARNING[6182] chan_dahdi.c: PRI Error on span 0: We think
we're the CPE, but they think they're the CPE too.
[Jan 28 17:32:34] NOTICE[6182]