Inbound rules ignored if two trunks - same provider proxy

[PRE114]

Hello community members

I stumbled across something rather strange, I'd like to know if anyone else has noticed this:

I have configured two trunks using the same provider. Configured inbound rules based on DIDs but all calls flow to the same extension as configured for trunk one.
The provider has two hosts we can use and the moment I changed the second trunk to use the secondary host, the problem was solved - calls are flowing as intended.

Any thoughts why this may happen?

Thanks in advance
Cris

 

[cobaltit]

Yes... because you are using an unsupported SIP trunk provider....

The settings you will need to adjust are on the inbound parameters tab of the trunk settings. 3CX needs to know how to differentiate between trunks/dids.

 

[PRE114]

It is a supported trunk the dashboard PBX status is recognising it as such...
I'll play around with the parameters and see if I can fix it.
Will also contact the provider to see if they have actually done their part...

Thanks for helping

 

[PRE114]

No luck so far, I wonder if someone can provide further advice.
I played with the inbound parameters but lack of specific information/documentation on the issue makes it difficult and I don't have time to experiment.
I wonder what changed - I have been using this kind of setup since forever and it always worked out of the box.
Whilst working on this I have also noticed a high level of instability in trunk registration. Any change done to the trunk drops registration (which seems logical) but is followed by repeat failures that sometimes last forever.
I have to manually force registration to bring the trunks up again. This happens regardless if I use a single trunk or multiple, and it does not happen with identical configurations on Version 15.

I guess it's just another case of pushing new software versions with new features that aren't thoroughly tested. Most likely, I will hold off upgrading any of the V15 systems.

 

[cobaltit]

So usually it just works with a supported trunk but it may be an older template or the provider might have made changes since the template was put out. Or maybe it was just never tested. You basically need to wireshark and find the what makes the call unique and set that on the inbound parameters section (the bottom section).