Ok, now I'm really getting places. Something else has got me stumped - asterisk does not receive any callerid information. If I set up an extension as follows: exten => 444444,1,Sayalpha(${CALLERID}) exten => 444444,2,Hangup I get the application saying Executing SayAlpha("Zap/1-1","") in new stack which implies that the ${CALLERID} variable is blank. Do I need to setup callerid on my incoming line (BT euroisdn), or is it a zapata.conf setting (I've investigated all of the callerid options) Also, is there a function / command to display information on the command line ? for example, it would be useful to be able to say exten => 1,DebugMessage("test message for ext &1, called from &2",${EXTEN},${CALLERID}) and have that message appear on the asterisk console. Julian.
On Fri, 13 Aug 2004, Asterisk wrote:> Do I need to setup callerid on my incoming line (BT euroisdn), or is it a > zapata.conf setting (I've investigated all of the callerid options)It is not too unlikely that BT will charge you for the CallerID information. Is it a PRI or a BRI?> Also, is there a function / command to display information on the command > line ?Nop will have it's arguments printed and logged unless you are running non-verbose. Start asterisk with a few -v. Peter
Maybe Matching Threads
- ISDN outgoing caller id
- Set caller id on Swedish PRI (euroisdn)
- Can't dial SIP<->EuroISDN (HFC-S based PCI ISDN card): Unable to create channel of type 'Zap'
- Zaptel doesn't see remote hangup ? euro-isdn
- auto-gain, or different gain between incoming and outgoing calls (EURO ISDN PRI) ?