Hi there!
I'm use FreePBX a long time and for outbound route I alway can setup few trunks with own prefix. When first trunk is busy, route uses next trunk and so on.
Own prefix/strip for every trunk is important part of this scheme.
How solve this task with MyPBX S100?
Yeastar is somewhat quite on the issue of fail-over trunks and you did not specify what kind of trunk and have stated a "MyPBX" which is a "U" series of PBX and not an "S", so my response may not correctly address the question.
Your question is somewhat conflicting in how presented. You indicated that you use a leading digit which I assume is to act as a prepend by which to be able to select a given trunk. This implies the need for a discrete route which is presumably needed to present the desired outbound caller-ID (CID) to the person being called. If using analog trunks, where you are not able to control the CID, the use of an automatic fail-over may remove the ability of being able to use the CID desired, but instead, the call may use the CID of the trunk on which the call was made. It simply depends on the trunk type and what the provider of same allows.
Most setups today no longer use a prepend to define a route and instead allow the PBX to manage which trunk the call will use. However Yeastar uses a slightly different mechanism and it is the dialing rule that is the initial filter.
When setting up a route, the dial plan used will be established first. This is the part of the rule that manipulates the dial string and makes it usable by the provider to include which trunk or trunks should be used. The second part is then including the trunks that should be used for the rule and the order of how the trunks should be used.
While I am not using analog trunks on my S PBX, the principal is the same :
Define the dial pattern, in my case 11 digits, but without a prepend (which I could easily add). Then, from the available trunks on the left, move the desired trunks into the selected area and then use the up and down arrows to tell the system which trunk should be at the top of the list (1st priority) and descend downward with the desire "other" trunks for this rule. When creating the rule, you can also move these around in the listing such that the system will use the first rule that matches.
When a caller dials a number, the system will look for a matching dial plan and will then strip or prepend as the rule states and will check the trunk(s) in the list from top to bottom to see which is available and will then send the call out the 1st trunk that is available.
Thanks, Larry, but it a different matter.
I know what a priority in route is, but for example:
- we have 4-channel GSM-gateway, we can select which channel use by prefix (01-04)
- we can connect 4 trunks (each trunk is one SIM-card/channel) to MyPBX
We can't use priority mechanism, because each trunk use own prefix.
How use these trunks consistently? Dial 01XXX over first trunk and if busy one, dial 02XXX.. over second.
I understand the prepend as I noted that in my post. I also noted that the prepend would allow you to specify a trunk.
However, the prepend is at the PBX level, not at the gateway level. I assume you strip the prepend at the rule for the trunk and the gateway never sees it. So. for example you have four trunks, one for each SIM - \
Trunk Sim Prepend
1 1 6
2 2 7
3 3 8
4 4 9
You create a rule for each trunk using the above strategy and a rule for each dial string that the provider needs for your calling areas. You then add the additional trunks in the order needed.
So rule 1 is trunk 1, Sim 1, prepend of 6, then trunk 2, trunk 3, etc.
Rule 2 is trunk 2, SIM 2, prepend of 7, then trunk 3, 4, 1
and so on.
It is the PBX that controls to which trunk a dial string is sent and because you want the busy fail-over, the prepend really does not matter. If you dial 6777777788, then the leading 6 will send the call to trunk 1 and if busy it will try to send it to trunk 2, and if also busy trunk 3 as the rule has (all?) the trunks you have selected set as available so, the prepend of 6 will still cause the PBX to send the call to the other trunks if trunk 1 is busy.
Gateway identify lines only by prefix! It's GoIP gateway.
If you are indicating that the gateway is the one that takes and filters the dial plan to know which trunk the call should go out, then would it not be helpful to know the gateway make and model?
Of cause!
GoIP4 or GoIP8 or GoIP16...
What is the make and model so I can review the manual?:
I have read the manual and some of the application notes on their website. The manual states for single server mode (only a single registration is required) -
c) None of the Routing Prefix es are set
- An idle channel is selected to dial out the call. If no idle channel is available, the call is rejected
by sending back a SIP 503 message
Based upon the settings shown in the screen shots, you are running in single line mode.
The manual is a little confusing in how it wants to treat the dial plan usage. When looking at the single line, group or trunk mode criteria, the use of a prefix is seemingly mandatory. As shown earlier for the single server mode, a prefix is not mandatory and the device will manage which SIM card is used based upon their availability.
Where the confusing part is in the description of the dial plan section -
This suggests that the issue is with regard to the restriction setting which imposes a set of criteria to make the dial string match before allow out to include, or not, a prefix.
My take is that if a specific channel is not specifically needed and you simply need to make a call and do not care what channel is used, then switch to single server mode, set the one registration, disable the restriction setting, eliminate the prefix and do the settings in the outbound rules of the PBX. As the GoIP is doing the hunting for the line when receiving the dial string from the PBX, it will chose which line/SIM to send the call.
Selection SIM is important part of routing, and I very disappointed that Yeastar not realize this feature over the many years of development.
If route is so important, then why a failover where it will go out another trunk anyway if the desired is busy? I still maintain that you should be able to route without a prefix in a single line mode by use of the registration. Every other gateway I know of does this. I do not perceive this as an issue with Yeastar at all, but a needless and pointless restriction on the part of the GoIP device. I should be able to use any trunk I want by setting up each channel as its own unique trunk. As this is a register trunk, the call will first have to authenticate to be allowed to go out that channel/trunk, I should not have to be so limited such that I have to place a prepend and imagine if I have a device (that they also make) with 32 GSM channels.
You could always try my initial suggestion in single line mode and then remove the prepend the restriction, and use the routing in the PBX. Just make a backup of the devices so you can restore to what you have. You could also contact the company that made the device and get their idea. You have nothing to lose either way and just maybe get what you seek.
I work with over 6 different vendors of commercially available IP-PBX systems and none accommodate automatically pre-pending a different digit on a busy trunk failure in order to rotate to another trunk that may or may not be busy.
Microsoft Teams Integration
Hikvision Intercom Integration
ISDN Switch-off Migration
All materials to evaluate Yeastar as a PBX vendor on products, solutions, partner program, support, learning resources, etc.
