Windows 16.3 Integration With %CallerDisplayName%

Status
Not open for further replies.

MP3

Free User
Joined
Jul 30, 2020
Messages
1
Reaction score
0
Hi,

I have 16.3.0.144 3CX Windows Client installed using feature in Settings > Advanced > Behavior > External Application. This is used to open web browser and pass URL parameters like Web Client integration does with "Open Contact URL". This works fine with config like:
https://our-site:56444/phonecall?user=me&incomingnumber=%CallerNumber%

Chrome opens new tab passing these parameters. But this URL has an issue:
https://our-site:56444/phonecall?user=me&incomingnumber=%CallerNumber%&callerid=%CallerDisplayName%

This %CallerDisplayName% is built-in functionality but does not appear to add URL encoding properly... a CallerDisplayName of "Caller Name" will cause a problem because the space character needs to be URL encoded as %20. Chrome ends up opening two tabs, the second of which only contains the URL of remaining content after space ("Name").

If the CallerDisplayName was "Caller%20Name" then there is no issue. This same URL with %CallerDisplayName% works fine from Web Client, so what is the problem with using in Windows app?

Thanks,
MP
 
Hi MP,

The parameters will pass the exact values they receive (because it's not designed for any specific CRM, its genericly passing the values). This might not work for your CRM solution unless you tweak it to accept those parameters and deal with them internally.

If this is not possible (or affects other things, preventing you from changing it) then just create a very simple wrapper URL that will convert the URL to the exact format you want to feed into your CRM.
 
  • Like
Reactions: MP3
Status
Not open for further replies.

Forum statistics

Threads
112,349
Messages
592,026
Members
165,512
Latest member
gmacinit