Asterisk PBX Installation for Call Routing
Budget: $10 – $30 USD
I'm looking for a professional who can install Asterisk PBX to facilitate a call routing system.
Key Requirements:
- Asterisk PBX will function primarily as a call router, modifying incoming caller ID's to the outgoing trunk DIDs.
- The system should handle both incoming and outgoing calls efficiently.
- The endpoint devices that will connect to the Asterisk PBX are Mobile Operator issued SIP trunks.
Ideal Skills and Experience:
- Prior experience in setting up and configuring Asterisk PBX systems is essential.
- Proficiency in handling and routing calls effectively.
- Knowledge of SIP trunks and mobile operators' systems would be a plus.
Specific Requirements
Requirement:
A simple Asterisk PBX installed on our server. It is a voice transit facility with incoming and outgoing SIP trunks.
All incoming caller ID’s will be replaced by the DIDs provided for each MNO trunk.
Connections
1) Multiple incoming customer Accounts from Soft switches like VOS3000
2) Multiple Outgoing SIP trunks provided by local MNO’s
DID assignment/Manipulation
Incoming calls to be assigned available DIDs as follows
Since each MNO trunk has 100 DIDs, we should be able to do the following:
i) Choose outgoing caller DID for use for any duration – eg for 1 day we can choose one of the DIDs to be used for all the 100 channels in a trunk.
ii) Be able to specify how many channels a specific DID can occupy. Eg, DID1 = 10 and DID2 =30 channels.
iii) (I think this facility is best availed on the basis of outgoing MNO SIP trunks)
iv) Be able to create clusters/groups of DID. Cluster Name & specify the DIDs in it – and be able to edit (add or remove DIDs). Every Cluster/Group of DID should be a route on the server because we can create 5 clusters with each cluster calling different destinations.
v) I believe it is easier if the clusters/Groups are called Routes. A route can have 1 DID and still occupy many channels.
Interface:
1) Easy to use interfaces
2) Easy to add and remove incoming and outgoing SIP trunks.
3) Easy routing of incoming traffic to defined DID or cluster/Group/Route
Call Distribution
For every route be able to define if random or sequential in a case where we have multiple DIDs on a route.
Billing/Call Duration (Optional)
Summary of Call Duration and cost per duration ( e.g daily)
We should be able to input MNO cost per Route to achieve this
Note 1:
The budget for this job is a maximum of $70.
Don't bother to send your quote if you expect anything more than $70.
Note 2:
The PBX doesnt have to be develped from scratch. I will also accept an existing open source PBX so long as it has the capability described above and bifdder can show me how to achive the end goals.
Key Requirements:
- Asterisk PBX will function primarily as a call router, modifying incoming caller ID's to the outgoing trunk DIDs.
- The system should handle both incoming and outgoing calls efficiently.
- The endpoint devices that will connect to the Asterisk PBX are Mobile Operator issued SIP trunks.
Ideal Skills and Experience:
- Prior experience in setting up and configuring Asterisk PBX systems is essential.
- Proficiency in handling and routing calls effectively.
- Knowledge of SIP trunks and mobile operators' systems would be a plus.
Specific Requirements
Requirement:
A simple Asterisk PBX installed on our server. It is a voice transit facility with incoming and outgoing SIP trunks.
All incoming caller ID’s will be replaced by the DIDs provided for each MNO trunk.
Connections
1) Multiple incoming customer Accounts from Soft switches like VOS3000
2) Multiple Outgoing SIP trunks provided by local MNO’s
DID assignment/Manipulation
Incoming calls to be assigned available DIDs as follows
Since each MNO trunk has 100 DIDs, we should be able to do the following:
i) Choose outgoing caller DID for use for any duration – eg for 1 day we can choose one of the DIDs to be used for all the 100 channels in a trunk.
ii) Be able to specify how many channels a specific DID can occupy. Eg, DID1 = 10 and DID2 =30 channels.
iii) (I think this facility is best availed on the basis of outgoing MNO SIP trunks)
iv) Be able to create clusters/groups of DID. Cluster Name & specify the DIDs in it – and be able to edit (add or remove DIDs). Every Cluster/Group of DID should be a route on the server because we can create 5 clusters with each cluster calling different destinations.
v) I believe it is easier if the clusters/Groups are called Routes. A route can have 1 DID and still occupy many channels.
Interface:
1) Easy to use interfaces
2) Easy to add and remove incoming and outgoing SIP trunks.
3) Easy routing of incoming traffic to defined DID or cluster/Group/Route
Call Distribution
For every route be able to define if random or sequential in a case where we have multiple DIDs on a route.
Billing/Call Duration (Optional)
Summary of Call Duration and cost per duration ( e.g daily)
We should be able to input MNO cost per Route to achieve this
Note 1:
The budget for this job is a maximum of $70.
Don't bother to send your quote if you expect anything more than $70.
Note 2:
The PBX doesnt have to be develped from scratch. I will also accept an existing open source PBX so long as it has the capability described above and bifdder can show me how to achive the end goals.