General
The Business-SIP Trunk from Virtual-Call is available in the following countries:
- Brazil
- Germany
- Austria
- Switzerland
- Spain
- UK
The Business-SIP Trunk from Virtual-Call was first tested and released with SwyxWare 14.00.
Virtual-Call offers a SIP trunk with user authentication, i.e. you receive information on UserID, UserName and UserPassword from Virtual-Call, whereby the designations can also differ, or you only receive the user name and password. In this case, the UserID is identical to the UserName.
Virtual-Call has its own profile for the SwyxWare. It is therefore important to inform Virtual-Call when ordering that a SwyxWare will connect to the Business SIP Trunk.
Platforms
SwyxWare
The Business-SIP Trunk of Virtual-Call can be used in the above-mentioned countries according to the settings listed below from SwyxWare 14.00. If an earlier version of SwyxWare is used, incompatibilities cannot be ruled out and use is at your own risk.
SwyxON
The Business-SIP Trunk of Virtual-Call is released for central connection for SwyxON.
Configuration
During creation of the SIP trunk group, profile 'Virtual-Call' must be selected. This profile is valid for all the above-mentioned countries.
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
In the codec dialog for FAX transmission via T.38 the two options "Remove T.38 codec from initial invite" and "Prohibit T.38 reinvite by sender" must be activated.
CLIP No Screening
The feature CLIP No Screening needs to be ordered from Virtual-Call.
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 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
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- Fax transmission via T.38
Restrictions
None
Test date
14/06/2024 with SwyxWare 14.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. Enreach in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.
Comments
0 comments
Article is closed for comments.