The ecotel sipTrunk 2.0 was first tested and released with a SwyxWare 220.127.116.11.
The information published here applies exclusively to ecotel sipTrunk2.0, but not to sipAccount2.0.
The ecotel sipTrunk 2.0 is a SIP trunk with user authentication. You will receive information to register the SIP trunk and which SIP server has to be used.
The ecotel sipTrunk 2.0 can be used according to the settings listed below from SwyxWare 18.104.22.168 on.
The ecotel sipTrunk 2.0 is released for central connection in the data center.
ecotel has expanded its SIP infrastructure and has installed a geo-redundant system with nodes in Frankfurt and Düsseldorf. For new installations information about the node to be used should be available.
Since SwyxWare 12.40 there are profiles for the two nodes:
- ecotel DUS (DE)
which have to be selected accordingly.
For older SwyxWare installations the profile "ecotel sipTrunk 2.0 (DE)" has to be selected. Afterwards the entry "trunk3.sip-ecotel.de" has to be changed to "trunkf.sip-ecotel.de" for Frankfurt or to "trunkd.sip-ecotel.de" for Düsseldorf in the properties of the trunk group in the tab 'SIP', in the fields 'Registrar' and 'Proxy'.
Existing customers already using ecotel sipTrunk 2.0 will be informed by ecotel when to reconfigure and which server to use.
Important: After creation of the SIP trunkgroup, underneath the properties of the trunkgroup, in the field 'Realm' of the 'SIP' tab, the customer individual value has to entered. This value is named 'SIP Registrar/Domain/Realm' in the documents from ecotel, i.e. '12345678.sip-ecotel.de'.
In order to assign incoming calls to the correct trunk, it is necessary to configure a SIP URI for the trunk. The assigned number block and the numberformat must be considered.
Numberblock: +49 231 9988776600 ... +49 231 9988776699
In this case, the SIP URI must be configured in the format 04923199887766*@*.
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported codecs: G.711
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- Fax transmission via G.711
FAX transmission via T.38 is not supported
03/01/2018 with SwyxWare 11.10.1
20/01/2021 with SwyxWare 12.30
Verifying interoperability between different SIP providers and the Swyx solution is part of the Enreach Technology Alliance Programme (TAP) tasks. Due to different implementations of the SIP RFCs, it is necessary to determine and provide an individual configuration for each SIP provider.
Within the TAP, Enreach tests a large number of national and international SIP providers in order to make statements about the interoperability with the Swyx solution and the functional scope of the respective SIP trunk. These results and, if needed, configuration advice are published in Help Center articles.
Enreach is in close contact with selected SIP providers to ensure a quick troubleshooting in case of incompatibilities. In addition, tests are repeated at regular intervals to ensure consistent quality.
Despite regular retests it cannot be excluded that incompatibilities with the Swyx solution may occur due to changes in the SIP connection on the provider side or that the provided profile is no longer valid. After creating the trunk group or SIP trunk, the profile settings should be compared with the provider's information and adjusted accordingly in case of deviations.
However, should incompatibilities or problems occur with a tested SIP trunk, no claims for recourse against Enreach GmbH can be derived from this. In such cases, you can contact Enreach Support via your specialist dealer.
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.