VoIP
(→TelcoBridges and VoIP: more content and links) |
Cboulanger (Talk | contribs) (→Supported SIP RFCs) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Voice over Internet Protocol (VoIP) is a means of transmitting voice calls over a packet-based transmission network. It | + | Voice over Internet Protocol (VoIP) is a means of transmitting voice calls over a packet-based transmission network. It uses [[SIP]], [[H.323]], or [[BICC]] as a [[Signaling protocols|signaling]]/control protocol. |
| − | + | ==TelcoBridges and VoIP == | |
| + | TelcoBridges' [[Tmedia]] and [[Tdev]] families of devices support VoIP via the SIP signaling protocol as well as via dedicated on-board hardware. This hardware is optional and can be configured at initial purchase or added later via mezzanine board upgrades. | ||
| + | At this time, TelcoBridges does not support VoIP signaling via the H.323 or BICC control protocols. | ||
| − | |||
| − | |||
| − | + | === Supported SIP RFCs === | |
| + | TelcoBridges supports the following [[RFC|RFCs]] for VoIP: | ||
| + | '''SIP''' | ||
| + | *RFC 3261 Session Initiate Protocol | ||
| + | *RFC 2976 SIP INFO Method | ||
| + | *RFC 3398 ISUP-SIP Mapping (*) | ||
| + | *RFC 3515 Refer Method (*) | ||
| + | *RFC 3578 Overlap (*) | ||
| + | *RFC 2327 Session Description Protocol | ||
| + | *RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing | ||
| + | *RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples | ||
| + | *RFC 3666 Public Switched Telephone Network (PSTN) Call Flows (*) | ||
| + | *RFC 3892 Referred-By Mechanism (*) | ||
| + | *RFC 3891 "Replaces" Header (*) | ||
| − | + | (*) TelcoBridges' SIP stack supports the parsing and implementation of the RFC. Not all system-level call flows are necessarily implemented in the routing engine. Contact TelcoBridges' technical support to enquiry about the implementation level of a specific call flow or RFC subsection. | |
| − | TelcoBridges supports the | + | |
| − | + | ||
| − | + | ||
== References == | == References == | ||
| Line 22: | Line 32: | ||
[[category:Glossary]] | [[category:Glossary]] | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 16:26, 27 August 2009
Voice over Internet Protocol (VoIP) is a means of transmitting voice calls over a packet-based transmission network. It uses SIP, H.323, or BICC as a signaling/control protocol.
TelcoBridges and VoIP
TelcoBridges' Tmedia and Tdev families of devices support VoIP via the SIP signaling protocol as well as via dedicated on-board hardware. This hardware is optional and can be configured at initial purchase or added later via mezzanine board upgrades.
At this time, TelcoBridges does not support VoIP signaling via the H.323 or BICC control protocols.
Supported SIP RFCs
TelcoBridges supports the following RFCs for VoIP:
SIP
- RFC 3261 Session Initiate Protocol
- RFC 2976 SIP INFO Method
- RFC 3398 ISUP-SIP Mapping (*)
- RFC 3515 Refer Method (*)
- RFC 3578 Overlap (*)
- RFC 2327 Session Description Protocol
- RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
- RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples
- RFC 3666 Public Switched Telephone Network (PSTN) Call Flows (*)
- RFC 3892 Referred-By Mechanism (*)
- RFC 3891 "Replaces" Header (*)
(*) TelcoBridges' SIP stack supports the parsing and implementation of the RFC. Not all system-level call flows are necessarily implemented in the routing engine. Contact TelcoBridges' technical support to enquiry about the implementation level of a specific call flow or RFC subsection.
