The SIP trunk of NetCom BW was first tested and released with SwyxWare 188.8.131.52.
The actual connection to the SIP trunk of NetCom BW is made via a separate SBC. SwyxWare itself connects to the SBC via a registerless SIP trunk. The static, local IP address of the SBC is required for configuration. The SBC must be configured to address port 65002 of SwyxWare Server as SIP endpoint and not the default SIP port 5060.
The actual interoperability tests were performed by NetCom BW itself, not by the Enreach TAP.
The SIP Trunk of NetCom BW can be used without restrictions from SwyxWare 184.108.40.206 on.
The SIP Trunk of NetCom BW is not released for central connection in the data center.
When creating the SIP trunk group, select the profile'NetCom BW (DE)'.
Because of the connection to the SBC it is not possible to pre-assign the entry for the registrar / proxy server in the "SIP" tab in the properties of the trunk group. The IP address of the SBC must be entered here after the trunk group has been created.
During creation of the actual trunk, in the codec configuration dialog, T.38 has to be deselected as supported codec. This step could also be performed afterwards in the properties of the SIP trunk, underneath the 'Codecs' tab.
- 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
- Mutually supported codecs: G.711a
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711
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.