{"id":3719,"date":"2020-07-20T14:43:53","date_gmt":"2020-07-20T12:43:53","guid":{"rendered":"http:\/\/&p=3719"},"modified":"2020-07-20T14:43:53","modified_gmt":"2020-07-20T12:43:53","password":"","slug":"configuring-astra-with-wintrunk","status":"publish","type":"docs","link":"https:\/\/www.winet.ch\/en\/support\/wiki\/konfiguration-astra-mit-wintrunk\/","title":{"rendered":"Configuring Astra with winTrunk"},"content":{"rendered":"

General<\/h1>\n\n\n\n
  1.  AG<\/strong><\/strong><\/li><\/ol>\n\n\n\n

    Product Name: winTrunk<\/p>\n\n\n\n

    Codec \/ Frame Length: G.711a \/ 20 ms<\/p>\n\n\n\n

    Fax: T.38 Minutes 1)<\/sup><\/p>\n\n\n\n

    Registration of SIP Accounts: The communications server registers using a special SIP account that is completely independent of the assigned number range.<\/p>\n\n\n\n

    ALG Function: The Winet platform communicates directly with the private IP addresses of the Aastra Communication Server and the IP phones. Therefore, the ALG function must not be enabled on either the NAT router or the Aastra Communication Server.<\/p>\n\n\n\n

    1) T.38 is only available for phone numbers that have been previously registered with Winet.<\/p>\n\n\n\n

    1. 400<\/strong><\/li><\/ol>\n\n\n\n

      Aastra Communication Server: Aastra 415, Aastra 430, Aastra 470 Release 3.0 SP1 HF1<\/p>\n\n\n\n

      Software Version: 8444a1<\/p>\n\n\n\n

      Voice Gateways: EIP or Standard Media Switch<\/p>\n\n\n\n

      Information on Aastra Mobility Solutions<\/h1>\n\n\n\n

      The following call scenarios were tested:<\/h3>\n\n\n\n
      • A cell phone calls an external subscriber via AMC 3 \u00abCall-Through,\u00bb places the call on hold using the AMC 3 application, and transfers it to an internal user with an IP endpoint.<\/li>
      • An external caller uses an Aastra 400 to call an internal user on a mobile phone. The mobile phone places this call on hold using the AMC 3 application and transfers the external caller to an internal user with an IP endpoint.<\/li>
      • An internal user with an IP-based device calls an internal user with a cell phone. The cell phone places this connection on hold using the AMC 3 application and transfers the caller to an internal user with an AD2 device.<\/li>
      • An external caller uses an Aastra 400 to call an internal user on a cell phone (in One Number 1:n).<\/li>
      • An internal user with an IP device initiates a Fast Take to an internal user with a cell phone, whose line is currently busy.<\/li>
      • A cell phone uses the AMC 3 application to initiate a \"Fast Take\" to an occupied internal user with an IP device.<\/li>
      • One cell phone calls another cell phone. The second cell phone places this call on hold using the AMC 3 application and transfers the caller to an internal user with an IP-based device.<\/li>
      • A cell phone (without an available data connection) calls an external subscriber using the AMC 3 application.<\/li>
      • An external caller dials a cell phone (without an available data channel).<\/li><\/ul>\n\n\n\n

        Notes on the AMC 3 Solution:<\/h3>\n\n\n\n
        • All tests were conducted using a mobile phone (Android operating system v4.3) and the AMC software versions AMCC 10684.16.5 and AMC 4-Client 4.0.2 Build 3527.<\/li>
        • The \u00abwinTrunk\u00bb must have the \u00abCLIP no screening\u00bb option enabled so that the CLIP number of the calling A subscriber is displayed on the mobile phone being called.<\/li>
        • In the call scenario \u00abAn external caller uses an Aastra 400 to call an internal user on a cell phone,\u00bb the cell phone displays\u00a0always\u00a0<\/strong>the CLIP number of the calling external A subscriber is presented.<\/li><\/ul>\n\n\n\n
          1. (Controller)<\/strong><\/li><\/ol>\n\n\n\n

            The following call scenarios1)<\/sup> The following were tested:<\/h3>\n\n\n\n
            • A GSM cell phone calls an external subscriber using a GSM integration number, places the call on hold, and transfers it to an internal user with an IP-based terminal.<\/li>
            • An external caller uses an Aastra 400 to call an internal user with a GSM device. The GSM cell phone places the call on hold and transfers it to an internal user with an IP device.<\/li>
            • An internal user with an IP device calls an internal user with a GSM device. The GSM cell phone places this connection on hold and transfers the caller to an internal user with an AD2 device.<\/li>
            • An external caller uses an Aastra 400 to call an internal user with a GSM device (in One Number 1:n).<\/li>
            • An internal user with an IP device initiates a Fast Take to an internal user with a GSM device, whose GSM cell phone is currently busy.<\/li>
            • A GSM cell phone performs a \"Fast Take\" on an occupied internal user with an IP terminal.<\/li><\/ul>\n\n\n\n

              Notes on GSM Integration:<\/h3>\n\n\n\n
              • The \u00abwinTrunk\u00bb must have the \u00abCLIP no screening\u00bb option enabled so that the CLIP number of the calling A subscriber is displayed on the called GSM cell phone.<\/li>
              • With the Aastra 400, it is possible to transmit the CLIP number of the Aastra 400\u00abs GSM terminal (B-subscriber) to the called GSM mobile phone instead of the CLIP number of the calling external A-subscriber (e.g., multi-tenant functionality). If this is desired, the parameter \u00bbSend incoming CLIP for PBX-to-PBX connections\u00ab must be set to \u00bbNo\u00ab in the corresponding SIP bundle (AMS CM_3.1.5 bundle, \u00bbCLIP\u201d tab).<\/li>
              • Conferences with two external participants initiated by an AMC 3 user are currently not possible.<\/li><\/ul>\n\n\n\n

                1) This also applies to an Aastra Mobile Client (AMC 2.0) installed on a GSM cell phone.<\/p>\n\n\n\n

                1. Restrictions<\/strong><\/li><\/ol>\n\n\n\n
                  • To enable all call scenarios in conjunction with \u00abwinTrunk,\u00bb the RTP data stream must always be routed through the communication server (known as \u00abindirect switching\u00bb; AMS_CM_3.2.4, parameter \u00abRoute RTP data stream via communication server\u00bb set to \u00abYes\u00bb). <\/strong>When planning your project, please note that \u00abindirect switching\u00bb may require more VoIP resources in the Aastra 400.<\/li><\/ul>\n\n\n\n

                    Important: <\/strong>No tests were conducted using \u00abDirect Switching,\u00bb so \u00abDirect Switching\u00bb in combination with \u00abwinTrunk\u00bb not <\/strong>Approved.<\/p>\n\n\n\n

                    • Winet uses domain names for the SIP registrar and the SIP proxy. Please configure at least one IP address of a valid DNS server (AMS_CM_2.2.1) in the Aastra 400.<\/li>
                    • If the Communication Server does not have any ISDN trunk lines, please disable clock synchronization on all ISDN trunk ports (if present) and then restart the Communication Server. Next, verify that the \u00abSync Status\u00bb parameter displays the status \u00abIdle\u00bb (AMS CM_3.2.1.1, \u00abClock Reference\u00bb tab).<\/li>
                    • To ensure that the Communication Server's clock remains accurate even when ISDN trunk lines are unavailable, we recommend using an NTP time server (AMS CM_2.3.3.5).<\/li><\/ul>\n\n\n\n

                      Example: europe.pool.ntp.org<\/p>\n\n\n\n

                      • For call forwarding via SIP trunk \u2013 SIP trunk, we recommend using the SIP Diversion header \u00abnon-recursing\u00bb (AMS_CM_3.2.4) so that the calling party\u2019s number (A-number) is displayed to the recipient. For SIP trunk call forwarding to SIP trunk (within the Aastra 400) without a SIP Diversion header, the external recipient of the forwarded call will always see the calling party\u2019s number (B number) as the CLIP.<\/li>
                      • To ensure that outgoing CLIP transmission works as well as possible, we recommend that each user leave the \u00abCLIP automatically\u00bb setting set to \u00abYes\u00bb (AMS CM_4.1 users).<\/li>
                      • \u00abwinTrunk\u00bb supports the \u00abCLIP no screening\u00bb feature. This feature allows Aastra 400 users to transmit CLIP numbers on outgoing calls that do not belong to the assigned number range (e.g., 0800 xxx xxx), or, when using one of the two Aastra mobility solutions, the phone numbers of external callers can also be transmitted to the called mobile phones in certain call scenarios.<\/li>
                      • When transferring external or internal calls without <\/strong>In rare cases, the A-participant may not hear a dial tone during pre-registration.<\/li><\/ul>\n\n\n\n

                        Configuring the Aastra 400 Communication System<\/h1>\n\n\n\n
                        • These configuration instructions describe only the SIP-specific configurations required to operate the Aastra 400 with \u00abwinTrunk\u00bb from Winet Network Solutions AG.<\/li><\/ul>\n\n\n\n

                          For information on required hardware, licenses, and other configuration options, please refer to the relevant system manuals.<\/p>\n\n\n\n

                          • The screenshots are based on AMS 3.0.22c and software version 8444a1 of the Aastra 400 Release 3.0 SP1 HF1.<\/li>
                          • Please change only the parameters that are specifically marked; leave the rest in their default settings as much as possible, as shown in the screenshots below.<\/li><\/ul>\n\n\n\n
                            • configure<\/strong><\/li><\/ul>\n\n\n\n

                              Aastra 400 WebAdmin allows you to import the SIP provider settings specified in \u00abCM_3.2.4 SIP Provider\u00bb using an XML file. This XML file is available for download in the KnowledgeBase under \u00abTI 1537.\u00bb.<\/p>\n\n\n\n

                              AMS CM_3.2.4 SIP Provider\/Account<\/h3>\n\n\n\n
                              2)<\/td><\/tr>
                              3)<\/td><\/tr>
                              4)<\/td><\/tr>
                              5)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                              1. \u00abSet the \u00bbFrom field for CLIR\u00ab to \u00bbRetrieve from SIP account (RFC 3323).\".<\/li>
                              2. \u00abSet \u00bbMusic While Waiting\u00ab to \u00bbYes.\".<\/li>
                              3. \u00abSet \u00bbMusic While Waiting: Signaling\u00ab to \u00bbNo Signaling (no media updates).\".<\/li>
                              4. \u00abSet \u00bbSend redirection information\u00ab to \u00bbYes, with Diversion header (non-recursing).\".<\/li>
                              5. Set the \u00abPreferred Codec\u00bb parameter to \u00abG.711a.\u00bb.<\/li>
                              6. Enter \u00absbc.winet.ch\u00bb as the registrar and proxy.<\/li>
                              7. Set the preferred registration interval to 120 seconds.<\/li>
                              8. \u00abSet \u00bbEnable keep-alive\u00ab to \u00bbYes\"<\/li>
                              9. \u00abSet \u00bbRoute RTP data stream via communication server\u00ab to \u00bbYes.\".<\/li>
                              10. Specify the desired bundle number for Winet.<\/li>
                              11. \u00abSet \u00bbProvider Authentication\u00ab to \u00bbWith an Account\"<\/li><\/ol>\n\n\n\n
                                • configure<\/strong><\/li><\/ul>\n\n\n\n

                                  AMS CM_3.1.5 Bundle, \u00abBundle\u00bb tab\u00bb<\/h3>\n\n\n\n
                                  <\/td><\/tr>
                                  <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                  <\/strong><\/p>\n\n\n\n

                                  1. Define the extension plan for the \u00abwinTrunk\u00bb phone numbers.<\/li><\/ol>\n\n\n\n

                                    If you need multiple extension plans (e.g., for a mixed \u00abwinTrunk\u00bb\/ISDN setup), define the extension plan in the SIP bundle before opening the SIP accounts. This should not <\/strong>must be identical to the extension plan for the ISDN bundle!<\/p>\n\n\n\n

                                    AMS CM_3.1.5 Bundle, \u00abFeatures\u00bb tab\u00bb<\/h3>\n\n\n\n
                                    <\/td><\/tr>
                                    <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                    • If the Diversion header is enabled in the SIP provider configuration (AMS CM_3.2.4), the \u00abSend redirection information\u00bb parameter must be set to \u00abYes\u00bb here.<\/li><\/ul>\n\n\n\n

                                      If the Diversion header is not enabled in the SIP provider configuration, the \u00abSend redirection information\u00bb parameter must be set to \u00abNo\u00bb here.<\/p>\n\n\n\n

                                      AMS CM_3.1.5 Bundle, \u00abCLIP\u00bb tab\u00bb<\/h3>\n\n\n\n
                                      • Define a CLIP number here for the following cases:
                                        • <\/li><\/ul><\/li><\/ul>\n\n\n\n
                                          3)    <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                          If an internal user (with \u00abAutomatic CLIP = Yes\u00bb) does not have an assigned extension number, the CLIP number configured here will be sent along with the call.<\/p>\n\n\n\n

                                          • Outgoing calls made using the line buttons on the switchboard units include the CLIP number configured here (if the system setting is AMS CM_2.3.2).<\/li><\/ul>\n\n\n\n
                                            • \u00abSet \u00bbTransit CLIP Format\u00ab to \u00bbUnknown with national prefix.\".<\/li><\/ul>\n\n\n\n
                                              • configure<\/strong><\/li><\/ul>\n\n\n\n

                                                AMS CM_3.1.6 Routes<\/h3>\n\n\n\n
                                                <\/td><\/tr>
                                                <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                                <\/strong><\/p>\n\n\n\n

                                                Add the previously configured SIP bundle to the desired route.<\/p>\n\n\n\n

                                                • configure<\/strong><\/li><\/ul>\n\n\n\n

                                                  AMS CM_3.2.4 SIP Provider\/Account<\/h3>\n\n\n\n
                                                  • Click in the empty field on the \u00abSIP Account\u00bb tab and select \u00abAdd.\u00bb.<\/li><\/ul>\n\n\n\n
                                                    1. In the \u00abSIP-ID\u00bb field, enter the username you received from Winet.<\/li><\/ol>\n\n\n\n
                                                      • The \"Extension Number\" field remains blank.<\/li><\/ul>\n\n\n\n
                                                        • Enter the information you received from Winet in the \u00abUsername\u00bb and \u00abPassword\u00bb fields.<\/li><\/ul>\n\n\n\n
                                                          • The \u00abRegistration Required\u00bb parameter must be set to \u00abYes.\u00bb.<\/li><\/ul>\n\n\n\n
                                                            • The \u00abDefault Account\u00bb parameter must be set to \u00abYes.\u00bb.<\/li><\/ul>\n\n\n\n
                                                              • The \u00abFrom Field Type\u00bb is \u00abSystem CLIP.\u00bb.<\/li><\/ul>\n\n\n\n

                                                                Note:<\/h3>\n\n\n\n

                                                                With \u00abwinTrunk,\u00bb the communications server registers using a special SIP account that is completely independent of the assigned number range.<\/p>\n\n\n\n

                                                                • configure<\/strong><\/li><\/ul>\n\n\n\n

                                                                  AMS CM_3.1.3 Extension Plans<\/h3>\n\n\n\n
                                                                  <\/td><\/tr>
                                                                  <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                                                  <\/strong><\/p>\n\n\n\n

                                                                  1. Use the \u00abNew Numbers\u00bb button to set up the entire SIP phone number block in the format 0xxxxxxxxx.<\/li><\/ol>\n\n\n\n

                                                                    AMS CM_3.1.3 Extension Plans, \u00abARV Destinations\u00bb tab\u00bb<\/h3>\n\n\n\n
                                                                    <\/td><\/tr>
                                                                    <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                                                    <\/strong><\/p>\n\n\n\n

                                                                    • Now configure the desired ARV destination for each extension number.<\/li><\/ul>\n\n\n\n
                                                                      • Fax port<\/strong><\/li><\/ul>\n\n\n\n

                                                                        AMS CM_4.2 Terminal Data, \u00abAnalog Settings\u00bb tab\u00bb<\/h3>\n\n\n\n
                                                                        <\/td><\/tr>
                                                                        <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                                                                        <\/strong><\/p>\n\n\n\n

                                                                        1) Set the \u00abFax Device\u00bb parameter to \u00abMultifunction Device (Voice\/T.38).\u00bb.<\/p>\n\n\n\n

                                                                        When using T.38, please note that you must use the appropriate DSP configuration with \u00abFoIP\u00bb (AMS CM_2.1.3) or an EIP card. For information on required hardware, licenses, and system limits, please refer to the relevant system manuals.<\/p>","protected":false},"excerpt":{"rendered":"

                                                                        Allgemein  AG Produktbezeichnung:                                                          winTrunk Codec \/ Framel\u00e4nge:                                                          G.711a \/ 20ms Fax:                                                                                     T.38 Protokoll 1) Registrierung der SIP-Konten:                                           Der Kommunikationsserver registriert …<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"doc_category":[42],"doc_tag":[],"class_list":["post-3719","docs","type-docs","status-publish","hentry","doc_category-sip-trunk-anbindungen"],"acf":[],"year_month":"2026-11","word_count":2105,"total_views":"19","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"admin-unmwoaed","author_nicename":"admin-unmwoaed","author_url":"https:\/\/www.winet.ch\/en\/author\/admin-unmwoaed\/"},"doc_category_info":[{"term_name":"SIP Trunk Anbindungen","term_url":"https:\/\/www.winet.ch\/en\/wiki-category\/sip-trunk-anbindungen\/"}],"doc_tag_info":[],"yoast_head":"\nKonfiguration Astra mit winTrunk - Winet<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.winet.ch\/en\/support\/wiki\/configuring-astra-with-wintrunk\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Konfiguration Astra mit winTrunk\" \/>\n<meta property=\"og:description\" content=\"Allgemein  AG Produktbezeichnung:                                                          winTrunk Codec \/ Framel\u00e4nge:                                                          G.711a \/ 20ms Fax:                                                                                     T.38 Protokoll 1) Registrierung der SIP-Konten:                                           Der Kommunikationsserver registriert ...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.winet.ch\/en\/support\/wiki\/configuring-astra-with-wintrunk\/\" \/>\n<meta property=\"og:site_name\" content=\"Winet\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.winet.ch\\\/support\\\/wiki\\\/konfiguration-astra-mit-wintrunk\\\/\",\"url\":\"https:\\\/\\\/www.winet.ch\\\/support\\\/wiki\\\/konfiguration-astra-mit-wintrunk\\\/\",\"name\":\"Konfiguration Astra mit winTrunk - Winet\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.winet.ch\\\/#website\"},\"datePublished\":\"2020-07-20T12:43:53+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.winet.ch\\\/support\\\/wiki\\\/konfiguration-astra-mit-wintrunk\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.winet.ch\\\/support\\\/wiki\\\/konfiguration-astra-mit-wintrunk\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.winet.ch\\\/support\\\/wiki\\\/konfiguration-astra-mit-wintrunk\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.winet.ch\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Docs\",\"item\":\"https:\\\/\\\/www.winet.ch\\\/wiki-sgdnckyfnvgdfhye\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Konfiguration Astra mit winTrunk\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.winet.ch\\\/#website\",\"url\":\"https:\\\/\\\/www.winet.ch\\\/\",\"name\":\"Winet\",\"description\":\"The VoIP Professionals\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.winet.ch\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Configuring Astra with winTrunk - Winet","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.winet.ch\/en\/support\/wiki\/configuring-astra-with-wintrunk\/","og_locale":"en_US","og_type":"article","og_title":"Konfiguration Astra mit winTrunk","og_description":"Allgemein  AG Produktbezeichnung:                                                          winTrunk Codec \/ Framel\u00e4nge:                                                          G.711a \/ 20ms Fax:                                                                                     T.38 Protokoll 1) Registrierung der SIP-Konten:                                           Der Kommunikationsserver registriert ...","og_url":"https:\/\/www.winet.ch\/en\/support\/wiki\/configuring-astra-with-wintrunk\/","og_site_name":"Winet","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.winet.ch\/support\/wiki\/konfiguration-astra-mit-wintrunk\/","url":"https:\/\/www.winet.ch\/support\/wiki\/konfiguration-astra-mit-wintrunk\/","name":"Configuring Astra with winTrunk - Winet","isPartOf":{"@id":"https:\/\/www.winet.ch\/#website"},"datePublished":"2020-07-20T12:43:53+00:00","breadcrumb":{"@id":"https:\/\/www.winet.ch\/support\/wiki\/konfiguration-astra-mit-wintrunk\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.winet.ch\/support\/wiki\/konfiguration-astra-mit-wintrunk\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.winet.ch\/support\/wiki\/konfiguration-astra-mit-wintrunk\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.winet.ch\/"},{"@type":"ListItem","position":2,"name":"Docs","item":"https:\/\/www.winet.ch\/wiki-sgdnckyfnvgdfhye\/"},{"@type":"ListItem","position":3,"name":"Konfiguration Astra mit winTrunk"}]},{"@type":"WebSite","@id":"https:\/\/www.winet.ch\/#website","url":"https:\/\/www.winet.ch\/","name":"Winet","description":"The VoIP Professionals","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.winet.ch\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/docs\/3719","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/comments?post=3719"}],"version-history":[{"count":0,"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/docs\/3719\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/media?parent=3719"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/doc_category?post=3719"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.winet.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=3719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}