[Asterisk-Users] Zaphfc CallerID problem...

[Massimo De Nadal]

>
> > Hi,
> >
> > On Mon, Aug 02, 2004 at 01:20:32PM +0200, Massimo De Nadal wrote:
> > > > we had similar problems and fixed them by setting the CIDName to the
> > > CallerID:
> > > >
> > > > [from-ISDN1]
> > > > exten=>s,1,Wait(1)
> > > > exten=>s,2,SetCIDName(${CALLERID})
> > > > exten=>s,3,Dial(Sip/cisco1&Sip/xlite1,30,tTr)
> > > > exten=>s,4,HangUp
> > >
> > > Thank you for your answer. I think my problem is a little bit
different.
> > > If I add a priority like:
> > > exten => s,2,NoOp (${CALLERID}_${CALLERIDNUM}${CALLERIDNAME})
> > > I can see that CALLERID and the other variables have no value.... it
> seems
> > > like channel zap knows the CALLERID but doesn't set the variables
> values.
> >
> > Its the same on our installation. Instead of zaphfc we're using quozap
> > with a QuadBRI. And its working with SetCIDName.
> >
> > > Maybe a zaphfc bug ?
> > It could also be a wanted behavior. There's antother Question: Do you
> > always trust the received number (this applies to all channel types)?
>
> Thanks for your help again.
>
> Well, I'll try to explain myself better (I'm really sorry for my bad
english
> :-)
>
> If I try to: exten =>s,2,SetCIDName(FOOBAR) , when I receive a call on
phone
> display I can read FOOBAR correctly, but the variable CALLERID (which is
> expanded by the syntax ${CALLERID} ) contains no values at all....
> Yes, I always want to trust received number. What I need is to read on the
> phone the caller number. If the number is masqueraded or hacked or other,
it
> doesn't matter.

OK!!! I've solved the problem removing PriTrustUserCID=yes from zapata.conf
.
Now CID works great !