Same DID available on multiple gateways

[SweetAction]

Customer has 2 T1's coming in, each with their own PRI, each connected to their own Patton PRI gateway.
The same DID is available on each PRI...

How should my inbound rules look like? Specifically the port tab. Do I duplicate all rules or can I do a comma separate value for each gateway?

 

[cobaltit]

So it's not clear from your title but I assume you are talking about importing rules since there's no port tab in the UI. Just add the same DID on each trunk, add the rules, then export and you can see how 3CX expects it.

 

[SweetAction]

@cobaltit
Yes, that's what I meant.

I did as you recommended.... it made 2 rules, one on each port.

400 rules doubled is 800.... is there a better way?

 

[cobaltit]

What do you mean by better? If your DIDs are sequential then auto-fill in Excel is your friend. If not, then maybe your provider can provide a list of DIDs in some format you can copy/paste.

 

[SweetAction]

@cobaltit I appreciate you taking the time to answer.

The problem isn't the import. The problem is, I will now have double the inbound rules (800+ rules). This is a management nightmare as now every inbound rule change becomes 2 rule changes and browsing a list becomes 2x as long.

What I'm hoping is there is another way - perhaps the PORT can contain comma separated values? Anyone here ever deal with a similar situation.

 

[cobaltit]

Oh I see what you are getting at. AFAIK there is no other way.

 

[eddv123]

I am always interested when I hear people using multiple Patton PSTN gateways, it is not an un-common occurrence on these forums: https://www.3cx.com/community/threads/multiple-patton-gateways.49795/

I could probably understand it for FXO (mildly) as you only have a single call per line but not for E1/T1
after all Patton provide multi port gateways of many different variants including ISDN - I would be keen to hear of why it is is setup like this.

You must also consider your outbound rules also as you will have 2x gateways and thus need to route them out of the trunk (I assume you will have primary/secondary).

 

[SweetAction]

@eddv123
In this case the customer started with 1 PRI but then expanded to 2 due to needing more channels. So intial investment is already in place and replacing that for a multi-port one is more then adding a second.

As well, Patton's running smartware instead of trinity are hard to come by (I know, patton has trinity templates and 3CX should be supporting it soon, but it is not supported at this time)

 

[eddv123]

I know, patton has trinity templates and 3CX should be supporting it soon

Next release I heard on the grapevine - this is really good new for Patton as in my opinion they are by far the better of the gateways 3CX support.