> I tried to leave these fields empty. It did not work. Making the trunkgroups section empty was to eliminate a different configuration problem you have. It is not related to the reverse charging issue.
> Not appear IE74 > in the debug. > The possibility exists that the carrier does not be sending? Yes. It does look like the carrier is not sending the Reverse Charging Indication ie. Richard > > > Att, > Rafael Saraiva > > > > > > 2012/2/17 Richard Mudgett < rmudg...@digium.com > > > > I had not noticed that you switched to direct email earlier. > > ----- Original Message ----- > > Switchtype: euroisdn > > > > > > This is my chan_dadhi.conf > > > > [trunkgroups] > > trunkgroup=>1,16 > > spanmap=>1,1 > > The trunkgroups section is only needed if you are using NFAS and > its presence may cause issues for switches that do not support it. > NFAS is not supported by euroisdn or qsig. > > After looking again at your traces, the STATUS messages are > complaining > about the channel id indicated by Asterisk. The trunk groups setup > you have here is causing it. > > Just make this an empty section. > > > > > > > [channels] > > language=pt_BR > > hidecallerid=no > > usecallerid=yes > > callwaiting=yes > > callwaitingcallerid=yes > > threewaycalling=yes > > transfer=yes > > canpark=yes > > cancallforward=yes > > callreturn=yes > > echocancel=yes > > echocancelwhenbridged=no > > callerid=asreceived > > switchtype=euroisdn ;qsig > > signalling=pri_cpe > > context=PABX > > facilityenable=yes > > hidecalleridname=no > > ;aoc_enable=s,d,e > > imediate=yes > > ;busydetect=yes > > overlapdial=yes > > inbanddisconnect=yes > > priindication=inband ;outofband > > nsf=none > > ;qsigchannelmapping=logical > > pridialplan=unknown > > prilocaldialplan=unknown > > ;internationalprefix=00 > > ;nationalprefix=55 > > ;localprefix=5551 > > ;privateprefix=55513205 > > ;unknownprefix= > > service_message_support=yes > > mohinterpret=default > > discardremoteholdretrieval=yes > > group=1 > > channel=>1-15,17-31 > > > > > > And system.conf: > > > > > > > > loadzone=br > > defaultzone=br > > > > > > > > > > #span=1,1,0,cas,hdb3 > > #cas=1-15,17-31:1101 > > > > > > span=1,0,0,ccs,hdb3 > > dchan=16 > > bchan=1-15,17-31 > > > > > > > > Att, > > Rafael Saraiva > > > > > > > > > > > > 2012/2/17 Richard Mudgett < rmudg...@digium.com > > > > > > > > I could not send attachments to the list. > > > Att, > > > Rafael Saraiva > > > > You could have put the traces inline like you did the console > > capture. > > However, the attached files were oddly garbled in that lines were > > duplicated. It looks like your network switch does not like the > > PROCEEDING or ALERTING messages. > > > > The SETUP message did not have any differences between a normal > > call > > and a collect call that I could see. So there does not appear to be > > a > > way to tell the calls apart. > > > > What is the configured switch type? > > > > Richard > > > > > > > -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users