In this guide would apply for all the routes of Yeastar gateways. It might have some little difference among the different model and products. But the main routing logic is similar.
- Call Match and Processing
- Route Match Sequence
- Simple Mode & Non-Simple Mode Understanding
Call Match and Processing
Here we take IPtoMobile route as example.
Incoming calls from SIP side will the match the DID Number field in section 1 (Math Incoming Calls) of Yeastar gateway. If the called number of the call matches, then the call will pass to section 2 (Incoming Calls Processing).
In section 2, you utilize the Outbound Dial Pattern, Strip and Prepend to manipulate your called number.
Route Match Sequence
In the route list. Incoming calls from SIP side will match from the top route to the bottom route. If the call matches the top route, then the call will not go through the next available route.
Simple Mode & Non-Simple Mode Understanding
Simple or Non-Simple Mode? It mainly depends on do you need the Yeastar Gateway to perform the called number manipulation.
- Simple Mode
The only field you care about the is the Hotline. It would be DID number sent to the destination trunk.
- Non-Simple Mode
Inbound Caller Pattern: this field is to match the caller ID number. It can be wildcards.
DID Number: this field is to match the called number. It can be wildcards.
For Wildcards which is also used in Outbound Patterns. You can refer to this article - Outbound Patterns to understand it better. (It's S-Series article, but the function logic is the same.)
DID Associated Number: this filed to convert the DID number to this number, and sent this number to the destination trunk. Usually it is used in the scenario of consecutive DID. ( Regular Consecutive DID and DOD Setup for TE Gateway) It can be numbers only.
Hotline: this field is to convert the DID number to this number, and sent this number to the destination trunk. Its priority is higher than the DID Associated Number field and Two stage Dialing. So try to avoid to use Hotline when you need to use the DID Associated Number field and Two stage Dialing field. It can be numbers only.
Two stage Dialing: If set to Yes, this filed to let the call enter into the DISA which gives the caller dial tone to dial the number. This option is used very few, as most users want one-time dial. Its priority is higher than the DID Associated Number field. So try to avoid to use Hotline when you need to use the DID Associated Number field.
Outbound Patterns: these fields are to match and also manipulate the called numbers.
- Outbound Dial Pattern
- Prepends these digits
You refer this guide to understand the function of the Outbound Patterns. (It's S-Series article, but the function logic is the same.)
Example of a Non-Simple Mode route.
- Call from SIP trunk to BRI trunk.
- Inbound Caller Pattern: X.
- DID Number: 865503301
- Outbound Dial Pattern: X.
- Strip: 2
- Prepend these digits: 0
- Other options are blank or set to no.
The caller ID number should be numeric. If it is "anonymous" or "unknown", the call could not allow to pass.
Also if the SIP trunk sends the DID 865503301, the call would pass.
Finally after the outbound patterns manipulation, the called number sent to BRI trunk would be 05503301.
The IPtoXXX route logic is similar for FXO gateway, TB, and TE.