{"id":3702,"date":"2024-07-10T07:47:40","date_gmt":"2024-07-10T04:47:40","guid":{"rendered":"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3702"},"modified":"2025-02-07T13:39:45","modified_gmt":"2025-02-07T10:39:45","slug":"the-routing-pipeline","status":"publish","type":"page","link":"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3702","title":{"rendered":"The routing pipeline"},"content":{"rendered":"\n

Traffic in the system is routed according to the principle of a routing pipeline.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The pipeline approach assumes that all traffic from the customer to the supplier passes through a unified chain of administered processes:<\/p>\n\n\n\n

    \n
  1. Filtration stage;<\/li>\n\n\n\n
  2. Routing stage;<\/li>\n\n\n\n
  3. Modification stage.<\/li>\n<\/ol>\n\n\n\n

    Each of these generalized stages at the interface level consists of a number of internally administered (configurable) components, which provides a flexible, fault-tolerant and transparent mechanism for passing traffic from the client to the provider through applications and services.<\/p>\n\n\n\n

    Filtering stage<\/h2>\n\n\n\n

    The first stage is to process incoming traffic \u2014 filtering<\/strong>. This is an administrator-configurable mechanism for blocking client traffic that does not meet the specified characteristics. By default, the services connected to contractors do not contain any filtering components. This means that the system will skip all incoming traffic without processing.<\/p>\n\n\n\n

    The filtering mechanism has an architecture based on creating a set of filtering rules<\/strong>. The rules are contained inside Filters<\/strong> \u2014 universal (not tied to any customer) sets of filtering rules.<\/p>\n\n\n\n

    Filters are created and stored in the Filters<\/a> section.<\/p>\n\n\n\n

    The created filters<\/strong> are linked as a configuration component to a specific service of a particular customer:<\/p>\n\n\n\n

    \"\"<\/a><\/figure>\n\n\n\n

    Routing stage <\/h2>\n\n\n\n

    Determining the name of the provider and selecting the trunk to which the last stage of traffic filtering will be sent is the result of the second stage of the routing pipeline.<\/p>\n\n\n\n

    To implement this stage, the following components are administered:<\/p>\n\n\n\n