SIP Provider O2 All-IP Voice SIP (DE)

General

The All-IP Voice SIP Trunk from O2 was first tested and released with SwyxWare 11.40.0.0.

The All-IP Voice SIP Trunk from O2 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 connection to the All-IP Voice SIP Trunk from O2 can only be made via an Internet connection from O2. For this purpose, the customer receives an Internet router that is integrated into the customer's network (OneAccess Gateway). SwyxWare uses this Internet router as a SIP proxy to connect to the All-IP Voice SIP Trunk from O2. The Internet router provides the Internet connection (data line) via Ethernet ports 0/2 and 03, the voice connection is provided via Ethernet ports 0/0 and 0/1. Additional information can be found in the attached document from O2 (in German only).

If the SwyxWare server has to use both connections, it needs a second network card.

Platforms

SwyxWare

The All-IP Voice SIP Trunk from O2 can be used from SwyxWare 11.40.0.0 on. When using an earlier version of SwyxWare incompatibilities cannot be excluded and use is at your own risk.

SwyxON

The All-IP Voice SIP Trunk from O2 is not suitable for central connection in the data center.

Configuration

SwyxWare Server

The SwyxWare Server is equipped with two network cards.

Network configuration

Network card 1: Data, connected to OneAccessPorts 0/2 or 0/3.
IP-Address, Subnetmask, Default-Gateway, DNS Server according to the ordinary data network or via DHCP respectively.
Network card 2: Voice, connected to OneAccessPorts 0/0 or 0/1.
- IP-Addresse from the Voice network of the OneAccess Gateway, e.g. 192.168.222.2
- Subnetmask: 255.255.255.248
- GW: empty
- DNS: empty

The LinkManager must use network card 2 for the voice connections. A new registration key must be created for this purpose:

Path: HKLM\Software\Wow6432Node\Swyx\LinkManager\CurrentVersion\Options.
Name: SipLocalInterface
Type: REG_SZ
Value: The assigned IP address of network card 2, e.g. 192.168.222.2

When creating the SIP trunk group, select the profile 'O2 All-IP Voice SIP (DE)'.

By using a customer-specific router, it is not possible to preset the entry for the Registrar / Proxy server in the "SIP" tab under the properties of the trunk group. The corresponding voice IP address of the OneAccess gateway must configured for Registrar and Proxy, with port 5060.

Session Interval

O2 requires a session interval of at least 1800 seconds for outgoing calls. In the case of a smaller session interval, a corresponding call is rejected. To adjust the default interval of 90 seconds, create the following two registry keys and set them to 1800.

Path (64-bit): HKLM\Software\Wow6432Node\Swyx\LinkMgr\CurrentVersion\Options
- Name1: SipMinSessionTimerIntervalSeconds
- Type1: DWORD
- Value1: 1800 (decimal)
- Name2: SipSessionTimerIntervalSeconds
- Type2: DWORD
- Value: 1800 (decimal)

After creating the registry keys, the 'LinkMgr' service must be restarted.

Important: This setting affects all SIP trunks.

Codec Configuration

For FAX transmission it is necessary to select the option "Remove T.38 from first negotiation (SIP INVITE)" via the tab "Codecs/Channels" of the properties of the created SIP trunk.

Tested Features

Incoming/outgoing national /international calls
Correct Calling Line Identification (CLI) on national / intenational calls
CLIP No Screening national
Holding and retrieving calls
Toggeling between two calls
Call transfer
Call forwarding
Conferencing
Mutually supported codecs: G.711a/ G.711u/ G.729
Incoming/outgoing DTMF signaling in accordance with via RFC2833
FAX transmission via T.38/G.711

Restrictions

None

Test date

15/04/2019 with SwyxWare 11.40.0.0

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.

Telefonica_All-IP_SIP-Trunk_Beschreibung_v1.7.pdf800 KB