SIP
(more content) |
|||
| Line 2: | Line 2: | ||
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]]. | 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 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. SAPs are services access points derived from one or more transport servers. For example, signaling traffic to a proxy server can be transported over UDP, while another service can be transported over TCP. A distinct transport server (IP endpoint) is | ||
| + | configured for each of these applications. In turn service access points are associated with one or more transport servers so that they can be easily and flexibly assigned to network access points (NAP). | ||
| + | |||
| + | A conceptual illustration is provided in figure 10.1 on page 92. | ||
| + | |||
| + | |||
| + | == Related actions == | ||
== 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 10:35, 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 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. SAPs are services access points derived from one or more transport servers. For example, signaling traffic to a proxy server can be transported over UDP, while another service can be transported over TCP. A distinct transport server (IP endpoint) is configured for each of these applications. In turn service access points are associated with one or more transport servers so that they can be easily and flexibly assigned to network access points (NAP).
A conceptual illustration is provided in figure 10.1 on page 92.
