{"id":3587,"date":"2024-06-07T14:33:41","date_gmt":"2024-06-07T11:33:41","guid":{"rendered":"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3587"},"modified":"2025-02-07T13:29:28","modified_gmt":"2025-02-07T10:29:28","slug":"trunks","status":"publish","type":"page","link":"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3587","title":{"rendered":"Trunks"},"content":{"rendered":"\n<p>Traffic to the <a href=\"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3572\">Supplier<\/a> is impossible without establishing a physical <strong>Trunk<\/strong> connection.<\/p>\n\n\n\n<p>Trunks are created and stored in the &#8220;Trunks&#8221; section and are always linked to a specific Supplier.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks0.png\"><img decoding=\"async\" width=\"292\" height=\"446\" src=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks0.png\" alt=\"\" class=\"wp-image-3588\" srcset=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks0.png 292w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks0-196x300.png 196w\" sizes=\"(max-width: 292px) 100vw, 292px\" \/><\/a><\/figure>\n\n\n\n<p>It is possible to create any number of trunks with different types and settings for any Supplier.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks1.png\"><img decoding=\"async\" width=\"1024\" height=\"212\" src=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks1-1024x212.png\" alt=\"\" class=\"wp-image-3589\" srcset=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks1-1024x212.png 1024w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks1-300x62.png 300w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks1.png 1588w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>When creating a trunk, the following information is required:<\/p>\n\n\n\n<ol>\n<li>Name (can be specified arbitrarily). In the case of creating a trunk for telephony, the name should be specified as follows:\n<ul>\n<li>Trunk with registration: SIP\/login;<\/li>\n\n\n\n<li>Trunk without registration: SIP\/(name in Latin) (any arbitrary but unique name);<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Provider (select a specific provider to which the trunk is connected);<\/li>\n\n\n\n<li>Trunk type (determined by the traffic transmission protocol);<\/li>\n\n\n\n<li>Modifier (specified if the outgoing traffic transmitted through the trunk requires preliminary transformation).<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks2.png\"><img decoding=\"async\" width=\"1024\" height=\"286\" src=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks2-1024x286.png\" alt=\"\" class=\"wp-image-3590\" srcset=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks2-1024x286.png 1024w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks2-300x84.png 300w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks2.png 1577w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>The <strong>type of trunk<\/strong> is determined by the protocol over which the traffic is transmitted. Each trunk type has a characteristic set of settings, in the form of fields that appear in the trunk creation form after selecting the trunk type.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks3.png\"><img decoding=\"async\" width=\"1024\" height=\"749\" src=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks3-1024x749.png\" alt=\"\" class=\"wp-image-3591\" srcset=\"https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks3-1024x749.png 1024w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks3-300x219.png 300w, https:\/\/docs.cpaas.mittoapi.net\/wp-content\/uploads\/2024\/06\/trunks3.png 1164w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p><strong>SMPP protocol:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th><strong>Setting<\/strong><\/th><th><strong>Description<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Host<\/td><td>SMPP server address<\/td><\/tr><tr><td>Port<\/td><td>SMPP server port<\/td><\/tr><tr><td>Password<\/td><td>SMPP server password<\/td><\/tr><tr><td>NumberOfPoll<\/td><td>number of survey attempts<\/td><\/tr><tr><td>SleepOfPoll<\/td><td>the time interval (in milliseconds or seconds) between server polling attempts<\/td><\/tr><tr><td>EnquireLinkInt<\/td><td>the time interval (in milliseconds or seconds) through which the client will send Enquire Link packets to verify the connection to the server<\/td><\/tr><tr><td>EnquireSleepRespInt<\/td><td>the time interval (in milliseconds or seconds) for waiting for a response from the server to the Enquire Link packet<\/td><\/tr><tr><td>Equipment<\/td><td>SMPP server hardware<\/td><\/tr><tr><td>Version<\/td><td>the version of the SMPP protocol used<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>HTTP protocol:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th><strong>Setting<\/strong><\/th><th><strong>Description<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Url<\/td><td>The URL of the server to be interacted with<\/td><\/tr><tr><td>CallbackUrl<\/td><td>The URL to which callbacks from the server will be sent<\/td><\/tr><tr><td>Version<\/td><td><strong>API version used<\/strong> \u2014 indicates the version of the API that is being used in the current context;<br><strong>API version in the URL<\/strong> \u2014 indicates the version of the API as part of the URL.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>SIP protocol<\/strong>:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th><strong>Setting<\/strong><\/th><th><strong>Description<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Host<\/td><td>server address<\/td><\/tr><tr><td>Port<\/td><td>server port<\/td><\/tr><tr><td>Context<\/td><td>context for SIP connections<\/td><\/tr><tr><td>CallLimit<\/td><td>limit on the number of calls<\/td><\/tr><tr><td>CpsLimit<\/td><td>limit on the number of calls per second<\/td><\/tr><tr><td>Sip Connection direction<\/td><td>SIP connection direction (input, output, two-way)<\/td><\/tr><tr><td>Equipment<\/td><td>type or model of equipment<\/td><\/tr><tr><td>Logging on SBC:<\/td><td>logging on the Session Border Controller (SBC)<\/td><\/tr><tr><td>Type of SIP authentication<\/td><td>authentication type for SIP connections<\/td><\/tr><tr><td>Area ID<\/td><td>the ID of the zone or region used for routing calls or other logic<\/td><\/tr><tr><td>Interface name<\/td><td>the name of the network interface used for SIP connections<\/td><\/tr><tr><td>Sending SIP OPTIONS, ms<\/td><td>the time interval (in milliseconds) for sending SIP OPTIONS requests in order to check the availability and connection status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>PUSH ID MTS protocol and PUSH ID Beeline protocol:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th><strong>Setting<\/strong><\/th><th><strong>Description<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Client ID<\/td><td>a unique identifier assigned to the client (application) when registering in the authentication or authorization system<\/td><\/tr><tr><td>AuthorizeUrl<\/td><td>The URL to which the user will be redirected to complete the authorization process<\/td><\/tr><tr><td>NotificationUrl<\/td><td>The URL to which notifications or responses will be sent after the authentication or authorization process is completed<\/td><\/tr><tr><td>Aud<\/td><td>ID of the resource or API to be accessed<\/td><\/tr><tr><td>AcrValues:<\/td><td><a><\/a> Authentication Context Class Reference (ACR) values that define the level of authentication, for example, the level of reliability of the authentication procedure (for example, 2FA or MFA)<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Traffic to the Supplier is impossible without establishing a physical Trunk connection. Trunks are created and stored in the &#8220;Trunks&#8221; section and are always linked to a specific Supplier. It is possible to create any number of trunks with different types and settings for any Supplier. When creating a trunk, the following information is required: <a href=\"https:\/\/docs.cpaas.mittoapi.net\/?page_id=3587\" class=\"more-link\">&#8230;<span class=\"screen-reader-text\">  Trunks<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"tpl\/administration-content.php","meta":[],"acf":[],"_links":{"self":[{"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/pages\/3587"}],"collection":[{"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3587"}],"version-history":[{"count":6,"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/pages\/3587\/revisions"}],"predecessor-version":[{"id":4209,"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=\/wp\/v2\/pages\/3587\/revisions\/4209"}],"wp:attachment":[{"href":"https:\/\/docs.cpaas.mittoapi.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}