Hi list,
I'm having a problem with CallerID names not showing up when calls come
in. I have dialplan code to store the callerid(name) away and it is
blank (null). However, the voicemail variable ${VM_CALLERID} has the
name field populated. For example, here is some of the dialplan code:
2. Set(CALLER_ID_INFO_ALL=${CALLERID(all)})
3. Set(CALLER_ID_INFO_NAME=${CALLERID(name)})
4. Set(CALLER_ID_INFO_NUM=${CALLERID(num)})
5. Set(CALLER_ID_INFO_ANI=${CALLERID(ANI)})
6. Set(CALLER_ID_INFO_DNID=${CALLERID(DNID)})
Which yields this at the CLI:
-- Executing [3703 at from_outside:2] Set("DAHDI/1-1",
"CALLER_ID_INFO_ALL="" <2565551212>") in new stack
-- Executing [3703 at from_outside:3] Set("DAHDI/1-1",
"CALLER_ID_INFO_NAME=") in new stack
-- Executing [3703 at from_outside:4] Set("DAHDI/1-1",
"CALLER_ID_INFO_NUM=2565551212") in new stack
-- Executing [3703 at from_outside:5] Set("DAHDI/1-1",
"CALLER_ID_INFO_ANI=2565551212") in new stack
Note the first line should have the name field with the number, but does
not.
HOWEVER the voicemail notification contains:
"Just wanted to let you know you were just left a 0:04 long message
(number 1) in mailbox 3703 from "SMITH CASSIUS "
<2565551212>"
So - I know the NAME field is getting into the system, but it's not
showing up on the phones (and with telemarketers, that annoys my
users).
I'm using Asterisk 1.6.2.9, DAHDI 2.3.0
I have added callerid=asreceived to chan_dahdi.conf for my inbound
trunks, and shrinkcallerid=no to my sip.conf. (without effect)
Any ideas?
THANKS
Cassius
On Mon, Aug 2, 2010 at 2:56 PM, Cassius Smith <cassius at cassius.org> wrote:> > Any ideas? > > THANKS > Cassius >Add a Wait(2) before your first Set statement. Sometimes callerid takes a few seconds to arrive over the line, depending on your technology. -- Thanks, --Warren Selby http://www.selbytech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100802/eeb72173/attachment.htm
Thanks Warren. That fixed it. I am using T1's and didn't think the spill would take that long. Ciao, Cassius>Add a Wait(2) before your first Set statement. Sometimes callerid >takes a >few seconds to arrive over the line, depending on your technology.
Sorry for the delay - I lost this message in the middle of a digest. I tried Answer(2000) and was getting an annoying warning: [Aug 15 17:20:11] WARNING[15516]: channel.c:1044 __ast_queue_frame: Exceptionally long voice queue length queuing to DAHDI/1-1 So I changed it back to Wait(2). I'll try shorter wait intervals and see what happens. Cassius> Subject: Re: [asterisk-users] Caller ID issue > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users at lists.digium.com> > Message-ID: > <AANLkTi=S6fboEqySvPVw25TmEvKDPNjbvjmsvniWuhbS at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > In most cases wait(.5) will do. I would not recommend using > answer(2000) as that answers the channel, which means you start > getting billed. > > On 8/2/10, Peder <peder at networkoblivion.com> wrote: > >> I am using T1's and didn't think the spill would take that long. > > > >> PRI no, E&M yes. > > > > Some PRI take that long too because the telco sends the name in a > followup > > message, not in the initial call setup. > > > > > > -- > >