Ticket #4781 (new Feature Requests)

Opened 2 years ago

Last modified 2 years ago

Allow multiple extensions (separated by bar character) in CallerID field of Outbound Routes Dial Patterns

Reported by: sir_sip Assigned to: p_lindheimer
Priority: minor Milestone: Undetermined
Component: Core - Trunks/Routing Version:
Keywords: Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

I don't know if this is possible but I will suggest it and you can let me know if it's feasible. In the CallerID (fourth) field of "Dial Patterns that will use this Route" in Outbound Routes, would it be possible to allow specifying multiple extensions separated by the bar character? For example, let's say you wanted to allow extensions 201, 209, and 475 to use a particular outbound route. What I'd like is to be able to do is this:

20[19]|475

or even:

201|209|475

to allow multiple (but numerically unrelated) extensions to use that particular pattern.

Would it be possible to add that functionality? I know you can specify the same pattern multiple times and use different CallerID patterns in each one but I'm looking for a way to keep the size of extensions_additional.conf down a bit.

Change History

01/31/11 14:46:15 changed by p_lindheimer

If we implement this feature, it won't have any affect on extensions_additinoal.conf, You would still get a different line for each CID when not using patterns.

It would make less lines to input in the GUI though.

If we do it, I'll probably stray away from using the '|' (pipe) as a separator given the history of it's use for prefixes in earlier versions of FreePBX, it could lead to confusion. Maybe simply comma separated if we decide to add this.

However, I'm a little reluctant, at least to store it that way. Currently the table field is only a varchar(60). If we stored it this way, then we need to start expanding that table given possible long lists of CIDs. In addition, now you have hidden information that flows out of the textbox.

However, what we might want to look at is to have something like that be a short hand way of entering multiple CIDs, but on submitting the page, we would then convert it to one row per CID so on page reload, you end up with the long hand current version.

02/23/11 19:49:51 changed by p_lindheimer

  • version deleted.
  • milestone changed from 2.9 to 2.10.

09/17/11 21:12:46 changed by mbrevda

  • milestone changed from 2.10 to Undetermined.