search for: overlapdial

Hi there, we have a problem with dahdi and overlapdial. We are running an E1 in Germany and are in need of overlapdial. The E1 is connected to a Sangoma A101. As soon as overlapdial is set to "yes" we have problems with incoming audio on the dahdi channels. When set to "no" all audio is fine. Basically we can choose between bei...

...nd outgoing legs as long as it comes accross the PRI? Some (Myself included) have noted a slight echo on the Definity to SIP leg of the connection. My zapata.conf is below: switchtype = national context = incoming signalling = pri_cpe echocancel=yes echotraining = yes echocancelwhenbridged=yes overlapdial = yes group = 1 channel => 1-23 All suggestions would be welcome. Thanks! Doug

...--- asterisk ---------- isdn pri --------- telco--> dest. Here is my dahdi config [channels] context=default usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes overlapdial=yes autofalltrought=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 ; Span 2: WPE1/1 "wanpipe2 card 1" HDB3/CCS/CRC4 RED group=1,12 context=from-internal switchtype = euroisdn ;overlapdial = outgoing priindication = inband signalling =...

...ernal S0 -------- | PBX | -------- | PBX internal P2P S0 NT Mode | | HFC-S Card P2P TE Mode --------- | * | | BOX | --------- Since nearly one year it runs Asterisk 1.0.2-BRIstuffed-0.2.0-RC2b fine. after dialing the internal S0 number (61) I get overlapdial and dialtone. [example dial the PBX S0 with Asterisk 1.0.2-BRIstuffed-0.2.0-RC2b] -- Accepting AUTHENTICATED call from 192.168.255.1, requested format = 8, actual format = 8 -- Executing Dial("IAX2/ogo@call_saar/1", "Zap/g1/61|60") in new stack -- Called g1/61 Se...

Hi, I am facing an audio-problem with the dial application and I (!) think, that it is connected to the dahdi parameter "overlapdial=yes". Sangoma support does not see any connection between this. But when enabling this option I face with some(!) dial-partners a audio one-way issue (the called party can not be heard). Only using PSTNS (germany e1 trunk) - no voip. Is there any other setup out there with this issue? Ke...

Hello! I have asterisk which is connected to avaya definity. I set trunk to overlap. When I call to this trunk (so called tac in avaya) without any number I hear dial tone for some time, any digit I try to dial are ignored by asterisk- still tone, then call is rejected: -- Accepting overlap call from '6401' to '<unspecified>' on channel 0/9, span 3 -- Starting

Hello, I am trying to make a call from our PABX to Asterisk on PRI interface. How can i configure Asterisk to enter the overlap receiving state if the complete number is not obtained in setup message. Looking forward to any help in this regard Regards Nauman Bin Ali __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection

...nnels] language=en rxwink=300 switchtype=euroisdn nationalprefix= <- also tried 0 and 90 here internationalprefix= <- tried 00 here signalling = bri_cpe_ptmp prilocaldialplan=local pridialplan=local rxgain=3.0 txgain=3.0 echocancel=64 echotraining=yes echocancelwhenbridged=yes immediate=no overlapdial=no group = 1 context=from-isdn channel => 1-2 signalling = bri_cpe_ptmp pridialplan=local prilocaldialplan=local rxgain=3.0 txgain=3.0 echocancel=64 echotraining=yes echocancelwhenbridged=yes immediate=no overlapdial=no group = 2 context=from-isdn channel => 4-5 signalling = bri_cpe_ptmp pr...

