Collaboration with VoIP Providers

You are here:

Home  Communications Systems  Collaboration with VoIP Providers

File:VoIP Provider SME.jpg

VoIP Providers released for Unify SME Platforms > table

Collaboration with VoIP Providers (also known as ITSP) via SIP Trunking is an important topic in the todays world of IP Voice/Data Communication. The following information will give an overview of the supported VoIP Providers in the different countries as well as additional considerations and hints regarding the SME platforms.

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

Overview

The SME platforms have 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 platforms and all SIP Providers.

SIP trunking features for all SME platforms

• up to 4 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)
• most important features available
  • CLIP
  • Hold, Consultation, Toggle
  • Transfer (attended, semi-attended)
  • Ringing group, Call pickup
  • Conference
  • Call Forwarding
  • DTMF transmission e.g. for voicemail access
• large number of simultaneous VoIP connections depending on 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 (or G.711)
  

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   SIP Endpoint Configuration

The following changes have been made starting from HiPath 3000 V9 and OpenScape Office V3R2: 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 HiPath 3000 or OpenScape Office.

The SME platforms with SIP Stack 4.0.26 have been validated with the BroadWorks SIP Interface. BroadWorks is the Carrier VoIP solution from Broadsoft, the global market leader. The tested SIP Stack is used in the current system versions Hipath 3000 V8 and OpenScape Office V3 as well.   Broadsoft Validation

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 and SME Platforms

• 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 many providers. These connections must be implemented via S0 access (administration default).
• DTMF is supported outbound via RFC 2833 or inband. The ITSP has to support outband DTMF (RFC2833) for using the OpenScape Office Autoattendant via SIP trunk.
• For Fax transmission the T.38 protocol is highly recommended. Fax pass-through using codec G.711 has been found much less reliable in most SIP provider environments. If your provider does not yet support Fax T.38, Fax pass-through with G.711 is possible but there is no warranty or further support. Fax communication with OpenScape Office application is only possible via Fax T.38.
• Other media types besides audio (voice and voice band data) and image (fax) are not supported.
• CLIP no screening (set a different number to be displayed at called party) is not available with our platforms for SIP trunks. Please check with your ITSP, if this can be accomplished at the provider side.
• In an OpenScape Office LX / MX / HiPath 3000 network, a configured ITSP can only be used at each respective node not network-wide.

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.

1. 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.
2. 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 - last update: 2012-07-01
3. Perform all tests in the VoIP provider test list, according to the instructions included. System configuration and tests require trained local personal. Remote support is available by the VoIP Provider certification team. Leading switch should be the OpenScape Office MX. After that, a reduced delta test list can be used for HiPath 3000.   VOIP provider test list and configuration - last update: 2012-08-02
4. Deliver the test results, including all Wireshark traces and final provider data to the VoIP Provider cerification 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 HiPath / OpenScape Office administration for easy setup.

General Information by platform

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

HiPath 3000

Valid for HiPath 3000 V9 with HG 1500.

SIP Trunking features

• For common features and restrictions see overview
• An external router is always necessary
• Maximum 32 concurrent calls between IP phones and ITSP (depending on the available bandwidth and used Codec). For TDM devices (analog, ISDN) 1 B-channel at HG 1500 has to be available for each concurrent call (gateway call).
• SIP trunks can not be used for dialing through or direct inward system access with DTMF tones e.g for the feature Mobility Entry. Please use a TDM line for those features.
• For OpenScape Office HX related features Fax via application, trunk prefix use and presence based forwarding see below.

Configuration

HiPath 3000 Configuration Guide for Internet Telephony:

•   HiPath 3000 Config Guide ITSP

See also:

• How to configure CLIP sent via SIP trunk / ITSP

OpenScape Office

Valid for OpenScape Office V3 LX / MX / HX.

SIP Trunking features

• All features, requirements and restrictions listed in overview are valid.
• Up to 32 simultaneous calls via SIP trunking for OpenScape Office MX (depending on available DSL bandwidth and used Codec)
• Up to 128 simultaneous calls via SIP trunking for OpenScape Office LX (depending on available DSL bandwidth and used Codec)
• An external router is always necessary for OpenScape Office LX, OpenScape Office MX can optionally be operated with the bulit-in router / firewall.
• SIP trunks cannot be used for dialing through or direct inward system access with DTMF tones e.g. for the feature Mobility Entry. Please use a TDM line for those features. Starting from OpenScape Office V3, myPortal for Mobile supports comprehensive control and UC functionality.
• FAX over IP with T.38 is supported for analog Fax devices, terminal adapters and the OpenScape Office application. Fax via G.711 is not supported with the application.
• A trunk prefix to select a SIP trunk as an alternate trunk can be used from the OpenScape Office 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.

Configuration

OpenScape Office Configuration Guide for Internet Telephony:

•   OpenScape Office Config Guide ITSP

See also:

• How to enter SIP Provider Account Data
  
• How to configure CLIP sent via SIP trunk / ITSP

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 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	HiPath 3000	OpenScape Office
COLT	DID
Skype Connect   3)	MSN

• Please check provider home page for supported countries.
  
• Skype Connect (former name Skype for SIP) 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	HiPath 3000	OpenScape Office
Engin	MSN
Internode	MSN

Austria

VoIP Providers	Type	HiPath 3000	OpenScape Office
UPC / inode   3)	MSN		-
IP Austria / my Tweak   3)	DID

Belgium

VoIP Providers	Type	HiPath 3000	OpenScape Office
Belgacom   3)	DID
Belgacom IMS   3)	MSN DID		*) *)
Destiny	MSN DID
Hexacom   3)	MSN DID		-
Telenet	MSN DID
WIN   3)	MSN DID		*) *)

 *) Platform released, OpenScape Office application test pending

