TCAP configuration - Revision history

Allyntree at 19:28, 24 April 2018

2018-04-24T19:28:06Z

← Older revision		Revision as of 15:28, 24 April 2018
Line 29:		Line 29:
	== References ==		== References ==
	*[http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part Wikipedia article]		*[http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part Wikipedia article]


	~~[[category:Needs revising]]~~

Ktrueman: added links

2009-09-09T19:56:18Z

added links

← Older revision		Revision as of 15:56, 9 September 2009
Line 4:		Line 4:
	== Prerequisites ==		== Prerequisites ==

	Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a ~~fully~~ sample application ~~provided~~ as with the Media Gateway application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API.		Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a full sample application as with the [[TB Media Gateway]] application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API.

	Prior to configuring TCAP support, you should have configured all relevant MTP2 and MTP3 information. You should also have a good idea of how you are going to use TCAP functionality once it is activated. This includes information related to SSN, such as destination, origin point codes, etc.		Prior to configuring TCAP support, you should have configured all relevant [[MTP2 Layer\|MTP2]] and [[MTP3 Layer\|MTP3]] information. You should also have a good idea of how you are going to use TCAP functionality once it is activated. This includes information related to [[SSN]], such as [[DPC\|destination]], [[OPC\|origin]] point codes, etc.


	== Steps ==		== Steps ==

	*The first step is to configure SCCP and TCAP via the Toolpack web portal.		*The first step is to configure SCCP and TCAP via the Toolpack web portal.
	*You configure SCCP in '''Global > Configurations > Hardware > SS7 > SCCP'''.		*You configure SCCP in '''Global > Configurations > Hardware > SS7 > SCCP'''.
Line 17:		Line 16:
	*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.		*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.
	*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack.		*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack.


			== Related actions ==
			*[[TCAP:Creating new transaction\|Creating new transaction]]
			*[[TCAP:Adding component portion\|Adding component portion]]
			*[[TCAP:Sending transaction and dialogue portions\|Sending transaction and dialogue portions]]
			*[[TCAP:Receiving component portion\|Receiving component portion]]
			*[[TCAP:Receiving transaction and dialogue portions\|Receiving transaction and dialogue portions]]
			*[[TCAP:Receiving transaction error indication\|Receiving transaction error indication]]


	== References ==		== References ==
	*[http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part Wikipedia article]		*[http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part Wikipedia article]


			[[category:Needs revising]]

Ktrueman: links

2009-07-08T20:03:40Z

links

← Older revision		Revision as of 16:03, 8 July 2009
Line 1:		Line 1:
	Starting with version 2.3, Toolpack fully exposes [[SCCP]] and [[TCAP]] stack functionality in the [[Toolpack]] [[web portal]], making it easier to access TCAP, as well as all new Toolpack features, programmatically.		Starting with version 2.3, Toolpack fully exposes [[SCCP]] and [[TCAP]] stack functionality in the [[Toolpack]] [[Web Portal\|web portal]], making it easier to access TCAP, as well as all new Toolpack features, programmatically.

Ktrueman at 20:03, 8 July 2009

2009-07-08T20:03:20Z

← Older revision		Revision as of 16:03, 8 July 2009
Line 1:		Line 1:
	~~This new release~~ fully exposes [[SCCP]] and [[TCAP]] stack functionality in the [[Toolpack]] [[web portal]], making it easier to access TCAP, as well as all new Toolpack features, programmatically.		Starting with version 2.3, Toolpack fully exposes [[SCCP]] and [[TCAP]] stack functionality in the [[Toolpack]] [[web portal]], making it easier to access TCAP, as well as all new Toolpack features, programmatically.

Ktrueman: added link to wikipedia

2009-07-08T20:02:46Z

added link to wikipedia

← Older revision		Revision as of 16:02, 8 July 2009
Line 17:		Line 17:
	*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.		*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.
	*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack.		*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack.


			== References ==
			*[http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part Wikipedia article]

Ktrueman at 20:52, 12 May 2009

2009-05-12T20:52:47Z

