SAP
(→Related actions) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 6: | Line 6: | ||
| − | == Related actions == | + | == Related actions == |
| − | '''Refer to the appropriate Toolpack release:''' | + | |
| − | *[[Toolpack v2.2:Creating a SAP]] | + | '''Refer to the appropriate Toolpack release:''' |
| − | *[[Toolpack v2.3:Creating a SAP]] | + | |
| − | *[[Toolpack v2.4:Creating a SAP]] | + | *[[Toolpack v2.2:Creating a SAP]] |
| + | *[[Toolpack v2.3:Creating a SAP]] | ||
| + | *[[Toolpack_v2.3:Creating_a_SAP|Toolpack v2.4:Creating a SAP]] | ||
| + | *[http://docs.telcobridges.com/mediawiki/index.php/Web_Portal_Tutorial_Guide_v2.5#ISDN-SIP_Gateway_Configuration Toolpack v2.5:Creating a SAP]<br> | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
Latest revision as of 14:31, 21 November 2011
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).
The NAP allows for service access points (SAPs), ISDN stacks, and SS7 ISUP interfaces to be associated as a combined resource for one type of access. A NAP is used to represent a collection of voice endpoints, for example: a group of SS7 CICs, ISDN controlled timeslots, SIP outgoing proxy to a specific provider, and more. SAPs are, later in the configuration process, used to define how calls are routed out of the Tmedia system.
Related actions
Refer to the appropriate Toolpack release:
