Testing the recent gits introduced a problem which I was able to work around but wondered if this is an intended change or bug: If the caller_id_number is one of the numbers in a bridge command only 1 ring is done and the bridge ends, it appears as if originate_timeout is ignored, the trace is normal. Prior to the git update the bridge would continue to ring to the timeout and the caller would be bridged to all the numbers in the bridge so any phone could answer the call. What used to work in older git: <action application="bridge" data="<originate_timeout=23,origination_caller_id_number=${caller_id_number},origination_caller_id_name=${caller_id_name}>group/home@${domain_name}:_:sofia/gateway/${dial_gateway}/19161112222:_:sofia/gateway/${dial_gateway}/19163334444"/> Newer git. Now I have to execute an extension to check who is calling so they are not in the bridge: <extension name="bridge_call"> <condition field="destination_number" expression="^bridge_call$"> </condition> <condition field="${caller_id_number_work}" expression="^9161112222$" break="on-true"> <action application="bridge" data="<originate_timeout=23,origination_caller_id_number=${caller_id_number},origination_caller_id_name=${caller_id_name}>group/home@${domain_name}:_:sofia/gateway/${dial_gateway}/19163334444"/> </condition> <condition field="${caller_id_number_work}" expression="^9163334444$" break="on-true"> <action application="bridge" data="<originate_timeout=23,origination_caller_id_number=${caller_id_number},origination_caller_id_name=${caller_id_name}>group/home@${domain_name}:_:sofia/gateway/${dial_gateway}/19161112222"/> </condition> <condition field="${caller_id_number_work}" expression="^(\d+)$"> <action application="bridge" data="<originate_timeout=23,origination_caller_id_number=${caller_id_number},origination_caller_id_name=${caller_id_name}>group/home@${domain_name}:_:sofia/gateway/${dial_gateway}/19161112222:_:sofia/gateway/${dial_gateway}/19163334444"/> </condition> </extension>