...ollowing errors when starting up Asterisk: [ Booting.....................Apr 19 11:07:28 WARNING[6237]: chan_zap.c:9615 setup_zap: Ignoring switchtype Apr 19 11:07:28 WARNING[6237]: chan_zap.c:9615 setup_zap: Ignoring pridialplan Apr 19 11:07:28 WARNING[6237]: chan_zap.c:9615 setup_zap: Ignoring overlapdial Apr 19 11:07:28 ERROR[6237]: chan_zap.c:9436 setup_zap: Unknown signalling method 'bri_cpe_ptmp' Apr 19 11:07:28 WARNING[6237]: chan_zap.c:9615 setup_zap: Ignoring overlapdial Apr 19 11:07:28 ERROR[6237]: chan_zap.c:9078 setup_zap: Signalling must be specified before any channels are. Apr...

...apata telephony interface ; ; Configuration file ; [trunkgroups] [channels] ; context=default switchtype=euroisdn pridialplan=unknown prilocaldialplan=unknown ; ; sample 1 for Germany ;internationalprefix = 00 ;nationalprefix = 0 ;localprefix = ;privateprefix = ;unknownprefix = ;relaxdtmf=yes overlapdial=yes ;priindication = outofband ;rxwink=300 ; Atlas seems to use long (250ms) winks ;toneduration=100 ;usedistinctiveringdetection=yes ;busydetect=no ;immediate=no usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes...

...to act like a PBX connected via a PRI gateway to a voice netowrk where Asterisk is doing outbound overlap dialing for calls that terminate via that PRI. AFter researching through the archives and online dcocs, I thought I had everyting setup right, dialplan configured for '_X!' and the 'overlapdial=yes' in the chan_dahdi.conf file, but when I try and make a call, while the first digit triggers the outbound SETUP message, that SETUP message always includes a 'Sending Complete' parameter and any subsequent digits received from the originaing client seem to be getting ignored as oppo...

...TIA for all help regarding this..... Here the setup: zaptel.conf: span=1,1,3,ccs,ami bchan=1-2 dchan=3 span=2,1,3,ccs,ami bchan=4-5 dchan=6 zapata.conf: switchtype = euroisdn signalling = bri_cpe pridialplan=local prilocaldialplan=local echocancel=yes echocancelwhenbridged=yes echotrainig=yes overlapdial=no immediate=no group = 3 context=vonaussenkommend channel => 1-2 switchtype = euroisdn signalling = bri_cpe pridialplan=local prilocaldialplan=local echocancel=yes echocancelwhenbridged=yes echotrainig=yes threewaycalling=yes overlapdial=no immediate=no group = 3 context=vonaussenkommend chann...

...hardhdlc=9 echocanceller=mg2,7-8 # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED span=4,2,0,ccs,ami # termtype: te bchan=10-11 hardhdlc=12 echocanceller=mg2,10-11 # Global data loadzone = uk defaultzone = uk the /etc/asterisk/dahdi-channels.conf group=0 context=from-PBX overlapdial=yes switchtype = euroisdn signalling = bri_net channel => 1-2 context=from-PBX ; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED group=0 context=from-PBX overlapdial=yes switchtype = euroisdn signalling = bri_net channel => 4-5 context=from-PBX ; Span 3: B4/0/3 "B4XXP...

Sorry that I wrote in german : Ich benutze asterisk mit dem zaphfc Treiber. Jetzt hab ich folgendes Problem, habe 2 ISDN-Telefone angeschlossen. zaphfc im nt-mode. Anrufe von ausserhalb per sip (sipgate.de) kommen an. Wenn ich aber intern zwischen den zwei Telefonen (Ascom Eurit 30) sprechen m?chte geht das nur wie folgt : Erst die Nebenstelle w?hlen und dann den H?rer am Telefon abnehmen.

...rades, I noticed these messages in full debug log: Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring switchtype Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring pridialplan Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring prilocaldialplan Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring overlapdial Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring internationalprefix Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring nationalprefix Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring localprefix Jun 21 12:58:11 WARNING[27273] chan_zap.c: Ignoring privateprefix Jun 21 12:58:11 WARNING[27273]...

I have my peers registered to SER.asterisk seems to be sending mwi for the peers seen in the sip show peers CLI command. i have my ser server registered with asterisk as a type=friend and all clients register to ser.how do i get mwi to work for these clients registered to SER. Thank you, -AA

...ant to upgrade Asterisk to 1.2 until I've got this all sorted, one problem at a time! Here are my configs : /etc/zaptel.conf # Global data span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17 dchan=16 unused=18-31 loadzone = au defaultzone = au /etc/asterisk/zapata.conf [channels] context=from-onramp overlapdial=yes priindication = outofband switchtype=euroisdn pridialplan=unknown prilocaldialplan=unknown signalling=pri_cpe echocancelwhenbridged=yes echocancel=128 echotraining=800 rxgain=5 ; 0 txgain=-4.5 ; 0 busydetect=no pridialplan=local internationalprefix=0011 nationalprefix=0 usecallerid=yes hideca...

...orts in their own groups so that I can have different signaling on each? [channels] language=en switchtype=euroisdn pridialplan=unknown resetinterval=600 echocancel=yes echotraining=yes ;echocancelwhenbridged=no ;rxgain=0 ;txgain=0 callerid=asreceived musiconhold=default group=1 overlapdial=yes signalling=pri_cpe context=extensions channel => 1-15,17-31 jbenable= yes jbforce= yes jbmaxsize= 120 jbimpl= fixed jbresyncthreshold= 1000 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachm...

...ty PBX that is onsite and located in the same room as *. * is set to clock off the Definity. I am seeing no problems on the PRI from the Definity side. zaptel.conf is as follows: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 defaultzone=us loadzone=us zapata.conf is as follows: switchtype=national overlapdial=yes signaling=pri_cpe group=15 channel => 1-23 usecallerid=yes callerid=asreceived musiconhold=default echocancel=yes echocancelwhenbridged=yes echotraining=yes Thanks.

...ld pbx to asterisk and sip. the setup is as follows: telco <---pri---> asterisk <---pri---> legacy pbx everything is fine exept that when dialling from the legacy pbx it takes about 3 seconds before the asterisk start to dial. where does this delay come from? has it to do with 'overlapdial=yes'? here is an excerpt from the logfile (i assume the number is dialled enbloc as it come with the redial function of the legacy pbx): 2005-07-28 17:23:37 VERBOSE[13873] logger.c: -- Accepting overlap call from '070314161XXX' to '<unspecified>' on channel 0/1, sp...