* You are viewing the archive for May 8th, 2012

Why did it Hangup?

I am learning how to use AMI and I am having 1 problem.. When I make a call
to my mobile phone and when I answer it – it get disconnected/hangup right

Why is that? What is the solution to stop that?

For example:

ACTION: Originate
Channel: SIP/447XXXXXXX@vpsprovider
Exten: 210
Priority: 1
CallerID: 0044123456789
Timeout: 60000
Context: test

exten => 210,1,Answer
exten =>
exten => 210,n,SendDTMF(wwww2w3w)
exten => 210,n,Monitor(wav,${MONITOR_FILENAME},ib)
exten => 210,n,Hangup()

Before I had Dial() in the dialplan and it work great and no hangup. Now I
am using AMI method.


interdigit timeout chan_dahdi

Hello Marcus,

Had the same problem, looked in the internet and found your question.
Since I now have an answer
I will put it here! :)

In the dialplan I had this:

exten => 4000,1,Dial(Dahdi/4)
exten => 4000,n,hangup()

exten => _4XXXX,1,Dial(IAX2/PBX/${EXTEN:1})
exten => _4XXXX,n,Hangup()

when I dial to 4000 asterisk took a while to make a call. When I
changed the dialplan to this:

exten => 4000,1,Dial(Dahdi/4)
exten => 4000,n,hangup()

exten => _5XXXX,1,Dial(IAX2/PBX/${EXTEN:1})
exten => _5XXXX,n,Hangup()

The dial is almost immediate. :)

Hope it helps,



2009/12/10 Marcus Vinicius :
> Hello,
> I have an extension  into an analog FXS interface.
> When
> taking the unit off the hook and dial any number of digits, it takes
> about 4 seconds for these digits are passed to the dial plan.
> Anybody know if this time can be customized?
> /etc/dahdi/system.conf
> echocanceller=mg2,1-36
> dynamic=eth,eth0/00:18:43:0b:00:46,36,1
> fxoks=1-36
> /etc/asterisk/chan_dahdi.conf
> [channels]
> context=default
> switchtype=national
> ;signalling=fxo_ls
> rxwink=300              ; Atlas seems to use long (250ms) winks
>                                ; where the ring cadence is changed *after* the callerid spill.
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> ; interfaces FXS (ramal)
> context=from-inside
> signalling=fxo_ks
> group=1
> callerid=226
> channel=>1
> callerid=200
> channel=>2
> thanks
> –
> Marcus Vinicius
>      ____________________________________________________________________________________
> Veja quais são os assuntos do momento no Yahoo! +Buscados
> http://br.maisbuscados.yahoo.com
> _______________________________________________
> — Bandwidth and Colocation Provided by http://www.api-digital.com
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

Lifetime & Replacement

On Mon, 2012-05-07 at 10:26 -0500, Russ Meyerriecks wrote:
> There were a few compatability issues with the tdm400’s pci interface chip
> and certain motherboards

Interesting idea, but it’s been running in this same server with the
same motherboard for at least two years now, and this problem started
only last week.

At this point, I am sure enough that the card has failed that I have
ordered a new base card. If I’m wrong, I will only be out return postage
and 10% restock fee.

Lifetime & Replacement

On Mon, May 07, 2012 at 10:10:24AM -0600, Greg Woods wrote:
> On Mon, 2012-05-07 at 10:26 -0500, Russ Meyerriecks wrote:
> > On Sun, May 06, 2012 at 10:42:16AM -0600, Greg Woods wrote:
> > > I have a Digium TDM400P card that appears to have died. The first noted
> > > symptoms were that dahdi would fail to reload on boot. On closer
> > > inspection, the card looks totally dead; no lights on at all.
> >
> > Does the device show up in lspci?
> I just checked, and as expected, it does not show up with lspci (all of
> the other PCI devices do).


There were a few compatability issues with the tdm400’s pci interface chip
and certain motherboards. Before you start writing its eulogy, I would pull
all the modules off and plug it into a separate server to check for lspci
enumeration again.

Asterisk 1.8 Transfer CallerID


when a call comes in and is answered by colleague A, this colleague A
sees the CallerID of the external calling number.

When colleague A transfers the call to colleague B, attended or
unattended, then colleague B sees the number of colleague A on his
screen while talking to the external calling number.

I expect here that colleague B would see the external calling number on
the screen of his IP-phone.

How can I get this behaviour ?