Brazil

VoIP Providers	Type	HiPath 3000	OpenScape Office
CTBC   1)	DID		-
GVT   1)	DID
Voitel	MSN	-

Czech Republic

VoIP Providers	Type	HiPath 3000	OpenScape Office
GTS	DID
T-mobile	MSN DID
Telefonica O2	MSN DID

Chile

VoIP Providers	Type	HiPath 3000	OpenScape Office
Entel NGN	MSN		-

Denmark

VoIP Providers	Type	HiPath 3000	OpenScape Office
Uni-tel A/S	MSN DID

Finland

VoIP Providers	Type	HiPath 3000	OpenScape Office
Elisa   3)	DID		-
Länsilinkki	MSN	-
Telia-Sonera	DID
TDC	MSN DID

France

VoIP Providers	Type	HiPath 3000	OpenScape Office
Acropolis Telecom   3)	DID	-
OpenIP   3)	DID	-
Paritel Operateur	MSN DID

Germany

VoIP Providers	Type	HiPath 3000	OpenScape Office
1&1   3)	MSN		-
Vodafone (formerly Arcor)   3)	VoIP Anlagenanschluss (DID)
ennit AG(formerly tng)	DID / MSN
GMX (now 1&1)   3)	MSN		-
Purtel   3)	MSN		-
QSC	IPfonie extended (DID)
sipgate   3)	sipgate basic (MSN) sipgate trunking (DID)
toplink   3)	MSN DID

Italy

VoIP Providers	Type	HiPath 3000	OpenScape Office
Infracom (ex Multilink)   3)	MSN		-
TWT	MSN DID	-
Viatek	MSN DID

Mexico

VoIP Providers	Type	HiPath 3000	OpenScape Office
Telefonica Mexico   1)	MSN	-

The Netherlands

VoIP Providers	Type	HiPath 3000	OpenScape Office
Infopact   3)	MSN DID		-
OneCentral   3)	MSN DID
OneXS	MSN DID
Priority Telecom   3)	MSN
RoutIT	DID
Speakup   3)	MSN DID
Tele2	MSN DID
Vodafone NL	MSN DID
Voiceworks   3)	DID

New Zealand

VoIP Providers	Type	HiPath 3000	OpenScape Office
TelstraClear   3)	MSN DID

Portugal

VoIP Providers	Type	HiPath 3000	OpenScape Office
Portugal Telecom	DID

Slovakia

VoIP Providers	Type	HiPath 3000	OpenScape Office
Slovak Telekom   3)	DID

Slovenia

VoIP Providers	Type	HiPath 3000	OpenScape Office
Amis   3)	MSN
Detel   3)	MSN
MegaM   3)	MSN
tustelekom   3)	DID
T-2   3)	DID	-
Telemach   3)	MSN

South Africa

VoIP Providers	Type	HiPath 3000	OpenScape Office
Nashua ECN	MSN DID
Telfree   3)	MSN DID	-
Vodacom	MSN DID

Spain

VoIP Providers	Type	HiPath 3000	OpenScape Office
LCR (Least Cost Routing)	MSN DID
vozelia   3)	MSN DID		-
Xtra Telecom   3)	MSN

Sweden

VoIP Providers	Type	HiPath 3000	OpenScape Office
Tele2   3)	DID
Telia   3)	MSN

Switzerland

VoIP Providers	Type	HiPath 3000	OpenScape Office
Cablecom	DID
sipcall	MSN	-
SofiCall   3)	MSN	-
vtx   3)	DID

United Kingdom

VoIP Providers	Type	HiPath 3000	OpenScape Office
BT IPVS	MSN DID
Gamma   3)	DID
HIPCOM	MSN DID
Opal   3)	DID
Voiceflex   3)	DID

United States of America

VoIP Providers	Type	HiPath 3000	OpenScape Office
Cbeyond   3)	MSN		-
CenturyLink   2)	DID		-
Sotel   3)	MSN DID	-
Windstream   3)	MSN DID
XO   1)	MSN DID	-

1) Access parameters depend on the region within the country. If no default provider profile is supplied within administration, please use "create profile" for configuration.
2) No fixed servers (manual config needed), two profiles with different server addresses and identical accounts and MSN shall be used.
3) ITSP does not support Fax T.38. Fax communication with OpenScape Office application is not possible. Other Fax over IP communication may be unreliable.

Released SIP Providers in Detail

The table provided here shows the ITSP providers that were successfully checked in a connectivity test. More details about test results are given in the pdf-file Overview of released SIP providers below. Informations concerning CLIP, CLIR, COLP etc. are listed, restrictions may be reported as well.

•   Overview of released SIP providers Latest update: 2012-12-20

Connectivity Test Information

The connectivity test is carried out with

• HiPath 3000
• OpenScape Office MX/LX

Tests are done for MSN- and DID-account (as long as the provider´s realm is different), also the platforms are checked as NAT router and / or behind a router.

Several test scenarios are clustered in the test list, main issues are:

• 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

The connectivity tests are performed using the following endpoints:

• Analogue
• ISDN
• HFA-phones
• UP0 phones
• SIP-phones
• AP 1120 HFA / SIP
• optiClient 130 HFA
• WLAN2-phones HFA / SIP

At least 3 different types of phones are used for each test case.

Frequently asked Questions

• VoIP Provider FAQ - answers to frequently asked questions

External Links

• Siemens Enterprise Business Area Partner Portal (login required, Internet Explorer only)
•   VoIP Anbieter (Übersicht, Feature, Vergleiche)