Well for instance data from SIP messages getting stuck into event headers/variables. Less critically, from XML files – is the XML reader actually compliant (rejecting invalid sequences)? From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: Wednesday, 3 August, 2016 8:26 To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] FS's string encoding - valid UTF-8? If it receives them from itself? We do very little to do with utf8 encoding in fs. If it passes through a char * its likely fine if its fine on the other side. On Aug 3, 2016, at 1:58 AM, Michael Giagnocavo <mgg@giagnocavo.net<mailto:mgg@giagnocavo.net>> wrote: Does FS enforce UTF-8 anywhere? I am writing a new interop module and need to know if handling non-UTF-8 char*s is a requirement. I’m thinking particularly from SIP messages and other external user inputs. In other words, if a FS ever receives a non-UTF-8 string from FS, is that automatically a bug in FS? Or considered within acceptable behaviour? Thanks, -Michael