it's not only for dialing in ... setup an extension that is shorter than the number ... and also without the "."
eg exten => 1000,1,Dial() also when you call out using the overlapdial circuit you do dial(zap/g1/) or dial(zap/g1/10) and the rest of the digits should come over overlapdial ... at least that's how it was designed to work Martin On Fri, Oct 30, 2009 at 8:25 AM, Vieri <rentor...@yahoo.com> wrote: > > I forgot to mention that I already have overlapdial=yes in zapata.conf. > Besides, overlapdial=yes is only for "dialing out" from Asterisk. Anyway, > that option is set. > > Any other ideas? > > --- On Fri, 10/30/09, Martin <asteriskl...@callthem.info> wrote: > >> overlapdial=yes in >> zapata.conf/chan_dahdi.conf >> google it out >> >> Martin >> >> On Fri, Oct 30, 2009 at 6:54 AM, Vieri <rentor...@yahoo.com> >> wrote: >> > Hi, >> > >> > I have a PRI euroisdn link between an Alcatel PBX and >> Asterisk. >> > >> > I'm having some trouble with overlap dialing. >> > >> > Suppose I dial '874053' from an Alcatel extension >> ('7034') where '87' is an Alcatel prefix of type "ARS >> Prof.Trg Grp Seiz.with overlap". >> > >> > I'm expecting Asterisk to receive '1004053' (where >> '100' is a prefix which always shows up in the euroisdn >> setup). >> > >> > However, Asterisk is only receiving '1004' which means >> that it's not reading the digits that follow. >> > >> > Are there issues with "receiving" overlap dials from >> zap channels? >> > >> > According to the Alcatel trace below, it looks like >> Asterisk is accepting the call before a "Sending complete" >> is released by Alcatel. >> > >> > I'm using libpri 1.2.8 and Asterisk 1.2.31.1. >> > >> > Alcatel trace: >> > >> >> t3 >> > --> Cleaning mtracer... >> > --> Positionning t3 filters... >> > >> +--------+-------+--------+--------+---------+---------+----------+------+ >> > | filter | desti | src_id | cr_nbr | cpl_nbr | us_term >> | term_nbr | type | >> > >> +--------+-------+--------+--------+---------+---------+----------+------+ >> > | 0 | ** | ** | * | ** >> | * | *** | 165 | >> > | 1 | ** | ** | * | ** >> | * | *** | 166 | >> > | 2 | ** | ** | * | ** >> | * | *** | 167 | >> > | 3 | | | | >> | | | | >> > | 4 | | | | >> | | | | >> > | 5 | | | | >> | | | | >> > | 6 | | | | >> | | | | >> > | 7 | | | | >> | | | | >> > >> +--------+-------+--------+--------+---------+---------+----------+------+ >> > Traces Analyser activated >> > >> > mtracer started ... >> > (476142:000001) MTRACER ♠©, version: >> R9.0-h1.301-31-d-es-c7s2 >> > (476142:000001) MTRACER num: 007, time: 2009/10/30 >> 11:53:02, loss: 0% >> > >> ______________________________________________________________________________ >> > | (476157:000002) 1095: Send_IO1 (link-nbr=19, sapi=0, >> tei=0) : >> > | long: 51 desti: 0 source: 15 cryst: 0 cpl: >> 19 us: 8 term: 0 type a5 >> > | tei: 0 <<<< message sent : SETUP >> [05] Call ref : 32 a8 >> > >> |______________________________________________________________________________ >> > | >> > | IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 >> > | IE:[18] CHANNEL (l=3) a9 83 9b -> T2 : B >> channel 27 exclusive >> > | IE:[1e] PROGRESS_ID (l=2) 80 83 >> > | IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num >> : 7034 >> > | IE:[70] CALLED_NUMBER (l=5) -> 80 Num : >> 1004 >> > | IE:[7d] HLC (l=2) 91 81 >> > >> |______________________________________________________________________________ >> > >> > >> ______________________________________________________________________________ >> > | (476157:000003) Concatenated-Physical-Event : >> > | long: 24 desti: 0 source: 0 cryst: 0 cpl: 19 >> us: 0 term: 0 type a5 >> > | tei: 0 >>>> message received : CALL >> PROC (02) Call ref : b2 a8 >> > >> |______________________________________________________________________________ >> > | >> > | IE:[18] CHANNEL (l=4) e9 81 83 9b >> > >> |______________________________________________________________________________ >> > >> > >> ______________________________________________________________________________ >> > | (476157:000004) Concatenated-Physical-Event : >> > | long: 28 desti: 0 source: 0 cryst: 0 cpl: 19 >> us: 0 term: 0 type a5 >> > | tei: 0 >>>> message received : >> CONNECT (07) Call ref : b2 a8 >> > >> |______________________________________________________________________________ >> > | >> > | IE:[18] CHANNEL (l=4) e9 81 83 9b >> > | IE:[1e] PROGRESS_ID (l=2) 81 82 >> > >> |______________________________________________________________________________ >> > >> > >> ______________________________________________________________________________ >> > | (476158:000005) 1095: Send_IO1 (link-nbr=19, sapi=0, >> tei=0) : >> > | long: 23 desti: 0 source: 15 cryst: 0 cpl: >> 19 us: 8 term: 0 type a5 >> > | tei: 0 <<<< message sent : CONNECT >> ACK (0f) Call ref : 32 a8 >> > >> |______________________________________________________________________________ >> > | >> > | IE:[18] CHANNEL (l=3) a9 83 9b -> T2 : B >> channel 27 exclusive >> > >> |______________________________________________________________________________ >> > >> > >> > In Asterisk I see: >> > >> > Oct 30 11:48:02 VERBOSE[11329] logger.c: -- >> Accepting call from '7034' to '1004' on channel 1/27, span >> 1 >> > >> > If I change the Alcatel 87 prefix to use "ARS Prof.Trg >> Grp Seizure" (without overlap) then I get the following >> trace: >> > >> > >> ______________________________________________________________________________ >> > | (488410:000060) 1093: Send_IO1 (link-nbr=19, sapi=0, >> tei=0) : >> > | long: 55 desti: 0 source: 15 cryst: 0 cpl: >> 19 us: 8 term: 0 type a5 >> > | tei: 0 <<<< message sent : SETUP >> [05] Call ref : 33 52 >> > >> |______________________________________________________________________________ >> > | >> > | IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3 >> > | IE:[18] CHANNEL (l=3) a9 83 8a -> T2 : B >> channel 10 exclusive >> > | IE:[1e] PROGRESS_ID (l=2) 80 83 >> > | IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num >> : 7034 >> > | IE:[70] CALLED_NUMBER (l=8) -> 80 Num : >> 1004053 >> > | IE:[7d] HLC (l=2) 91 81 >> > | [a1] Sending complete >> > >> |______________________________________________________________________________ >> > >> > This time Asterisk gets what I expect but I prefer to >> use overlap dialing. >> > >> > Are there known issues with this? >> > >> > Thanks, >> > >> > Vieri >> > >> > >> > >> > >> > >> > _______________________________________________ >> > -- 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 >> >> _______________________________________________ >> -- 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 > > > > > _______________________________________________ > -- 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 _______________________________________________ -- 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