TBwiki - User contributions [en]

SBC:CertifiedHardware

2020-05-11T15:17:46Z

Marc St-Onge: Changed "high" for "medium".

{{DISPLAYTITLE:SBC Certified Hardware}}

== List of certified baremetal servers ==
*[[SBC:TSBC-HW-SRV-HIGH|Dell high performance server for 60,000 sessions]]
*[[SBC:TSBC-HW-SRV-MID|Dell medium performance server for 30,000 sessions]]
*[[SBC:Ciena|Ciena Virtual Network Function (VNF) Customer Premises Equipment (CPE) for less than 10,000 sessions]]
*[[SBC:Qotom|Qotom Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions]]
*[[SBC:Lanner|Lanner Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions]]
*[[SBC:TelcoSystems|TelcoSystems Virtual Network Function (VNF) Universal Customer Premises Equipment (uCPE) for less than 4,000 sessions]]

SBC:TSBC-HW-SRV-MID

2020-05-11T15:16:14Z

Marc St-Onge: Changed "High" for "Medium".

{{DISPLAYTITLE:Medium Performance Baremetal Server}}

This unit has been tested at up to 30,000 sessions and 1,000 calls per second.

== Model ==
* Dell R330

== Characteristics ==
* Single Xeon E3-1240, 4C/8T (4 cores/8 Threads), 3.5GHz
* 16GB RAM RDIMM, 2400MHz
* NUMA optimized for PCIe faster accesses

== Network Interfaces ==
* Management: 2x 1Gbps copper
* Control: 2x 1Gbps copper
* VoIP/SBC interfaces: 2x 10Gbps SFP+ SR optics (850nm) (or copper)

== High Availability & Redundancy ==
* Power supply redundancy
* Hardware RAID1 on 2x 200GB SSD

<div class="mw-collapsible mw-collapsed" data-collapsetext="Bios settings" data-expandtext="Click here for specific BIOS settings on this server" style="width: 400px;">
Upon initial bootup, type "F2" to enter setup
* Boot Settings
** Boot Mode [BIOS] (NOt UEFI)
* Processor Settings
** Virtualization Technology -> [Disabled]
* System Profile Settings
** CPU Power Management [Maximum Performance]
** Turbo Boost [Disabled]
</div>

== Performance Data ==

{| cellpadding="5" border="1" class="wikitable style="text-align: center"
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | vCPU
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | vCPU dedicated
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | RAM
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | CPS
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | CAPS
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Sessions
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Sessions with Transcoding
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | No Anchoring
|-
| 8 || yes || 16 GB || 500 || 2,000 || 30,000 || 15,000 || 60,000
|}

== References ==
[https://www.dell.com/en-ca/work/shop/povw/poweredge-r330 Dell R330 server]

Interoperability:Vendors

2020-04-23T20:33:57Z

Marc St-Onge: Added Ribbon AS

TelcoBridges equipment has been successfully deployed by customers and partners in over 100 countries in a broad range of scenarios, involving hardware and software from other providers. While not exhaustive, here is a list of vendors (in alphabetical order) with which TelcoBridges' products have been deployed or certified:

'''Softswitch/Session Border Controllers (SBC)'''
*Acme Packet
*Mera/ALOE Systems/SwitchRay/46Labs (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=800&langue=en&modeAffichage=0&forceMode=0 certified])
*Asterisk
*AVAYA
*Broadsoft
*Cataleya
*Cisco PGW
*Cirpack
*FreeSWITCH
*Huawei X3000
*MetaSwitch (softswitch)
*openSIPS
*NetSapiens (softswitch)
*Ribbon (Genband/Nortel)
**C3
**C15
**C20
**CS2000
*PhoenixSoft Cirrus (softswitch)
*PortaOne (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=839&langue=en&modeAffichage=0&forceMode=0 certified])
*REDCOM
*Samsung
*Sansay VSXi
*Sipwise
*Sippy Softswitch
*Teles (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=825&langue=en&modeAffichage=2 certified])
*VoIPGroup
*VoIPSwitch
*VSC
*Xener Systems (softswitch; certified)
*YATE

'''TDM Switches/STP'''
*Adtran
*Alcatel-Lucent
**4ESS
**5ESS
**Compact Switch
**various MSC models
*Ericsson
**AXE
**various MSC models
*Huawei
*Nokia-Siemens
**various MSC models
*Nortel
**various DMS models
*REDCOM
*Siemens DCO
*Tekelec
*Tropico
*ZTE

'''IP PBX/Unified Communications/SaaS'''
*3CX
*Asterisk
*AVAYA
*Centile
*Elastix
*FreePBX
*Microsoft Lync
*Mitel/Shoretel
*Ribbon Application Server
*Telestax
*TransNexus ClearIP
*Twilio
*Vital PBX

'''IVR/Voicemail Systems'''
*Altitude
*Atento
*ATS Argentina
*AVAYA
*Interact SoftSpot
*OpenMethods
*Movius CAFE
*RadiSys
*StreamWIDE

'''Media gateways / telecommunications hardware'''
*Aculab
*Adtran
*AudioCodes
*Cisco
*Dialogic
*Ribbon (Genband)
*Huawei
*Mediatrix
*Metaswitch
*Quintum

'''Fax'''
*Axacore
*COMISDN
*Dialogic Brooktrout Fax Server
*FaxBack
*Faxcore

'''Billing/Routing'''
*Alaris Labs
*Fastlink Software
*JeraSoft
*PortaOne PortaBilling
*TransNexus

Interoperability:Vendors

2020-04-23T20:28:39Z

Marc St-Onge: Added many vendors

TelcoBridges equipment has been successfully deployed by customers and partners in over 100 countries in a broad range of scenarios, involving hardware and software from other providers. While not exhaustive, here is a list of vendors (in alphabetical order) with which TelcoBridges' products have been deployed or certified:

'''Softswitch/Session Border Controllers (SBC)'''
*Acme Packet
*Mera/ALOE Systems/SwitchRay/46Labs (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=800&langue=en&modeAffichage=0&forceMode=0 certified])
*Asterisk
*AVAYA
*Broadsoft
*Cataleya
*Cisco PGW
*Cirpack
*FreeSWITCH
*Huawei X3000
*MetaSwitch (softswitch)
*openSIPS
*NetSapiens (softswitch)
*Ribbon (Genband/Nortel)
**C3
**C15
**C20
**CS2000
*PhoenixSoft Cirrus (softswitch)
*PortaOne (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=839&langue=en&modeAffichage=0&forceMode=0 certified])
*REDCOM
*Samsung
*Sansay VSXi
*Sipwise
*Sippy Softswitch
*Teles (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=825&langue=en&modeAffichage=2 certified])
*VoIPGroup
*VoIPSwitch
*VSC
*Xener Systems (softswitch; certified)
*YATE

'''TDM Switches/STP'''
*Adtran
*Alcatel-Lucent
**4ESS
**5ESS
**Compact Switch
**various MSC models
*Ericsson
**AXE
**various MSC models
*Huawei
*Nokia-Siemens
**various MSC models
*Nortel
**various DMS models
*REDCOM
*Siemens DCO
*Tekelec
*Tropico
*ZTE

'''IP PBX/Unified Communications/SaaS'''
*3CX
*Asterisk
*AVAYA
*Centile
*Elastix
*FreePBX
*Microsoft Lync
*Mitel/Shoretel
*Telestax
*TransNexus ClearIP
*Twilio
*Vital PBX

'''IVR/Voicemail Systems'''
*Altitude
*Atento
*ATS Argentina
*AVAYA
*Interact SoftSpot
*OpenMethods
*Movius CAFE
*RadiSys
*StreamWIDE

'''Media gateways / telecommunications hardware'''
*Aculab
*Adtran
*AudioCodes
*Cisco
*Dialogic
*Ribbon (Genband)
*Huawei
*Mediatrix
*Metaswitch
*Quintum

'''Fax'''
*Axacore
*COMISDN
*Dialogic Brooktrout Fax Server
*FaxBack
*Faxcore

'''Billing/Routing'''
*Alaris Labs
*Fastlink Software
*JeraSoft
*PortaOne PortaBilling
*TransNexus

MOS

2018-07-26T14:16:45Z

Marc St-Onge: Corrected some spelling and sentence structure.

Mean Opinion Score, more commonly known as MOS, is a voice call quality metric that ranges from 5 (excellent) to 1 (bad). It is a subjective method of quality assessment.

== TelcoBridges and MOS ==

