We're updating the issue view to help you get more done. 

Dialplan not generated when IVR sound files are not ascii

Description

When you add a sound file with a special caracter (ex: `ç`) and assign it to an IVR
When you reload Asterisk

Then the dialplan fails to load


This is the traceback I’m getting in wazo-confgend

My feeling is that wazo-confd should not allow file names to contain non ascii characters but maybe we could also fix confgend to be able to generate extensions.conf and test if it actually works with Asterisk

Environment

None

Assignee

Pascal Cadotte

Reporter

Zendesk Support for Jira

Approvers

None

Pair

None

Sprint

None

Fix versions

Priority

Medium
Configure