Solved Outbound Routes with several DID lines

Status
Not open for further replies.

Tim S.

Customer
Joined
Feb 16, 2022
Messages
2
Reaction score
2
Hello.

I have a situation that I can't seem to solve.

We host our own linux systems. The Version is: 18.0 Update 2 (Build 314).

We have several (3) DID lines coming into our system. I have setup a handful (7) of Outgoing rules to define which line to use, and each line has the CallerID specified. The problem is that the system seems to be ignoring the rules.

I know the first rule works, as unfortunately our staff needed to dial it a few weeks back: (*note: I am not sure if this was before the update or after)
The first rule: Prefix 911, Length 3, Route 1 - DID Line #3 (Outbound Caller ID: Not Set), all other Routes are BLOCK

I defined that no one in the system should be able to call a specific extension: (*note: I believe this rule was working correctly before the update)
Defined as the second rule: Prefix 4999, Length 4, all Routes are BLOCK

I defined that all calls from this specific extension should only go out one specific DID line, with the defined CallerID of 2222222:
Defined as the third rule: Call from Ext. 4999, Route 1 - DID Line #2 (Outbound CallerID 2222222), all other Routes are BLOCK

I defined any calls to a 2xxx extension goes to our first Remote Office through our Bridge-to Remote1
Defined as the forth rule: Prefix 2, Length 4, Route 1 - Bridge-to Remote1, all other Routes BLOCK

I defined any calls to a 3xxx extension goes to our second Remote Office through our Bridge-to Remote2
Defined as the fifth rule: Prefix 3, Length 4, Route 1 - Bridge-to Remote2, all other Routes BLOCK

I defined the final rules that all other calls should go out our secondary line, and cascade to the main line.
Defined a sixth and seventh rule (Local and Long Distance) all calls should go out the DID Line #1, or DID Line #3 (both with Outbound Caller ID: 1111111)
Length 10, Route 1 - DID Line #3 (Outbound Caller ID 1111111), Route 2 - DID Line #1 (Outbound Caller ID: 1111111), all other Routes BLOCKED
Length 11, Route 1 - DID Line #3 (Outbound Caller ID 1111111), Route 2 - DID Line #1 (Outbound Caller ID: 1111111), all other Routes BLOCKED

This is what I am seeing:
When I dial Extension 4999 from Extension 1000, it connects
When I dial an external Local number (10 digits) from Extension 1000, it connects displaying CallerID 1111111
When I dial an external Local number (10 digits) from Extension 4999, it connects displaying CallerID 1111111

I am very confident I set up the Outgoings Rules correctly, but have no idea as to where to start looking for this issue. Outbound routing should be trivial.

Any and all input is appreciated.

Thanks.

-Tim.
 
When I dial Extension 4999 from Extension 1000, it connects


First, you can't block the dialing of an extension, by creating an outbound rule. Those rules are just that, for outbound calls, not internal calls.

Is your trunk SIP? If that is the case, and they are not individual PSTN lines, then you cannot control which "DID line" they call out on as the calls simply use a "channel", not something physical. The difference in the calls is the caller ID sent, that's it. All outbound calls will use the same trunk group. If you are using PSTN lines, then you cannot change the caller ID from the one assigned by the provider.

You should be able to define caller ID by creating rules with different caller ID, to be sent outbound. This will only work however, if it is permitted by your provider, they may only allow the sending of your main number..

Extensions can also have the outside caller ID defined in the settings, usually the full PSTN DID number.

Also...keep in mind that rules are read from the top down, and the first rule that matches will be used.
 
  • Like
Reactions: NickD_3CX
Thank you for the explanation. Yes, they are SIP Trunks.

So I guess I'll have to set it up in the extensions Dial Plan to exclude calling the one extension.

My apologies, I believe I am probably using the wrong terms, and interchanging SIP Trunk and DID. I am still recovering from a Head injury, and have difficulties at times. Please bare with me,

I am specifying the SIP Trunk to use in the Route. Each SIP Trunk has the Outgoing Caller ID set appropriately, as does the Extension. No matter what is set in the Outgoing Caller ID fields, the Caller ID of the main SIP Trunk is what the called sees.

When you said "All outbound calls will use the same trunk group.", it all came into focus what I was doing wrong. Thank you. I was confusing how things were being managed at our provider, verses our PBX.

A modification to the SIP Trunk configuration at our Provider fixed the issue. With several DID lines going through the same SIP Trunk, I needed to specify at the Provider, for them to inherit the Caller ID being sent from us.

I hope this helps someone else.

Thank you for your time.
 
Glad you got it working. I know that some providers do require that you enable an option, if you choose to send a caller ID other than the "main" number.
 
  • Like
Reactions: ChrisC_3CX
As this seems to have been resolved I'll be marking this thread as closed.

Please do start a new thread should anything else come up!
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet