Skip to content

DialAction is not executed when everyone is busy #2435

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghjansen opened this issue Aug 18, 2017 · 1 comment
Closed

DialAction is not executed when everyone is busy #2435

ghjansen opened this issue Aug 18, 2017 · 1 comment
Assignees
Labels

Comments

@ghjansen
Copy link
Contributor

Related to issues #2271, #2432 and PR #2420.

Scenario:

  • Restcomm creates multiple outbound calls through a Dial forking RCML like:
<Response>
  <Dial timeLimit="1000" timeout="2" action="http://127.0.0.1:8090/test">
    <Number>+131313</Number>\
    <Uri>sip:[email protected]:5092</Uri>
    <Client>alice</Client>
  </Dial>
</Response>
  • each one of the call branches answers back with SIP 486 (BUSY)

Failure:

  • no request is received at the action address informed

This issue was noticed only after the optimisation of the patch implemented at #2432

@ghjansen ghjansen added this to the Video-RCML-Sprint-2 milestone Aug 18, 2017
@ghjansen ghjansen self-assigned this Aug 18, 2017
@ghjansen
Copy link
Contributor Author

Solution:
Prevented VoiceInterpreter to move to the next verb when MediaGroupResponse is received, if action attribute is different than null.

Closed via PR #2420 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant