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.

Jump to: navigation, search
(→‎Belgium)
(→‎Canada)
Line 186: Line 186:
 
| align="center" |  
 
| align="center" |  
 
| align="center" | {{yes}}
 
| align="center" | {{yes}}
 +
| align="center" |
 +
|}
 +
 +
 +
=== Czech Republic ===
 +
 +
{| {{DefaultTable}}
 +
! width="200" | VoIP Providers
 +
! width="30" | Type
 +
! width="70" | [[HiPath 3000]]
 +
! width="125" | [[HiPath OpenOffice EE]]
 +
! width="125" | [[HiPath OpenOffice ME]]
 +
|-
 +
| [http://www.cz.o2.com/ Telefonica O2]
 +
| align="center" |
 +
| align="center" | {{yes}}
 +
| align="center" |
 
| align="center" |
 
| align="center" |
 
|}
 
|}

Revision as of 11:05, 3 December 2009

◄ Platforms

File:VoIP Provider SME.jpg
Released VoIP Providers with HiPath 3000 / Hipath OpenOffice EE and HiPath OpenOffice ME
(Providers per system see below)

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

Overview

The SME HiPath platforms have been tested with a large number of Internet telephony providers that support SIP. Continuously new providers are tested, released and included within HiPath 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 HiPath platforms

  • up to 4 active SIP providers and one Internet connection
  • direct connection to DSL modem or operation behind another router using STUN
  • SIP trunking with single numbers (MSN) and up to 30 SIP user accounts
  • Direct Inward Dialing (DID)
  • most important features like transfer and call forwarding available
  • number of simultaneous VoIP connections is only limited by DSL bandwidth
  • automatic fallback to ISDN at SIP trunk failure
  • Voice Codecs G.711, G.729 and G.723
  • Fax over IP via T.38 (or G.711)

Interoperability with Carrier VoIP Platforms

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.

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.

Restrictions for all Providers and SME HiPath 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 most providers. These connections must be implemented via S0 access (administration default)
  • Only one external destination is allowed for ringing groups which are to be called via SIP trunk from VoIP provider.
  • 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.
  • DTMF is supported via RFC 2833 or inband. SIP INFO method is not supported.
  • 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.

General Information by platform

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

HiPath OpenOffice EE

SIP trunking features

  • see overview
  • Up to 32 simultaneous calls (depending on the available bandwidth and used CODEC)

Configuration

HiPath OpenOffice EE V1 Configuration Guide for Internet Service Providers:

HiPath 3000

HiPath 3000 ≥V7 with HG 1500 can be used for SIP trunking in the same way as HiPath OpenOffice EE.

  • see overview
  • An external router is always necessary
  • No FAX via ITSP from/to OpenScape Office client applications. A TDM trunk has to be used.

HiPath OpenOffice ME

SIP Trunking features

  • See overview.
  • G.711 and G.729 codecs are supported by the HiPath OpenOffice appliance.
  • For Call Forwarding to SIP provider announcements before connect are not audible (solved with V2).
  • FoIP (FAX over IP) with T.38 is available since the release of HiPath OpenOffice ME V1 R4 for FAX devices connected to Analog ports or Terminal Adapters. For FAX communication with OpenScape Office (OSO) a TDM Trunk has to be used.
    • The following T.38 FAX scenarios via ITSP are supported by HiPath OpenOffice ME:
      • 1. FAX devices (G.3) connected to an a/b (Analog) subscriber port of an HiPath GMSA, GMAA or GMAL Module or FAX devices (G.4) connected to a BRI/S0 (Digital) subscriber port of an HiPath GMSA or GMS Module.
      • 2. FAX devices (G.3) connected to an Analog port of an HiPath AP1120 Terminal Adapter (with SIP Loadware).
    • Currently not supported:
      • FAX services via ITSP from/to OpenScape Office client applications.

Configuration

HiPath OpenOffice ME V1 Configuration Guide for Internet Telephony:

Tested VoIP Providers by Countries

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

tick.gif = 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 HiPath OpenOffice EE HiPath OpenOffice ME
COLT DID tick.gif tick.gif tick.gif

Please check provider home page for supported countries.

Australia

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
engin MSN
DID 		tick.gif
tick.gif

Austria

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
inode MSN tick.gif tick.gif
WNT DID tick.gif tick.gif

Belgium

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Belgacom tick.gif tick.gif
Hexacom tick.gif tick.gif

for details on Type please refer to pdf-file below

Canada

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
thinktel tick.gif


Czech Republic

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Telefonica O2 tick.gif

France

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
OpenIP tick.gif
Optimitel tick.gif

Germany

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
1&1 MSN tick.gif tick.gif
Arcor DID tick.gif tick.gif tick.gif
freenet MSN tick.gif tick.gif
freenetBusiness DID tick.gif tick.gif tick.gif
GMX MSN tick.gif tick.gif
Purtel MSN tick.gif tick.gif
QSC DID tick.gif tick.gif
sipgate MSN
DID 		tick.gif tick.gif tick.gif
tick.gif [1]
T-Online MSN tick.gif tick.gif
T-Systems BAIP DID
toplink MSN
DID 		tick.gif
tick.gif 		tick.gif
tick.gif 		tick.gif
tick.gif
XSip DID tick.gif tick.gif
  1. ↑ For availability of DDI account by sipgate, please refer to http://www.sipgate.de

Greece

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
FORTHnet tick.gif
HellasOnLine tick.gif
ViVodi tick.gif

Italy

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Infracom (ex Multilink) tick.gif tick.gif
BT Italia DID tick.gif
Welcome Italia DID tick.gif

The Netherlands

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
I2Connect MSN
DID 		tick.gif
tick.gif 		tick.gif
tick.gif
Infopact MSN
DID 		tick.gif
tick.gif 		tick.gif
tick.gif 		tick.gif
Priority Telecom MSN
DID 		tick.gif tick.gif tick.gif

Portugal

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
G9-Telecom tick.gif
netcall discontinued
Portugal Telecom tick.gif tick.gif tick.gif

Slovenia

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Amis MSN
DID 		tick.gif tick.gif tick.gif
Detel MSN
DID 		tick.gif tick.gif tick.gif
MegaM MSN
DID 		tick.gif tick.gif tick.gif
tustelekom DID tick.gif tick.gif tick.gif
T-2 DID tick.gif tick.gif
UPC Telemach MSN
DID 		tick.gif tick.gif tick.gif

South Africa

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Telfree MSN
DID 		tick.gif
tick.gif

Spain

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
vozelia MSN
DID 		tick.gif
tick.gif 		tick.gif
tick.gif
Xtra Telecom MSN
DID 		tick.gif tick.gif tick.gif

Sweden

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Telia MSN tick.gif tick.gif

Switzerland

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Cablecom tick.gif tick.gif
sipcall MSN tick.gif
SofiCall MSN tick.gif
vtx DID tick.gif tick.gif

United Kingdom

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Voiceflex DID tick.gif 1) tick.gif 1)
Opal DID
Node4 DID

1) minor restrictions: no Fax T.38 supported by provider, no semi-attended transfer via SIP trunk

United States of America

VoIP Providers Type HiPath 3000 HiPath OpenOffice EE HiPath OpenOffice ME
Cbeyond tick.gif tick.gif
Covad tick.gif
Sotel MSN
DID 		tick.gif
tick.gif

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.

Connectivity Test Information

The connectivity test is carried out with

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

External Links

Retrieved from "http://wiki.unify.com/index.php?title=Collaboration_with_VoIP_Providers&oldid=25274"