Numberlist Items
Numberlist items allow to do something with source or destination number or reject call in general before its routing and after rewriting on the level of Customer Auth <customer_auth>.
Attributes
- Id
Unique Numberlist item's id.
- Numberlist
Numberlist <numberlists>that is associated with this Numberlist item.- Key
Full number or Prefix. Interpretation of this field depends on Mode of comparison that was chosen in the
Numberlist <numberlists>.- Action
This action will be applied to the call in case of conformity source (A) or destination (B) number and the Key field (according to the Mode that was chosen in the
Numberlist <numberlists>):- Default action
- Actions that is set for the
Numberlist <numberlists>) will be used. - Reject call
- Reject call in case of conformity source (A) or destination (B) number and the Key field (according to the Mode that was chosen in the
Numberlist <numberlists>). Action from theNumberlist <numberlists>) will be ignored in case of choosing this action. - Allow call
- Allow call in case of conformity source (A) or destination (B) number and the Key field (according to the Mode that was chosen in the
Numberlist <numberlists>). Action from theNumberlist <numberlists>) will be ignored in case of choosing this action.
- Src rewrite rule
Pattern parameter of regexp_replace function from the POSIX Regular Expressions. As Source parameter of regexp_replace function is used source number (number A), as a Replacement parameter of regexp_replace function is used value from Src rewrite result bellow. Returned value of regexp_replace function will be used as source number (number A) for the call during future routing. It helps to change format of the source number for providing compatibility. See
how to use POSIX Regular Expressions in Yeti <posix_regular_expressions2>{.interpreted-text role="ref"}.- Src rewrite result
Replacement parameter of regexp_replace function from the POSIX Regular Expressions. As Source parameter of regexp_replace function is used source number (number A), as a Pattern parameter of regexp_replace function is used value from Src rewrite rule above. Returned value of regexp_replace function will be used as source number (number A) for the call during future routing. It helps to change format of the source number for providing compatibility. See
how to use POSIX Regular Expressions in Yeti <posix_regular_expressions2>{.interpreted-text role="ref"}.- Dst rewrite rule
Pattern parameter of regexp_replace function from the POSIX Regular Expressions. As Source parameter of regexp_replace function is used destination number (number B), as a Replacement parameter of regexp_replace function is used value from Dst rewrite result bellow. Returned value of regexp_replace function will be used as destination number (number B) for the call during future routing. It helps to change format of the destination number for providing compatibility. See
how to use POSIX Regular Expressions in Yeti <posix_regular_expressions2>{.interpreted-text role="ref"}.- Dst rewrite result
Replacement parameter of regexp_replace function from the POSIX Regular Expressions. As Source parameter of regexp_replace function is used destination number (number B), as a Pattern parameter of regexp_replace function is used value from Dst rewrite rule above. Returned value of regexp_replace function will be used as destination number (number B) for the call during future routing. It helps to change format of the destination number for providing compatibility. See
how to use POSIX Regular Expressions in Yeti <posix_regular_expressions2>{.interpreted-text role="ref"}.- Tag action/Tag action value
Call tags modification logic. See Using Routing tags guide
- Rewrite SS Status
This attribute allows overriding the original STIR/SHAKEN attestation level by redefining
Customer Auth Rewrite SS Status value <customer_auth_stir_shaken>