Solved Problem routing DID's to different digital receptionists or extensions

[JaySolano]

SOLVED
: Problem was with my SIP trunk PROVIDER. It was actually my own configuration problem. Within the DID configuration at SIP provider (hosting the DID) there is an option for the DID to "Send Did Prefix". It was unchecked, so 3CX would just send everything to the default trunk.
--------------


We have 3 DID's with our SIP trunk provider, let's say:

• 111-111-1111
• 222-222-2222
• 333-333-3333

All 3 DID's there point to our 3CX server as the only peer/trunk.

In 3CX SIP Trunks we have 1 trunk defined (for the provider above).

Here we have:

• General TAB: main trunk # set as 111-111-1111
• General TAB: destination for main trunk is digital receptionist for 111-111-1111 for all hours
• DIDs TAB: we have all 3 DID's defined

We have 2 digital receptionist extensions defined...

• Ext 8000 which is DR for the number at 111-111-1111
• Ext 8010 which is different DR for number at 222-222-2222

We have 3 extensions defined....

• Operator 0000
• User 1 (at ext 9000) associated with 111-111-1111
• User 2 (at ext 9050) associated with 222-222-2222

The problem.....

Can't figure out how to get 222-222-2222 to route to its own digital receptionist extension OR directly to extension 9050. Every call regardless of what DID it is originating from, dials in to the DR associated with 111-111-1111.

Any ideas?

 

[jed]

Its late here, so I might have misread your post. However did you setup indbound roules for your did’s?

 

[JaySolano]

I've tried using inbound rules for each DID.

No effect... they all route to whatever is defined for the SIP TRUNKS > GENERAL > Route Calls to.

 

[JaySolano]

Maybe it's my DIDs (on the SIP TRUNKS > DIDs tab)....

I've tried defining them as both 10 and 11 digit DIDs

So right now I have on DIDs tabs dual entries like...

11111111111
1111111111
12222222222
2222222222
13333333333
3333333333

Which each of those 6 dids (3 unique) mapped to where I want them to go.

But whatever is defined for the SIP trunk in the "Route calls to" section is what takes priority over all else. Everything else is ignored.

 

[JaySolano]

SOLVED: Problem was with my SIP trunk PROVIDER. It was actually my own configuration problem. Within the DID configuration at SIP provider (hosting the DID) there is an option for the DID to "Send Did Prefix". It was unchecked, so 3CX would just send everything to the default trunk.

 

[YiannisH_3CX]

Glad to see the issue has been resolved