SAP - Revision history

Luc Morissette at 18:31, 21 November 2011

2011-11-21T18:31:42Z

Luc Morissette: Added link to 2.5 configuration

2011-11-21T18:31:02Z

Added link to 2.5 configuration

Allyntree: /* Related actions */

2009-11-18T20:30:38Z

Related actions

Allyntree: /* Related actions */

2009-11-18T20:25:31Z

Related actions

Allyntree: /* Related actions */

2009-11-18T20:25:10Z

Related actions

Ktrueman: added link to CIC

2009-08-24T20:20:51Z

added link to CIC

Ktrueman: clean up

2009-08-10T20:23:41Z

clean up

Ktrueman: glossary

2009-07-16T20:11:34Z

glossary

Ktrueman at 17:31, 14 July 2009

2009-07-14T17:31:32Z

Ktrueman: more content

2009-07-14T17:30:49Z

@@ Line 12: / Line 12: @@
 *[[Toolpack v2.2:Creating a SAP]]
 *[[Toolpack v2.3:Creating a SAP]]
-*[[Toolpack v2.4: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]]

@@ 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]]
 [[Category:Glossary]]

@@ Line 10: / Line 10: @@
 *[[Toolpack v2.2:Creating a SAP]]
 *[[Toolpack v2.3:Creating a SAP]]
+*[[Toolpack v2.4:Creating a SAP]]
 [[Category:Glossary]]

@@ Line 8: / Line 8: @@
 == Related actions ==
 '''Refer to the appropriate Toolpack release:'''
-*[[Toolpack v2.2: Creating a SAP]]
+*[[Toolpack v2.2:Creating a SAP]]
-*[[Toolpack v2.3: Creating a SAP]]
+*[[Toolpack v2.3:Creating a SAP]]
 [[Category:Glossary]]

@@ Line 7: / Line 7: @@
 == Related actions ==
-*[[Toolpack:Creating a SAP|Creating a SAP]]
+'''Refer to the appropriate Toolpack release:'''
+*[[Toolpack v2.2: Creating a SAP]]
 [[Category:Glossary]]

← Older revision		Revision as of 20:20, 24 August 2009
Line 3:		Line 3:
	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).

−	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 [[Circuit ~~identifier codes~~\|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.	+	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 [[Circuit identification code\|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.

← Older revision		Revision as of 20:23, 10 August 2009
Line 3:		Line 3:
	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).

−	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 [[Circuit ~~Identifier Codes~~\|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.	+	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 [[Circuit identifier codes\|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.

← Older revision		Revision as of 20:11, 16 July 2009
Line 8:		Line 8:
	== Related actions ==		== Related actions ==
	*[[Toolpack:Creating a SAP\|Creating a SAP]]		*[[Toolpack:Creating a SAP\|Creating a SAP]]
		+
		+
		+
		+	[[Category:Glossary]]

@@ Line 3: / Line 3: @@
 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).
-The Network Access Point (NAP) allows for [[SAP|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 [[Circuit Identifier Codes|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.
+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 [[Circuit Identifier Codes|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 ==
 *[[Toolpack:Creating a SAP|Creating a SAP]]