SIP Provider UPC Cablecom (CH)

General

The registerless SIP Trunk from UPC Cablecom was first tested and released with a SwyxWare2013 R3.

UPC Cablecom is offering a registerless SIP trunk. This means that the authentication is based on the public IP address of the SwyxWare server. Therefore, you need a static, public IP address from your ISP assigned to the SwyxWare server.

Information about the SIP Trunk from UPC Cablecom with regsitration can be found here: SIP Provider UPC Cablecom, Registered (CH)

Platforms

SwyxWare

The registerless SIP Trunk from UPC Cablecom can be used according to the settings listed below from SwyxWare2013 R3 on.

SwyxON

The registerless SIP Trunk from UPC Cablecom is not released for central connection in the data center.

Configuration

During creation of the SIP trunk group, profile 'UPC CableCom (CH)' must be selected.

UPC Cablecom is operating with a number of different servers. Therefore it is not possible to preconfigure the Proxy Server addresses in the 'SIP' tab of the Trunkgroup properties dialog. In this field, the server names or IP addresses that UPC Cablecom has specified, must be filled.

Session-Interval

UPC Cablecom expects a Session interval of 1800 (seconds) on outbound calls. The prevent reINVITES which would slow down the call establishment, two new DWORD values underneath HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options can be created named SipSessionTimerIntervalSeconds and SipMinSessionTimerIntervalSeconds and assigned a value of 1800 (decimal). After creating these values, the LinkMgr service must be restarted.

Important: These settings will affect all SIP trunks.

• Incoming/outgoing national calls
• Incoming/outgoing international calls
• Correct Calling Line Identificaion (CLI) on national and international calls
• CLIP No Screening
• Holding and retrieving calls
• Toggeling between two calls
• Call transfer
• Conferencing
• Mutually supported audio codec: G.711a/ G.711u/ G.729
• Incoming/outgoing DTMF signaling via RFC2833
• FAX transmission via T38

Restrictions

Tests

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.