Not associating 3CX / Hubspot numbers for outgoing local calls

[A Valenti]

Good morning,
within our hubspot all numbers are archived according to the E164 standard, therefore, also the national numbers are saved as +39 0212345678. By making calls from the hubspot with click to call from the Chrome browser, the numbering is regularly passed to 3CX with the country code. However when making the call, 3CX automatically removes the +39 as these are domestic calls. This means that for outgoing calls the event is not recorded on the correct contact (given that +39 0212345678 is different from 0212345678). I tried to change the "Remove same country" setting from SETTINGS > E164 but the + is removed anyway and the call is forwarded to the wrong number 390212345678.
Are there alternative solutions to having to store numbers without the international prefix for national numbers and with the international prefix for foreign countries in hubspot?

 

[edossantos]

Your SIP Trunk is requiring you to make calls to them in local format? Can you configure your outbound rules and SIP Trunk to use the full number in E164 format?

 

[A Valenti]

For incoming calls no problem, I ticked the conversion to e164 the number is formatted with +39 regularly. I have the problem for outgoing calls, if I add +39 to the outgoing rules, the call is blocked by 3CX and the error message "forbidden_byadmin.wav" is reproduced

 

[TheodorosG_3CX]

Are you using any restrictions in the outbound rule?

 

[A Valenti]

no no block in outgoing rules, here is the log: Call or Registration to +39............@(Ln.10001@2N GSM n 1) has failed. 127.0.0.1 replied: 603 Decline; from IP:127.0.0.1:5080

 

[TheodorosG_3CX]

is it possible to provide a screenshot from the outbound rule?

 

[A Valenti]

here it is

 

[A Valenti]

I solved the problem, the blocking occurred in the gateway and not in the switchboard. The localhost address in the error was due to the gateway connecting via SBC.