Confused about DID

[Lusk]

SIP Trunks > edit > general > route calls to: there is the section for routing calls in and outside of normal working hours and it seems you have to enter an extension number there.

However, there is also the Inbound Rules too.

I am a little confused as it seems you have to add one in the SIP Trunk set up so what is then the purpose of having the inbound rules too?

 

[Evolute IT]

The one in the trunk config is the default one. If a call comes in on a DID that is not configured in Inbound Rules, this rule will apply.

Inbound Rules are used to configure those DIDs. So if all your DIDs goes to the same place, you can use the trunk config, else use the Inbound Rules.

 

[Lusk]

The one in the trunk config is the default one. If a call comes in on a DID that is not configured in Inbound Rules, this rule will apply.

Inbound Rules are used to configure those DIDs. So if all your DIDs goes to the same place, you can use the trunk config, else use the Inbound Rules.

Ah, thank's a lot for that. So it is a catch all really - the one in the trunk that is.

So am I right in saying that you have your trunk and any number of phone numbers can come down that trunk?

Am I also right in saying that it would be up to the trunk provider to ensure that all of those different phone numbers carry their own DID? Presumably if the provider does not give each number it's own DID, then you'd need to get another trunk for each number or you'd not actually be able to know what the caller ID was?

 

[craigreilly]

The provider is going to present the DID on each call - however, not all providers present them the same.
In the US here, I use * followed by the 10 digit number. If you are using a PSTN, the telco may only send last 4 digits.
FWIW - I put my main Trunk number into the DID rules as well just so all DID's are in one place to change if I need to.

 

[leejor]

So am I right in saying that you have your trunk and any number of phone numbers can come down that trunk?

Yes. However the number of simultaneous conversations going on are going to be limited by several things. The number of channels you are paying for, the number of channels you allow the 3CX trunk to handle, and the 3CX licence limit.

Am I also right in saying that it would be up to the trunk provider to ensure that all of those different phone numbers carry their own DID?

That is what you pay your provider for. You ask them for 10 DIDs (for example), and if someone dials one, the DID number is sent to the PBX so that you can route the call appropriately.

Presumably if the provider does not give each number it's own DID, then you'd need to get another trunk for each number or you'd not actually be able to know what the caller ID was?

You might have a number that is not a DID, like a "main" number, that allows 10 simultaneous call. That would use the "default" that you set, for that trunk group. DID information (dialled number) and Caller ID (callers number) are two different things. You should get caller ID regardless, if you are paying for it.

 

[Lusk]

Yes. However the number of simultaneous conversations going on are going to be limited by several things. The number of channels you are paying for, the number of channels you allow the 3CX trunk to handle, and the 3CX licence limit.




That is what you pay your provider for. You ask them for 10 DIDs (for example), and if someone dials one, the DID number is sent to the PBX so that you can route the call appropriately.



You might have a number that is not a DID, like a "main" number, that allows 10 simultaneous call. That would use the "default" that you set, for that trunk group. DID information (dialled number) and Caller ID (callers number) are two different things. You should get caller ID regardless, if you are paying for it.

Thank you for this, it is very helpful.

 

[Lusk]

I've another slight issue here:

I have set up a trunk and under the route calls to section for both in and out of hours, I have for the sake of simplicity set this to extension 300.

I was then playing around with the inbound rule and I added a rule for the above trunk to route all calls to IVR extension 800.

It was my understanding that if you set up inbound rules this overrides the rules in the trunk but having gone and called the inbound number, I have found the call is being routed to 300 and not 800.

I've clearly missed something here.

 

[craigreilly]

What is the inbound caller Id? The trunk is a catch all when there isn’t a match.
perhaps the provider is sending +14805551212

try *5551212 and see if that works.

 

[Lusk]

What is the inbound caller Id? The trunk is a catch all when there isn’t a match.
perhaps the provider is sending +14805551212

try *5551212 and see if that works.

Thank you, so the inbound rules don't override the trunk settings then.

 

[craigreilly]

Inbound rules DO override the trunk - but need to match. If it’s not matching then the trunk catches it and uses default path.