Skip to content

Call is not established after a failed transfer #310

@thomas-s97

Description

@thomas-s97

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

  • Establish a PSTN call
  • Transfer a call to another PSTN number
  • let the call transfer fail (e.g. by declining the call)
  • attempt to play a prompt after the Microsoft.Communication.CallTransferFailed event

Please run this demo for reproduction: https://github.com/marsidev/acs-transfer-failed-bug-repro

Any log messages given by the failure

Image

Expected/desired behavior

Call Connection shall still be in established state, even after failed transfer

Versions

@azure/communication-call-automation: "1.3.0"

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions