Open GoogleCodeExporter opened 9 years ago
This might be a place where mod_odbc_query or a simple lua query to a database
makes it easier than a whole string of DID mappings. Or mod_easyroute which is
supposed to be for this.
True, you're adding a DB dependency to the call routing then.
Original comment by kLd...@gmail.com
on 6 Jan 2012 at 12:00
I would have to agree... If you have that many DID's I'd probably go with using
mod_easyroute.
Original comment by bdfos...@endigotech.com
on 7 Jan 2012 at 4:58
I also agree and will plan on adding a mod_easyroute to fusionpbx as an add on.
Original comment by markjcrane@gmail.com
on 12 Apr 2012 at 5:30
Any update on this guys.....I was able to convince a friend to migrate from a
commercial Asterisk based PBX system over to FusionPBX but one of the
disadvantages with the migration is we have no way to upload DIDs in bulk
especially when they have about 300 DIDs.
Original comment by ewsamu...@gmail.com
on 20 Aug 2013 at 7:35
Here is a patch to Inbound Dialplan that will allow bulk upload. It functions
like the one I wrote for Destinations. I have been able to slim down the sql
inserts to two per entry.
Notes:
- Works only for mapping DID to extension. If you are mapping to
IVR/Conference/Fax please add those manually.
- Setting the limit field to 0 disables limit.
- Tested with 100 entries and no issues. (intend to test larger batches to see
if any issues arise)
Future Changes:
- Allow for IVR/Conference/Fax entries to be uploaded as well.
- Integrate permission to allow/block access to the bulk upload.
CSV format:
Name, Number, Action, Limit, Order, Enabled, Discription
9728888888,9728888888,9000 XML Domain,0,000,true,9000 exten
I have attached my modified dialplans.php as well as a sample csv file for
review.
Original comment by spartian...@gmail.com
on 14 Sep 2013 at 6:42
Attachments:
The inbound routes should be tied via a uuid to the dialplan -> destinations.
To consider an inbound route tool without that is to limit future features that
will benefit from that association.
Original comment by markjcrane@gmail.com
on 16 Sep 2013 at 2:26
Thanks Mark. I am still working through the source figuring things out. Must
have missed this though if I understand correctly when the inbound route is
created the v_destinations table should be updated with the dialplan_uuid for
the destination_number. Let me know if the modifications on the attached
dialplans.php is what it should be or if I need to do something further.
Original comment by spartian...@gmail.com
on 16 Sep 2013 at 4:53
Attachments:
Original issue reported on code.google.com by
esamuels...@gmail.com
on 5 Jan 2012 at 11:34Attachments: