Azure-Samples / Azure-Samples/communication-services-javascript-quickstarts
Typo in CallAutomation_OutboundCalling/src/app.ts
- Langage dominant
- JavaScript
- Étoiles
- 108
- Forks
- 207
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
> 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.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Ouvrez CallAutomation_OutboundCalling/src/app.ts à la ligne 161 et examinez la gestion du callback pour Microsoft.Communication.PlayFailed. Reproduisez la lecture ayant échoué d’un TextSource, FileSource ou SsmlSource et vérifiez que l’événement corrigé est reconnu et que l’appel est terminé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- azure, javascript, node.js
- Domaine
- api, backend
- Type d'issue
- Bug
- Difficulté
- 1/5
- Temps estimé
- Moins d'une heure
- Activité
- À l'abandon
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 68/100