Revision as of 07:43, 21 October 2016

VoIP Providers released for Unify SME Platforms > table

The connection of communication systems to the public network via SIP Trunking can be used instead of or in addition to traditional PSTN trunks. Many VoIP Providers, also known as ITSPs, are offering corresponding services. The following article gives an overview of the SIP trunking features and limitations and lists the Providers, which have been tested and released with the SME platform OpenScape Business.

You did not find your provider? Find out how to get it released!

Overview

OpenScape Business has been tested with a large number of Internet telephony providers that support SIP. Continuously new providers are tested, released and included within administration. As the SIP recommendations leave some room for interpretation, there are differences in the range of features supported with a specific provider. In this chapter general information is given which is valid for all SIP Providers.

SIP trunking features

Up to 8 active SIP providers and one Internet connection
Operation behind another router using STUN (can be configured per provider with current software) - integrated SBC functionality
SIP trunking with single numbers (MSN) and up to 30 SIP user accounts (called Internet telephony stations in WBM)
Direct Inward Dialing (DID)
Comprehensive feature set available e.g.
- CLIP
- Hold, Consultation, Toggle
- Transfer (attended, semi-attended)
- Ringing group, Call pickup
- Conference
- Call Forwarding
- DTMF transmission e.g. for voicemail access
Simultaneous VoIP connections depending on system and available DSL bandwidth, used Codec and system. G.711 needs up to 92 kbit/s, G.729A needs up to 36 kbit/s in both directions.
Automatic fallback to ISDN at SIP trunk failure
Voice Codecs G.711 and G.729
Fax over IP via T.38

Security Warning - Malicious attacks from the Internet may lead to reduced service quality or toll fraud!
Please strictly follow these basic rules:

Never open up the firewall in an internal or external router e.g. by forwarding port 5060.
The SME platforms take care of opening the firewall for traffic with the selected VoIP providers. Attacks from other internet addresses are therefore blocked. Opening up the router's firewall would invalidate this security measure.
Never configure SIP subscribers at a HiPath / OpenScape system without a strong password.
Authentication blocks registration of unauthorised SIP clients. See http://wiki.unify.com/wiki/Features_and_Configuration_of_SIP_Devices

The following changes have been made starting from OpenScape Business V1:

Enhanced SIP attack protection has been implemented. For diagnostics and SIP provider configuration hints see How to enable blocked SIP Providers.
STUN handling has been improved. STUN can now be configured per ITSP profile. If you were not using STUN for a provider (Global STUN mode is off), please verify that the profile flag "Use STUN" is disabled. If you were using STUN (Global STUN mode is other than off), then please verify that the flag "Use STUN" is enabled in the provider profile. For further information see the ITSP configuration guides at OpenScape Business.

General Requirements for VoIP

LAN with 10/100/1000 MBit/s and no more than 40% network load
Separate port on the switch or router for every component in the IP network (no hubs as concentrators)
Not more than 50 ms delay in one direction (One Way Delay); not more than 150 ms total delay
Not more than 3% packet loss and 20 ms jitter
Quality of Service (QoS) support - IEEE 802.p, DiffServ (RFC 2474) or ToS (RFC 791)
Sufficient WAN bandwidth (uplink and downlink) for intended simultaneous calls and CODEC
External modem, such as a DSL modem
Intermediate routers shall support quality of service and bandwidth control mechanisms if the WAN link is used for voice and data simultaneously. SIP messages have to be routed transparently.

For interworking with different network configurations and edge devices and how to use STUN please see Network Configuration for VoIP Providers.

Restrictions for all Providers