[[Toolpack]] uses a well-known model to evaluate a MOS value based on collected statistics for a call. There are 3 factors that significantly impact the call quality: latency, packet loss and jitter of RTP packets. Using these statistics, we calculate an R-value that ranges from 1 to 100 where a higher number is better. Finally the MOS is calculated using this formula.

MOS = 1 + 0.035R + ((R - 60) * (100 – R) * 0.000007R)

=== TelcoBridges' MOS Implementation ===
For the MOS calculated from the R-value, there is no notion of codec. We decided to apply a ratio in relation to the codec's ideal MOS.

See the table below:

[[Image:mos_codec_conversion.jpg| ]] 

==== Network quality ====
TelcoBridges' MOS implementation adds another concept over the standard MOS: Network quality. The network quality parameter provides a fast way to identify a bad network condition. The MOS is useful when comparing calls for the same [[NAP]] or for the same network. But if you are using several codecs, the MOS value might be misleading to detect network problems.

*'''Examples:'''
**A perfect network (i.e. no packet loss, no latency) using G.723 will have a MOS of 3.6. This is relatively low, but it represents a network quality of 100%. The only way to improve the MOS will be to use a higher quality codec.
**On the other hand, a G.711 call with a MOS of 3.7 represents a network quality of 86%. This rather low and based on these values, you know there is something that can be improved in the network.

==== Ingress-Egress ====
There are 2 MOS values calculated per call leg. The ingress value is using RTP reception statistics and the egress value is using RTCP statistics received from the peer. Using these statistics, w can calculate MOS and network quality for the ingress and egress directions.

When using [[Call_Trace|Call Trace]], the lowest value between ingress and egress MOS and network quality are displayed.

[[Category:Glossary]]
[[Category:Sbc_Features]]

