The SIP trunk from AXXESS was first tested an released with SwyxWare 2015 R30.5.
- With a direct connection to the network of <Providername>, the SIP messages of the proxy must be sent to port 65002 of the SwyxWare Server. The network infrastructure has to be adopted accordingly.
- When using a gateway with an Internet connection with static IP address, a port forwarding rule from public port 5060 to port 65002 of SwyxServer has to be configured on the gateway.
The actual interoperability tests were performed by AXXESS, not by the Swyx TAP.
The SIP Trunk of AXXESS can be used without restrictions from SwyxWare 2015 R30.5 on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.
Because of the dependency of the static public IP address, the SIP Trunk from AXXESS is not suitable for direct termination in a datacenter.
During creation of the SIP Trunkgroup, profile 'AXS SIP-Trunk' has to be selected.
AXXESS is operating with individual proxies per customer. Therefore it is not possible to preconfigure the Proxy Server in the "SIP" tab of the Trunkgroup Properties dialog. In field of Proxy Server, please enter the server name or IP address provided by AXXESS.
For FAX transmission it is necessary to select the the option "Remove T.38 codec from initial invite" in the properties of the created SIP trunk underneath the tab "Codecs/Channel".
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening in accordance with RFC3325
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Mutually supported codecs: G.711a/ G.711µ/ T.38 for FAX negotiation
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T.38 Negotiation and FAX transmission
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.
Please sign in to leave a comment.