Special call numbers and emergency calls
- Special call numbers (e.g. 0800, 0900, 0137) or analog fax/modem connections are not supported by all SIP providers.
- Emergency call numbers (e.g. 110, 112) are not supported by all providers. These connections must be implemented via TDM trunks.
For DTMF transmission outband transport via RFC 2833/RFC4733 is highly recommended. The ITSP MUST support outband DTMF (RFC2833) if UC Suite functions via SIP trunk (e.g. auto attendant, voicemail control) shall be used.
For DTMF transmission inband transport may be used, but the functionality cannot be guaranteed as endpoints (e.g. UC-Suite) may not support inband DTMF.
For Fax transmission the T.38 protocol is highly recommended. From OpenScape Business V2R0.3 UC Suite is able to proceed T.38 and G.711 faxes as well.
If your provider does not support Fax T.38, Fax pass-through with G.711 is possible but transmission quality depends on network infrastructure in this case.
CLIP no screening (set a different number to be displayed at called party) is available in OpenScape Business from V1R3 with ITSPs in DID mode. More details in "OSBiz V1/V2 Configuration for ITSP".
In a network, a configured ITSP can be used at each respective node. From OpenScape Business V1R3 only one centralized ITSP in a network can be used.(with ITSP in DID mode)
An incoming ITSP call can be transferred or forwarded to another public subscriber via ITSP. Concatenation of such 'trombone scenarios' is not supported. So 2 lines (one incoming and one outgoing) are used while the call is active.

How to get a new VoIP provider released

Tests are necessary with every new provider before making installations in the field due to different implementations of the SIP protocol. Otherwise no support is available for an ITSP. Test resources have to be provided by the region or partner.

Select the VOIP / SIP trunking providers, which are most important for your business, estimate business relevance and get agreement for start of certification from product management.
Get the IP and SIP settings for the specific provider. Send the completed document "VoIP Provider Data Collection" to the VoIP Provider certification team. This is essential for correct PBX setup. The tables in chapter 2 have to be filled in.
VOIP provider data collection and test list - last update: 2016-10-14

--> Hint: Simplified and optimized test procedure from OSBiz V2.

Perform all tests in the VoIP provider test list from above, according to the instructions included. System configuration and tests require trained local personal. Remote support is available by the VoIP Provider certification team.
Deliver the test results, including all Wireshark traces and final provider data to the VoIP Provider certification team.
Prepare a Provider specific configuration guide, which will be published on this wiki page later on. An example-doc is included in the ZIP-file. Use English screenshots from OpenScape Business please. Explanations can be added in your language. e.g. German Provider in German language, French Provider in French language, International provider in English language... Deliver the document to the VoIP Provider certification team.

After successful tests the VoIP provider is released, and published on this page. Regular back level support is available for issues with the new provider after that. A preconfigured VoIP provider profile will be included in the OpenScape Business administration for easy setup.

General Information by platform

For discontinued platforms see Collaboration with VoIP Providers (discontinued platforms).

OpenScape Business

For common features and restrictions see overview
Concurrent calls via ITSP (depending on the available bandwidth and used Codec).
- 30 for OpenScape Business X1
- 60 for OpenScape Business X3 / X5 / X8
- 180 for OpenScape Business S
An external router is always necessary for OpenScape Business S, OpenScape Business X1 / X3 / X5 / X8 can optionally be operated with the bulit-in router / firewall.
Mobility Entry with DTMF call control is supported for OpenScape Business X1 / X3 / X5 / X8, S.
FAX over IP with T.38 is supported for analog Fax devices, terminal adapters and the OpenScape Business UC Suite.
*If your provider does not support Fax T.38, Fax pass-through with G.711 is possible but transmission quality depends on network infrastructure in this case.
From OpenScape Business V2R0.3 UC Suite is able to proceed T.38 and G.711 faxes as well.
A trunk prefix to select a SIP trunk as an alternate trunk can be used from the OpenScape Business client's dial box but not from client's directories and settings (myPortal, myAttendant, myAgent).
SIP trunks cannot be used for presence based call forwarding, if a TDM trunk is also present because of the limitation above.

.

General Configuration guides

.

OSBiz V1 Configuration for ITSP- latest update: 2014-12-17

OSBiz V2 Configuration for ITSP- latest update: 2016-01-15

HowTo-CLIPnoScreeningEng- latest update: 2015-10-26

HowTo-CLIPnoScreeningDeu- latest update: 2015-11-04

.

Specific configuration guides:

.

Vodafone IP-ALA-R3 Germany- latest update: 2016-01-25

BCOM Netherlands- latest update: 2016-03-21

Deutsche Telekom DIPVD- latest update: 2016-06-03

KCOM UK ITSP SIP Trunk Configuration- latest update: 2016-06-03

X2COM Netherlands- latest update: 2016-06-03

