Protocols and approvals
Worldwide IP and TDM protocols for applications using boards and software from Aculab
Aculab's protocol coverage extends to the broadest range of worldwide call control and signalling protocols with appropriate, host independent regulatory approvals. the list includes many different national and international variants of Signalling System Number 7 (SS7), CAS and ISDN (including Q.931, Q.SIG and DPNSS), for operation over E1 and T1 trunks on our tdM boards. In addition, for IP telephony and VoIP applications, Aculab offers H.323 and SIP stacks for use with our IP and media processing boards.
Combined protocols
Many applications require voice board or IP-based media processing functionality, such as record, playback, DTMF handling, wideband audio conferencing, encoding/transcoding and T.38 fax. All these essential functions and more are available with Aculab's Prosody X IP or DSP boards, which can be combined with any protocol, including SIP and SS7, to deliver powerful, cost-effective, telecoms server-based solutions.
In addition, offering the same core functionality, Prosody S, Aculab's advanced HMP, offers a viable alternative to using IP boards for telco and enterprise applications or service delivery platforms, bringing granular scalability and cost-efficiencies to those familiar with traditional, board-based designs.
Obtaining the software
With the exception of SIGTRAN and Prosody S, which are licensed, all protocols, including SIP and C7, are freely available via a software download utility for use with all of Aculab's board hardware. Developers can simply collect the protocol firmware, free of charge, when they need it, gaining a distinct advantage in terms of system cost and value per channel.
Access the download utility here
Regulatory approvals
Aculab has obtained many country specific, host independent regulatory approvals, such that Aculab's boards can be integrated into PC or server-based solutions without further telecom approvals being needed. In regions where this option is not available, Aculab has experience to offer in support of users seeking system level type approvals.
To discuss your requirements, contact your Account Manager or send an email to sales@aculab.com and one of our representatives will get right back to you.
Summary detail
A detailed summary of the available approvals and protocol information can be viewed as a PDF file. Please note that a number of protocols are used throughout the world, (like DPNSS, Q.SIG and SS7) and are indexed as 'Worldwide' in the tables.
IP
protocols SS7 protocol
conformance Host independent
approvals China Compulsory
Certification Worldwide
protocol coverage
protocols SS7 protocol
conformance Host independent
approvals China Compulsory
Certification Worldwide
protocol coverage
| Protocol | IETF Specification | Feature description |
|---|---|---|
| SIP (session initiation protocol) | RFC 3261 | Session initiation protocol SIP on UDP and TCP SIPS (SIP over TLS) |
| RFC 3262 | Reliable provisional responses | |
| RFC 3310 | SIP authentication | |
| RFC 2327 | Session description protocol (SDP) | |
| RFC 3665 | Basic call flow examples | |
| RFC 3666 | SIP/PSTN call flows | |
| RFC 3264 | Offer/answer model with SDP | |
| RFC 3725 | third party call control best practices | |
| RFC 3515 | the REFER method | |
| RFC 3204 | MIME media types for Q.SIG/ISUP | |
| RFC 2976 | INFO method | |
| RFC 3891 | Replaces header | |
| Draft-ietf-sipping-service-examples-09 | Hold and transfer | |
| Draft-ietf-sipping-cc-transfer-06.txt | Blind transfer for SIP | |
| RFC 3892 | Referred by header | |
| RFC 3261 | TCP support | |
| RFC 3581 | Symmetric signalling ports | |
| Draft-ietf-mmusic-sdescriptions-12 | Secure RTP support | |
| RFC 4028 | SIP session timers | |
| RFC 32651 | Subscribe/specific event notification1 | |
| RFC 3311 | UPDATE method | |
| RFC 3489 | STUN API1 | |
| MRCP (media resource control protocol) | MRCP v1, draft 7 | |
| MRCP v2, draft 11 | ||
| Protocol | ITU-T Specification | Feature description |
| H.323 | H.323 version 2 | Packet-based multimedia communications systems |
| H.225 version 2 | Including support for fast-start, non-standard data field (NSDF), RAS gatekeeper failover, H.323-ID addressing, NSM RAS and connectionless facility messages | |
| H.245 version 3 | Including support for H.245 tunnelling, third party hold, early H.245 and DTMF relay | |
| H.450.1; H.450.2; H.450.3; H.450.4; H.450.6 | Supplementary services (call transfer, call diversion, call waiting and call hold) | |
| H.324M1 | H.324M | Including support for H.223 |
| 3G-324M1 | Including support for H.223 | |
| Note: 1. Roadmap feature, contact your Account Manager for details | ||
| Protocol conformance | ||
|---|---|---|
| TCAP (transaction capabilities application part)2 4 | ITU Q.771-Q.774 (1996/white book); ANSI TCAP T1.114 1996; China TCAP GF011-95 | |
| SCCP (signalling connection control part)2 4 | ITU Q.711-Q.714 (1996/white book); ANSI SCCP T1.112 1996; China SCCP GF010-95 | |
| ISUP (ISDN user part)2 | ITU-T ISUP (1997/white book); ANSI ISUP T1.113 (1995); Q.767 International ISUP; China ISUP YDN-038 (1997); ETSI ISUP V4 (2001); UK ISUP (2001); user definable variants1 | |
| MTP 3 (message transfer part layer 3)2 | Q.704 (1996/white book); ANSI T1.111 (1996); China GF001-9001 (1990) | |
| MTP 2 (message transfer part layer 2)2 | Q.703 (1996/white book); ANSI T1.111 (1996); China GF001-9001 (1990) | |
| M3UA (message transfer part 3 user adaptation layer)3 | IETF RFC 4666; ETSI TS 102 142 V1.1.1 (2003-05) | |
| SCTP (stream control transmission protocol) | IETF RFC 2960; RFC 3257; RFC 4166 | |
|
Notes: 1 - Aculab's SS7 software enables user-configurable ISUP message formats through which other national and international variants can be defined to meet specific needs. 2 - These signalling protocols are offered under a cost free license when used with Aculab's cards in cPCI, PCI or PCIe form factor. 3 - M3UA signalling software is offered for a fee under the terms of a software license for use on a per host PC basis. 4 - The software supports the combination of ANSI TCAP with ITU SCCP (and vice versa), as required in some markets. | ||
| Country | Approved product | Protocol | Approval standard | Approval number | Additional notes | |
|---|---|---|---|---|---|---|
| Australia | All Prosody X boards with PMX/PMXC | Q.931/Q.932 | AS/ACIF S038 | Self declaration | E1 | |
| Australia | All PCI/cPCI boards with PM | Q.931/Q.932 |  | AS/ACIF S038 | Self declaration | E1 |
| Brazil | E1/T1 PCI with PM | Brazilian ISDN | | Anatel | 0030-06-1140 | E1 |
| Canada | Prosody X PCI with PMX/PMXC1 | Aculab T1 protocols | CS03 part 8 | 2789A-AC5200 | T1 | |
| Canada | All Prosody X and E1/T1 PCIe boards | Aculab T1 protocols | CS03 part 8 | 2789A-PCIEX | T1 — fitted with DSP for CAS/SS7 if applicable | |
| Canada | All PCI/cPCI boards with PM | Aculab T1 protocols | | CS03 part 8 | 2789A 12217 | T1 — fitted with DSP if applicable |
| China | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | Chinese ISDN | 12-7170-060345 | E1 | |
| China | E1/T1 PCI with PM | Q.931/Q.932 | | Chinese ISDN | 15-5288-020439 | E1 |
| EU-wide | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | TBR4 | Self declaration under RTTE | E1 | |
| EU-wide | All PCI/cPCI boards with PM | Q.931/Q.932 | | TBR4 | Self declaration under RTTE | E1 |
| Hong Kong | Prosody X PCI with 1 DSP and PMX/PMXC | ITU T1 | HKTA2015 | IN606049 | T1 | |
| Hong Kong | Prosody X PCI with 2 DSPs and PMX/PMXC | ITU T1 | HKTA2015 | IN606048 | T1 | |
| Hong Kong | Prosody X PCI with 4 DSPs and PMX/PMXC | ITU T1 | HKTA2015 | IN406047 | T1 | |
| Hong Kong | E1/T1 PCI with PM | ITU T1 | | HKTA2015 | IN403011 | T1 |
| India | Prosody X PCI | Q.931/Q.932 | TEC | TEC/NR/I/CTI-01/03/068.DEC07 | E1 | |
| India | Prosody X PCIe | Q.931/Q.932 | TEC | TEC/NR/I/CTI-01/03/069.DEC07 | E1 | |
| India | E1/T1 PCI with PM | Q.931/Q.932 | | TEC | TEC/WR/I/CTI-01/02/052.SEP 04 | E1 |
| Japan | Prosody X PCIe with DSP module | INS 1500 | Japan | T C 08-0002 205 | T1 | |
| Japan | Prosody X PCI with PMXC 1 | INS 1500 | Japan | 07225004/AA/00 | T1 | |
| Japan | Prosody X PCI with PMXC 2 | INS 1500 | Japan | 07225005/AA/00 | T1 | |
| Japan | Prosody X PCI with PMXC 4 | INS 1500 | Japan | 07225006/AA/00 | T1 | |
| Japan | Prosody X PCI with PMXC 8 | INS 1500 | Japan | 07225002/AA/00 | T1 | |
| Japan | E1/T1 PCI with PM | INS 1500 | | Japan | 04225006/AA/OO | T1 — fitted with DSP |
| Korea | E1/T1 PCI with PM | Q.931/Q.932 | | Korean requirements | TE-C99/K900-03-00093 | E1 |
| Malaysia | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | TPS-013-01 | CETS/394B/0506/T | E1 | |
| Malaysia | E1/T1 PCI with PM | Q.931/Q.932 | | TPS-013-01 | ISDA/48A/0603/S | E1 |
| Mexico | E1/T1 PCI with PM | Q.931/Q.932 | | Cofetel | RCPACAC04-712 | E1 |
| New Zealand | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | PTC 232 | PTC232/06/001 | E1 | |
| New Zealand | E1/T1 PCI with PM | Q.931/Q.932 | | PTC 232 | PTC220/02/029 | E1 |
| Singapore | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | IDA TS ISDN-PRA | G0373-06 | E1 | |
| Singapore | E1/T1 PCI with PM | Q.931/Q.932 | | iDAS ISDN2 | ISDN2-0631-2003 | E1 |
| South Africa | Prosody X PCIe with 1 DSP and 2 E1/T1 trunks | Q.931/Q.932 | TBR4 | TE-2008/110 | E1 | |
| South Africa | Prosody X PCIe with 2 DSPs and 4 E1/T1 trunks | Q.931/Q.932 | TBR4 | TE-2008/109 | E1 | |
| South Africa | Prosody X E1/T1 PCIe with 4 E1/T1 trunks | Q.931/Q.932 | TBR4 | TE-2008/111 | E1 | |
| South Africa | Prosody X PCI with PMX/PMXC | Q.931/Q.932 | TBR4 | SS-743.01 | E1 | |
| South Africa | E1/T1 PCI with PM | Q.931/Q.932 | | TBR4 | SS-425.01 | E1 |
| Ukraine | Prosody PCI with 2 DSPs and PM1/2/4 | Euro ISDN | | Ukraine | UA1 025.0132909-08 | E1 |
| Ukraine | Prosody X PCI with 1 DSP and PMX/PMXC | Euro ISDN | Ukraine | UA1 025.0132915-08 | E1 | |
| Ukraine | Prosody X PCI with 2 DSP and PMX/PMXC | Euro ISDN | Ukraine | UA1 025.0132914-08 | E1 | |
| Ukraine | Prosody X PCI with 4 DSP and PMX/PMXC | Euro ISDN | Ukraine | UA1 025.0132911-08 | E1 | |
| USA | Prosody X PCI with PMX/PMXC | Aculab T1 protocols | FCC part 68 | 5TCXDNANPMXPCIX | T1 — fitted with DSP if applicable | |
| USA | All PCI/cPCI boards with PM | Aculab T1 protocols | | FCC part 68 | 5TCXDNANPM4MODT1 | T1 — fitted with DSP if applicable |
|
Notes: 1. Protocols marked ' ' in the table are compatible with Aculab's Passive monitor products based upon E1/T1 PCI boards. In the case of Canada and the USA, the applicable protocols are T1 Q.931/Q.932-based ISDN protocols only. Aculab's 'p-monitor' firmware is required.2. Primary rate modules PM4/2/1 are used on E1/T1 PCI, and Passive monitor PCI boards. A PMX/PMXC module is used on Prosody X variants. A DSP 65 module is required for DTMF and CAS tone signalling (excluding Prosody X variants). View the product pages, contact your Account Manager or email sales@aculab.com for details of configuration options available. 3. EU-wide member states are: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, the Netherlands, United Kingdom (UK). Although not member states, Iceland, Norway and Switzerland have accepted EU telecommunications approvals. 4. All products are fully RoHS compliant and are Safety and EMC approved to meet all international certification schemes (e.g., CB, UL, CUL) and mandatory international standards. 5. Products approved for China also carry China Compulsory Certification; see the detail table by clicking the appropriate tab header above this table. |
||||||
| Country | Approved product | Approval standard | Approval number |
|---|---|---|---|
| China | Prosody X PCI | China Compulsory Certification | 2006021607000001 |
| E1/T1 PCI with PM | 2004011607105503 | ||
| Prosody PCI with PM | 2004011607105495 | ||
| Prosody cPCI with PM | 2004011607105497 |
| Country | Protocol | Protocol type | Additional notes | Aculab protocol stack | |
|---|---|---|---|---|---|
| Argentina | R2 CAS | CAS1 | R2T12 | ||
| Australia | TS014 | CCS | No longer supplied | AUSTEL-TS014 | |
| Australia | TS038 | CCS | ETS 300 | ||
| Australia | P2 | CAS1 | TS003/TPH1271/R2D | R2T12 | |
| Belgium | National R2 | CAS1 | R2T12 | ||
| Belgium | National R2 | DTMF CAS1 | BELGU | ||
| Brazil | Euro ISDN | CCS | ETS 300 | ||
| Brazil | MFC R2 | CAS1 | Brazil 5C | R2T12 | |
| Canada | T1 Robbed bit | CAS1 | T1RB | ||
| Chile | MFC R2 | CAS1 | R2T12 | ||
| China | R2 | CAS1 | China#1 | R2T12 | |
| China | Chinese ISDN | CCS | ETS300 | ||
| Colombia | R2 | CAS1 | R2T12 | ||
| Croatia | R2 | CAS1 | R2T12 | ||
| Czech Republic | R2 | CAS1 | R2T12 | ||
| Czech Republic | MFC R2 | CAS1 | Type K | R2T12 | |
| Denmark | National MFC R2 | CAS1 | R2DK | ||
| Egypt | MFC R2 | CAS1 | R2T12 | ||
| EU wide | Euro ISDN | CCS | ETS 300 | ||
| Finland | R2 | CAS1 | R2T12 | ||
| France | MF R1 Socotel | CAS1 | FMFS | ||
| France | VN3 | CCS | No longer supplied | VN3 | |
| France | VN6 | CCS | ETS 300 | ||
| Germany | 1tr6 | CCS | No longer supplied | 1tr6 | |
| Greece | OTE 4 | CAS1 | 4-bit CAS | OTE4 | |
| Greece | OTE 2 | CAS1 | 2-bit CAS | OTE2 | |
| Hong Kong | CR13 IDA-P | CCS | No longer supplied | ETS 300 | |
| Hong Kong | HKTA 2015 | CCS | ETS 300 | ||
| Hong Kong | HKT 2018 Robbed bit | CAS1 | T1HK; AMI or B8ZS encoding | T1HK | |
| India | MFC E&M | CAS1 | R2T12 | ||
| India | MFC R2 | CAS1 | Type 1/2/3 | R2T12 | |
| Indonesia | R2 (Q.421) | CAS1 | Ericsson loop signalling | R2T12 | |
| Indonesia | SMFC R2 | CAS1 | Semi-compelled | IEM | |
| Iran | R2 | CAS | 3-bit decadic | R2T12 | |
| Israel | ETS 300 | CCS | ETS 300 | ||
| Israel | MFC R2 | CAS1 | Israel R2 | R2T12 | |
| Italy | I701 | CAS1 | I701 | ||
| Japan | INS 1500 | CCS | INS1500 | ||
| Jordan | R2 | CAS1 | R2T12 | ||
| Korea | Euro ISDN | CCS | ETS 300 | ||
| Korea | R2 | CAS1 | R2T12 | ||
| Kuwait | R2 | CAS1 | R2T12 | ||
| Latvia | MFC R2 | CAS1 | R2T12 | ||
| Malaysia | MFC R2 | CAS1 | R2T12 | ||
| Malaysia | MFC R2 | CAS1 | IEM | ||
| Malta | MFC R2 | CAS1 | R2T12 | ||
| Mexico | R2 | CAS1 | R2T12 | ||
| Netherlands | ALS70D | CAS1 | T11-53E | ALSN/ALSU | |
| Netherlands | MFC R2 | CAS1 | R2T12 | ||
| New Zealand | TNA134 | CCS | Q.931 | ETS 300 | |
| Norway | National MFC R2 | CAS1 | R2T12 | ||
| Peru | MFC R2 | CAS1 | R2T12 | ||
| Philippines | R2 | CAS1 | R2T12 | ||
| Poland | EuroISDN | CCS | ETS 300 | ||
| Poland | MFC R2 | CAS1 | R2T12 | ||
| Portugal | MFC R2 | CAS1 | R2T12 | ||
| Sierra Leone | MFC R2 | CAS1 | R2T12 | ||
| Singapore | IDA TS ISDN2 | CCS | ETS 300 | ||
| Singapore | Fetex | CCS | FETEX | ||
| Singapore | MFC R2 | CAS1 | R2T12 | ||
| Singapore | MFC R2 | CAS1 | IEM | ||
| South Africa | Euro ISDN | CCS | ETS 300 | ||
| South Africa | MFC R2 | CAS1 | R2T12 | ||
| Spain | MF R1 Socotel | CAS1 | SMFS | ||
| Sweden | CAS extension EL7 | CAS1 | Ericsson ASB/voicemail | EL7 | |
| Sweden | P8 | CAS1 | P8 DDI and P7 non-DDI option | P8 | |
| Taiwan | MF R1 | CAS1 | Modified | T1RB | |
| thailand | National R2 DTMF | CAS1 | R2T12 | ||
| Turkey | R1 | CAS1 | E1LS | ||
| UK | DASS2 | CCS | DASS | ||
| UK | DPNSS | CCS | DPNSS | ||
| UK | BT/MCL Interconnect | CAS1 | Asymmetrical | BTMC | |
| UK | BT Callstream | CAS1 | SIN 205/356 | BTCU/BTCN | |
| UK | PD1 | CAS1 | MCL PD1/DC5A | PD1 | |
| USA | AT&T | CCS | tr41459 | ATT-T1 | |
| USA | DMS 100 | CCS | Nortel DMS (T1) | DMS100 | |
| USA | National ISDN 2 | CCS | NI1 and NI2 | NI2 | |
| USA | National ISDN2 | CCS | NFAS (with D-channel back-up) | NI2 | |
| USA | T1 robbed bit | CAS1 | T1RB | ||
| Worldwide (ex USA) | E1 line side CAS | CAS1 | AT&T Definity and Nortel Meridian | E1LS | |
| Worldwide | MFC R2 | CAS1 | Q.421/Q.441 | R2T12 | |
| Worldwide | SS5 | CAS1 | CCITT SS5 (C5) | SS5 | |
| Worldwide | Decadic CAS | CAS | Generic use with PBXs | R2T12 | |
| Worldwide | E&M type A | CAS1 | Ericsson DC5 and E&M options | EEMA | |
| Worldwide | 30Dli | CAS1 | NEC PA-30DTS | 30Dli | |
| Worldwide | SS7 | CCS | ITU-T: ISUP Q.767; TCAP Q.771-Q.774; SCCP Q.711- Q.714; MTP Q.703, Q.704, Q.707 | ISUP/TCAP | |
| Worldwide | Q.SIG | CCS | QSIG | ||
|
Notes: 1. A DSP 65 module is required for DTMF or CAS tone signalling with E1/T1 PCI and Passive monitor PCI boards. A PMXC is needed for SS7 and DTMF or CAS tone signalling with Prosody X variants. 2. Protocols marked ' ' in the table are compatible with Aculab's Passive Monitor products based upon the E1/T1 PCI and cPCI boards. In the case of Canada and the USA, the applicable protocols are T1 Q.931/Q.932-based ISDN protocols only. Aculab's 'p-monitor' firmware is required.3. Aculab's R2T1 firmware provides a generic MFC R2 protocol stack, which uses switches to establish specific national or signalling variants. See the individual protocol release notes available via the Aculab installation tool (AIT). 4. Many CAS protocols provide for selection of either decadic (dial pulse), DTMF or MFR1 or MFC R2 register signalling and a number of line signalling methods. See the individual protocol release notes. 5. the majority of protocols are balanced, meaning that the same protocol may be used at both user and network ends of a link. In some cases user and network ends are established by switches in the firmware. Some protocols are provided by means of separate firmware for user and network ends. See the individual protocol release notes. 6. Some protocols offer both DDI and non-DDI options. See the individual protocol release notes. 7. In some cases the source specification documentation is less than thorough in its treatment of the protocol, leaving operations open to interpretation. Aculab is grateful for any feedback regarding the use of any listed protocol. 8. If you cannot find the protocol you need listed here, we may be able to help, as often, particularly with CAS protocols, an existing variant can prove viable. Aculab's generic MFC R2 stack often proves suitable for use even in countries where it has not already been validated for use against a specification. Aculab are able to compare an existing protocol stack against your specification, or alternatively may be able to produce the required variant for you. Please contact your Account Manager or email sales@aculab.com to discuss your requirements. 9. Developers looking to use 'host independent' approved Aculab products in their complete CT systems should not require further telecoms approval for that system prior to network connection. |
|||||
