SAP
From TBwiki
(Difference between revisions)
(added related actions) |
(more content) |
||
| Line 1: | Line 1: | ||
| − | + | The [[SAP|Service Access Point]] is used to bind the [[SIP]] stack with a transport server. Depending on the system configuration, multiple SAPS can be configured. | |
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 [[NAP|network access points]] (NAP). | 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 [[NAP|network access points]] (NAP). | ||
Revision as of 13:34, 13 July 2009
The Service Access Point is used to bind the SIP stack with a transport server. Depending on the system configuration, multiple SAPS can be configured.
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).
