Asterisk ZAP ghost call looping and looping

Hi,

I installed Asterisk 1.4.18 and I have a FXO port using OEM Wildcard X100P card. I am able to make outbound call and receive an inbound call through this FXO port. But here is the strange thing: I have 2 phone lines (A and B) from AT&T. The Asterisk set-up is working with line A but not line B.

For example: when I switched the phone line to connect to line B from line A, I started to receive some “ghost” call. I mean, a call was received in Zap channel and my extension was ringing. When I answered it, I just heard the dial-tone. After I hung up, the same ghost call was produced again and again. When I used another real handset to connect to line B, there was no incoming call at all. Therefore I think this might be something wrong in my set up which making my Zap driver is too sensitive or something.

Your help is greatly appreciated!! Below is what I saw from Asterisk CLI.

-- Starting simple switch on 'Zap/1-1'

[May 27 15:43:18] NOTICE[3339]: chan_zap.c:6376 ss_thread: Got event 18 (Ring Begin)…
[May 27 15:43:18] NOTICE[3339]: chan_zap.c:6376 ss_thread: Got event 2 (Ring/Answered)…
[May 27 15:43:19] NOTICE[3339]: chan_zap.c:6376 ss_thread: Got event 18 (Ring Begin)…
== Starting Zap/1-1 at DID_trunk_1,s,1 failed so falling back to exten ‘s’
== Starting Zap/1-1 at DID_trunk_1,s,1 still failed so falling back to context ‘default’
[May 27 15:43:19] WARNING[3339]: pbx.c:2470 __ast_pbx_run: Channel ‘Zap/1-1’ sent into invalid extension ‘s’ in context ‘default’, but no invalid handler
– Hungup ‘Zap/1-1’

(… here we go again, another call will be created again and again…)

-- Starting simple switch on 'Zap/1-1'

[May 27 15:43:22] NOTICE[3340]: chan_zap.c:6376 ss_thread: Got event 18 (Ring Begin)…
[May 27 15:43:23] NOTICE[3340]: chan_zap.c:6376 ss_thread: Got event 2 (Ring/Answered)…
[May 27 15:43:24] NOTICE[3340]: chan_zap.c:6376 ss_thread: Got event 18 (Ring Begin)…
== Starting Zap/1-1 at DID_trunk_1,s,1 failed so falling back to exten ‘s’
== Starting Zap/1-1 at DID_trunk_1,s,1 still failed so falling back to context ‘default’
[May 27 15:43:24] WARNING[3340]: pbx.c:2470 __ast_pbx_run: Channel ‘Zap/1-1’ sent into invalid extension ‘s’ in context ‘default’, but no invalid handler
– Hungup ‘Zap/1-1’

The x100p is no longer supported. They work just enough to make you think there’s just some configuration change you need to make. However, the configuation changes will have no effect.

I fought with one for 6 months. I was helping a friend who was building a system, and he cheaped out on the card. I finally convinced him to give up. His card did exactly the same thing you describe and we never got the CallerID working.

The zap drivers will recognize an x100p card, but they don’t work with it correctly. You’re better off with a supported card. Buy a Digium TDM card. You’ll be much happier with the results.