Search results

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...

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.

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.

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...

@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.

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...

What are your experiences with using SRV records for failover instead of a health script + DNS switch? Should SRV only be used for more load balancing situations?

Not quite sure I understand the use case fully however here is an example the way I understand it. In your bridge dialplan add this line before the bridge: <action application="export" data="nolocal:execute_on_answer=execute_extension sdaa:12# XML ${context}" /> Then create this...

He says it takes code changes but refuses to send code patches to me. Instead he wants login to PBX and bulkvs. I don't trust him.

After making changes to the XML files you will have to reload your XML to pickup the changes. In the FusionPBX interface you can do that via Status > SIP Status and click the "Reload XML" button at the top right of the page.

It looks like your extension is registering from possibly a T-Mobile cellular ip address. This is the behaviour of cellular networks in the USA. I think it has to do with their CGNAT setups. I always use TCP when registering over a cellular network in the USA.