Displaying 20 results from an estimated 6000 matches similar to: "DAHDI, IAX2 and SIP considerations for Early-Media / Alerting"
2014 Feb 09
0
How to Busy signals on DAHDI [SOLVED]
2014-02-06 11:09 GMT+01:00 giovanni.v <iax at keybits.org>:
> Il 05/02/2014 8.42, Olivier ha scritto:
>
> channel then it depends upon what you have the priindication option
>> set to. With
>> priindication=outofband then a busy cause code is sent to the
>> network and the call
>> is hung up. With priindication=inband then a busy tone
2009 Jul 03
0
DAHDI CDR problem
Hello gang,
We just got MaBell to turn on our callerid. I tested the
capability with a southwest bell box and a plain phone, so I know the line
is sending the signal. I'm running Asterisk SVN-branch-1.4-r204834 using a
TDM400P card. Here is my dahdi_cfg -vv output:
dahdi_cfg -vv
DAHDI Tools Version - 2.1.0.2
DAHDI Version: 2.1.0.3
Echo Canceller(s): MG2
2014 May 27
0
dahdi-dahdi native bridging and audio level
Hello!
I use asterisk with TE420 as PRI switch for two channels :
;panasonic uplink
group=3
context=panasuplink
; relaxdtmf=yes
; immediate=yes
rxgain=0.0
txgain=0.0
mohsuggest=default
jbenable = no
; jbenable = yes
; jbmaxsize = 200
; display_send=name_initial
display_send=name
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
2005 Mar 28
0
Re: Asterisk-Users Digest, Vol 8, Issue 229
> On Sun, 27 Mar 2005, Nenad Radosavljevic wrote:
>> Only way I have managed to get Zap channel to reject a call on TE110P
>> without answering it, is to dial number that is not handled in dialplan
>> (I
>> have a ISDN PRI with 100 number DID service, and about 30 of them are
>> handled by dialplan). So far I didn't manage to reject call that are
>>
2005 Dec 05
3
PRI indications.
Hello,
i have succesfullu setup asterisk with Sangoma E1 card, evrything works well
but i don't know how to pass indications from telco switch to the user - when
users call bad number telco switch shuld talk "unallocated number" but its only
send PRI_CAUSE 1. How to pass voice indications thru asterisk to clients?
My /etc/zaptel.conf:
span=1,0,0,CCS,HDB3,CRC4
dchan=16
2006 May 30
0
no extension from ISDN phone with bristuff
Hello,
I have a Gigaset S44 connected to a quadBRI NT port. Receiving calls
works phone, however when dialing out from the phone the call is dropped
to the 's' extension, as if no extension had been dialed:
-- Accepting voice call from '492389990' to 's' on channel 0/2, span 4
-- Executing Directory("Zap/11-1", "default") in new stack
--
2005 Jun 20
1
Looking for PRI Outbound Caller ID Configuration
I'm having trouble setting the outbound caller ID on calls I make from my
PRI trunk group. The PRIs are served out of a 5ESS. Telco has set the PRIs
up for user provided caller id information, so I believe I just don't have
it set up right in my dialplan or something. I can't seem to find an
example of setting the outbound caller ID specifically for a 5ESS. Does
anyone have an
2005 Mar 15
1
Unknown signalling 896?
I've been beating my head a bit against the 1.0.6 Debian builds of
Asterisk, using an E100P (E1, single span) board.
In machines I've built in the past (back in 1.0.0 days), config I'm
using and that card and 1.0.0 driver combo worked fine.
ztcfg reports no problems:
SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
31 channels configured.
And zttool sees the card, and
2005 Jul 03
1
asterisk strips off trailing digit from incoming calls
so here it is, the problem that's been nagging me for the past 2 days:
connected a box to my telco's NTBA <-> zap/asterisk. which works:
box:/etc/asterisk# cat /proc/zaptel/1
Span 1: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 ACTIVATED (F7)" HDB3/CCS
1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In
2006 Apr 04
2
Fax over 2 bridged TE110P channels
Hi,
I have an asterisk installation with 2 E1 cards
Software version is
Asterisk 1.2.6
Libpri 1.2.2
Zaptel 1.2.5
I'm having problem with fax transmission, let me explain better my
setup:
My fist TE110P E1 card is connected to the telco line
the second TE110P E1 one to an Nexspan PBX
so the server is basically sitting between the line, and the pbx.
every call coming from the line is
2009 Jun 20
1
PRI cause codes
I am trying to retrieve the cause code of a outgoing call over a PRI
where the number called is out of service. When an out service number is
called I get a recording that the number dialed is not a working
number. I see cause code 1 in in the CLI as soon as the call is dialed
the Telco recording goes on for 30 sec. then hangs up. Any idea on how
retrieve info that the called number is is
2006 Apr 10
4
callerid name inboune from PRI
I switched PRI vendors recently, and one of my questions was "do you provide caller ID name in addition to number?"
AT&T Local did not, But XO communications said they did.
Before I call to complain, is there an setting to turn this on in asterisk?
I want to make sure that I have my side covered before I call XO.
My current zaptel.conf is:
context=from-pstn
switchtype=national
2009 Apr 03
1
conference calling
Greetings listers.
I'm running asterisk 1.4.21.2 on SUSE 11.0 using
Polycom 501 phones. My outgoing connections are Zapata using a TDM401P.
For the most part I can make and receive calls fine except for these 3
issues:
1. When I call an external conference, the call never bridges and
hangs up after 60-90 seconds.
2. When I call another number there is a
2008 Mar 11
1
WARNING[4294]: chan_zap.c:8851 zt_pri_error: 1 copying 5 bytes LLC
Hi
I have recently upgraded my Asterisk system (from 1.2 to 1.4) and I have started to
notice the following messages when I recieve a call on my Zap channel
:-
[Mar 11 09:20:17] WARNING[4294]: chan_zap.c:8851 zt_pri_error: 1 copying 5 bytes LLC
I have a single PRI ISDN 30 link to a Siemens Realitis DX. Here is my
zapata.conf :-
[channels]
echocancel=no
echocancelwhenbridged=no
rxgain=-5.0
2008 Mar 05
1
Newbie dialplan: dial 0 for outside line
I just managed to put in a TE410 card in an Asterisk box to work with
OnRamp 20(E1 downunder). I am able to dial in but was not able to dial
out.
Can anyone offer me some advice please?
In my extensions.conf, I just put in:
[default]
...
exten => 0,1,Dial(Zap/g1)
and I get this on the console when I dialled 0.
-- Executing [0 at default:1] Dial("SIP/5166-b76004f8",
2011 Feb 18
1
Asterisk with TE 121 DADHI incoming calls fail
Dear Customer Support,
i connected the asterisk to a e1 interface of our hipath4000. outgoing
calls from a sip peer of my asterisk to an up0 telephone which iss
connected to the hipath4000 are working. If you want to dial from an up0
device to the e1 interface where asterisk is connected to, you have to
use the prefix 83. But when you enter the 3rd cipher this error appears
at the cli
2009 May 23
1
1.6.0.9: Unknown signalling method 'pri_cpe' ??
I'm trying to upgrade from 1.4.24.1 to 1.6.0.9 with a TE120P card.
I can't make any connection over the T1.
From CLI:
ERROR[26017]: chan_dahdi.c:14300 process_dahdi: Unknown signalling
method 'pri_cpe' at line 37.
cat chan_dahdi.conf
cat chan_dahdi.conf
[trunkgroups]
[channels]
language=en
;internationalprefix = 00
;nationalprefix = 0
context=from-pstn
switchtype=national
2007 Jul 12
0
No subject
the CNAM info in the Q.931 call setup message. I've tried all
permutations of switchtype (dms100 & national) and facilityenable that I
can think of, but I still don't see CNAM coming out the other side.
Telco confirms that "Name Out" is enabled on our PRI.
Any pointers on what I'm missing, and/or how to debug further?
zapata.conf:
---
[channels]
context=default
2006 Mar 02
0
Australian E1 from Optus still not working
I still can't get this thing to work. Outgoing calls are fine, incoming just hangup straight away. I get a lot of & characters in my logs, I'm wondering whether they're caused by some sort of bad data ?
Mar 3 16:03:01 VERBOSE[10437]: