h1. Check routing

{{>toc}}

h2. Input

!check_routing.gif!

*time* - here you can specify date and time for which to check hunting. 
This might be handy when you actively use +activation date+ or [[Timetable]] in [[Prices]], then routing will be performed according to this data.

*E.164 caller ID* - check routing taking into account A-number.
This might be handy if A-number filtration is configured.

*E.164 callee ID* - field to enter B-number or destination code for which to check routing.
*technology* - need to specify inbound [[Signalling protocols|Signalling protocol]] for which to check routing.
*node* - specify node for which to check hunting. 
This might be handy for [[Clustering]] case.
*replace caller/caller ID* - if enabled, caller/callee [[Regex patterns]] will be taken in account.
*check number format* - check that number has enough digits according to [[E.164 codes]].
*outbound peer* - if specified and routing to this peer does not pass, the system displays the reason.


h2. Output

!check_routing2.gif!

Upper table - information of a call regarding inbound peer.
Lower table - routes to outbound peers.

h2. Debugging

In case if when Checking routing some dialog with information is displayed - therefore there is an issue in peer settings, for which you check routing.
In case if when Checking routing you see a price for peer for which you check routing (upper table), but don't see expected route(s), enter in field *outbound peer* a name of expected terminator/gateway/user and system will show, why there is no route to it.

h3. Errors

*Peer is disabled*
In peer's settings option *enabled*  = no

*E.164 callee ID is blocked*
In peer's settings either destination code or destination zone is blocked

*E.164 caller ID is inside a black list*
In peer's settings black caller ID pool is configured and specified caller ID is inside that list

*Caller name is inside a black list*
In peer's settings black caller name pool is configured and specified caller name is inside that list

*E.164 callee ID is inside a black list*
In peer's settings black callee ID pool is configured and specified number is inside that pool

*Blocked by Origination controller*
Dialed number is blocked by [[Origination control]]

*Route class is not configured*
[[Route class]] is not configured on peer

*Route class is not active at chosen time*
There is a [[Route class]] chosen on peer, inside which there is a Timetable which doesn't match time specified when checking routing.

*Unable to initialize peer*
There are references inside peer to deleted entities (for example, deleted Billing pack).
Try to save peer settings again to update those references.

*No matching technology configured*
There is no technology configured in peer settings which matches chosen technology when checking routing (for example. SIP)

*Profit is not acceptable*
According to [[Profit control]] it's not possible to route a call to this peer

*No route in route class*
There is no route to this peer inside [[Route class]], which activation time and timetable matches time specified when checking routing

*Wrong peer name*
Specified peer doesn't exist

*Unable to replace E.164 caller ID*
Unable to replace caller ID according to [[Regex patterns|Caller ID replace patterns]] in peer's settings

*Unable to replace caller name*
Unable to replace caller name according to [[Regex patterns|Caller name replace patterns]] in peer's settings

*Unable to replace E.164 callee ID*
Unable to replace callee ID according to [[Regex patterns|Callee ID replace patterns]] in peer's settings

*Unable to initialize billing*
There is no [[Billing pack]] configured in peer's settings, or there is no suitable price for entered number inside [[Billing pack]]

*Destination code is disabled*
Specified billing code is disabled inside [[Billing pack]], which is configured on a peer

*Blocked by Termination controller*
[[Termination control|Termination controller]] decided to block this billing code

*Outbound calls are not permitted due to balance*
Peer [[Balances|Balance]] doesn't allow to perform calls

*Endless recursion in route class configuration*
[[Route class]] contains reference to base route class, while the latter directly or indirectly refers to this route class.

*Loop to the same peer*
Call is blocked because there is is a routing loop to the same peer from which the call came inside [[Route class]].

*Loop to the same company*
Call is blocked because there is is a routing loop to the same company from which the call came inside [[Route class]].

*Unable to initialize routing*
There is no [[Route class]] configured in peer's settings, or in specified route class there are references to deleted entities (for example. [[Hunting class]])

[[Проверить хантинг|Русский перевод]]