search for: use_callerid

...bank (24 FXS) span=1,2,2,esf,b8zs # span 2 is for NuVox PRI (1-23B, 24D) span=2,1,2,esf,b8zs # span 3 is unused span=3,0,0,esf,b8zs # span 4 is unused span=4,0,0,esf,b8zs # # zapata.conf [channels] ; ; Default language ; language=en ; ; Default context ; context=dialnational ; signalling=fxo_ks use_callerid=yes callwaiting=no restrictcid=no usecallingpres=yes callwaitingcallerid=no threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=no echotraining=yes relaxdtmf=no rxgain=0.0 txgain=0.0 callgroup=1 pickupgroup=1 immediate=no amaflags=billing <cha...

...8 WARNING[1217602880]: File chan_zap.c, Line 1321 (zt_call): cidspill already exists?? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ /* Don't send audio while on hook, until the call is answered */ ????????????????????????p->dialing = 1; ????????????????????????if (p->use_callerid) { ????????????????????????????????/* Generate the Caller-ID spill if desired */ ????????????????????????????????if (p->cidspill) { ????????????????????????????????????????ast_log(LOG_WARNING, "cidspill already exists??\n"); ????????????????????????????????????????free(p->cidspill);...

All, Having problems terminating to a Nuvox PRI, the tech at Nuvox is saying Asterisk is transmitting in CCITT (aka ITU?) when they're expecting (and will only accept) ANSI. The question is, is there a simple way to change this or am I stuck with rewriting code? I googled and checked the mailing list and found nothing, I could be barking up the wrong tree I guess. PRI is not my forte.

Hi All, Having searched the archives, I can see there has been much discussion at various points regarding capture of caller id information from good old BT. If I understand correctly, it seems that not only do the drivers not currently support it, but my X101P possibly/probably can't do it anyway due to hardware? So, that leaves me with the modem route, which seems more and more unlikely,