Is there a reason the variable ${DNIS} does not get set with incoming
calls via chan_capi ?
Is it related to the MSN=X in capi.conf ?
version = chan_capi-cm-0.6.3
example;
exten => _95555555XX,1,NoOp, ${EXTEN}, ${DNIS}
== ISDN1: Incoming call '0400000000' -> '95555555'
-- Executing SetCDRUserField("CAPI/ISDN1/955555 55-135",
"Incoming")
in new stack
-- Executing NoOp("CAPI/ISDN1/95555555-135", " 95555555, ")
in new stack
8< **SNIP**
> CAPI INFO 0x3490: Normal call clearing
== Spawn extension (main, s, 2) exited non-zero on 'CAPI/
ISDN1/95555555-135'
== ISDN1: CAPI Hangingup
On 2/20/06, Nathan Alberti <asterisk@iipc.com.au> wrote:> Is there a reason the variable ${DNIS} does not get set with incoming > calls via chan_capi ? > > Is it related to the MSN=X in capi.conf ?Just a guess, are you thinking of ${DNID} instead? There's no direct mention of ${DNIS} on the wiki variables page, but ${DNID} works for me with a BRI... Andrew -- Linux supports the notion of a command line or a shell for the same reason that only children read books with only pictures in them. Language, be it English or something else, is the only tool flexible enough to accomplish a sufficiently broad range of tasks. -- Bill Garrett
On Mon, 20 Feb 2006, Nathan Alberti wrote:> Is there a reason the variable ${DNIS} does not get set with incoming calls > via chan_capi ?I don't know any channel setting DNIS. What are you expecting with that variable?> Is it related to the MSN=X in capi.conf ?No. msn= is obsolete and does not exist in chan_capi since many releases.> version = chan_capi-cm-0.6.3 > > example; > > exten => _95555555XX,1,NoOp, ${EXTEN}, ${DNIS}If you mean the caller number, then try ${CALLERID(number)} Armin