VozTelecom_Spain- latest update: 2016-08-07

FL1 Liechtenstein- latest update: 2016-04-14

OpenScape Business V2 Config ITSP BLU telecom- latest update: 2016-05-02

Deutsche Telekom ALL-IP SIP-Trunk- latest update: 2016-09-07

COSMOTE Greece- latest update: 2016-10-02

SIGNET telecom Netherlands- latest update: 2016-09-30

Tested VoIP Providers by Countries

The main SIP trunking functions of the SME platforms have been tested with the following Internet telephony providers. For detailed information see the document Overview about Released SIP Providers below.

= has been successfully tested by development or customer
DID = accounts for PBX-trunking / Direct Inward Dialling
MSN = accounts for single number(s)

International

VoIP Providers	Type	OpenScape Business
COLT	DID
Verizon	MSN / DID	AppNote OpenScape_Business_V1 with_Verizon_IP_Trunks ML 10052013 V05
Skype Connect	MSN

Please check provider home page for supported countries.
Skype Connect is a fee-based business service from Skype. It allows voice communication between Skype clients and office phones using the standard SIP trunking interface. Other Skype client features like chat or video are currently not supported.

Our SME Platforms have been officially certified by Skype. Skype Connect with SME platforms

Australia

VoIP Providers	Type	OpenScape Business
Engin	MSN
Internode	MSN
Commander Primus	MSN / DID
Telstra	MSN / DID

Austria

VoIP Providers	Type	OpenScape Business
UPC / inode	MSN
IP Austria / my Tweak	DID
/Kabelplus Business Phone	DID
/ LinzAG City Voice	DID
/ Neotel	DID
/ SalzburgAG CableLink	DID
/ Tele2	DID

Belgium

VoIP Providers	Type	OpenScape Business
Belgacom	DID
Belgacom IMS	MSN / DID
Destiny	MSN / DID
Hexacom	MSN / DID
Telenet	MSN / DID
WIN	MSN / DID

Brazil

VoIP Providers	Type	OpenScape Business
CTBC	DID
GVT	DID
Voitel	MSN

Canada

VoIP Providers	Type	OpenScape Business
BabyTEL	DID

Czech Republic

VoIP Providers	Type	OpenScape Business
GTS	DID
T-mobile	MSN / DID
O2	MSN / DID

Chile

VoIP Providers	Type	OpenScape Business
Entel NGN	MSN

Denmark

VoIP Providers	Type	OpenScape Business
Uni-tel A/S	MSN / DID
Global Connect	DID

Finland

VoIP Providers	Type	OpenScape Business
Elisa	DID
Länsilinkki	MSN
Telia-Sonera	DID
TDC	MSN / DID

France

VoIP Providers	Type	OpenScape Business
Acropolis Telecom	DID
MyStream	MSN / DID
OpenIP	DID
Paritel Operateur	MSN / DID
Completel	DID
Hexatel	DID
Sewan Communications	MSN / DID
Bouygues	MSN / DID

Germany

VoIP Providers	Type	OpenScape Business
1&1	MSN
Vodafone (formerly Arcor)	VoIP Anlagenanschluss (DID)
Vodafone	Vodafone Anlagenanschluss R3 (DID)
ennit AG(formerly tng)	DID / MSN
GMX (now 1&1)	MSN
Purtel	MSN
QSC	IPfonie extended (DID)
QSC	IPfonie extended Connect (DID)
sipgate	sipgate basic (MSN) sipgate trunking (DID)
toplink	MSN / DID
Deutsche Telekom	Telekom IP-As mit MSN
ecotel sipTrunk DDI	DID
ecotel sipTrunk Connect 1.0	DID
M-Net	DID
MK Netzdienste	DID
Peoplefone AG	DID
Equada	MSN / DID
HFO	MSN / DID
Deutsche Telekom	Telekom DeutschlandLAN SIP-Trunk

Italy

VoIP Providers	Type	OpenScape Business
Infracom (ex Multilink)	MSN
TWT	MSN / DID
Viatek	MSN / DID

Liechtenstein

VoIP Providers	Type	OpenScape Business
/ FL1 Telekom)	DID

Mexico

