SAP
From TBwiki
(Difference between revisions)
(initial content) |
(added related actions) |
||
| Line 2: | Line 2: | ||
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). | ||
| + | |||
| + | |||
| + | == Related actions == | ||
| + | *[[Toolpack:Creating a SAP|Creating a SAP]] | ||
Revision as of 12:18, 13 July 2009
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).
