[Asterisk-Users] Re: Two FXO: How to dial a number when a RING comes in?

[Vincent Delporte]

Thanks Noah for the help, but... no go :-/

>From: "Noah Miller"
>
>ONE: You should answer an incoming zap line before doing anything with it, 
>so do this:
>
>exten => s,1,Answer
>exten => s,2,Dial(Zap/2/014XXXXXX)

When I try this, instead of using the Zap/2 interface to ring the other 
number, Asterisk goes off hook and I hear some kind of static:

Jun 19 18:17:46 NOTICE[2186] chan_zap.c: Got event 18 (Ring Begin)...
Jun 19 18:17:47 NOTICE[2186] chan_zap.c: Got event 2 (Ring/Answered)...
Jun 19 18:17:51 NOTICE[2186] chan_zap.c: Got event 18 (Ring Begin)...

>TWO: Are there any console messages?  Can you dial into the system and get 
>internal extensions?  Maybe you could try a testing dialplan like this:
>
>exten => s,1,Answer
>exten => s,2,Waitexten(10)
>
>exten => 100,Dial(Zap/2/014XXXXXX)
>
>Then call in and after you're connected, dial 100 to see if it will dial 
>out on ZAP/2

When I try this, /var/log/asterisk/messages says:

Jun 19 18:12:38 NOTICE[1660] pbx.c: Cannot find extension '100' in context 
'(null)'
Jun 19 18:12:38 WARNING[1660] pbx_config.c: Invalid priority/label 'Dial' 
at line 172

I just realized that I blindly typed the above, without realizing that the 
second parameter is missing. Regardless, since even the first test doesn't 
work... Just in case, I'd like to repeat that I don't want Asterisk to 
answer the call: I just want it to use the second FXO to ring another 
phone, at a remote location.

For reference, I went back to the original configuration that I used, but 
it picks up the line and remains silent (static noises):

------- extensions.conf ----------
[cherbourg]
exten => s,1,Dial(Zap/2/0145815059)
------- zaptel.conf -----------
fxsks=1,2
loadzone=fr
defaultzone=fr
-------- zapata.conf -----------
[channels]
;context=default
context=cherbourg
signalling=fxs_ks
usecallerid=yes
echocancel=yes
callgroup=1
pickupgroup=1
immediate=no
callerid="my caller id"<(123) 123-1234>
channel=>1
;context=default
context=cherbourg
signalling=fxs_ks
usecallerid=yes
echocancel=yes
callgroup=1
pickupgroup=1
immediate=no
callerid="my caller id"<(123) 123-1234>
channel=>2

and just in case you're wondering if the FXO cards are correctly loaded...
----- dmesg ---------
Jun 19 18:12:31 localhost syslogd 1.4.1: restart.
Jun 19 18:12:31 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jun 19 18:12:31 localhost kernel: Linux version 2.6.13.4-1.x86.i686.cmov 
(conary.rpath.com at rpl:1) (gcc version 3.4.4) #1 Wed Nov 23 11:31:48 EST 2005
[...]
Jun 19 18:12:31 localhost kernel: Zapata Telephony Interface Registered on 
major 196
Jun 19 18:12:31 localhost kernel: Zaptel Version:  Echo Canceller: KB1
Jun 19 18:12:31 localhost kernel: Registered Tormenta2 PCI
Jun 19 18:12:31 localhost kernel: ACPI: PCI Interrupt Link [LNKA] enabled 
at IRQ 5
Jun 19 18:12:31 localhost kernel: PCI: setting IRQ 5 as level-triggered
Jun 19 18:12:31 localhost kernel: ACPI: PCI Interrupt 0000:00:08.0[A] -> 
Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
Jun 19 18:12:32 localhost kernel: wcfxo: DAA mode is 'FCC'
Jun 19 18:12:32 localhost kernel: Found a Wildcard FXO: Generic Clone
Jun 19 18:12:32 localhost kernel: ACPI: PCI Interrupt Link [LNKD] enabled 
at IRQ 10
Jun 19 18:12:32 localhost kernel: PCI: setting IRQ 10 as level-triggered
Jun 19 18:12:32 localhost kernel: ACPI: PCI Interrupt 0000:00:09.0[A] -> 
Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
Jun 19 18:12:32 localhost kernel: wcfxo: DAA mode is 'FCC'
Jun 19 18:12:32 localhost kernel: Found a Wildcard FXO: Generic Clone
Jun 19 18:12:32 localhost kernel: usbcore: registered new driver wcusb
Jun 19 18:12:32 localhost kernel: Wildcard USB FXS Interface driver registered
Jun 19 18:12:35 localhost kernel: Registered tone zone 2 (France)

=> Surely, I can't be the only one in this list who needs to set up 
Asterisk simply to ring a remote phone when a call comes in at the office. 
Anybody has a working configuration that I could use as a reference?

Thank you :-)
VD.


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.394 / Virus Database: 268.9.1/369 - Release Date: 19/06/2006