← Older revision		Revision as of 16:52, 12 May 2009
Line 1:		Line 1:
	This new release fully exposes [[SCCP]] and TCAP stack functionality in the [[Toolpack]] [[web portal]], making it easier to access [[TCAP]], as well as all new Toolpack features, programmatically.		This new release fully exposes [[SCCP]] and [[TCAP]] stack functionality in the [[Toolpack]] [[web portal]], making it easier to access TCAP, as well as all new Toolpack features, programmatically.

Ktrueman at 20:46, 12 May 2009

2009-05-12T20:46:12Z

← Older revision		Revision as of 16:46, 12 May 2009
Line 1:		Line 1:
			This new release fully exposes [[SCCP]] and TCAP stack functionality in the [[Toolpack]] [[web portal]], making it easier to access [[TCAP]], as well as all new Toolpack features, programmatically.

	~~== This new release fully exposes SCCP and TCAP stack functionality in the Toolpack web portal, making it easier to access TCAP, as well as all new Toolpack features, programmatically.~~

	~~'''~~Prerequisites~~'''~~		== Prerequisites ==

	Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a fully sample application provided as with the Media Gateway application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API.		Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a fully sample application provided as with the Media Gateway application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API.
Line 12:		Line 12:

	*The first step is to configure SCCP and TCAP via the Toolpack web portal.		*The first step is to configure SCCP and TCAP via the Toolpack web portal.
	*You configure SCCP in '''Global > Configurations > Hardware > SS7 > SCCP'''.~~''''''~~		*You configure SCCP in '''Global > Configurations > Hardware > SS7 > SCCP'''.
	*You configure TCAP support via '''Global > Configurations > Hardware > SS7 > TCAP'''.		*You configure TCAP support via '''Global > Configurations > Hardware > SS7 > TCAP'''.
	*The next step is to Activate the new configuration, which is performed in the configuration in '''Global > Systems'''. There you select the system to which you want to apply the configuration, clicking '''Edit''' besides its name. In the new page that opens, click '''Activate''' in the '''Active Configuration''' section.		*The next step is to Activate the new configuration, which is performed in the configuration in '''Global > Systems'''. There you select the system to which you want to apply the configuration, clicking '''Edit''' besides its name. In the new page that opens, click '''Activate''' in the '''Active Configuration''' section.
	*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.		*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.
	*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack. ==		*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack.

Ktrueman: New page: == This new release fully exposes SCCP and TCAP stack functionality in the Toolpack web portal, making it easier to access TCAP, as well as all new Toolpack features, programmatically. '...

2009-05-12T20:43:12Z

New page: == This new release fully exposes SCCP and TCAP stack functionality in the Toolpack web portal, making it easier to access TCAP, as well as all new Toolpack features, programmatically. '...

New page

== This new release fully exposes SCCP and TCAP stack functionality in the Toolpack web portal, making it easier to access TCAP, as well as all new Toolpack features, programmatically.

'''Prerequisites'''

Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a fully sample application provided as with the Media Gateway application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API.

Prior to configuring TCAP support, you should have configured all relevant MTP2 and MTP3 information. You should also have a good idea of how you are going to use TCAP functionality once it is activated. This includes information related to SSN, such as destination, origin point codes, etc.

== Steps ==

*The first step is to configure SCCP and TCAP via the Toolpack web portal.
*You configure SCCP in '''Global > Configurations > Hardware > SS7 > SCCP'''.''''''
*You configure TCAP support via '''Global > Configurations > Hardware > SS7 > TCAP'''.
*The next step is to Activate the new configuration, which is performed in the configuration in '''Global > Systems'''. There you select the system to which you want to apply the configuration, clicking '''Edit''' besides its name. In the new page that opens, click '''Activate''' in the '''Active Configuration''' section.
*Once SCCP and TCAP are configured, you can start your TCAP application using the tbx_ss7_ha_tcapctrl library.
*Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP_CTRL_” . For example, the TCAP user part configuration name is TCAP_ITU_6, then your application name must be TCAP_CTRL_TCAP_ITU_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack. ==