SIP
(initial content) |
(→TelcoBridges and SIP) |
||
| Line 11: | Line 11: | ||
A conceptual illustration is provided below: | A conceptual illustration is provided below: | ||
| + | |||
| + | |||
| + | [[Image:SIP stack conceptual illustration.jpg| ]] | ||
== Related actions == | == Related actions == | ||
Revision as of 12:37, 13 July 2009
Toolpack provides support for signalling 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 media gateways support SIP signalling concurrently with SS7, ISDN and other signalling protocols.
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.
TelcoBridges and SIP
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:
