We begin our discussion with no forking to help you understand how normal call flow occurs in a Call Routing Table, then we introduce the concept of forking.
Call Flow With No Forking
The call flow begins with an Inbound Signaling Group passing the call to a Call Routing Table (CRT). The routing table comprises one or more Call Route Entries (rows) that specify Transformation Tables where given aspects of the call are examined and matched, and then reported back to the Routing Table Entry as a success or failure.
Upon Success, the call is then routed to the Outbound Signaling Group as specified in the #Destination Information Panel of the Call Route Entry and no further routing is performed.
Call Flow With Forking
As with the example above, the call flow begins the same way with the call going to the CRT and the CRT passing the information to a Transformation Table and receiving a success or failure.
If a CRT entry is not forked and the transformation fails, the call is passed to the next element in the table and its associated transformation is tested. If the transformation is successful the call is sent to the destination Signaling Group and no further traversing of the table occurs.
If a CRT entry is forked and the associated transformation fails, the call is passed to the next element in the table as above.
If that CRT entry is forked, whether or not its transformation fails, the call is passed to the next entry in the CRT. If that successive entry succeeds and it is not forked, the call is sent to the destination Signaling Group and no further traversing of the table occurs.
Destination Information Panel
An incoming call may be forked up to 8 destinations.