100 Percent consistent. If the callers number is in the bridge the bridge rings once and no wait for timeout. If the callers number is not in the bridge it always works fine. Never any deviation. This is not important to me since the workaround is probably better since we are not calling ourself (but would have like a better if/then/else to do it). I just wanted to pass this along in case the action was unintended and may cause other problems if it's a bug. If it was intended then rather than not work it would be better to simply have FS remove the caller from the bridge. The traces are console debug, it you need more let me know, but again, I am running fine with the changes below to accommodate the newer git. Mario G

Caller number not also part of bridge, works always:
http://pastebin.freeswitch.org/18845

Caller number is also part of bridge, fails always:
http://pastebin.freeswitch.org/18846


On Apr 9, 2012, at 12:20 PM, Michael Collins wrote:

I would like to see the console debug log and corresponding sip trace on a working call vs. non-working call. Does it only fail if the destination number is the same as the origination_caller_id_number, or are there other scenarios where it works (or doesn't work)? Throw that up on pb and let's have a look.

-MC

On Mon, Apr 9, 2012 at 10:39 AM, Mario G <mario_fs@mgtech.com> wrote:
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>


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.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