Inbound rule issue coming via Yeastar trunk

[netadminsa]

Hi Team,
We've built SIP Trunk from PSTN (Mobily) to Yeastar and it's successfully registered. Then we wanted to route this to 3CX system, we built another Trunk Yeastar >> 3CX it's also registered. Problem calls are landing to 3CX system but to IVR only. Top Inbound rule is taking precedence and 2nd inbound rule is not being hit. We want your help cause 3CX inbound rules are bound by DID number which is assigned in SIP Trunk configuration in 3CX. your support or suggestions will be highly appreciated.

Please note this is on premise 3cx server on physical server. Both Yeastar and 3cx are in same LAN network. no NAT is involved.

BR
Imran

 

[KyriacosS_3CX]

You can assign DIDs directly to any extension (user or system) and these assignments take precedent over the default routing set in the trunk config.

 

[netadminsa]

You can assign DIDs directly to any extension (user or system) and these assignments take precedent over the default routing set in the trunk config.

Hi Team,

Thank you for your long awaited response, I'm actually new to 3CX, Can you please help me to configure this DID to an Extension? Target it they want to assign this DID to another IVR / Call Que for a seperate dept. At least for now we should be able to get calls to desired extension, testing inbound rule successfully.

 

[Alphabetic]

Go in to your extension and select their "assigned DID Numbers"