VoIP Providers	Type	OpenScape Business
Telefonica Mexico 1)	MSN

The Netherlands

VoIP Providers	Type	OpenScape Business
Infopact	MSN / DID
OneCentral	MSN / DID
OneXS	MSN / DID
Priority Telecom	MSN
RoutIT	DID
Speakup	MSN / DID
Tele2	MSN / DID
Vodafone NL	MSN / DID
Voiceworks	DID
Ziggo	DID
T-Mobile NL	MSN / DID
Motto Communications	MSN / DID
BCOM	DID
X2COM	DID
BLU	DID

New Zealand

VoIP Providers	Type	OpenScape Business
TelstraClear	MSN / DID
ORCON	MSN / DID

Portugal

VoIP Providers	Type	OpenScape Business
Portugal Telecom	DID

Serbia

VoIP Providers	Type	OpenScape Business
Telenor	DID

Slovakia

VoIP Providers	Type	OpenScape Business
Slovak Telekom	DID

Slovenia

VoIP Providers	Type	OpenScape Business
Amis	MSN
Detel	MSN
MegaM	MSN
tustelekom	DID
T-2	DID
Telemach	MSN

South Africa

VoIP Providers	Type	OpenScape Business
Nashua NCN	MSN / DID
Telfree	MSN / DID
Vodacom	MSN / DID

Spain

VoIP Providers	Type	OpenScape Business
LCR (Least Cost Routing)	MSN / DID
vozelia	MSN / DID
Xtra Telecom	MSN
Telecable	DID
VozTelecom	DID

Sweden

VoIP Providers	Type	OpenScape Business
Tele2	DID
Telia	MSN

Switzerland

VoIP Providers	Type	OpenScape Business
Cablecom	DID
efon	MSN / DID
sipcall	MSN
SofiCall	MSN
Sunrise	MSN / DID
Swisscom BCON	DID
vtx	DID
Telco Pack SA	DID
Peoplefone AG	DID
Swisscom Smart Business Communication	DID
Swisscom VoIP Gate	DID
Swisscom Enterprise SIP	DID

United Kingdom

VoIP Providers	Type	OpenScape Business
BT IPVS	MSN / DID
Gamma	DID
HIPCOM	MSN / DID
Opal	DID
Voiceflex	DID
VoIP Ltd i-Line	MSN / DID
tIPicall	DID
TalkTalk	N.A.
KCOM	DID

United States of America

VoIP Providers	Type	OpenScape Business
AT&T	DID OSO_ATT SipTrk Configuration Note 07092013 V1
Cbeyond	MSN
CenturyLink	DID
Sotel	MSN / DID
Windstream (Broadsoft platform only)	MSN / DID
XO	MSN / DID
Intermedia	DID

1) For this ITSP no profile is provided in the system.

Released SIP Providers in Detail

The table above shows the ITSPs that passed successfully a connectivity test. More details about test results, supported features and restrictions for a specific ITSP are listed in following PDF document.

Overview about Released SIP Providers Latest update: 2016-10-17

The following scenarios are covered within the connectivity test:

Registration
Basic Calls from / to ITSP
Feature Tests
- Consultation, transfer, toggle, conference
- Call Pickup / ringing group scenarios
- call forwarding scenarios
- DTMF
- CLIP / CLIR
- COLP / COLR
- FAX
Special Tests
- emergency calls
- service calls
- long duration calls
Calls handled via UC application

The connectivity tests are performed using various endpoints (for details see test list).

Frequently asked Questions

VoIP Provider FAQ - answers to frequently asked questions

External Links

Partner Portal (login required, Internet Explorer only)
VoIP Anbieter (Übersicht, Feature, Vergleiche)

@@ Line 142: / Line 142: @@
 ==={{File-DL|VozTelecom_Spain|pdf}}- latest update: 2016-08-07 ===
-==={{File-DL|Anleitung_FL1|pdf}}- latest update: 2016-04-14 ===
+==={{File-DL|FL1 Liechtenstein|pdf}}- latest update: 2016-04-14 ===
 ==={{File-DL|OpenScape Business V2 Config ITSP BLU telecom|pdf}}- latest update: 2016-05-02 ===

Views

Difference between revisions of "Collaboration with VoIP Providers"

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.