Displays clients in a conference
Good afternoon. I use the asterisk 13 and fop2 2.30.05, the problem is that when in the course of the conference room such as 6666 numbers 6000 (Супермаркет) are no longer displayed participants. The asterisk log contain the next messages:
[2016-03-21 15:59:17] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:20] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:22] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:25] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:27] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:17] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:20] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:22] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:25] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
[2016-03-21 15:59:27] ERROR[12930]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
Comments
The error in Asterisk might be related, but it is not responsibility of FOP2 in any way. Using cyrilic on a member name seems to cause that problem *within* asterisk. As for FOP2, unfortunately the level 1 debug is not enough, I see AMI responses but not the actions sent nor the actual websocket dialog between the fop2 server and the browser, a debug level 15 would be better. And also, you might want to create a special manager user for FOP2 using event filters as described in the installation guide: http://www.fop2.com/docs/#ConfiguringtheServer
That way the log will be smaller and more readable and easier to track.
Best regards,
10.75.0.75:37879 => { "btn": "2@GENERAL", "cmd": "members", "data": "WyB7ICJpc21hcmtlZCI6ICJvZmYiLCAiaXNtdXRlZCI6ICJvbiIsICJpc3RhbGtpbmciOiAib2ZmIiwgImNvbmZlcmVuY2UiOiAiQ09ORkVSRU5DRS82NjY2IiwgImNoYW5uZWwiOiAiMSIsICJuYW1lIjoiNjAwMCDQodGD0L/QtdGA0LzQsNGA0LrQtdGCINCS0LDRgdC40LvRjNC10LLQIiB9IF0=", "slot": "" }
Decoding that shows correct cyrilic. You might need to see the javascript console to see if you get any particular errors after receiving that command.
meetme list 6666 concise
And you will see that the name is not shown correctly (note the last ? in the name, that is an invalid char):
1!601!Супермаркет Васильев?!SIP/601-0000000d!!!!!0!00:00:12
and you will also see the error in the asterisk CLI:
ERROR[2333]: json.c:704 ast_json_vpack: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string.
All of that happens WITHOUT fop2 in the middle. It is a problem within Asterisk itself.
FOP2 inherits the bad formatted utf8 string and pass it along, but it cannot fix it as it is broken from the start.
Note that the same name can be used for a queue member name, and Asterisk behaves correctly in this regard, with no errors, using the same callerid/name.
Perhaps that problem was fixed in more recent Asterisk versions... I tested with Asterisk 13.1.0 only.
Executing [s@macro-user-callerid:26] Set("SIP/6000-00000a09", "CALLERID(number)=6000") in new stack
-- Executing [s@macro-user-callerid:27] Set("SIP/6000-00000a09", "CALLERID(name)=Супермаркет Васильев�") in new stack
-- Executing [s@macro-user-callerid:28] Set("SIP/6000-00000a09", "CHANNEL(language)=ru") in new stack
Сan fop2 panel in the future to call the problems encoding?
Best regards,