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.
|
You are here: |
 Home Communications Systems Collaboration with VoIP Providers
|
|
29.09.2024 - general editorial updates on configuration guides |
|
05.07.2024 - V3R3.2: new certifications and configuration descriptions available |
| Date | Summary | |
|---|---|---|
| 03.12.2024 |
|
herweck callamar, Virtual-Call |
|
Vodafone Anlagenanschluss R6 | |
| 05.07.2024 |
|
Net4You-Voice4Biz |
|
EWE Voice+ SIP Trunk, M-net Premium SIP-Trunk, Universe SIP Connect | |
|
Swisscom Smart Business Communication | |
|
HFO Telecom NGN, Skype for Business, Swisscom BCON, Swisscom VoipGate | |
| 11.03.2024 |
|
BITel Business SIP Flex, Gamma NGN (DE), Helinet, htp Business FleX smart, wittenberg-net GmbH |
|
Net4You-Voice4Biz | |
|
easybell, EWE Voice+ SIP Trunk | |
|
M-net Premium SIP-Trunk, Universe SIP Connect | |
| 11.12.2023 |
|
BITel Business SIP Flex, Gamma NGN (DE), wittenberg-net GmbH |
|
EWE Voice+ SIP Trunk | |
| 06.10.2023 |
|
Drei, Dstny, Komro, Magenta, RoutIT TLS, Vodafone Anlagenanschluss R5 |
|
Helinet, htp Business FleX smart | |
|
BT Wholesale, Deutsche Telekom CompanyFlex | |
|
ecotel sipTrunk Connect 1.0, ecotel sipTrunk DDI, Tele 2, UPC Austria, Vodafone Anlagenanschluss, Vodafone Anlagenanschluss R3 | |
| 15.12.2022 |
|
EasyFone, envia TEL, G9 Telecom, Keyyo, Orange BE SIP, Spark Voice Connect |
|
KPN TLS NL, Orange BE S&F, Sunrise, Vodafone Anlagenanschluss R4 | |
|
Orcon Ltd, TelstraClear WSIP | |
| further details: | https://wiki.unify.com/wiki/Collaboration_with_VoIP_Providers#Released_SIP_Providers_in_Detail | |
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!
Contents
- 1 Overview
- 2 SIP trunking features
- 3 General Requirements for VoIP
- 4 Hints for all Providers
- 5 How to get a new VoIP provider released
- 6 General Configuration guides
- 7 Tested VoIP Providers by Countries
- 7.1 International
- 7.2 Australia
- 7.3 Austria
- 7.4 Belgium
- 7.5 Brazil
- 7.6 Canada
- 7.7 Chile
- 7.8 Czech Republic
- 7.9 Denmark
- 7.10 Estonia
- 7.11 Finland
- 7.12 France
- 7.13 Germany
- 7.14 Greece
- 7.15 Hong Kong
- 7.16 Hungary
- 7.17 Italy
- 7.18 Liechtenstein
- 7.19 Luxembourg
- 7.20 Mexico
- 7.21 Netherlands
- 7.22 New Zealand
- 7.23 Portugal
- 7.24 Serbia
- 7.25 Slovakia
- 7.26 Slovenia
- 7.27 South Africa
- 7.28 Spain
- 7.29 Sweden
- 7.30 Switzerland
- 7.31 United Kingdom
- 7.32 United States of America
- 8 Released SIP Providers in Detail
- 9 External Links
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
- integrated SBC functionality
- SIP trunking with single numbers (MSN) and up to 30 SIP user accounts (called Internet telephony stations in WBM)
- SIP trunking with 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
- Call deflection
- DTMF transmission e.g. for voicemail access
- Location information for emergency calls
- Simultaneous VoIP connections depending on available DSL bandwidth, used Codec and system.
- Automatic fallback 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:
|
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 router
- 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.
Hints for all Providers
- Concurrent calls via ITSP (depending on the available bandwidth and used Codec).
- 30 for OpenScape Business X1
- up to 120 for OpenScape Business X3 / X5 / X8
- 180 for OpenScape Business S
- DTMF transmission
- outband transport via RFC 2833/RFC4733 is highly recommended. The ITSP MUST support outband DTMF (RFC2833/RFC4733) if UC Suite functions via SIP trunk (e.g. auto attendant, voicemail control) shall be used.
- inband transport may be used, but the functionality cannot be guaranteed as endpoints (e.g. UC-Suite) may not support inband DTMF.
- FAX over IP
- Please check the documentation available for your ITSP which Fax transmission is preferred.
- T.38 is activated by default in OpenScape Business
- If your provider does not support Fax T.38 or T.38 transmission causes problems, Fax pass-through with G.711 is possible but transmission quality depends on network infrastructure in this case.
- Call Forwarding
- By default an incoming ITSP call is forwarded to another public subscriber via a second ITSP trunk (one incoming and one outgoing).
- Call rerouting can be used for selected ITSPs, in this case NO line is used when call is active
- Special call numbers and emergency calls may need alternate TDM connections
- Special call numbers (e.g. 0800, 0900, 0137) are not supported by all SIP providers
- analog fax/modem connections are not supported by all SIP providers.
- Emergency call numbers (e.g. 110, 112) are not supported by all providers.
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.
|
-->> 24.07.2024 New documents and templates available check the .zip file <<-- |
- 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.
- Download
VOIP provider data collection and test list
- In the .zip-file you find the
- process description updated with new parameters V3R3
- ITSP questionnaire
- HowTo guide for system setup and hints for test execution
- the testlist updated with new test description for V3R3.1
- templates for writing a configuration guide updated for V3R3.1
After successful tests the VoIP provider will be 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. Certified providers are entitled to label their SIP Trunking Service with the OpenScape Business certified ITSP emblem
General Configuration guides
OpenScape Business SIP Trunk Configuration
Clip no Screening (CNS) for DID SIP Trunks
Mobile Extension (MEX) Connectivity
Multisite Management for DID SIP Trunks
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.
