Incoming call Popup character

bazoozoobazoozoo
in Support
Good day, again.
For incoming calls, in the pop-up notification, queue name is displayed in the wrong encoding.
271e155776b7.png

I checked encoding of a "queue config" table in freepbx mysql. Encoding is correct UTF-8_unicode: 
   queues_config | CREATE TABLE `queues_config` (
  `extension` varchar(20) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `descr` varchar(35) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `grppre` varchar(100) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `alertinfo` varchar(254) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `ringing` tinyint(1) NOT NULL DEFAULT '0',
  `maxwait` varchar(8) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `password` varchar(20) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `ivr_id` varchar(8) COLLATE utf8_unicode_ci NOT NULL DEFAULT '0',
  `dest` varchar(50) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `cwignore` tinyint(1) NOT NULL DEFAULT '0',
  `queuewait` tinyint(1) DEFAULT '0',
  `use_queue_context` tinyint(1) DEFAULT '0',
  `togglehint` tinyint(1) DEFAULT '0',
  `qnoanswer` tinyint(1) DEFAULT '0',
  `callconfirm` tinyint(1) DEFAULT '0',
  `callconfirm_id` int(11) DEFAULT NULL,
  `qregex` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
  `agentannounce_id` int(11) DEFAULT NULL,
  `joinannounce_id` int(11) DEFAULT NULL,
  `monitor_type` varchar(5) COLLATE utf8_unicode_ci DEFAULT NULL,
  `monitor_heard` int(11) DEFAULT NULL,
  `monitor_spoken` int(11) DEFAULT NULL,
  `callback_id` varchar(8) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
    PRIMARY KEY (`extension`)
    ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci

Comments

  • AlexRSAlexRS
    edited January 2017
    The same problem is there http://forum.fop2.com/4419-translate-issue (777 picture). I have clear asterisk and didnt use mysql for FOP2 config. The problem is with 'label' name. I didn't solve it
    It happens with queue name only.
  • nicolasnicolas
    json has issues with utf8, so I will use base64 encode/decode for the "fromqueue" value on the next release. That should fix the little notification coding issue in queue names with multi byte strings.
  • AlexRSAlexRS
    @admin I have tested new version. FOP2 shows correctly pop-up and tagQueueCall encoding. But the problem with queuestats still exists(attach). Can we solve it? Our costomer will be happy to use native language=)
  • nicolasnicolas
    I have updated the queue stats plugin and it should show wide characters correctly in queue names now.

    Best regards,
  • AlexRSAlexRS
    Works perfectly! Thank you!
  • BorserBorser
    edited January 2017
    Please, update also FullWallboard plugin - same issues:
  • AlexRSAlexRS
    Try to update the plugin. In my case after updating all works fine.
  • nicolasnicolas
    I am currently abroad, so I won't have time to work on code until next week. I will review the full wallbaord as soon as I get back.

    Best regards,
  • bazoozoobazoozoo
    Best regards,[/quote]
    12785:@admin wrote:
    I have updated the queue stats plugin and it should show wide characters correctly in queue names now.
    What about incoming call notification?
  • BorserBorser
    12866:@bazoozoo wrote:
    What about incoming call notification?

    Update FOP 2.31.07
  • bazoozoobazoozoo
    12902:@Borser wrote:
    Update FOP 2.31.07
    Thank you!
Sign In or Register to comment.

© Asternic Corp 2024