Differing dialed number behaviour causing CRM integration to fail on Windows 5.4 App

[steve.moran]

There is an issue with the 3CX Windows App (tested on 5.4) where you use CRM integration. I an using Hubspot integration which is very fussy about posting E164 numbers with '+' prefix. If you make an outbound call to an area code e.g in Australia 029xxxxxxx and outbound rules changes this to 6129xxxxxxx using the Web Client to Add a contact it will use the outbound rules formatted number. The windows client however just uses the number as it was dialed in the client. This fails validation at hubspot as 029xxxxxxx get's posted. I can only see moving back to the web client to fix this. P.S for inbound calls you can manipulate the number displayed and get it to work, but outbound it uses whatever the user enters and fails!

Can we get this as a feature fix/update/consistency bug for next release?

Thanks

Steve,
CloudCall

 

[ThomB_3CX]

@steve.moran just to clarify.

You have a number in hubspot saved as 6129xxxxxxx

You have an outbound rule which strips first digit (in your case 0) and appends 61 infront.

You perform a call to 029xxxxxxx and this is not being converted to 6129xxxxxxx and matching the crm contact correct?

If so:
- Using the softphone and dialing 6129xxxxxxx, does it resolve the crm contact?
- Can you try exiting the app and relaunching + try to reproduce?

Thanks