General
The IPfonie Extended Connect SIP trunk from Plusnet was first tested and released as QSC IPfonie Extended Connect with a SwyxWare 2015.
The IPfonie Extended Connect SIP trunk is 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 IPfonie Extended Connect SIP Trunk from Plusnet is compatible with the SIPConnect1.1 and BITKOM recommendations about SIP trunking. Additionally, it is possible to handle several number ranges with different area codes.
The IPfonie Extended Connect SIP trunk supports encryption of payload and signaling data. This feature is an additional option when ordering the SIP trunk and is first released for SwyxWare 11.
Update:
By the latest 27.07.2019 it is necessary to have the DigiCert Global Root G2 installed in the certificate store of the SwyxWare server. Additional information, download links and installation instructions can be found in the PDF file at the end of this article.
Platforms
SwyxWare
The IPfonie Extended Connect SIP Trunk from Plusnet can be used from SwyxWare 2015 on.
SwyxON
The IPfonie Extended Connect SIP Trunk from Plusnet (without TLS) is suitable for central connection in the data center.
Important: The IPfonie Extended Connect SIP Trunk from Plusnet with encryption (TLS) is not yet supported for SwyxON!
Configuration
Even though the SIP trunk is able to handle several different area codes, it is only necessary to create one location within the SwyxWare.
During creation of the SIP trunk group, the profile 'Plusnet SIPconnect R (DE)' must be selected. If the SIP trunk with encryption wants to be used, the profile 'Plusnet SIPconnect R TLS (DE)' has to be selected.
If the SIP trunk with encryption shall be used, during the initial creation of the SIP trunk in the codec settings, it is necessary to deactivate T.38 as supported codec, since T.38 cannot be encrypted. The T.38 codec can also be deactivated after creating the SIP trunk.
The newly created location must be configured to a new user to be created, even if the assigned public number does not match that location.
Tested Features
- Incoming/outgoing national calls
- Incoming/outgoing international calls
- Correct Calling Line Identification (CLI) on national and international calls
- CLIP No Screening in accordance with the description above
- Holding and retrieving calls
- Toggeling between two calls
- Call transfer
- Call forwarding
- Conferencing
- Mutually supported codecs:
- G.722
- G.711a
- G.711µ
- G.729
- T.38 for FAX negotiation
- Incoming/outgoing DTMF signaling in accordance with via RFC2833
- T.38 Negotiation and FAX transmission (unencrypted only)
- Encryption of speech and signalling data
Restrictions
None
Test date
14/05/2024 with SwyxWare 14.00
05/10/2017 with SwyxWare 11 with encryption (QSC IPfonie Extended Connect)
14/09/2017 with SwyxWare 11 without encryption (QSC IPfonie Extended Connect)
05/11/2014 with SwyxWare2015 (QSC IPfonie Extended Connect)
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.