incoming call transfers

[3CXAdmin]

I am trying to setup my 3CX system with 1 trunk and multiple DIDs. If i call directly to any DID from an outside number, the calls are routed correctly. If I forward an external number to one of my DIDs, it only goes to the primary(enhanced) extension, and not to the dialed DID.
Is there a setup or something I might be missing?

 

[eddv123]

Yes an inbound rule.

You in put your DDI's per trunk but then route individually with inbound rules (If of course you are using a block).

 

[3CXAdmin]

yes, i have all of the inbound rules set, and it acts correctly when i call the DIDs directly, but if i have another number forwarded to the DID, it only goes to the main number, not to any of the DIDs.
For example:
In the SIP, main number is 444-555-6666,
DID1 is 444-555-6666,
DID2 is 444-555-6667,
DID3 is 444-555-6668,
DID4 is 444-555-6669,

I have another outside line 444-555-8888 that i forward to 444-555-6667.

when i call 444-555-6667, it goes through as you would expect,
BUT when I call 444-555-8888, it only goes to 444-555-6666.

 

[leejor]

I would check the 3CX Activity Log and compare a call that works, with one that doesn't. i suspect that the DID number, on the call that is failing, cannot match the DID rules you have set-up.. It may be that the call comes in on a different trunk (for some reason), or additional digits have been prefixed to the DID number. Do you use a wildcard at the beginning of your DID rule numbers to guarantee a match?

 

[3CXAdmin]

Hi Ieejor, I have an asterisk before the number. I couldn't tell much from the activity log, since I don't really know what to expect. With that in mind, I didn't see anything that was very different between the 2 calls.
What I ended up doing is having all incoming calls go straight to a digital receptionist that sorts out the calls into the target numbers (Press 1 for XXX, Press 2 for YYY).

 

[JohnS_3CX]

Hi,

Are you using a supported provider? If so please tell us who so we can also check from our end.

If not, then it's just a matter of taking a capture and checking which field your provider uses for the "CalledNum" part (i.e where does 444-555-6667 appear).

You can change this in your trunk's Inbound Parameters, and the calls will begin to work as you expected. My guess is that you now have it set to To:User Part, but your provider probably sends it in Request Line URI:User Part and since the PBX does not see a number it knows (it probably sees 444-555-8888 in that field instead of 6667) then it just sends the call to the main trunk.