[Asterisk-Users] CallerID hosed
Karl Putland
karl at putland.linux-site.net
Thu Apr 24 11:22:51 MST 2003
On Thu, 2003-04-24 at 11:49, Eric Wieling wrote:
> Shouldn't that be:
>
> exten => s,2,SetCallerID("${CALLERIDNAME}" <${CALLERIDNUM}>)
>
Wouldn't matter. CALLERIDNAME is still a bad pointer.
> or am I missing something?
>
>
> On Thu, 2003-04-24 at 11:09, Karl Putland wrote:
> > This is with an x100p (the motorola chipset)
> >
> > Two problems.
> > Looks like CALLERIDNAME is being used uninitialized.
> > On my other phones the callerid is fine and my buttset shows that the
> > callerid passes the checksum.
> >
> >
> > This is the relevant portion of extensions.conf
> > exten => s,1,Answer
> > exten => s,2,SetCallerID(H ${CALLERIDNAME} <${CALLERIDNUM}>)
> > exten => s,2,Dial(${MGCP_ALL})
> >
> > Here is the console output.
> >
> > -- Starting simple switch on 'Zap/1-1'
> > NOTICE[13326]: File callerid.c, Line 238 (callerid_feed): Caller*ID
> > failed checksum
> > NOTICE[13326]: File chan_zap.c, Line 4060 (ss_thread): Got event 2
> > (Ring/Answered)...
> > DEBUG[13326]: File chan_zap.c, Line 922 (zt_enable_ec): Enabled echo
> > cancellation on channel 1
> > -- Executing Answer("Zap/1-1", "") in new stack
> > DEBUG[13326]: File chan_zap.c, Line 1746 (zt_answer): Took Zap/1-1 off
> > hook
> > -- Executing SetCallerID("Zap/1-1",
> > "Hïÿ½j;@, at hf@Ôï ìïø <>") in new stack
> >
--
Karl Putland <karl at putland.linux-site.net>
More information about the asterisk-users
mailing list