BulkVS integration app for FusionPBX

SilverComm

SilverComm

New Member
Jul 30, 2024
11
5
3
I built and open sourced a FusionPBX app to integrate BulkVS functions into your FusionPBX. Simply lookup any of your phone numbers, edit it's destination, edit it's E911 address or update it's CNAM or portout PIN. You can also search for and purchase DIDs with a single click. Enjoy and feel free to contribute!
github.com

GitHub - eliweaver732/fusionpbx-app-bulkvs

Contribute to eliweaver732/fusionpbx-app-bulkvs development by creating an account on GitHub.
github.com github.com
 
  • Like
Reactions: markjcrane and voipBull
@rabbidiesel I have accepted your PR.
I can update the clone instructions. I use ssh and keys hence my reason to write it that way.
Thank you for trying it out.
 
The app now caches everything in the database for super fast page load times and uses a background process to sync the APIs. If after a sync completes and there is updated info it will display a refresh button.

I also add an E911 page to manage E911 records (all your BulkVS E911 records) as well as the ability to add records for numbers not yet provisioned. There is also a new LRN lookup button on the main page.

We use this app every day, it has been a huge timesaver managing the thousands of numbers on our servers.
@markjcrane add this to fusionpbx app collection?
 
  • Like
Reactions: vuthy09 and voipBull
Johnpbx said:
What should be entered by http_secret ?
Click to expand...
This is your customer id/key that bulkvs uses for HTTPS LRN/CNAM lookups.
BulkVS Portal > CNAM > CNAM Instructions > CNAM Methods. In the URL it is shown as id= followed by an md5 hash. This hash string is what you need to enter.
 
Hi,

It seems like the SOAP API key in API > API Credentials is the same key in the method you mentioned.

I am getting a CNAM with this, but not any other info.
I get an Invalid JSON response: Syntax error under CNAM Lookup Results.

Best Regards,
 
You are correct. It is the SOAP API KEY that you want to use. You will need to be the account owner to see this as sub accounts are restricted. The LRN uses an http endpoint so there may be security on your end preventing it from working. I will update to use https.
 
I updated this app.
  • There is now a domain and all permissions for the numbers and E911. When only the domain permission exists you can only see the numbers/E911 for the active domain. When all permission exists you can see all numbers for the specified trunk group and all E911 registrations regardless of which server they exist. There is a server permission for E911 that allows restricting to only the DIDs E911 for this server. There is also a Show All/Show Domain toggle button to filter to numbers that have a destination in the current domain.
  • Added ability to apply messaging campaigns and webhooks to numbers. This requires a new permission.
  • Registering an E911 will update the corresponding destinations to have the "emergency" type enabled. This plays nicely if you have the drop-down enabled for emergency caller id selection in extensions. Deleting an E911 removes this type so it can no longer be used.
  • Updating the LIDB will also update the matching destination's Caller ID Name.
  • Other incremental improvements. Thanks to @rabbidiesel for the contributions.
 
  • Like
Reactions: voipBull
You must log in or register to reply here.
Top Bottom