Closed gersmann closed 11 years ago
Thanks for report. Please provide logs at trace level so that we may properly assist.
Hi Ben,
thanks for the quick feedback. I have attached the trace log. Please note that changing the log level to trace changed the predictability of the results. I actually had one case now where the dial plan was executed as expected, another case where the second number was called, even though the inbound call was hung up after ending the first outbound call. The trace shows the behavior I originally reported.
https://gist.github.com/gersmann/f51a5f71d73e931d09c2
Best regards
@polysics is apparently also seeing this. Can one (or both :+1:) of you please try bisecting Adhearsion/Punchblock to locate the commit that broke this? That'll help me get you a resolution much faster :)
There's a guide to doing that here, http://mojolingo.com/blog/2013/using-git-bisect-to-troubleshoot-ruby-gems/ btw ;)
Hi Ben,
re. your recommendation to bisect the gems: I have tested on a completely different configuration: freeswitch (1.4), ruby 1.9.3, adhearsion 2.2.1 and punchblock 1.8.0.
I still have the same problem, so I am not sure what is going on here. Maybe I have a misconception re. the adhearsion API.
If I define two dial statements in a CallController like: dial 'user/1000@192.168.2.112' dial 'user/1001@192.168.2.112' What is the expected behaviour? Should the inbound leg be hung up after the first outbound call is terminated?
Best regards
No, it should not. I just remembered what you'll need, which is to set the following channel variables in your FreeSWITCH dialplan prior to parking:
http://wiki.freeswitch.org/wiki/Variable_hangup_after_bridge = false http://wiki.freeswitch.org/wiki/Variable_park_after_bridge = true
If you could confirm that these work and propose a documentation update ( https://github.com/adhearsion/adhearsion-website/blob/master/views/docs/getting-started/freeswitch.mdand https://github.com/adhearsion/adhearsion/blob/develop/lib/adhearsion/generators/app/templates/README.md) that would be awesome :)
Hi Ben,
yes, the issue has been resolved for Freeswitch by updating the configuration as recommended. Strange, that I experienced exactly the same behavior with Asterisk. Is there a similar configuration setting for Asterisk?
Best regards
@bklang or @polysics will be able to answer about Asterisk better than I.
Thanks, I've merged those two PRs :)
See https://github.com/adhearsion/punchblock/issues/193 for further details on the issue on Asterisk.
I have a new installation of asterisk 11 and adhearsion 2.3 with a very simple controller:
The inbound call gets correctly forwarded to the first dial actions number. However, if that call is terminated by the receiver, I would expect the call to be forwarded to the second number. This is not happening, both calls are hanged up.
See the following log for reference: