Feature #151

context and dial pattern for lookup source selection

Added by patrick_elx over 2 years ago. Updated over 2 years ago.

Status:Closed Start:06/23/2009
Priority:High Due date:
Assigned to:- % Done:

100%
Category:-
Target version:Caller ID Superfecta v 2.2.0

Description

I would like to be able to select some lookup source depending of the number presented.

create a superfecta.conf file where we list different superfecta 'context'.
Each context has a list of dial pattern.

[USNPA]
201XNNNNNN
202XNNNNNN
etc
[US800]
800XNNNNNN
866XNNNNNN
etc
[Canada]

[MySpecificgroup]

[default] //if all the other failed

In the freepbx module, instead of having each source with Disabled/Enabled radio button, put a column for each context with a checkbox.

When the superfecta php is called, it first detect what context should be used. And then apply the selection.

It will solve the problem of numbers with more or less than 10 digits and will help people to develop their own country lookup process.

To push even farther, we can add the + | operator in the context to take care of providers transmitting the leading 1.

superfecta.cnf (831 Bytes) patrick_elx, 06/26/2009 11:43 am

Related issues

related to Caller ID Superfecta - Feature #55: Size / disucss task of having Superfecta support numbers from UK, etc. Closed 05/11/2009

History

Updated by tshif over 2 years ago

  • Status changed from New to Feedback

This seems like it would work. Very creative also :-). Would the number of contexts be fixed, or determined by the user? DO you suggest the user interface to be dynamic - to detect the number of contexts in the superfecta.conf file?

Also Patrick - would you please post here a complete example of how a superfecta.conf file would look for your country and location. It will help visualize the final results.

Updated by patrick_elx over 2 years ago

I would see something like:
before sending the number to the list, strip from the front 00 or +

[US]
20ZNXXXXX
210NXXXXX
21NNXXXXX
224NXXXXX
225NXXXXX
228NXXXXX
229NXXXXX
etc...

1|20ZNXXXXX
1|210NXXXXX
1|21NNXXXXX
1|224NXXXXX
1|225NXXXXX
1|228NXXXXX
1|229NXXXXX
etc...

[US 800]
800NXXXXXX
866NXXXXXX
877NXXXXXX
1|800NXXXXXX
1|866NXXXXXX
1|877NXXXXXX

[CAN]
204NXXXXXX
226NXXXXXX
250NXXXXXX
289NXXXXXX
306NXXXXXX
etc...

1|204NXXXXXX
1|226NXXXXXX
1|250NXXXXXX
1|289NXXXXXX
1|306NXXXXXX
etc...

[France Landline]
01XXXXXXXX
02XXXXXXXX
03XXXXXXXX
04XXXXXXXX
05XXXXXXXX
09XXXXXXXX

33|0+1XXXXXXXX
33|0+2XXXXXXXX
33|0+3XXXXXXXX
33|0+4XXXXXXXX
33|0+5XXXXXXXX
33|0+9XXXXXXXX

[France Mobile]
06XXXXXXXX
33|0+6XXXXXXXX

[Default] ; if no other context was found valid
XXXXXXXXXX ; accept 10 digits
XXXXXXXXX ; accept 9 digits
.|XXXXXXXXXX; strip numbers with more than 10 digits

I don't see an urgent need to have a gui for editing the .cnf file as changing it could be considered advanced mods the same way than changing a custom cnf file in asterisk.

However, the context group should be read by the module and then dynamicaly update a mysql superfectasource table with two fields: context group and value (list of sources used for that context)

Updated by patrick_elx over 2 years ago

in my previous message the contexts disappeared with the html formating. I have attached it as a file.

Updated by tshif over 2 years ago

  • Priority changed from Normal to High

I am particularly interested in hearing jjacobs thoughts and design ideas on this topic. This seems to be a way to add nearly ultimate flexibility in dealing with various number patterns and the various '+' or other characters send with CID info.

The superfecta.conf file would be editable though the already in-place config editor FreePBX module.

This leave the main task to change the module ui in the way you outlined. I do not have the requisite coding skills - and this task should really be completed by jjacobs if he is willing. He designed the current webui.

Updated by jacobsj over 2 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 70

See notes on related issues, but this I believe is implemented now and needs to be thoroughly tested.

Updated by jacobsj over 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 70 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

Also available in: Atom PDF