{"id":6053,"date":"2026-02-13T15:16:54","date_gmt":"2026-02-13T14:16:54","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=6053"},"modified":"2026-02-13T15:16:54","modified_gmt":"2026-02-13T14:16:54","slug":"sip-endpoints","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/sip-endpoints\/","title":{"rendered":"SIP endpoints"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

[Reading time: 3 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

SIP endpoints allow you to connect external telephony systems to INO cx. They are used when calls must be routed through a specific telephony server instead of the default telephony infrastructure.<\/p>\n\n\n\n

This feature is particularly useful if you need to:<\/p>\n\n\n\n

\u2022 Connect your own telephony infrastructure
\u2022 Route calls through a dedicated or private SIP trunk
\u2022 Connect to internal or secured phone networks
\u2022 Use different trunks depending on your routing strategy<\/p>\n\n\n\n

Once configured, a SIP endpoint can be used in voice smart routing scenarios to send calls to an external telephony system.<\/p>\n\n\n\n

Note: In most cases, SIP trunks are already configured during the initial platform setup. You usually do not need to create additional SIP endpoints.<\/em><\/p>\n\n\n\n

1. Accessing the SIP endpoints module<\/h2>\n\n\n\n

To manage SIP endpoints:<\/p>\n\n\n\n

    \n
  1. Open the Maker<\/li>\n\n\n\n
  2. Go to the SIP endpoints module<\/li>\n<\/ol>\n\n\n\n

    The page displays all existing SIP endpoints. You can:<\/p>\n\n\n\n

    \u2022 Search for an endpoint using the search bar
    \u2022 Create a new endpoint
    \u2022 Edit or delete existing endpoints
    \u2022 Duplicate configurations to save time<\/p>\n\n\n\n

    2. Creating a SIP endpoint<\/h2>\n\n\n\n

    To create a new SIP endpoint:<\/p>\n\n\n\n

      \n
    1. Click Create<\/li>\n\n\n\n
    2. Fill in the required information<\/li>\n\n\n\n
    3. Click Add SIP endpoint<\/li>\n<\/ol>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      2.1. SIP endpoint<\/h3>\n\n\n\n

      Enter the destination telephony server.<\/p>\n\n\n\n

      You can use either:
      \u2022 A domain name
      \u2022 An IP address<\/p>\n\n\n\n

      This corresponds to the SIP trunk that INO cx will use to route calls.<\/p>\n\n\n\n

      2.2. Port<\/h3>\n\n\n\n

      Defines the SIP communication port.<\/p>\n\n\n\n

      The default value is 5060<\/strong>, which is commonly used for SIP communications. You should only modify this value if your telephony provider requires a different port.<\/p>\n\n\n\n

      2.3. Reference<\/h3>\n\n\n\n

      The reference is a unique name used to identify the SIP endpoint in your configuration.<\/p>\n\n\n\n

      It can include the following special characters:
      _ . @ –<\/p>\n\n\n\n

      Choose a clear and meaningful reference to make future maintenance easier.<\/p>\n\n\n\n

      2.4. Codec<\/h3>\n\n\n\n

      Defines the audio format used during calls.<\/p>\n\n\n\n

      Available options:
      \u2022 alaw
      \u2022 ulaw
      \u2022 alaw and ulaw<\/p>\n\n\n\n

      The codec must be compatible with the connected telephony infrastructure. If you are unsure, check with your telephony provider.<\/p>\n\n\n\n

      2.5. User name<\/h3>\n\n\n\n

      Authentication username used to connect to the SIP server.<\/p>\n\n\n\n

      2.6. Password<\/h3>\n\n\n\n

      Password associated with the SIP authentication.<\/p>\n\n\n\n

      2.7. Realm<\/h3>\n\n\n\n

      Optional parameter used for SIP authentication. When configured, this value is transmitted during the authentication process. You usually only need to fill in this field if your telephony provider specifically asks for it.<\/p>\n\n\n\n

      3. Managing SIP endpoints<\/h2>\n\n\n\n

      Once created, SIP endpoints are displayed in a list showing:<\/p>\n\n\n\n

      \u2022 SIP endpoint
      \u2022 Port
      \u2022 Reference
      \u2022 Codec
      \u2022 User name<\/p>\n\n\n\n

      You can manage each endpoint using the action buttons available at the end of the row.<\/p>\n\n\n\n

      3.1. Cogged wheel<\/h3>\n\n\n\n

      Allows you to:<\/p>\n\n\n\n

      \u2022 Duplicate the endpoint configuration
      \u2022 View configuration history
      \u2022 Manage tags<\/p>\n\n\n\n

      3.2. Edit<\/h3>\n\n\n\n

      Allows you to modify the SIP endpoint configuration.<\/p>\n\n\n\n

      3.3. Delete<\/h3>\n\n\n\n

      Permanently removes the SIP endpoint.<\/p>\n\n\n\n

      4. Using a SIP endpoint in voice smart routing<\/h2>\n\n\n\n

      After creating a SIP endpoint, you can use it in routing scenarios.<\/p>\n\n\n\n

      To do it:<\/p>\n\n\n\n

        \n
      1. Open your voice smart routing scenario<\/li>\n\n\n\n
      2. Add the action Distribution to SIP endpoint<\/li>\n\n\n\n
      3. Select the SIP endpoint you want to use<\/li>\n<\/ol>\n\n\n\n
        \"\"<\/figure>\n\n\n\n

        Calls matching the routing conditions will then be sent to the selected telephony server.<\/p>\n","protected":false},"excerpt":{"rendered":"

        [Reading time: 3 minutes] Overview SIP endpoints allow you to connect external telephony systems to INO cx. They are used when calls must be routed through a specific telephony server instead of the default telephony infrastructure. This feature is particularly useful if you need to: \u2022 Connect your own telephony…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[107],"ht-kb-tag":[],"class_list":["post-6053","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-configuring"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6053","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=6053"}],"version-history":[{"count":2,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6053\/revisions"}],"predecessor-version":[{"id":6057,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/6053\/revisions\/6057"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=6053"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=6053"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=6053"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}