asterisk users - May 2006 - Callerid and trunk

Ok, I must be really stupid here -

I'm playing with ael and svn trunk.

given the following in ael:

context isdn10 {

        444601 => {
                 Answer();
                 NoOp(${CALLERIDNUM});
                 Hangup();
         };
};

isdn10 is the incoming isdn context.

why do I get this on the console:

   -- Accepting call from '01702xxxxxx' to 'yyyyyy' on channel
0/1, span 1
     -- Executing [isdn10:1] Answer("Zap/1-1", "") in new
stack
     -- Executing [isdn10:2] NoOp("Zap/1-1", "") in new
stack
     -- Executing [isdn10:3] Hangup("Zap/1-1", "") in new
stack

callerid must be working: get the from (01702xxxxxx) and to yyyyyy

but why is ${CALLERIDNUM} blank ?

Julian.

On Wednesday 31 May 2006 09:08, Julian Lyndon-Smith
wrote:
> Ok, I must be really stupid here -
>
> I'm playing with ael and svn trunk.
>
> given the following in ael:
>
> context isdn10 {
>
>         444601 => {
>                  Answer();
>                  NoOp(${CALLERIDNUM});
>                  Hangup();
>          };
> };
>
> isdn10 is the incoming isdn context.
>
> why do I get this on the console:
>
>    -- Accepting call from '01702xxxxxx' to 'yyyyyy' on
channel 0/1, span 1
>      -- Executing [isdn10:1] Answer("Zap/1-1", "") in
new stack
>      -- Executing [isdn10:2] NoOp("Zap/1-1", "") in new
stack
>      -- Executing [isdn10:3] Hangup("Zap/1-1", "") in
new stack
>
> callerid must be working: get the from (01702xxxxxx) and to yyyyyy
>
> but why is ${CALLERIDNUM} blank ?
Because it's deprecated and I assume dropped completely for 1.4. Use 
${CALLERID(num)}

hads

-- 
Destiny is a good thing to accept when it's going your way. When it
isn't,
don't call it destiny; call it injustice, treachery, or simple bad luck.
		-- Joseph Heller, "God Knows"