postgres db contains non existent channels
Hi, we have about 800 connected users, 150 simultaneous calls and some user agents send sip messages with non UTF-8 characters. When FreeSWITCH tries to alter the channel information in the postgres db it throughs an error: 2018-03-29 15:47:46.794346 [ERR] switch_pgsql.c:656 Error executing query: ERROR: invalid byte sequence for encoding "UTF8": 0xf6 0x63 0x68 0x6c The Problem now is that we see some calls in the database which do not exist anymore (uuid_exists returns false). This are other calls, not the one which cause the error above! It seems that everytime the error happens, Freeswitch cannot delete other channels from db when the bye is arriving +/- 100ms near the error. We tried to set client_encoding in the postgres connection string to some options e.g. LATIN1 but that didn’t solve our problem. Whichever client_encoding we used, we always had some user agents with some unknown characters. How should we deal with that? Thanks, Roman RDI SOLUTIONS e.U. Hollenthon 105 2812 Hollenthon, Österreich T: +43 1 3530349 - 10 F: +43 1 3530349 - 99 roman.dissauer@rdi.at www.rdi.at
Hi, can you capture what fs is trying to save ? do you have a sip message capture in wireshark ? On 29 March 2018 at 20:14, Roman Dissauer <roman@dissauer.net> wrote:
Hi,
we have about 800 connected users, 150 simultaneous calls and some user agents send sip messages with non UTF-8 characters. When FreeSWITCH tries to alter the channel information in the postgres db it throughs an error:
2018-03-29 15:47:46.794346 [ERR] switch_pgsql.c:656 Error executing query: ERROR: invalid byte sequence for encoding "UTF8": 0xf6 0x63 0x68 0x6c
The Problem now is that we see some calls in the database which do not exist anymore (uuid_exists returns false). This are other calls, not the one which cause the error above! It seems that everytime the error happens, Freeswitch cannot delete other channels from db when the bye is arriving +/- 100ms near the error.
We tried to set client_encoding in the postgres connection string to some options e.g. LATIN1 but that didn’t solve our problem. Whichever client_encoding we used, we always had some user agents with some unknown characters.
How should we deal with that?
Thanks, Roman
*RDI SOLUTIONS e.U.* Hollenthon 105 2812 Hollenthon, Österreich T: +43 1 3530349 <+43%201%203530349> - 10 F: +43 1 3530349 <+43%201%203530349> - 99 roman.dissauer@rdi.at *www.rdi.at <http://www.rdi.at>*
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Roman Dissauer
-
Tihomir Culjaga