Weird issue with v18 beta and SIP Trunk caller ID

[Callinectes]

I have set up a beta hosted server. I have the trunks configured identically to that of a v16 system - both an inbound and an outbound trunk. Both trunks have the same "Main Trunk No" and this was not a problem in v16, but if configured this way in v18 the call is rejected by 3CX. Not until I changed to another "Main Trunk No" on the outbound trunk did calls start being received and processed according to the PBX rules. I had tried adjusting both the trunk default destinations and actually created an Inbound rule and none of those helped. I ran a call report and the status for the rejected calls showed as "unanswered" and the reason was "Line is busy". Also, I had to set the "Configure Outbound Caller ID" to the the proper caller ID for outbound calls to show the correct caller ID, which in the long run is not how I want the system to handle calls. Is this by design or is it an anomaly?

 

[cobaltit]

Is this for a 3CX certified trunk?

 

[YiannisH_3CX]

It appears you run into a source identification process where the PBX tries to match the inbound call to a trunk but it finds the same number in 2 trunks so the call is rejected.
Is this a supported provider? if so then we can advice on how to set it up correctly. If not then you will need to figure how to set it up your self since we have not tested the provider.
The following guide will help you understand how the PBX does the source identification so you can set it up better.
https://www.3cx.com/docs/sip-trunk-inbound-calls/

Alternatively please use a switch to a supported provider which has been tested and we can provide all settings.
https://www.3cx.com/partners/sip-trunks/