Yes Bleg hangs up first but i am not able to fetch the hangupcause here,

hangup cause: ${bridge_hangup_cause}

in logs i get as :-

EXECUTE sofia/internal/7001@203.153.53.181 log(1 B-leg hangup Q850 cause: )
2010-12-18 09:37:08.342225 [DEBUG] switch_core_state_machine.c:449 (sofia/external/1234@203.153.53.188) Callstate Change HANGUP -> DOWN
2010-12-18 09:37:08.342225 [ALERT] mod_dptools.c:1152 B-leg hangup Q850 cause:
2010-12-18 09:37:08.342225 [DEBUG] switch_core_state_machine.c:452 (sofia/external/1234@203.153.53.188) Running State Change CS_DESTROY


Regds
Sam



On Sat, Dec 18, 2010 at 3:21 AM, Michael Collins <msc@freeswitch.org> wrote:
You're almost there. First off, you can delete this line:
<action application="set" data="hangup_after_bridge=false"/>
That's the default behavior and you have to set it prior to the bridge anyway.

Move this line before the bridge:
<action application="set" data="continue_on_fail=true"/>
Otherwise it won't have any effect.

The other stuff should work if the b-leg hangs up first, but not if the a-leg does. 

-MC


On Thu, Dec 16, 2010 at 2:28 AM, Sam <u2nsam@gmail.com> wrote:

I am not able to fetch the hangup cause in the dial-plan by using log function .
I would like to use that hangup cause variable for further routing so that
the routing would be conditional to hangup cause.

Regards
Sam

On Wed, Dec 15, 2010 at 9:48 AM, samir <u2nsam@gmail.com> wrote:

Hello friends,

was trying to create a routing rule to to route calls by accounting to the
hangup causes,

I have written below syntax but it fails to give the cause code to the
varriable for routing.

<extension name="refer">
              <condition field="destination_number" expression="^1234$">


      <action application="bridge" data="sofia/external/1234@X.X.X.X"/>
      <action application="set" data="hangup_after_bridge=false"/>
      <action application="set" data="continue_on_fail=true"/>
      <action application="log" data="1 B-leg hangup cause:
${bridge_hangup_cause}"/>
      <action application="transfer" data="${bridge_hangup_cause} XML
conbridge"/>

              </condition>


  </extension>

      <extension name="no user">
              <condition field="destination_number"
expression="^(NO_USER_RESPONSE)$">
              <action application="bridge"
data="sofia/external/4567@X.X.X.X"/>

              </condition>
      </extension>


here the ${bridge_hangup_cause} is not getting executed. Am I doing it right
or is there any other way to do it.

Regards
Sam
--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/routing-via-hangup-cause-tp5837136p5837136.html
Sent from the freeswitch-users mailing list archive at Nabble.com.

_______________________________________________
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


_______________________________________________
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



_______________________________________________
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