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