==Related subject==
*[[Toolpack:RADIUS_CDR_attributes_D|MOS scores in CDRs]]
**[[Call_statistics_format_C|Statistics in the CDRs ]]
*[[Routing_script_tutorial:Mini_Development_Guide#Nap_status|MOS in routing scripts]]

SIGTRAN

2018-03-12T18:19:29Z

Marc St-Onge: Changed RFCs with Real

SIGTRAN refers to the ability to provide [[SS7]] and [[ISDN]] signaling over an IP network.

SIGTRAN is the name given to an Internet Engineering Task Force (IETF) working group that produced specifications for a family of protocols that provide reliable datagram service and user layer adaptations for SS7 and ISDN communications protocols. SIGTRAN is logically an extension of the SS7 protocol family. It supports the same application and call management paradigms as SS7 but uses an IP transport called Stream Control Transmission Protocol (SCTP) as its underlying transport vehicle. Indeed, the most significant protocol defined by the SIGTRAN group was SCTP, which is used to carry PSTN signaling over IP.

== TelcoBridges and SIGTRAN ==

TelcoBridges provides support for SIGTRAN starting in [[Web_Portal_Tutorial_Guide_v2.4|Toolpack v2.4]]. TelcoBridges' SIGTRAN implementation provides support for [[SCTP]], [[M2UA]], [[M2PA]], [[M3UA]] and [[IUA]]. ([[SUA]] support is not currently planned as part of the initial SIGTRAN release.)

Among the features of TelcoBridges' SIGTRAN implementation are the following:
*M2PA with 64 links (termination)
*M2UA in SG and ASP mode (relay)
*M3UA in SG, ASP and IPSP mode (relay)
*M3UA with load distribution features similar to the [[MTP3 Layer|MTP3]] stack (termination)

=== Maximum Capacity ===
{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! Model !!SCTP links!!SCTP streams/links !!M2PA links!!M2UA links!!M3UA links!!M3UA routing context
|-
| TMG800 || 64 || 64 in&out || 64 || 64 || 64 || 60
|-
| TMG3200|| 64 || 64 in&out || 64 || 64 || 64 || 60
|-
| TMG7800|| 1024 (64/Tmedia) || 64 in&out || 512 (64/Tmedia) || 1024 (64/Tmedia) || 64 || 60
|}

Standard references:
*SCTP

:RFC 4960, September 2007

*M3UA

:RFC 4666, IETF

:M3UA, Implementation Guide, IETF, 2002

*M2UA

:SS7 MTP2-User Adaptation Layer, RFC 3331, IETF

*M2PA

:RFC 4165, IETF

*IUA

:IETF RFC 5133 ISDN Q.921 User Adaptation Layer, December 2007

:ETSI TS 102 332 V1.1.1 ISDN Q.921 User Adaptation Layer

== Configuration ==

*[[Toolpack:Protocol_Stack_Settings_A|Web Portal v2.8: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.7#M2PA-MTP3-ISUP|Web Portal v2.7: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.6#M2PA-MTP3-ISUP|Web Portal v2.6: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.5#SIGTRAN Application Scenarios|Web Portal v2.5: SIGTRAN Application Scenarios]]
*[[Web_Portal_Tutorial_Guide_v2.4#SIGTRAN Application Scenarios|Web Portal v2.4: SIGTRAN Application Scenarios]]

== References ==
*[http://en.wikipedia.org/wiki/SIGTRAN Wikipedia article]
*[http://www.sigtran.net/sigtran-introduction.pdf Introduction to SIGTRAN, by Jim Darroch]
*[[SIGTRAN pricing model 2011|Pricing model (TelcoBridges)]]

[[category:Glossary]]
[[category:Needs revising]]
[[Category:Revise on Major]]

SIGTRAN

2018-03-12T18:15:58Z

Marc St-Onge:

SIGTRAN refers to the ability to provide [[SS7]] and [[ISDN]] signaling over an IP network.

SIGTRAN is the name given to an Internet Engineering Task Force (IETF) working group that produced specifications for a family of protocols that provide reliable datagram service and user layer adaptations for SS7 and ISDN communications protocols. SIGTRAN is logically an extension of the SS7 protocol family. It supports the same application and call management paradigms as SS7 but uses an IP transport called Stream Control Transmission Protocol (SCTP) as its underlying transport vehicle. Indeed, the most significant protocol defined by the SIGTRAN group was SCTP, which is used to carry PSTN signaling over IP.

== TelcoBridges and SIGTRAN ==

TelcoBridges provides support for SIGTRAN starting in [[Web_Portal_Tutorial_Guide_v2.4|Toolpack v2.4]]. TelcoBridges' SIGTRAN implementation provides support for [[SCTP]], [[M2UA]], [[M2PA]], [[M3UA]] and [[IUA]]. ([[SUA]] support is not currently planned as part of the initial SIGTRAN release.)

Among the features of TelcoBridges' SIGTRAN implementation are the following:
*M2PA with 64 links (termination)
*M2UA in SG and ASP mode (relay)
*M3UA in SG, ASP and IPSP mode (relay)
*M3UA with load distribution features similar to the [[MTP3 Layer|MTP3]] stack (termination)

=== Maximum Capacity ===
{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! Model !!SCTP links!!SCTP streams/links !!M2PA links!!M2UA links!!M3UA links!!M3UA routing context
|-
| TMG800 || 64 || 64 in&out || 64 || 64 || 64 || 60
|-
| TMG3200|| 64 || 64 in&out || 64 || 64 || 64 || 60
|-
| TMG7800|| 1024 (64/Tmedia) || 64 in&out || 512 (64/Tmedia) || 1024 (64/Tmedia) || 64 || 60
|}

Standard references:
*SCTP

:RFC 4960, September 2007

*M3UA

:RFC 4666, IETF

:M3UA, Implementation Guide, IETF, 2002

*M2UA

:SS7 MTP2-User Adaptation Layer, RFC 3331, IETF

*M2PA
**draft-ietf-sigtran-m2pa-13: SS7 MTP2 User Peer-to-Peer Adaptation Layer (M2PA)
**RFC 4165

*IUA

:IETF RFC 4233 ISDN Q.921 User Adaptation Layer 01/2006

:IETF draft-ietf-sigtranrfc4233update-01 IUA (RFC 4233) TEI Query Request Number 07/2007

:ETSI TS 102 332 V1.1.1 ISDN Q.921 User Adaptation Layer

== Configuration ==

*[[Toolpack:Protocol_Stack_Settings_A|Web Portal v2.8: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.7#M2PA-MTP3-ISUP|Web Portal v2.7: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.6#M2PA-MTP3-ISUP|Web Portal v2.6: SIGTRAN Configuration]]
*[[Web_Portal_Tutorial_Guide_v2.5#SIGTRAN Application Scenarios|Web Portal v2.5: SIGTRAN Application Scenarios]]
*[[Web_Portal_Tutorial_Guide_v2.4#SIGTRAN Application Scenarios|Web Portal v2.4: SIGTRAN Application Scenarios]]

== References ==
*[http://en.wikipedia.org/wiki/SIGTRAN Wikipedia article]
*[http://www.sigtran.net/sigtran-introduction.pdf Introduction to SIGTRAN, by Jim Darroch]
*[[SIGTRAN pricing model 2011|Pricing model (TelcoBridges)]]

[[category:Glossary]]
[[category:Needs revising]]
[[Category:Revise on Major]]

Call detail record

2018-03-07T17:39:09Z

Marc St-Onge: Corrected the English

Call detail records, or CDR for short, are the foundation of subscriber billing activities by telecom service providers. They are data records containing call-related information such as:
*Incoming Network
*Outgoing Network
*Calling number
*Called number
*Start time
*End Time
See this link from more details [http://en.wikipedia.org/wiki/Call_detail_record Wikipedia - Call Retail Record]

== TelcoBridges and call detail records ==
TelcoBridges [[TMG800]], [[TMG3200]] and [[TMG7800]] products support the generation of call detail records in [[Text Call Detail Records (CDR)|text]] format. They also support the ability to export call detail records to a [[RADIUS]] server for accounting purposes. Both methods can be used simultaneously.

[[Text Call Detail Records (CDR)|Text CDRs ]] are stored locally on the TMG units and must be extracted from the system either manually, or automatically.

If the network supports [[RADIUS]], this method is preferred as each record will be sent in a timely manner to an external database for storage.

[[File:CDR_High-level_drawing v2.bmp]]

== Call Detail Records Generation ==
TelcoBridges CDRs are generated on a per-leg bases when the call is answered and when the call is terminated.

In the cases illustrated below:

'''Id''' is a 128 bits unique identifier for all the records of a same call.
* '''h323-conf-id''' for RADIUS and '''@{SessionId}''' for Text CDR

'''Original Id''' is a 128 bits unique identifier used for Call Transfer records. Each call transfer outgoing legs has its own unique '''Id''' with its '''Original Id'' associated call legs (incoming+outgoing).
* '''h323-incoming-conf-id''' for RADIUS and '''@{OriginalSessionId}''' for Text CDR

=== Case 1: Call Answered ===
[[File:CDR_CallAnswer.jpg|640px]]

=== Case 2: Call Unanswered ===
[[File:CDR_UnansweredCall.jpg|640px]]

=== Case 3: Call Transferred ===
[[File:CDR_CallTransferBleg.jpg|640px]]

[[File:CDR_CallTransferCleg.jpg|640px]]

== Text-based Call Detail Records ==
[[Text Call Detail Records (CDR)|Text-based call detail records]]

== RADIUS Call Detail Records ==
[[RADIUS]]

== Call Detail Records in High Availability (HA) Environment ==
The term HA refers to a system equipped with primary and secondary host controllers (i.e. An SBC deployed in a 1+1 configuration, a TMG7800 gateway with redundant controllers or Tmedia gateways deployed in a 1+1 configuration)

* '''Text CDR only''' Mode
** The active gateway application is storing text-based CDR records on the active host (i.e. non-zero bytes of CDR log file)
** Each CDR record will only be present either on the primary or on the secondary host
** The user needs to merge the CDR records from both the primary and secondary hosts to get all the data
* '''RADIUS CDR only''' Mode
** CDR records will be sent out to the RADIUS server(s) from the gateway application on the active host only
** No CDR records are stored on the HA system
* '''Text and RADIUS CDR''' Mode
** CDR records will be sent out to RADIUS server(s) from the gateway application on the active host
** The active gateway application is also storing text-based CDR records on the active host (i.e. non-zero bytes of CDR log file)
** Also, each text-based CDR record will only be present either on the primary or on the secondary host
** The user needs to merge the CDR records from both the primary and secondary hosts to get all the data
* '''RADIUS CDR with text CDR fallback''' Mode
** If the RADIUS server(s) is(are) in service
*** CDR records will be sent out to the RADIUS server(s) from the gateway application on the active host only
** If the RADIUS server(s) is(are) out of service
*** The active gateway application is storing text-based CDR records on the active host (i.e. non-zero bytes of CDR log file)
*** Each CDR record will only be present either on the primary or on the secondary host
*** The user needs to merge the CDR records from both the primary and secondary hosts to get all the data

[[category:Glossary]]
[[category:Tmedia_Features]]
[[Category:RevisionV2]]

Interoperability:Vendors

2018-02-21T17:08:36Z

Marc St-Onge: Changed the way TransNexus was written

TelcoBridges equipment has been successfully deployed by customers and partners in over 100 countries in a broad range of scenarios, involving hardware and software from other providers. While not exhaustive, here is a list of vendors (in alphabetical order) with which TelcoBridges' products have been deployed or certified:

'''Softswitch/Session Border Controllers (SBC)'''
*Acme Packet
*Mera/ALOE Systems/SwitchRay (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=800&langue=en&modeAffichage=0&forceMode=0 certified])
*Asterisk
*AVAYA
*Broadsoft
*Cataleya
*Cisco PGW
*Cirpack
*FreeSWITCH
*Huawei X3000
*MetaSwitch (softswitch)
*openSIPS
*NetSapiens (softswitch)
*GENBAND/NORTEL
**C3
**C15
**C20
**CS2000
*PhoenixSoft Cirrus (softswitch)
*PortaOne (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=839&langue=en&modeAffichage=0&forceMode=0 certified])
*Samsung
*Sansay VSXi
*Teles (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=825&langue=en&modeAffichage=2 certified])
*VoIPGroup
*VoIPSwitch
*VSC
*Xener Systems (softswitch; certified)
*YATE

'''TDM Switches/STP'''
*Adtran
*Alcatel-Lucent
**4ESS
**5ESS
**various MSC models
*Ericsson
**AXE
**various MSC models
*Huawei
*Nokia-Siemens
**various MSC models
*Nortel
**various DMS models
*Siemens DCO
*Tekelec
*Tropico
*ZTE

'''IP PBX/Unified Communications'''
*Asterisk
*AVAYA
*Centile
*Elastix
*FreePBX
*Microsoft Lync

'''IVR/Voicemail Systems'''
*Altitude
*ATS Argentina
*AVAYA
*Interact SoftSpot
*OpenMethods
*Movius CAFE
*RadiSys
*StreamWIDE

'''Media gateways / telecommunications hardware'''
*Aculab
*Adtran
*AudioCodes
*Cisco
*Dialogic
*Genband
*Huawei
*Mediatrix
*Metaswitch
*Quintum

'''Fax'''
*Axacore
*COMISDN
*Dialogic Brooktrout Fax Server
*FaxBack
*Faxcore

'''Billing/Routing'''
*Alaris Labs
*Fastlink Software
*JeraSoft
*PortaOne PortaBilling
*TransNexus

Interoperability:Vendors

2018-02-21T17:07:41Z

Marc St-Onge: Changed the order of the GENBAND switches

TelcoBridges equipment has been successfully deployed by customers and partners in over 100 countries in a broad range of scenarios, involving hardware and software from other providers. While not exhaustive, here is a list of vendors (in alphabetical order) with which TelcoBridges' products have been deployed or certified:

'''Softswitch/Session Border Controllers (SBC)'''
*Acme Packet
*Mera/ALOE Systems/SwitchRay (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=800&langue=en&modeAffichage=0&forceMode=0 certified])
*Asterisk
*AVAYA
*Broadsoft
*Cataleya
*Cisco PGW
*Cirpack
*FreeSWITCH
*Huawei X3000
*MetaSwitch (softswitch)
*openSIPS
*NetSapiens (softswitch)
*GENBAND/NORTEL
**C3
**C15
**C20
**CS2000
*PhoenixSoft Cirrus (softswitch)
*PortaOne (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=839&langue=en&modeAffichage=0&forceMode=0 certified])
*Samsung
*Sansay VSXi
*Teles (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=825&langue=en&modeAffichage=2 certified])
*VoIPGroup
*VoIPSwitch
*VSC
*Xener Systems (softswitch; certified)
*YATE

'''TDM Switches/STP'''
*Adtran
*Alcatel-Lucent
**4ESS
**5ESS
**various MSC models
*Ericsson
**AXE
**various MSC models
*Huawei
*Nokia-Siemens
**various MSC models
*Nortel
**various DMS models
*Siemens DCO
*Tekelec
*Tropico
*ZTE

'''IP PBX/Unified Communications'''
*Asterisk
*AVAYA
*Centile
*Elastix
*FreePBX
*Microsoft Lync

'''IVR/Voicemail Systems'''
*Altitude
*ATS Argentina
*AVAYA
*Interact SoftSpot
*OpenMethods
*Movius CAFE
*RadiSys
*StreamWIDE

'''Media gateways / telecommunications hardware'''
*Aculab
*Adtran
*AudioCodes
*Cisco
*Dialogic
*Genband
*Huawei
*Mediatrix
*Metaswitch
*Quintum

'''Fax'''
*Axacore
*COMISDN
*Dialogic Brooktrout Fax Server
*FaxBack
*Faxcore

'''Billing/Routing'''
*Alaris Labs
*Fastlink Software
*JeraSoft
*PortaOne PortaBilling
*Transnexus

Interoperability:Vendors

2018-02-21T17:06:50Z

Marc St-Onge: Added GENBAND C15 softswitch

TelcoBridges equipment has been successfully deployed by customers and partners in over 100 countries in a broad range of scenarios, involving hardware and software from other providers. While not exhaustive, here is a list of vendors (in alphabetical order) with which TelcoBridges' products have been deployed or certified:

'''Softswitch/Session Border Controllers (SBC)'''
*Acme Packet
*Mera/ALOE Systems/SwitchRay (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=800&langue=en&modeAffichage=0&forceMode=0 certified])
*Asterisk
*AVAYA
*Broadsoft
*Cataleya
*Cisco PGW
*Cirpack
*FreeSWITCH
*Huawei X3000
*MetaSwitch (softswitch)
*openSIPS
*NetSapiens (softswitch)
*GENBAND/NORTEL
**CS2000
**C20
**C15
**C3
*PhoenixSoft Cirrus (softswitch)
*PortaOne (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=839&langue=en&modeAffichage=0&forceMode=0 certified])
*Samsung
*Sansay VSXi
*Teles (softswitch; [http://www.telcobridges.com/afficher02.aspx?page=825&langue=en&modeAffichage=2 certified])
*VoIPGroup
*VoIPSwitch
*VSC
*Xener Systems (softswitch; certified)
*YATE

'''TDM Switches/STP'''
*Adtran
*Alcatel-Lucent
**4ESS
**5ESS
**various MSC models
*Ericsson
**AXE
**various MSC models
*Huawei
*Nokia-Siemens
**various MSC models
*Nortel
**various DMS models
*Siemens DCO
*Tekelec
*Tropico
*ZTE

'''IP PBX/Unified Communications'''
*Asterisk
*AVAYA
*Centile
*Elastix
*FreePBX
*Microsoft Lync

'''IVR/Voicemail Systems'''
*Altitude
*ATS Argentina
*AVAYA
*Interact SoftSpot
*OpenMethods
*Movius CAFE
*RadiSys
*StreamWIDE

'''Media gateways / telecommunications hardware'''
*Aculab
*Adtran
*AudioCodes
*Cisco
*Dialogic
*Genband
*Huawei
*Mediatrix
*Metaswitch
*Quintum

'''Fax'''
*Axacore
*COMISDN
*Dialogic Brooktrout Fax Server
*FaxBack
*Faxcore

'''Billing/Routing'''
*Alaris Labs
*Fastlink Software
*JeraSoft
*PortaOne PortaBilling
*Transnexus

FreeSBC:Cloud:VmWare Installation A

2018-01-30T20:30:05Z

Marc St-Onge: Changed the wording for the minimal cloud requirements.

{{DISPLAYTITLE:FreeSBC:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64-bit infrastructure only
* E1000 NIC emulation or VMXNET3 interfaces
* One Ethernet adapter for management (mgmt0)
* One or more Ethernet adapter(s) for SIP and RTP traffic according to the table below (LAN/WAN)
* If you are deploying FreeSBC with transcoding devices or in a 1+1 configuration, you will two additional Ethernet adapters to be used as control ports (ctrl0/ctrl1).

{| cellpadding="5" border="1" class="wikitable"
|-
! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Sessions
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | CPU
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | RAM
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Disk Space
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Data Ethernet ports
|-
| valign="top" |
Up to 5,000
| valign="top" |
2
| valign="top" |
4 Gb
| valign="top" |
40 Gb
| valign="top" |
1 Gbps
|-
| valign="top" |
5,000-20,000
| valign="top" |
4
| valign="top" |
8 Gb
| valign="top" |
60 Gb
| valign="top" |
4 X 1 Gbps or
1 X 10 Gbps
|-
| valign="top" |
20,000-50,000
| valign="top" |
4**
| valign="top" |
16 Gb
| valign="top" |
80 Gb
| valign="top" |
1 X 10 Gbps
|-
| valign="top" |
Above 50,000
| valign="top" |
6**
| valign="top" |
24+ Gb
| valign="top" |
100 Gb
| valign="top" |
Multiple 10 Gbps
|}
<nowiki>**</nowiki> The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPUs number if yours are from a earlier generations.

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* CPU resource: allocation shares set to 'high'
* CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
* Memory resource: reserve all guest memory (all locked)
* Disk: shares 'high'
* Advanced CPU: Hyperthread core sharing to 'None'
* Latency Sensitivity: 'High'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC VmWare Image ===
A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.

You will need to upload the latest TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

[[TSBC-SW:Cloud:VmWare_Launching_Instance_Web_A|Using the ESXi Web client]]

[[TSBC-SW:Cloud:VmWare_Launching_Instance_vSphere_A|Using the vSphere client application]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
* Open a web browser to the management IP of the TSBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be: http://192.168.178.30:12358
 
:You should get to the TSBC Configuration Wizard 
:[[File:TSBC_WebPortal_Configuration_wizard.jpg|700px]]
 
* If you do not know the IP address, you can find it from the VMware interface: 
:[[File:FreeSBC Initial IP address.png|700px]]
 
* From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration|Web Portal Initial Configuration Guide]] to continue the installation, and/or [[TSBC-SW:Baremetal:VmWare_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

FreeSBC:Cloud:VmWare Installation A

2018-01-30T20:26:48Z

Marc St-Onge: Changed wording

{{DISPLAYTITLE:FreeSBC:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64-bit infrastructure only
* E1000 NIC emulation or VMXNET3 interfaces
* One Ethernet adapter for management (mgmt0)
* Two Ethernet adapters for control (ctrl0/ctrl1) when transcoding or 1+1 is used. Not needed otherwise.
* One or more Ethernet adapter(s) for data (SIP/RTP) according to the table below (LAN/WAN)

{| cellpadding="5" border="1" class="wikitable"
|-
! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Sessions
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | CPU
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | RAM
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Disk Space
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Data Ethernet ports
|-
| valign="top" |
Up to 5,000
| valign="top" |
2
| valign="top" |
4 Gb
| valign="top" |
40 Gb
| valign="top" |
1 Gbps
|-
| valign="top" |
5,000-20,000
| valign="top" |
4
| valign="top" |
8 Gb
| valign="top" |
60 Gb
| valign="top" |
4 X 1 Gbps or
1 X 10 Gbps
|-
| valign="top" |
20,000-50,000
| valign="top" |
4**
| valign="top" |
16 Gb
| valign="top" |
80 Gb
| valign="top" |
1 X 10 Gbps
|-
| valign="top" |
Above 50,000
| valign="top" |
6**
| valign="top" |
24+ Gb
| valign="top" |
100 Gb
| valign="top" |
Multiple 10 Gbps
|}
<nowiki>**</nowiki> The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPUs number if yours are from a earlier generations.

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* CPU resource: allocation shares set to 'high'
* CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
* Memory resource: reserve all guest memory (all locked)
* Disk: shares 'high'
* Advanced CPU: Hyperthread core sharing to 'None'
* Latency Sensitivity: 'High'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC VmWare Image ===
A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.

You will need to upload the latest TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

[[TSBC-SW:Cloud:VmWare_Launching_Instance_Web_A|Using the ESXi Web client]]

[[TSBC-SW:Cloud:VmWare_Launching_Instance_vSphere_A|Using the vSphere client application]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
* Open a web browser to the management IP of the TSBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be: http://192.168.178.30:12358
 
:You should get to the TSBC Configuration Wizard 
:[[File:TSBC_WebPortal_Configuration_wizard.jpg|700px]]
 
* If you do not know the IP address, you can find it from the VMware interface: 
:[[File:FreeSBC Initial IP address.png|700px]]
 
* From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration|Web Portal Initial Configuration Guide]] to continue the installation, and/or [[TSBC-SW:Baremetal:VmWare_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]