Interesting. I have essentially the same settings but if I don't wait a brief period then I don't get the callerid filled in. This was with 1.2 or 1.4
> Haven't tried with new 1.4 branch of Asterisk/Zaptel, but in 1.2, if > correctly configured, there was no need to "Wait(x)" to let zaptel to get > the CID on analog lines: it was zaptel itself to not let the call go through > the dialplan until the second ring. I think it shoud be something like: > > usecallerid=yes > callerid=asreceived > > in zapata.conf for relevant channels. > > Hope this helps... > > Regards > > picciux > > 2007/8/16, Matthew Harrell <[EMAIL PROTECTED]>: >> >> >> Thanks. I was hoping there might be a way to detect whether the CID >> routine was done or not. I've still seen occasions where it wasn't >> available >> for callers that I know had it. Maybe my phone service is just a little >> slow sometimes >> >> >> > Wait(2) is what I do. >> > >> > Matthew Harrell wrote: >> >>>> First, it seems I have to have a 2 - 3 second wait before the AGI >> call in >> >>>> order to get valid CID data. Usually 2 seconds suffices for this one >> setup >> >>>> but during that time the caller has had two rings before the local >> extension >> >>>> has even begun to ring. Is there something I am doing wrong that >> causes it >> >>>> to take so long to get the CID? >> >>> CallerID info is sent between the first and second ring. >> >> >> >> Well that would explain that problem, wouldn't it? Is there a proper >> way >> >> to wait for the CID data to be filled in if available or is Wait(2) my >> best >> >> option? >> >> >> > >> > >> > _______________________________________________ >> > --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 >> >> -- >> Matthew Harrell Never underestimate the power >> of >> Bit Twiddlers, Inc. very stupid people in large >> groups. >> [EMAIL PROTECTED] >> >> _______________________________________________ >> --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 >> > > ------=_Part_138095_28898178.1187347107635 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > Haven't tried with new 1.4 branch of Asterisk/Zaptel, but in 1.2, if > correctly configured, there was no need to "Wait(x)" to let zaptel > to get the CID on analog lines: it was zaptel itself to not let the call go > through the dialplan until the second ring. I think it shoud be something > like: ><br><br>usecallerid=yes<br>callerid=asreceived<br><br>in zapata.conf for >relevant channels.<br><br>Hope this >helps...<br><br>Regards<br><br>picciux<br><br><div><span >class="gmail_quote">2007/8/16, Matthew Harrell <<a href="mailto:[EMAIL >PROTECTED]"> > [EMAIL PROTECTED]</a>>:</span><blockquote class="gmail_quote" > style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; > padding-left: 1ex;"><br>Thanks. I was hoping there might be a way > to detect whether the CID ><br>routine was done or not. I've still seen occasions where it >wasn't available<br>for callers that I know had it. Maybe my >phone service is just a little<br>slow sometimes<br><br><br>> Wait(2) is >what I do. ><br>><br>> Matthew Harrell wrote:<br>>>>> First, it seems I >have to have a 2 - 3 second wait before the AGI call in<br>>>>> >order to get valid CID data. Usually 2 seconds suffices for this >one setup ><br>>>>> but during that time the caller has had two rings before >the local extension<br>>>>> has even begun to ring. Is >there something I am doing wrong that causes it<br>>>>> to take so >long to get the CID? ><br>>>> CallerID info is sent between the first and second >ring.<br>>><br>>> Well that would explain that problem, >wouldn't it? Is there a proper way<br>>> to wait for the >CID data to be filled in if available or is Wait(2) my best ><br>>> option?<br>>><br>><br>><br>> >_______________________________________________<br>> --Bandwidth and >Colocation Provided by <a >href="http://www.api-digital.com--";>http://www.api-digital.com--</a> ><br>><br>> asterisk-users mailing list<br>> To UNSUBSCRIBE or update >options visit:<br>> <a >href="http://lists.digium.com/mailman/listinfo/asterisk-users";>http://lists.digium.com/mailman/listinfo/asterisk-users ></a><br><br>--<br> Matthew >Harrell Never > underestimate the power of<br> Bit Twiddlers, >Inc. > very stupid people in large groups.<br> <a href="mailto:[EMAIL >PROTECTED]"> > [EMAIL > PROTECTED]</a><br><br>_______________________________________________<br>--Bandwidth > and Colocation Provided by <a > href="http://www.api-digital.com--";>http://www.api-digital.com--</a><br><br>asterisk-users > mailing list ><br>To UNSUBSCRIBE or update options visit:<br> <a >href="http://lists.digium.com/mailman/listinfo/asterisk-users";>http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br> > > ------=_Part_138095_28898178.1187347107635-- > > > --===============5209651550428981859== > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > _______________________________________________ > --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 > --===============5209651550428981859==-- -- Matthew Harrell Light travels faster than sound. Bit Twiddlers, Inc. That's why some people seem smart [EMAIL PROTECTED] until you hear them speak _______________________________________________ --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
