Azure-Samples / Azure-Samples/communication-services-javascript-quickstarts
Typo in CallAutomation_OutboundCalling/src/app.ts
- Vorherrschende Sprache
- JavaScript
- Sterne
- 108
- Forks
- 207
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
> 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
>Purposely make a TextSource / FileSource / SsmlSource fail to reporduce.
### Any log messages given by the failure
>
Call back event received, callConnectionId=xxxx-xxxx-xxxx, serverCallId=yyyyyyyyyy, eventType=Microsoft.Communication.**PlayFailed**
### Expected/desired behavior
>The call should be terminated.
### OS and Version?
> Node.js running on Windows
### Versions
> Commit d46e964 (latest when opening this issue)
### Mention any other details that might be useful
Hello, I'd like to report a type error in line 161 of the file CallAutomation_OutboundCalling/src/app.ts, the event checked should be "Microsoft.Communication.**P**layFailed" but it's "Microsoft.Communication.**p**layFailed".
This causes the call to not be terminated in case of a failure while playing the message.
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.
Beitragsleitfaden
Rechercherichtung
Öffne CallAutomation_OutboundCalling/src/app.ts in Zeile 161 und überprüfe die Callback-Behandlung für Microsoft.Communication.PlayFailed. Reproduziere die fehlgeschlagene Wiedergabe einer TextSource, FileSource oder SsmlSource und verifiziere, dass das korrigierte Ereignis erkannt und der Anruf beendet wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, javascript, node.js
- Bereich
- api, backend
- Issue-Typ
- Bug
- Schwierigkeit
- 1/5
- Geschätzter Aufwand
- Unter einer Stunde
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 68/100