English (GB) Deutsch

Articles in this section

See more

SIP Provider PCH (AT)

Avatar
Swyx Info
  • Updated

General

The SIP Trunk from PCH was first tested and released with SwyxWare 11.25.0.0.

The SIP Trunk from PCH is a SIP Trunk with user authentication, i.e. you receive information on user ID, user name and password. The names may differ, or you may only receive a name or ID with password. In this case the user ID is identical to the user name when configuring the SIP trunk in SwyxWare.

The actual interoperability tests were performed by PCH, not by the Enreach TAP.

Platforms 

SwyxWare

The SIP Trunk from PCH can be used from SwyxWare 11.25.0.0 on.

SwyxON

The SIP Trunk from PCH is suitable for central connection in the data center.

Configuration 

When creating the SIP trunk group, select the profile 'PCH IT Solution GmbH - Taurus (AT)'.

SIP URIs

When creating the actual SIP trunk, a SIP URI must be entered after entering the phone number range so that incoming calls can be assigned. The assigned number block must be taken into account in the correct format.

Example
Number block: +43 51 9988776600 ... +43 51 9988776699
In this case, the SIP URI must be entered in the format 05199887766*@*.

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.

Session Timer

Since the PCH SIP trunk uses a higher session interval than the SwyxWare for calls, in the windows registry on the SwyxWare server under HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options two new DWORD values can be created named SipMinSessionTimerIntervalSeconds and SipSessionTimerIntervalSeconds assign the value 120 (decimal) to each of them. Finally, the LinkMgr service must be restarted.
Important: This setting affects all SIP trunks.


Tested Features 

  • Incoming/outgoing national calls
  • Correct Calling Line Identification (CLI) on national and calls
  • Holding and retrieving calls
  • Toggeling between two calls
  • Call transfer
  • Conferencing
  • Mutually supported codecs: G.711a/ G.711u/ G.729
  • Incoming/outgoing DTMF signaling in accordance with via SIP INFO
  • FAX transmission via G.711

Restrictions

None

Test date

01/10/2018 with SwyxWare 11.25.0.0
25/05/2020 with SwyxWare 12.00.0.0
19/09/2021 with SwyxWare 13.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. Swyx in no way guarantees the accuracy of this third-party contact information nor is responsible for it's content.

Related articles

Comments

0 comments

Please sign in to leave a comment.