[Asterisk-Users] Asterisk ISDN CallerID identification failure

[Armin Schindler]

On Tue, 23 Aug 2005, Voicomm User wrote:
> Hello,
> 
> We have 4 'Onramp-2' Telstra ISDN BRI services operating on Asterisk
> Server with Eicon 4BRI card. For most part the service is okay.
> However, we are are having problems with passing callerID to internal
> extensions.
> 
> This is the set of command executed.
> 
> exten => <pattern>,1,Answer ; Answer the line
> exten => <pattern>,2,NoOp(${DNIS}) ; debug statements
> exten => <pattern>,3,NoOp(${CALLERID})
> exten => <pattern>,4,NoOp(${CALLERIDNUM})
> exten => <pattern>,5,NoOp(${CALLERIDNAME})
> 
> exten => <pattern>,6,SetCIDNum(${CALLERIDNUM}) ; setting caller id
> exten => <pattern>,7,Macro(dialexten,${DNID:${PRETRIM}},SIP/${VIC}${DNID})
> exten => <pattern>,8,Hangup
> 
> Now all the above NoOp cmds display null "". I am able to see the
> caller id appear on asterisk CLI when a call comes in by on a channel,
> but it doesn't get set. Any leads will be much appreciated. This is what 
> I see in asterisk cli,
> 
>     -- Executing Answer("CAPI[contr4/86986114]/105", "") in new stack
>     -- CAPI Answering for MSN 6986114
>     -- Executing NoOp("CAPI[contr4/86986114]/105", "") in new stack
>     -- Executing NoOp("CAPI[contr4/86986114]/105", "") in new stack
>     -- Executing NoOp("CAPI[contr4/86986114]/105", "") in new stack
>     -- Executing NoOp("CAPI[contr4/86986114]/105", "") in new stack
> 
> I have confirmed with the telco that ISDN services come with Caller ID by 
> default.
> The ISDN mode is pointtopoint.

If you enable capi debugging (set verbose 5, capi debug), you can see if the 
callerid is present.

Armin