General
The easybell 'Business' trunk was first tested an released with a SwyxWare 2015 R40.3.0.
The easybell 'Business' trunk is a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the nameing may differ, or you have only received UserName and -password. In this case, UserID and UserName are identical.
Platforms
SwyxWare
The SIP Trunk from easybell can be used from SwyxWare 2015 R40.3.0 on.
IMPORTANT Due to an incompatibility in the area of number suppression, older SwyxWare versions may be blacklisted on the easybell side. This blocks the SwyxWare connection to the easybell SIP trunk for a certain period of time and outgoing and incoming public calls are not possible. At least SwyxWare 13.27 is required to avoid this blacklisting. |
SwyxON
The SIP Trunk from easybell is released for central connection in the data center.
easybell web-portal configuration
For user related signalling of phone numbers underneath "Phone Settings | Manage numbers" it is necessary to set the attributes of the SIP trunk for option "Calling line identification" to "P-Preferred-Identity".
Configuration
During creation of the SIP Trunkgroup, profile 'easybell (DE)' has to be selected.
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.
Numberblock: +49 40 1234560 ... +49 40 1234569
In this case, the SIP URI must be entered in the format 4940123456*@*.
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 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 national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Conferencing
- Mutually supported codec: G.711a
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711
Restrictions
None
Test dates
06/06/2017 with SwyxWare 2015 R40.3.0
20/02/2019 with SwyxWare 11.38.0.0
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.