Azure-Samples / Azure-Samples/communication-services-javascript-quickstarts

Typo in CallAutomation_OutboundCalling/src/app.ts

Abierto Apto para principiantes
#317 0 comentarios 0 reacciones 0 asignados Ver en GitHub
status:triage
Lenguaje dominante
JavaScript
Estrellas
108
Forks
207
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Abre CallAutomation_OutboundCalling/src/app.ts en la línea 161 e inspecciona el manejo del callback para Microsoft.Communication.PlayFailed. Reproduce la reproducción fallida de un TextSource, FileSource o SsmlSource y verifica que el evento corregido se reconozca y que la llamada finalice.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
azure, javascript, node.js
Área
api, backend
Tipo de issue
Error
Dificultad
1/5
Tiempo estimado
Menos de una hora
Estado de actividad
Estancado
Claridad
Bien especificado
Aptitud para principiantes
68/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.