Has the behavior of loopback endpoint changed since 92e89cb4532913a3fd7a4888f8c94df379775cc3 commit
Today, as always, i just made git pull to the latests updates and found strange behaviour @ vanilla configuraton of the extension "Local_Extension". FreeSWITCH Version 1.1.beta1 (git-e9abdac 2012-04-17 23-05-48 -0400) <extension name="Local_Extension"> <condition field="destination_number" expression="^(10[01][0-9])$"> <action application="export" data="dialed_extension=$1"/> <action application="bind_meta_app" data="1 b s execute_extension::dx XML features"/> <action application="bind_meta_app" data="2 b s record_session::$${recordings_dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/> <action application="bind_meta_app" data="3 b s execute_extension::cf XML features"/> <action application="bind_meta_app" data="4 b s execute_extension::att_xfer XML features"/> <action application="set" data="ringback=${ru-ring}"/> <action application="set" data="transfer_ringback=$${hold_music}"/> <action application="set" data="call_timeout=30"/> <action application="set" data="hangup_after_bridge=true"/> <!--<action application="set" data="continue_on_fail=NORMAL_TEMPORARY_FAILURE,USER_BUSY,NO_ANSWER,TIMEOUT,NO_ROUTE_DESTINATION"/> --> <action application="set" data="continue_on_fail=true"/> <action application="hash" data="insert/${domain_name}-call_return/${dialed_extension}/${caller_id_number}"/> <action application="hash" data="insert/${domain_name}-last_dial_ext/${dialed_extension}/${uuid}"/> <action application="set" data="called_party_callgroup=${user_data(${dialed_extension}@${domain_name} var callgroup)}"/> <action application="hash" data="insert/${domain_name}-last_dial_ext/${called_party_callgroup}/${uuid}"/> <action application="hash" data="insert/${domain_name}-last_dial_ext/global/${uuid}"/> <action application="hash" data="insert/${domain_name}-last_dial/${called_party_callgroup}/${uuid}"/> <action application="bridge" data="user/${dialed_extension}@ ${domain_name}"/> <action application="answer"/> <action application="sleep" data="1000"/> <action application="bridge" data="loopback/app=voicemail:default ${domain_name} ${dialed_extension}"/> </condition> </extension> The purpose of that extension is simple, just rings to another extension and, for example, if the other side is busy go to voicemail. But with the lattest git it doesn't work at all. Why does it proceed "voicemail" into default context? Here is the log: http://pastebin.freeswitch.com/18886 Actually it works when using 92e89cb4532913a3fd7a4888f8c94df379775cc3 revision.
If you don't mind doing some more testing you can help us narrow down exactly what commit it broke for you on and will result in the fastest fixing of the issue. Using git bisect will do a binary search between the known good and known bad commits to help you find exactly what broke it in the shortest amount of time. To try and find the issue that you know is broken in HEAD but fine in that revision you posted: git bisect start HEAD 92e89cb4532913a3fd7a4888f8c94df379775cc3 then compile / test etc/ the tell git: git bisect bad or git bisect good then it will move on to the next git bisect reset when done git bisect skip if you cant test a specific revision If you have a script that can determine if it works or not you can use: git bisect run [my_script] [arguments] Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad. Either way file a JIRA bug report on the broken / changed functionality. ~Mitch
And again.... The mailing list is not appropriate for reporting bugs. We have a dedicated bug tracker http://jira.freeswitch.org I have reproduced this problem and will fix it but I am trying to resist the urge to refuse simply because there is no bug report I can file the fix against. On Wed, Apr 18, 2012 at 8:56 AM, Mitch Capper <mitch.capper@gmail.com> wrote:
If you don't mind doing some more testing you can help us narrow down exactly what commit it broke for you on and will result in the fastest fixing of the issue. Using git bisect will do a binary search between the known good and known bad commits to help you find exactly what broke it in the shortest amount of time. To try and find the issue that you know is broken in HEAD but fine in that revision you posted:
git bisect start HEAD 92e89cb4532913a3fd7a4888f8c94df379775cc3
then compile / test etc/ the tell git: git bisect bad or git bisect good then it will move on to the next git bisect reset when done
git bisect skip if you cant test a specific revision
If you have a script that can determine if it works or not you can use:
git bisect run [my_script] [arguments] Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad.
Either way file a JIRA bug report on the broken / changed functionality.
~Mitch
_________________________________________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
commit c469321d8b8350ad6c03cd90d70c1b5b14c9b580 Author: Anthony Minessale <anthm@freeswitch.org> Date: Wed Apr 18 08:24:15 2012 -0500 fix regression in commit 19f441c6f4516f035828aa112bcf92f47f4e0f28 On Wed, Apr 18, 2012 at 10:22 AM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
And again.... The mailing list is not appropriate for reporting bugs. We have a dedicated bug tracker http://jira.freeswitch.org I have reproduced this problem and will fix it but I am trying to resist the urge to refuse simply because there is no bug report I can file the fix against.
On Wed, Apr 18, 2012 at 8:56 AM, Mitch Capper <mitch.capper@gmail.com> wrote:
If you don't mind doing some more testing you can help us narrow down exactly what commit it broke for you on and will result in the fastest fixing of the issue. Using git bisect will do a binary search between the known good and known bad commits to help you find exactly what broke it in the shortest amount of time. To try and find the issue that you know is broken in HEAD but fine in that revision you posted:
git bisect start HEAD 92e89cb4532913a3fd7a4888f8c94df379775cc3
then compile / test etc/ the tell git: git bisect bad or git bisect good then it will move on to the next git bisect reset when done
git bisect skip if you cant test a specific revision
If you have a script that can determine if it works or not you can use:
git bisect run [my_script] [arguments] Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad.
Either way file a JIRA bug report on the broken / changed functionality.
~Mitch
_________________________________________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
On Wed, Apr 18, 2012 at 9:28 AM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
commit c469321d8b8350ad6c03cd90d70c1b5b14c9b580 Author: Anthony Minessale <anthm@freeswitch.org> Date: Wed Apr 18 08:24:15 2012 -0500
fix regression in commit 19f441c6f4516f035828aa112bcf92f47f4e0f28
Thanks for fixing this one so quickly. I would have reported a JIRA myself, but thought it would be more appropriate for the OP to do so. Jason
Sorry guys. Done http://jira.freeswitch.org/browse/FS-4130 18 апреля 2012 г. 19:22 пользователь Anthony Minessale < anthony.minessale@gmail.com> написал:
And again.... The mailing list is not appropriate for reporting bugs. We have a dedicated bug tracker http://jira.freeswitch.org I have reproduced this problem and will fix it but I am trying to resist the urge to refuse simply because there is no bug report I can file the fix against.
On Wed, Apr 18, 2012 at 8:56 AM, Mitch Capper <mitch.capper@gmail.com> wrote:
If you don't mind doing some more testing you can help us narrow down exactly what commit it broke for you on and will result in the fastest fixing of the issue. Using git bisect will do a binary search between the known good and known bad commits to help you find exactly what broke it in the shortest amount of time. To try and find the issue that you know is broken in HEAD but fine in that revision you posted:
git bisect start HEAD 92e89cb4532913a3fd7a4888f8c94df379775cc3
then compile / test etc/ the tell git: git bisect bad or git bisect good then it will move on to the next git bisect reset when done
git bisect skip if you cant test a specific revision
If you have a script that can determine if it works or not you can use:
git bisect run [my_script] [arguments] Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad.
Either way file a JIRA bug report on the broken / changed functionality.
~Mitch
_________________________________________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_________________________________________________________________________ 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
participants (4)
-
Anthony Minessale
-
Anton Kvashenkin
-
Komar, Jason
-
Mitch Capper