Enterprise bridge, groups and "follow me" dialplan
I am trying to implement the following bridging scenario: <action application="set" data="call_timeout=30"/> <action application="bridge" data="group/group1@domain,[leg_delay_start=10]group/group2@domain"/> ... i.e. all phones in group1 should ring for 10 seconds and if nobody answers group1+group2 rings for additional 20 seconds. That almost works, but only the first phone rings in either group: [WARNING] switch_ivr_originate.c:2339 Only calling the first element in the list in this mode. Surely I need enterprise bridge: <action application="bridge" data="group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/> but now there is no correct caller id and no leg delay. Caller id can be restored with: <action application="bridge" data=" <origination_caller_id_name=${caller_id_name},origination_caller_id_number=${caller_id_number}> group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/> (is this a bug or design decision?), but what to do with leg delay? [leg_delay_start=10] is simply ignored there. - Dmitry Bely
How are you defining what is in each group? Are these simply locally registered users? External phone numbers? Both? Those questions will help determine how to proceed. -MC On Sat, Feb 19, 2011 at 9:05 AM, Dmitry Bely <dmitry.bely@gmail.com> wrote:
I am trying to implement the following bridging scenario:
<action application="set" data="call_timeout=30"/> <action application="bridge" data="group/group1@domain,[leg_delay_start=10]group/group2@domain"/> ...
i.e. all phones in group1 should ring for 10 seconds and if nobody answers group1+group2 rings for additional 20 seconds.
That almost works, but only the first phone rings in either group: [WARNING] switch_ivr_originate.c:2339 Only calling the first element in the list in this mode.
Surely I need enterprise bridge:
<action application="bridge" data="group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/>
but now there is no correct caller id and no leg delay. Caller id can be restored with:
<action application="bridge" data="
<origination_caller_id_name=${caller_id_name},origination_caller_id_number=${caller_id_number}> group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/>
(is this a bug or design decision?), but what to do with leg delay? [leg_delay_start=10] is simply ignored there.
- Dmitry Bely
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Tue, Feb 22, 2011 at 3:39 AM, Michael Collins <msc@freeswitch.org> wrote:
How are you defining what is in each group? Are these simply locally registered users? External phone numbers? Both? Those questions will help determine how to proceed.
Yes, they are mostly locally registered users. The groups are defined like <group name="group1"> <users> <user id="1001" type="pointer"/> <user id="1002" type="pointer"/> </users> </group> Some users are associated with external numbers: <include> <user id="external_user"> <params> <param name="dial-string" value="[toll_allow=local]loopback/XXXXXXX/default/XML"/> </params> <variables> <variable name="user_context" value="default"/> </variables> </user> </include> if that matters.
On Sat, Feb 19, 2011 at 9:05 AM, Dmitry Bely <dmitry.bely@gmail.com> wrote:
I am trying to implement the following bridging scenario:
<action application="set" data="call_timeout=30"/> <action application="bridge" data="group/group1@domain,[leg_delay_start=10]group/group2@domain"/> ...
i.e. all phones in group1 should ring for 10 seconds and if nobody answers group1+group2 rings for additional 20 seconds.
That almost works, but only the first phone rings in either group: [WARNING] switch_ivr_originate.c:2339 Only calling the first element in the list in this mode.
Surely I need enterprise bridge:
<action application="bridge" data="group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/>
but now there is no correct caller id and no leg delay. Caller id can be restored with:
<action application="bridge" data="
<origination_caller_id_name=${caller_id_name},origination_caller_id_number=${caller_id_number}> group/group1@domain:_:[leg_delay_start=10]group/group2@domain"/>
(is this a bug or design decision?), but what to do with leg delay? [leg_delay_start=10] is simply ignored there.
- Dmitry Bely
participants (2)
-
Dmitry Bely
-
Michael Collins