SIP
(more content and editing) |
(clean-up) |
||
| Line 21: | Line 21: | ||
== Related actions == | == Related actions == | ||
*[[Creating a SIP Signaling Stack]] | *[[Creating a SIP Signaling Stack]] | ||
| + | |||
== References == | == References == | ||
[http://en.wikipedia.org/wiki/Session_Initiation_Protocol Wikipedia article] | [http://en.wikipedia.org/wiki/Session_Initiation_Protocol Wikipedia article] | ||
Revision as of 14:59, 13 July 2009
Session Initiation Protocol, more commonly known as SIP, is a signaling protocol for packet-based networks and is commonly used, along with H.323 to provide signaling for voice over IP (VoIP) communications.
TelcoBridges and SIP
Toolpack provides support for signaling using the Session Initiation Protocol, more commonly known as SIP, for voice over IP (VoIP) communications. SIP may be used in conjunction with various voice codecs for the media component of a call. TelcoBridges Tmedia media gateways and Tdev development platforms support SIP signaling concurrently with SS7, ISDN and other signaling protocols.
SIP signaling stacks are configured for IP applications and for each Tmedia or Tdev unit requiring SIP signaling.
Based upon your system requirements, you can configure a SIP stack to carry signaling traffic over multiple transport servers, which are IP endpoints comprised of: protocol type (TCP/UDP), port number, IP interface, IP address, IP name, and SAPs.
A conceptual illustration is provided below:
While TelcoBridges media gateways can perform multiple simultaneous functions such as switching and transcoding as well as deliver value-added services such as IVR or conferencing, they can also be configured to perform a single function. In this case, it is possible to configure TelcoBridges media gateway to act as a SIP gateway.
Related actions
