When dialing out, Freeswitch/Openzap is not detecting that an analog FXO channel is disconnected and tries dialing out on the channel anyway. No error is reported. The call doesn’t timeout until a minute later. Shouldn’t Freeswitch/Openzap skip over a disconnected channel to the next connected channel?

I have configured a Sangoma A200 FXO card as a FXO span.

[span wanpipe FXO]

name => PSTN Line 1

number => 4253491059

fxo-channel => 2:3

name => PSTN Line 2

number => 4253491058

fxo-channel => 2:4

The wanpipe driver does detect and report when a CO line is connected or disconnected (in /var/log/messages), and Freeswitch/Openzap gets an event as reported in the log.

/var/log/messages: Feb 25 15:23:10 roberth-c53 kernel: wanpipe2: Module 3: FXO Line is disconnected!

FS_CLI: 2010-02-25 15:23:10.711604 [DEBUG] ozmod_analog.c:788 EVENT [ALARM_TRAP][3:1] STATE [DOWN]

/var/log/messages: Feb 25 15:23:44 roberth-c53 kernel: wanpipe2: Module 4: FXO Line is connected!

FS_CLI: 2010-02-25 15:23:44.901979 [DEBUG] ozmod_analog.c:788 EVENT [ALARM_CLEAR][3:2] STATE [DOWN]

I have the dialplan configured to use the next available port in the FXO span (there will be more than 2 channels later).

</condition>

</extension>

Here is a portion of the log when that shows dialing out on a disconnected analog FXO channel.

EXECUTE sofia/internal/5410@192.168.72.45:5060 bridge(openzap/FXO/a/93491045)

2010-02-25 15:26:17.891443 [DEBUG] mod_openzap.c:366 Set codec PCMU 20ms

2010-02-25 15:26:17.891443 [DEBUG] mod_openzap.c:1257 Connect outbound channel OpenZAP/3:1/93491045

2010-02-25 15:26:17.891443 [NOTICE] switch_channel.c:642 New Channel OpenZAP/3:1/93491045 [3c8f46f5-77a8-498f-a51c-015837746cb7]

2010-02-25 15:26:17.891443 [DEBUG] mod_openzap.c:1269 (OpenZAP/3:1/93491045) State Change CS_NEW -> CS_INIT

2010-02-25 15:26:17.891443 [DEBUG] switch_core_session.c:1019 Send signal OpenZAP/3:1/93491045 [BREAK]

2010-02-25 15:26:17.891443 [DEBUG] ozmod_analog.c:59 Changing state on 3:1 from DOWN to DIALING

2010-02-25 15:26:17.891443 [WARNING] switch_core_session.c:486 OpenZAP/3:1/93491045 does not support the proxy feature, disabling.

2010-02-25 15:26:17.891443 [DEBUG] ozmod_analog.c:279 ANALOG CHANNEL thread starting.

2010-02-25 15:26:17.891443 [DEBUG] ozmod_analog.c:450 Executing state handler on 3:1 for DIALING

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:314 (OpenZAP/3:1/93491045) Running State Change CS_INIT

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:338 (OpenZAP/3:1/93491045) State INIT

2010-02-25 15:26:17.891443 [DEBUG] mod_openzap.c:394 (OpenZAP/3:1/93491045) State Change CS_INIT -> CS_ROUTING

2010-02-25 15:26:17.891443 [DEBUG] switch_core_session.c:1019 Send signal OpenZAP/3:1/93491045 [BREAK]

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:338 (OpenZAP/3:1/93491045) State INIT going to sleep

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:314 (OpenZAP/3:1/93491045) Running State Change CS_ROUTING

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:341 (OpenZAP/3:1/93491045) State ROUTING

2010-02-25 15:26:17.891443 [DEBUG] mod_openzap.c:417 OpenZAP/3:1/93491045 CHANNEL ROUTING

2010-02-25 15:26:17.891443 [DEBUG] switch_ivr_originate.c:66 (OpenZAP/3:1/93491045) State Change CS_ROUTING -> CS_CONSUME_MEDIA

2010-02-25 15:26:17.891443 [DEBUG] switch_core_session.c:1019 Send signal OpenZAP/3:1/93491045 [BREAK]

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:341 (OpenZAP/3:1/93491045) State ROUTING going to sleep

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:314 (OpenZAP/3:1/93491045) Running State Change CS_CONSUME_MEDIA

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:360 (OpenZAP/3:1/93491045) State CONSUME_MEDIA

2010-02-25 15:26:17.891443 [DEBUG] switch_core_state_machine.c:360 (OpenZAP/3:1/93491045) State CONSUME_MEDIA going to sleep

Thanks,

Robert