General
The SIP Trunk from M-net was first tested and released with a SwyxWare 2015 R40.
This article refers to a SIP Trunk of the domain business.mnet-voip.de.
M-net is offering a SIP trunk with user authentication. You have received information about UserID, UserName and UserPassword, whereas the naming may differ, or you might have only received UserName and -password. In this case, UserID and UserName are identical.
The actual interoperability tests were executed by M-net itself, not by the Enreach TAP.
Platforms
SwyxWare
The SIP Trunk from M-net can be used according to the settings listed below from SwyxWare 2015 R40 on. If you use an earlier version of SwyxWare, incompatibilities cannot be excluded and you are responsible for your own usage.
SwyxON
The SIP Trunk of M-net is released for central connection in the data center from SwyxWare 13.26.
Configuration
During creation of the SIP trunk group, profile 'M-net (DE)' must 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.
In this case, the SIP URI must be entered in the format +4989123456*@*.
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 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
- Conferencing
- Mutually supported codecs: G.722/ G.711a/ G.711u/ G.729
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- FAX transmission via G.711a
Restrictions
None
Tests
28/08/2017 with SwyxWare 2015 R40.3.0
15/02/2022 with SwyxWare 13.00
24/04/2023 with SwyxWare 13.26
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.