Uppercase UUID problem with Call Center

MikkoR

New Member
May 8, 2019
1
0
1
When we create a call center from FusionPBX, it creates 2 sets of call centers and agents.
One set with lowercase UUIDs and another with uppercase UUIDs. Only the uppercase set works.

This problem is similar to what mutt referred to in thread:
https://www.pbxforums.com/threads/call-is-disconnected-after-90-seconds-in-call-center-module.2655/

#> fs_cli -x "callcenter_config queue list"
name|strategy|moh_sound|time_base_score|tier_rules_apply|tier_rule_wait_second|tier_rule_wait_multiply_level|tier_rule_no_agent_no_wait|discard_abandoned_after|abandoned_resume_allowed|max_wait_time|max_wait_time_with_no_agent|max_wait_time_with_no_agent_time_reached|record_template|calls_answered|calls_abandoned|ring_progressively_delay|skip_agents_with_external_calls|agent_no_answer_status
7C7044C8-F301-41F3-82E4-CD2E08D2A43C|longest-idle-agent|local_stream://default|system|false|30|true|true|900|false|0|90|5||1|10|0|true|On Break
7c7044c8-f301-41f3-82e4-cd2e08d2a43c|ring-all|local_stream://default|queue|false|30|true|true|900|false|600|0|5||0|0|0|true|On Break

#> fs_cli -x "callcenter_config agent list"
name|system|uuid|type|contact|status|state|max_no_answer|wrap_up_time|reject_delay_time|busy_delay_time|no_answer_delay_time|last_bridge_start|last_bridge_end|last_offered_call|last_status_change|no_answer_count|calls_answered|talk_time|ready_time|agent_uuid|external_calls_count
dbe53546-e566-4a43-a99c-02a6ea2347e4|single_box||callback|{call_timeout=15,sip_invite_domain=DOMAIN}user/3000@DOMAIN|Available|Waiting|0|10|90|90|30|0|0|0|1557222092|0|0|0|0|F82074D5-F0A3-496D-AC55-24064E77121B|0
DBE53546-E566-4A43-A99C-02A6EA2347E4|single_box||callback|{call_timeout=15}user/3000@DOMAIN|Available|Waiting|0|10|90|90|30|1557235249|1557235250|1557305305|1557222122|0|1|1|1557305399|F5DC4379-2AA9-4F24-A039-40AA5D1D380B|0

Our FusionPBX version is 4.4.2
We are running FreeSwitch 1.8.1 (64bit) from Debian Stretch's package repo. Version: 1.8.1~2~4f54cff36a-1~stretch+1
Our database is PostgreSQL 9.6.10


I tried to fix this by writing the UUID to PostgreSQL in uppercase, but PostgreSQL's uuid-datatype is case-insensitive like ordinary hex-digits.
Our temporary fix was to modify fusion's code to write $call_center_queue_uuid in uppercase into the dialplan line 'action application="callcenter"'. After that the call center works and we can modify it with FusionPBX.