Quick Start: Tariff Plan and Captive Portal [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Next revision    		Previous revision
    en:dpi:dpi_options:use_cases:qs_rateplans [2023/08/28 14:52] – created elena.krasnobryzhen:dpi:dpi_options:use_cases:qs_rateplans [2025/04/29 07:40] (current) – elena.krasnobryzh
    Line 2: Line 2:
     {{indexmenu_n>3}} {{indexmenu_n>3}}
     ====== Introduction ====== ====== Introduction ======
    -To implement [[en:dpi:bras_bng:opt_bras_l3:bras_steps:start|BRAS]], this section provides an example of creating two tariff plans (policing):+To implement [[en:dpi:bras_bng:general_setup|BRAS]], this section provides an example of creating two tariff plans (policing):
       * ** rate_10M ** - basic tariff plan that is used after subscriber authorization.   * ** rate_10M ** - basic tariff plan that is used after subscriber authorization.
       * ** blocked ** - a tariff plan that is used to block a subscriber and provide access only for certain protocols. His name must be passed to the Radius-Reject.   * ** blocked ** - a tariff plan that is used to block a subscriber and provide access only for certain protocols. His name must be passed to the Radius-Reject.
     After blocking, the subscriber is assigned (Service 5) ** my_white_list ** - Allow list of resources to which he has access to pay for the service. It also redirects HTTP resources to the Captive Portal. After blocking, the subscriber is assigned (Service 5) ** my_white_list ** - Allow list of resources to which he has access to pay for the service. It also redirects HTTP resources to the Captive Portal.
    -<note important> [[en:dpi:bras_bng:opt_bras_l3:bras_steps:radius_auth_server_integration:radius_auth_response:start|The names of these profiles must be passed in the corresponding message attributes Radius-Accept, Radius-Reject.]] </note>+<note important> The names of these profiles must be passed in the [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:radius_auth_response|corresponding message attributes Radius-Accept, Radius-Reject.]] </note>
     ===== Traffic distribution by class for the tariff plan ===== ===== Traffic distribution by class for the tariff plan =====
    -To mark the priorities, use the option [[en:dpi:dpi_options:opt_priority:priority_config:start| Assigning priorities depending on the protocol]].\\+To mark the priorities, use the option [[en:dpi:dpi_options:opt_priority:priority_config| Assigning priorities depending on the protocol]].\\
      
     1. Create a **protocols.txt** file with a description of the protocol groups that we want to separate from the general traffic, and the priorities (classes) assigned to them: 1. Create a **protocols.txt** file with a description of the protocol groups that we want to separate from the general traffic, and the priorities (classes) assigned to them:
    Line 37: Line 37:
     </code> </code>
     ===== Creating a tariff plan ===== ===== Creating a tariff plan =====
    -To organize the subscriber bandwidth according to the tariff plan, use the option [[en:dpi:dpi_options:opt_bandwidth_mgmt:start|Distribution of the access channel between subscribers]].\\+To organize the subscriber bandwidth according to the tariff plan, use the option [[en:dpi:dpi_options:opt_bandwidth_mgmt|Distribution of the access channel between subscribers]].\\
     \\ \\
     1. For each tariff plan of the subscriber in the billing, create a configuration file with a description of its settings for DPI. 1. For each tariff plan of the subscriber in the billing, create a configuration file with a description of its settings for DPI.
    Line 74: Line 74:
     </code> </code>
      
    -3. So that our settings for subscribers, which we will make in the future, do not disappear when the DPI is rebooted, we connect [[en:dpi:dpi_components:platform:dpi_admin:admin_db:start#activating_the_built-in_database|UDR database]]+3. So that our settings for subscribers, which we will make in the future, do not disappear when the DPI is rebooted, we connect [[en:dpi:dpi_components:platform:dpi_admin:admin_db#activating_the_built-in_database|UDR database]]
     <code> <code>
     udr=1 udr=1
    Line 88: Line 88:
      
     1.Create a description of the tariff plan for subscribers in blocked.cfg blocking. 1.Create a description of the tariff plan for subscribers in blocked.cfg blocking.
    -Allow only cs0 traffic [[en:dpi:dpi_bestpractice:qs_rateplans|(see the list in item 1).]]+Allow only cs0 traffic [[en:dpi:dpi_options:use_cases:qs_rateplans|(read more).]]
     <code> <code>
     htb_inbound_root=rate 10mbit htb_inbound_root=rate 10mbit
    Line 115: Line 115:
     </code> </code>
      
    -3. Create a list of sites available in the Captive Portal mode. More details in the description of the [[en:dpi:dpi_options:opt_capture:start|Allow list]] option.+3. Create a list of sites available in the Captive Portal mode. More details in the description of the [[en:dpi:dpi_options:opt_capture|Allow list]] option.
      
     Create a file ** my_white_list.txt ** from the url of payment system sites. Create a file ** my_white_list.txt ** from the url of payment system sites.
    Line 131: Line 131:
     [[https://api.lightbilling.cloud/static/library/skat/white.txt| List of banks prepared by our partners]]. ** [[https://api.lightbilling.cloud/static/library/skat/white.txt| List of banks prepared by our partners]]. **
      
    -The list is ready for uploading to SKAT.+The list is ready for uploading to SSG.
     The link is updated periodically. The link is updated periodically.
     </note> </note>
    Line 155: Line 155:
      
     ===== Integration with billing without Radius ===== ===== Integration with billing without Radius =====
    -<note important> If the network still uses Radius, but you do not intend to configure the interaction of Stingray Service Gateway with billing through it and have dynamic IP addresses, you must use [[en:dpi:dpi_components:radius:start|Radius-monitor]], which would add a thread of IP-Login in the UDR.</note>+<note important> If the network still uses Radius, but you do not intend to configure the interaction of Stingray Service Gateway with billing through it and have dynamic IP addresses, you must use [[en:dpi:dpi_components:radius|Radius-monitor]], which would add a thread of IP-Login in the UDR.</note>
     1. We carry out integration with billing 1. We carry out integration with billing
      
    Line 196: Line 196:
     fdpi_ctrl del --service 5 --ip $ {ip_address} fdpi_ctrl del --service 5 --ip $ {ip_address}
     </code> </code>
    -~~ DISCUSSION | Help us improve the documentation: if something is not clear or you find a bug, please let us know. ~~+