No subject

point, and then calling the DISA application.  Jamie then dials 94126101,
and that gets routed to the [features] context, where we print out the
CallerID information before calling the number via another DAHDI channel.


Here's the flow when we call DISA without the third parameter:

    -- Executing [6101 at disa:1] Set("DAHDI/23-1", "CALLERID(num)=6101") in
new stack
    -- Executing [6101 at disa:2] Verbose("DAHDI/23-1", "2,Caller ID
information is ["" <6101>]") in new stack
  == Caller ID information is ["" <6101>]
    -- Executing [6101 at disa:3] DISA("DAHDI/23-1", "no-password,features")
in new stack
[Apr  7 19:47:31] WARNING[13186]: chan_dahdi.c:2683 dahdi_enable_ec:
Unable to enable echo cancellation on channel 23 (No such device)
    -- Executing [94126101 at features:1] NoOp("DAHDI/23-1", "CallerID is:
"STAPLETON JAMIE" <8045551212>") in new stack
    -- Executing [94126101 at features:2] Dial("DAHDI/23-1",
"DAHDI/g1/4126101") in new stack

As you can see, the outbound caller ID was the original CallerID number
(8045551212), not the new caller id (6101) that was set on the channel
before calling DISA.  The DISA application is obviously *not* looking at
the CallerID number on the channel set via the CALLERID dialplan function. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-07 19:17 jsmith         Note Added: 0120200                          
======================================================================