Call is not established after a failed transfer

> 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

### 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.

Start by running the linked acs-transfer-failed-bug-repro demo with @azure/communication-call-automation 1.3.0 and follow the PSTN transfer steps. Inspect behavior after Microsoft.Communication.CallTransferFailed; done means the call remains established and a prompt can still be played.

Written by the indexing model from the issue text.