Table of content
History
|
Revision |
Date Published |
Authors |
Reason for Revision |
|
1 |
July 2007 |
Mkt |
Creation |
|
2 |
August 2007 |
Mkt |
Add OXO configuration
document for Netcall |
|
|
|
|
|
Abbreviations
n SBC : Session Border Controller
n SIP : Session Initiation Protocol
1. Introduction
This document gives the list of SIP providers for whom interoperability
with OXO SIP Trunking Public feature has been proved
by the means of interworking tests. For each provider it gives Feature
restrictions and Deployment constraints.
2. Restriction
So far, it is mandatory to connect at least one IDSN or one analogue
trunk to OmniPCX Office to guarantee remote access
for configuration and/or maintenance.
3. Portugal
Netcall
·
Feature restrictions :
o Fax T38 not available => use ISDN
trunk
o Only installation number in the CLIP
(not DDI numbers)
o ISDN operator must accept CLIP = SIP
head number in case of overflow from SIP trunk to ISDN trunk (ex. Portugal
Telecom)
·
Deployment constraints
:
o External router at customer premises
is mandatory for NAT SIP, ex. :
§ Cisco 2611XM, IOS = IOS 12.4 (4).T1
§ LinkSys WRT54GS,
Firmware Version: v1.50.8, May. 23, 2006
§ DrayTeK Vigor 2800
§ DrayTeK Vigor 2700
§
FunkWerk x2302
o ISDN or analogue trunk mandatory for :
§
Remote configuration and maintenance
§
Fax service
§
Back up in case of SIP failure
·
Document giving configuration of OXO for Netcall
4.
UK
Voiceflex
·
Feature restrictions :
o Fax T38 not available => use ISDN
trunk
·
Deployment constraints :
o External router for NAT is
mandatory, ex. :
§
Thomson
ST510
o ISDN or analogue trunk mandatory for :
§
Remote configuration and maintenance
§
Fax service
§
Backup in case of SIP failure
·
Document giving configuration of OXO for Voiceflex
END OF DOCUMENT