SIP Provider BITel (DE)

General

When ordering a SIP Trunk from BITel, an AudioCodes SBC as the actual remote station for the SwyxWare is delivered by BITel. The configuration of the AudioCodes SBC is aligned by BITel to the SwyxWare and to the SIP Trunk of BITel.

The actual interoperability testing was done by Awacon Solutions, not by the Enreach TAP.

Platforms

SwyxWare

The SIP Trunk from BITel can be used without restrictions starting with a SwyxWare 13.00. If an earlier version of SwyxWare is used, incompatibilities cannot be ruled out and use is at your own risk.

SwyxON

Due to the dependency on the locally installed AudioCodes SBC, the SIP Trunk from BITel cannot be used for direct termination of SwyxON installations.

Configuration

When creating the SIP Trunk group, the profile 'BITel (DE)' has to be selected. If the profile is not included in the corresponding list, the required CustomProviderProfiles.config for SwyxWare is available for download at the end of this article. For more information about using this file, see Configuration and Adaptation of SIP Providers via Provider Profiles.

Codec Configuration

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.

CLIP No Screening

To activate the feature CLIP No screening in the SwyxWare, it is necessary to set the option "Always use originator's number" in the tab "Number signalling" of the SIP trunk settings.

Tested features

• Incoming/outgoing calls national
• Incoming/outgoing calls international
• Correct caller number signaling National/International
• CLIP No Screening
• Hold and resume calls
• Toggle between two calls
• Call transfer
• Conference
• Commonly supported codec:
  • G.711a
• Incoming/outgoing DTMF signaling via RFC2833
• FAX transmission via G.711

Restrictions

None

Tests

12/09/2022 with SwyxWare 13.00

Disclaimer

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.