General
The SIP Trunk from Brennercom was first tested and released with a SwyxWare 12.30.
The SIP Trunk from Brennercom is a SIP Trunk with user authentication, i.e. you receive information about user ID, user name and password from Brennercom. The names may differ, or you will only receive a name or ID with password. In this case the user ID is identical with the user name when configuring the SIP Trunk in SwyxWare.
The actual interoperability tests were carried out by our partner ACS, not by Enreach TAP.
Platforms
SwyxWare
The SIP Trunk from Brennercom can be used without restrictions from SwyxWare 12.30. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.
SwyxON
The SIP Trunk from Brennercom is not released for central connection in the data center.
Configuration
During creation of the SIP trunk group, profile 'Brennercom-Pub (IT)' must be selected. 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.
SIP URIs
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.
Example:
Numberblock: +39 047109988776600 ... +39 047109988776699
In this case, the SIP URI must be entered in the format +39 0471099887766*@*.
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.
Tested Features
- Incoming/Outgoing Calls National
- Incoming/outgoing calls international
- Correct call number signaling national/international
- CLIP No Screening according to RFC3325
- Hold and resume calls
- Toggle between two calls
- Call transfer
- Conference
- Mutually supported codecs: G.711a, G711u, G.729
- Incoming/outgoing DTMF signaling via RFC2833
- Fax transmission via G.711
Restictions
None
Tests
02/06/2012 with SwyxWare 12.30
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.
Comments
0 comments
Please sign in to leave a comment.