Feature #160
Different source lookup for different inbound routes
| Status: | Closed | Start: | 06/26/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Caller ID Superfecta v 2.2.0 |
Description
In addition to the feature/ticket #151 regarding having a different list of lookup source per 'context' matching phone pattern;
I would also like to see a way in each inbound route to select a superfecta group of context too.
ie: I have DID in different countries. Often the CLID presented to me for national calls does not include the country code. I can then have two identical callerID for two different callers in two different countries.
However if in the inbound route for a DID I have the choice to select instead of Superfecta a Superfecta (group country A); Superfecta (group context C), etc.. that would solve the problem.
An easy way to implement it would be to create multiple instance of superfecta module with each a different subname.
A better looking way would be to have tabs in the superfecta module like in the inbound route, or extension page.
History
Updated by tshif over 2 years ago
- Status changed from New to Feedback
This ticket discusses very basic structural and approach changes in Superfecta. This ticket is designed to foster discussion about them. Let me know if we should move it to a dev forum here for more complete discussion.
Updated by tshif over 2 years ago
Patrick - if you were to provide more details - it might stimulate discussion. Im not sure your goals here are well understood yet.
Updated by patrick_elx over 2 years ago
The goal is to have a choice in the inbound route / source lookup between different superfecta profile.
I will see the superfecta ID freepbx page like the ring group page for instance:
you ave a sub menu on the top right to add a new superfecta profile.
You give a name (ie superfecta01) to the profile and the rest of the page is still the same as now (with the other mods discussed in ticket #151).
If you add a new profile (ie superfecta02) you can choose other lookup source, order, etc...
Now on a specific inbound route (for instance a sip DID from UK) you will choose as lookup source superfecta02 that will look only on uk lookup source as nobody will call this number from the US.
On your normal US inbound route (zaptel, US DID, etc...) you will choose as lookup source superfecta01 where you will have selected the major US lookup source...
Updated by jacobsj over 2 years ago
I don't think we can do this the way that you proposed, but I think it is possible to do this in reverse.
In other words, I don't think we can specify the CID group to use on the inbound route, but on CID group (I'm using "group" loosely right now, a better term might be "Scheme") we can probably specify an inbound DID for which it will work in addition to CID patterns...so it can work basically like the existing inbound route system. I know it's duplicate info in two places, but we don't have control over the inbound route module.
Updated by jacobsj over 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 60
The latest commit as of this writing has an implementation of this. It allows users to specify CID patterns or DID. If nothing is specified the scheme will run.
This new system may have holes and needs to be tested. Of particular concern is the pattern matching. I couldn't find a pre-built function to handle pattern matching the asterisk way, so I built a function from scratch to handle it. I included support for the following characters: []!.NZX+| but I'm not sure that's an exhaustive list of the characters used in pattern matching in asterisk. Please test out some different patterns and try to find bugs.
Updated by jacobsj over 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 60 to 100
Updated by jacobsj over 2 years ago
- Target version changed from Caller ID Superfecta - Future Versions to Caller ID Superfecta v 2.2.0