Elastix Asterisk incoming / outgoing routes configuration
This a modified version of a previous job post that we've reconsidered based on more exact requirements and ignoring specific rating outgoing routes.
We have an Elastix (220.127.116.11) new installation running on an OpenVZ virtualized system which we are testing in order to replace our office phone setup. The system will be backed as a VM to be restored on separate hardware if required.
We have created basic users, trunks and extensions but have only a basic knowledge of asterisk conigurations and require advice on best queuing and routing methods considering our requirements.
There will be 5 initial trunks that will be based on physical "real" telephone" lines via converter gateways + 1 or 2 extra pure VOIP trunks for geographical numbers and voice outgoing calls.
We have a medium sized office with 3 to 4 operators attending all incoming calls. Incoming calls can be heard from any phone and at the moment whoever is free tends to “catch” the call currently dialing “72” on his/her telephone. The new system should allow a similar behaviour and “search” for a free extension in a certain order. This order might vary slightly depending on trunk and incoming call ID (international or local). We are a bit confused about the different strategies to archive this... queue, groups of extension, user login, etc
There will be a “central” automatic voice mail account to receive missed calls (maybe also based on office normal working hours) but we would perhaps also use individual voice mail on certain extensions.
We also plan perhaps for some operators to have an additional soft-phone account on their mobiles and or PCs so they can change the route of their calls and or work from home.
To configure all the required dialing groups and extensions for our inbound routes (see attached graph) with basic explanations via comments or in a reference document so we can maintain and do small changes ourselves in the future.
- suggest for our approval best queuing methods considering our requirements (see attached)
- setup incoming queue and routes
- setup music for onhold calls
- setup a central answering voice mail in case is not attended after certaing time.
As for outgoing routes we mainly dial / need to differentiate order of trunks for:
- local (spanish) land lines
- local (spanish) mobiles
- UK mobiles
- UK land lines
- international calls (mobile)?
- international calls
EXTRAS (second phase/separate jobs)
We'll be considered on a second phase, so please quote them separately.
Optimized dial plans for certain trunks.
Our objective is to be able to change the order priority of a certain trunk in some of the outgoing routes that have XX amount of prepaid minutes. For example if a trunk is first for local mobile numbers, maybe after 120 minutes of call that month that trunk might change to last in priority or at least be skipped.
We already have a small PHP file that can write to /var/spool/asterisk from certain local Ips. We might need some explanation of file format in order to dial an external number but not until the requesting operator has answered a triggering call. This is, we don't want asterisk to send the call until the operator is listening on his requesting extension.
This is a long term job for the right candidate as we expect further requirements and maintenance requirements to turn up in the future... failed trunk monitors, qos, etc
WHAT WE NEED TO RECEIVE FROM CANDIDATES
Before determining a contractor we would like to receive feedback for:
- aprox. Preferred method requirements to fulfil the job... receive the OpenVZ tar.gz we already have and return, send conf files for /etc/asterisk, elastix config. Import, etc
- aprox. expected required hours/price to complete the basic job requirements (incoming + outgoing routes)
CURRENT STATE OF OUR SYSTEM
In order to clarify current system status. We are runnning a local OpenVZ container completely working with Elastix latest version (18.104.22.168), trunks and basic extensions are configured. We can supply this machine via a dump tar.gz. Or export whatever required configurations. We use Proxmox but any OpenVZ system should work.