Improvement of IssabelPBX System

My name is Daniel and I’m from Pear Australia. We’re a small telecommunications company with a focus on providing VoIP phone solutions to small and medium businesses. In the past we’ve concentrated on re-selling existing products and services, such as 3CX phone systems and over the past few years we’ve been working on developing our own products. The main thing we’re working on at present is an Issabel PBX based system running on CentOS 7 hosted by a Cloud Hosting Service. We currently have about 50 clients using this system and have recently come across some items that we’re looking for a developer experienced with Asterisk-based systems, particularly with Issabel, that we can work with to improve upon our PBX solution. The primary items we’re looking for help with at this point in time are: 1. To implement a parking lot setup in the same way as FreePBX – ie to have a single code to park against a specific parking lot and to pick up from that same lot. For example *8571 to park calls in Parking Lot 1, and then the same code again to retrieve from that parking lot. This is how it worked in a previous iteration of our system that utilised FreePBX and in other systems our customers use, but we have not been able to get Issabel to work the same way. 2. To have a failover SIP server set for each trunk. We currently use a combination of service providers for Trunks on our systems, each with a different primary and secondary SIP server. Currently our trunk settings only accommodate for a single SIP server to be entered, but we would like to also include the secondary SIP server as a failover in the event the primary server is unreachable. Since we do use different providers on a single system we need to be able to do this on a trunk-by-trunk basis. 3. To help investigate a problem. We’ve had some customers experiencing loss of audio, particularly during transfers, while using our Issabel based system. The same problem is not occurring to customers using other systems, and for some customers experiencing problems we’ve moved them off the Issabel system to an alternative PBX and issues no longer occur. We’d like to get to the bottom of this before it becomes a more widespread problem. In addition to the immediate points above, we’re looking for someone who’s willing to work with us over time to develop our system as we grow, helping us expand the functionality and improve upon the stability of the system, in addition to other related projects such as improving the visual layout of the web interface, development of a customer portal and implementing a provisioning platform for our preferred equipment (primarily Yealink handsets). Confidentiality and accountability are an absolute high priority for us. We have a large number of clients with a very strict data security requirements which also apply to their phone systems, so any work undertaken for us must be done under the utmost discretion. Further to this we also request that any modifications and additions be thoroughly documented for reference.