[Freeswitch-users] Sangoma A200 FXS callwaiting and dialplan statements

Robert Hadley robert.hadley at teotech.com
Tue Feb 2 14:54:27 PST 2010


I have a server that has Freeswitch (1.0.5.pre9) a Sangoma A101 (E1/T1) and
Analog A200 cards using OpenZap.  The cards are connected.  The wanrouter
version is 3.5.8.6 as the newer version didn't work for us yet.  Also trying
to test with the FS trunk but having other wanpipe driver issues.

 

I have a question about using the A200 card.  The intent is to hook up FAX
machines to the two FXS ports.  The desired behavior is the first call goes
to the first FXS port one, and while port one is busy a second call goes to
the second port.

 

In the Freeswitch dialplan there is a statement to bridge to FXS port 1 and
if that fails then bridge to FXS port 2.  However, the first bridge never
fails even when it's busy.  I notice the A200 card supports call waiting.
The FS debug messages show that is what is happening.

 

Question: How do I disable call waiting on the A200 card when used with
OpenZap?

 

I am not sure about whether the hangup_after_bridge=true and
continue_on_fail=true are necessary or in the correct spots.  I've tried
calling with these statements present or not and moved after the first
bridge but doesn't appear to affect the status of the first bridge
statement.

 

Question: Are the hangup_after_bridge=true and continue_on_fail=true
statements necessary and in the right spot?

 

Dialplan statements:

    <extension name="fxsfax">

      <!-- This routes destinations 1010 and 1011 calls to FXS card -->

      <condition field="destination_number" expression="^(101[0-1])$">

        <action application="answer"/>

        <action application="set" data="hangup_after_bridge=true"/>

        <action application="set" data="continue_on_fail=true"/>

        <action application="bridge" data="openzap/FXS/1"/>

        <action application="bridge" data="openzap/FXS/2"/>

 

Debug statements for second call to FXS/1 extension:

(Notice that several of statements mention CALLWAITING.)

2010-02-02 14:00:55.193948 [DEBUG] switch_core_session.c:639 Send signal
sofia/internal/1045 at 192.168.72.141:5060 [BREAK]

2010-02-02 14:00:55.193948 [NOTICE] mod_dptools.c:658 Channel
[sofia/internal/1045 at 192.168.72.141:5060] has been answered

2010-02-02 14:00:55.193948 [DEBUG] switch_channel.c:182
sofia/internal/1045 at 192.168.72.141:5060 receive message [AUDIO_SYNC]

EXECUTE sofia/internal/1045 at 192.168.72.141:5060 set(continue_on_fail=true)

2010-02-02 14:00:55.193948 [DEBUG] sofia.c:3787 Channel
sofia/internal/1045 at 192.168.72.141:5060 entering state [completed][200]

2010-02-02 14:00:55.193948 [DEBUG] mod_dptools.c:768
sofia/internal/1045 at 192.168.72.141:5060 SET [continue_on_fail]=[true]

EXECUTE sofia/internal/1045 at 192.168.72.141:5060 bridge(openzap/FXS/1)

2010-02-02 14:00:55.194948 [DEBUG] mod_openzap.c:366 Set codec PCMU 20ms

2010-02-02 14:00:55.194948 [DEBUG] mod_openzap.c:1191 Connect outbound
channel OpenZAP/2:1/

2010-02-02 14:00:55.194948 [NOTICE] switch_channel.c:613 New Channel
OpenZAP/2:1/ [bc08ce84-eff2-491c-b601-14b7329c71ea]

2010-02-02 14:00:55.194948 [DEBUG] mod_openzap.c:1203 (OpenZAP/2:1/) State
Change CS_NEW -> CS_INIT

2010-02-02 14:00:55.194948 [DEBUG] switch_core_session.c:1018 Send signal
OpenZAP/2:1/ [BREAK]

2010-02-02 14:00:55.194948 [DEBUG] ozmod_analog.c:78 Changing state on 2:1
from UP to CALLWAITING

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:314
(OpenZAP/2:1/) Running State Change CS_INIT

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:338
(OpenZAP/2:1/) State INIT

2010-02-02 14:00:55.194948 [DEBUG] mod_openzap.c:390 (OpenZAP/2:1/) State
Change CS_INIT -> CS_ROUTING

2010-02-02 14:00:55.194948 [DEBUG] switch_core_session.c:1018 Send signal
OpenZAP/2:1/ [BREAK]

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:338
(OpenZAP/2:1/) State INIT going to sleep

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:314
(OpenZAP/2:1/) Running State Change CS_ROUTING

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:341
(OpenZAP/2:1/) State ROUTING

2010-02-02 14:00:55.194948 [DEBUG] mod_openzap.c:413 OpenZAP/2:1/ CHANNEL
ROUTING

2010-02-02 14:00:55.194948 [DEBUG] switch_ivr_originate.c:66 (OpenZAP/2:1/)
State Change CS_ROUTING -> CS_CONSUME_MEDIA

2010-02-02 14:00:55.194948 [DEBUG] switch_core_session.c:1018 Send signal
OpenZAP/2:1/ [BREAK]

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:341
(OpenZAP/2:1/) State ROUTING going to sleep

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:314
(OpenZAP/2:1/) Running State Change CS_CONSUME_MEDIA

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:360
(OpenZAP/2:1/) State CONSUME_MEDIA

2010-02-02 14:00:55.194948 [DEBUG] switch_core_state_machine.c:360
(OpenZAP/2:1/) State CONSUME_MEDIA going to sleep

2010-02-02 14:00:55.210047 [DEBUG] sofia.c:3787 Channel
sofia/internal/1045 at 192.168.72.141:5060 entering state [ready][200]

2010-02-02 14:00:55.213006 [DEBUG] ozmod_analog.c:450 Executing state
handler on 2:1 for CALLWAITING

2010-02-02 14:00:55.657988 [DEBUG] switch_rtp.c:2004 Correct ip/port
confirmed.

2010-02-02 14:01:05.723334 [DEBUG] ozmod_analog.c:422 Changing state on 2:1
from CALLWAITING to UP

 

 

Thanks,

Robert

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100202/cc56a777/attachment-0002.html 


More information about the FreeSWITCH-users mailing list