[asterisk-r2] Outgoing call to a PBX interface is being dropped

Wed Feb 24 20:34:54 CST 2010

in Brazil by default "operators" generate clock..
check that the link.

took me to read the mail, I am very tasksk

Renato dos Santos
renato at opens.com.br
OpenS Tecnologia Ltda
Rua Padre Marcelino Champagnat, 236
Jardim Atlântico - Florianópolis - SC - Brasil
+55 (48) 3954-8000
http://www.opens.com.br
shazaum.wordpress.com

On 19 February 2010 11:32, Isamar Maia <isamar at gmail.com> wrote:

> Ok. The problem with calls being dropped by the PBX was solved.
> It was really the collect-calls-drop stuff.  Great. I am happy.
>
> The problem now is that I am getting tons of  non-stop "Yellow Alarms"
> filling up
> my console.
>
> "[Feb 19 10:52:34] WARNING[30304] chan_dahdi.c: Detected alarm on
> channel 22: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30303] chan_dahdi.c: Detected alarm on
> channel 11: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30304] chan_dahdi.c: Detected alarm on
> channel 23: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30303] chan_dahdi.c: Detected alarm on
> channel 12: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30304] chan_dahdi.c: Detected alarm on
> channel 24: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30303] chan_dahdi.c: Detected alarm on
> channel 13: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30304] chan_dahdi.c: Detected alarm on
> channel 25: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30303] chan_dahdi.c: Detected alarm on
> channel 14: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30302] chan_dahdi.c: Detected alarm on
> channel 1: Yellow Alarm
> [Feb 19 10:52:34] WARNING[30329] chan_dahdi.c: Detected alarm on
> channel 4: Yellow Alarm
> "
> Seems to be clock sync. I am using PSTN as time source.
>
> span=2,1,0,cas,hdb3
> cas=32-46:1101
> cas=48-52:1101
> dchan=47
> echocanceller=mg2,32-46,48-52
>
> What it can be ?
>
> Thanks in advance,
>
> Isamar
>
> 2010/2/19 Isamar Maia <isamar at gmail.com>:
> > Hey Shazam!,
> >
> > That's the tip that Marcos, from Aligera, gave me right after I sent
> > this message.
> >
> > I believe there is a big chance to be indeed the "drop-collect-call"
> > feature the cause
> > of this prob.
> >
> > Since changing this stuff at the PBX side will not be an easy thing,
> > he suggested me
> > to set "mfcr2_metering_pulse_timeout=1500" and check it out.
> >
> > I will be doing that hopefully in couple hours and after that, I get back
> here.
> >
> > Thanks for replying.
> >
> > Isamar
> >
> > P.S.: I was a big fan of Shazam in the old times:
> > http://en.wikipedia.org/wiki/Shazam!_(TV_series)<http://en.wikipedia.org/wiki/Shazam%21_%28TV_series%29>
> > Next time, when I have a problem here, I will shout "Shazam!" :-)
> >
> > 2010/2/19 Shazaum <shazaum at gmail.com>:
> >> Hey Isamer...
> >>
> >> the pbx has double-answer(duplo-atendimento/drop-collect-call)?
> >>
> >> had a similar case with "double-answer/drop-collect-call"
> >>
> >> Renato dos Santos
> >> renato at opens.com.br
> >> OpenS Tecnologia Ltda
> >> Rua Padre Marcelino Champagnat, 236
> >> Jardim Atlântico - Florianópolis - SC - Brasil
> >> +55 (48) 3954-8000
> >> http://www.opens.com.br
> >> shazaum.wordpress.com
> >>
> >>
> >>
> >> 2010/2/19 Isamar Maia <isamar at gmail.com>
> >>>
> >>> Hello Folks,
> >>>
> >>> I have a 2E1 ports board produced by company in Brazil named Aligera
> >>>
> >>> I have one E1 port connected to PSTN(Embratel) and the other connected
> to
> >>> a
> >>> digital converter named "Intelbras IC-E1".
> >>>
> >>>
> http://www.intelbras.com.br/ecenter/downloads/manuais/interface_ic_e1.zip
> >>>
> >>> It converts 15 or 30 analog lines in one R2 trunk. It converts the
> >>> analog trunks from the PBX to R2, connected to Asterisk.
> >>>
> >>> So:
> >>> PBX <-->  IC-E1 <--> Asterisk  <--> PSTN(Embratel)
> >>>
> >>> I can send and receive calls through  the PSTN line and I *can*
> >>> receive calls from the
> >>> PBX/IC-E1 side. The problem is when I receive a call from the PSTN
> >>> line to the PBX,
> >>> the outbound call to the PBX is answered by the operator, I can hear
> >>> some seconds of
> >>> audio and then it drops.
> >>>
> >>> My environment is:
> >>>
> >>> Kernel version:  Kernel 2.6.18-164.el5PAE
> >>> Distro: CentOS release 5.4 (Final)
> >>> Versao do Asterisk: 1.6.2.1
> >>> Dahdi Package used: dahdi-linux-2.1.0.3-ap400.tar.gz
> >>> R2 lib package: openr2-1.2.0.tar.gz
> >>>
> >>> My setup is:
> >>>
> >>> DAHDI's  system.conf:
> >>>
> >>> # pabx
> >>> span=1,0,0,cas,hdb3
> >>> cas=1-15:1101
> >>> cas=17-31:1101
> >>>
> >>>
> >>> # embratel
> >>> dchan=16
> >>> echocanceller=mg2,1-15,17-31
> >>>
> >>> span=2,1,0,cas,hdb3
> >>> cas=32-46:1101
> >>> cas=48-52:1101
> >>> dchan=47
> >>> echocanceller=mg2,32-46,48-52
> >>>
> >>> # Global data
> >>>
> >>> loadzone    = br
> >>> defaultzone    = br
> >>>
> >>>
> >>>
> >>> chan_dahdi.conf
> >>>
> >>> ; PBX
> >>> [channels]
> >>> context=from-pbx
> >>> signalling=mfcr2
> >>> mfcr2_variant=br
> >>> mfcr2_get_ani_first=yes
> >>> ; Max amount of ANI to ask for
> >>> mfcr2_max_ani=20
> >>> ; Max amount of DNIS to ask for
> >>> mfcr2_max_dnis=20
> >>> mfcr2_category=national_subscriber
> >>> mfcr2_logdir=span1
> >>> mfcr2_logging=all
> >>> mfcr2_allow_collect_calls=no
> >>> mfcr2_forced_release=no
> >>> callerid=asreceived
> >>> group=1
> >>> callgroup=1
> >>> pickupgroup=1
> >>> channel => 1-15,17-31
> >>>
> >>> ; --------------------------------- PSTN
> >>>
> >>> context=from-pstn
> >>> signalling=mfcr2
> >>> mfcr2_variant=br
> >>> mfcr2_get_ani_first=yes
> >>> ; Max amount of ANI to ask for
> >>> mfcr2_max_ani=20
> >>> ; Max amount of DNIS to ask for
> >>> mfcr2_max_dnis=20
> >>> mfcr2_category=national_subscriber
> >>> mfcr2_logdir=span1
> >>> mfcr2_logging=all
> >>> mfcr2_allow_collect_calls=no
> >>> mfcr2_forced_release=no
> >>> callerid=asreceived
> >>> group=2
> >>> callgroup=2
> >>> pickupgroup=2
> >>> channel => 32-46,48-52
> >>>
> >>>
> >>> The only weird messages I can find in the logs are:
> >>>
> >>> [Feb 12 11:09:35] ERROR[31600] chan_dahdi.c: MFC/R2 protocol error on
> >>> chan 22: Invalid CAS
> >>> [Feb 12 11:09:35] ERROR[31600] chan_dahdi.c: Chan 23 - Protocol error.
> >>> Reason = Invalid CAS, R2 State = Seize ACK Transmitted, MF state =
> >>> Seize ACK Transmitted, MF Group = Backward MF init, CAS = 0x0C DNIS =
> >>> , ANI = , MF = 0x20
> >>>
> >>> What it should be ?
> >>>
> >>> --
> >>>
> >>> Isamar Maia
> >>> Brazil: 55-71-9146-8575
> >>>            55-71-4062-8688
> >>> 日本: +81-(0)3-4550-1212
> >>> "In a world without walls. Who needs windows and gates?"
> >>>
> >>> --
> >>> _____________________________________________________________________
> >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>>
> >>> asterisk-r2 mailing list
> >>> To UNSUBSCRIBE or update options visit:
> >>>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >>
> >>
> >> --
> >> _____________________________________________________________________
> >> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>
> >> asterisk-r2 mailing list
> >> To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >>
> >
> >
> >
> > --
> > Isamar Maia
> > Brazil: 55-71-9146-8575
> >            55-71-4062-8688
> > 日本: +81-(0)3-4550-1212
> > "In a world without walls. Who needs windows and gates?"
> >
>
>
>
> --
> Isamar Maia
> Brazil: 55-71-9146-8575
>            55-71-4062-8688
> 日本: +81-(0)3-4550-1212
> "In a world without walls. Who needs windows and gates?"
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100224/d11ce012/attachment-0001.htm 