SIP Provider net-cloud (AT) (kb5151)

The information in this article applies to:

  • SwyxWare 11.00

[ Summary | Information | Links ]


Information und configuration hints for SIP provider net-cloud (Austria).


General information

The SIP trunk of net-cloud was first tested and released with SwyxWare

The SIP trunk of net-cloud is a SIP trunk with user authentication, i.e. you get information about user ID, user name and password from net-cloud. The names may differ, or you will only receive a name or ID with password. In this case the user ID is identical to the user name when configuring the SIP trunk in SwyxWare.

The actual interoperability tests were performed by net-cloud itself, not by Swyx.


SwyxWare: The SIP Trunk of net-cloud can be used without restrictions from SwyxWare on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.

SwyxON: The SIP Trunk of net-cloud is suitable for central connection in the data center.


When creating the SIP trunk group, select the profile 'net-cloud (AT)'. If the profile is not included in the corresponding list, you can download the required CustomProviderProfiles.config for SwyxWare at the end of this article. For more information about using this file, see Configuration and Adaptation of SIP Providers via Provider Profiles (kb3436).

When creating the actual SIP trunk, a SIP URI must be entered after entering the phone number range so that incoming calls can be assigned. The assigned number block must be taken into account in the correct format.

Number block: +43 1239988776600 ... +43 1239988776699
In this case, the SIP URI must be entered in the format 4312399887766*@*.

When creating the actual SIP trunk, all audio codecs except G.711 can be deselected  in the codec dialog.
For FAX transmission it is necessary to select the option "Remove T.38 from first negotiation (SIP INVITE)" via the tab "Codecs/Channels" of the properties of the created SIP trunk.

Tested Features
  • Incoming/outgoing national calls
  • Correct Calling Line Identification (CLI) on national and calls
  • CLIP No Screening in accordance with RFC3325
  • Holding and retrieving calls
  • Toggeling between two calls
  • Call transfer
  • Conferencing
  • Mutually supported codecs:
    • G.711a
    • T.38
  • Incoming/outgoing DTMF signaling in accordance with via RFC2833
  • FAX transmission via T.38

Restrictions: -

Test date
11/07/2018 with SwyxWare

Overview of tested SIP provider


As far as software supplied or used by us, includes open source elements the additional terms under apply in addition. An overview which products from the Swyx portfolio include open source elements and which open source license is relevant can be found under

The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.


Comment on this article

If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.