SIGTRAN pricing model 2011 - Revision history

Luc Morissette: Updated page to remove 'pricing'

2022-07-19T18:53:57Z

Updated page to remove 'pricing'

← Older revision		Revision as of 14:53, 19 July 2022
Line 1:		Line 1:
	~~Pricing for~~ TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of SS7 relay and termination.		{{DISPLAYTITLE:SIGTRAN Implementation}}
			TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of SS7 relay and termination.

	The relay concept is where the SS7 signaling received from MTP2 links is forwarded directly to SIGTRAN peer(s).		The relay concept is where the SS7 signaling received from MTP2 links is forwarded directly to SIGTRAN peer(s).
Line 18:		Line 19:

	== Other details ==		== Other details ==
	* The SIGTRAN Relay software license enables: 64 M2UA links, ~~up to~~ 20 M3UA-SG links and 64 IUA links. (SS7 links must be purchased separately)		* The SIGTRAN Relay software license enables up to 64 M2UA links, 20 M3UA-SG links and 64 IUA links. (SS7 links must be purchased separately)
	* The SIGTRAN Termination software license enables: 64 M2PA links and ~~up to~~ 20 M3UA-IPSP links.		* The SIGTRAN Termination software license enables up to 64 M2PA links and 20 M3UA-IPSP links.
	*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.

	<br>		<br>

Sylvain Fontaine at 13:59, 3 August 2012

2012-08-03T13:59:03Z

← Older revision		Revision as of 09:59, 3 August 2012
Line 5:		Line 5:
	[[Image:Sigtran_Relay.jpeg\|600px]]		[[Image:Sigtran_Relay.jpeg\|600px]]

	~~In the above example,~~ SIGTRAN is used to RELAY ~~the~~ SS7 to the peer using either M2UA or M3UA-SG, without local processing of SS7 messages.		SIGTRAN is used to RELAY SS7 signaling to the peer using either M2UA or M3UA-SG, without local processing of SS7 messages.

	<br />		<br />

Sylvain Fontaine at 13:57, 3 August 2012

2012-08-03T13:57:43Z

← Older revision		Revision as of 09:57, 3 August 2012
Line 13:		Line 13:
	[[Image:Sigtran_Termination.jpeg\|600px]]		[[Image:Sigtran_Termination.jpeg\|600px]]

	The SIGTRAN termination ~~in this context~~ is used to receive SS7 signaling on the gateway for local processing (ISUP,SCCP,MTP3 routing).		The SIGTRAN termination is used to receive SS7 signaling on the gateway for local processing (ISUP,SCCP,MTP3 routing).

	<br>		<br>

Sylvain Fontaine at 13:56, 3 August 2012

2012-08-03T13:56:53Z

← Older revision		Revision as of 09:56, 3 August 2012
Line 5:		Line 5:
	[[Image:Sigtran_Relay.jpeg\|600px]]		[[Image:Sigtran_Relay.jpeg\|600px]]

	In the above example, SIGTRAN is used to RELAY the SS7 to the peer using either M2UA or M3UA-SG, without local processing.		In the above example, SIGTRAN is used to RELAY the SS7 to the peer using either M2UA or M3UA-SG, without local processing of SS7 messages.

	<br />		<br />

Sylvain Fontaine at 13:55, 3 August 2012

2012-08-03T13:55:44Z

← Older revision		Revision as of 09:55, 3 August 2012
Line 5:		Line 5:
	[[Image:Sigtran_Relay.jpeg\|600px]]		[[Image:Sigtran_Relay.jpeg\|600px]]

	In the above example~~, a single TMedia is connected to one SIGTRAN peer. In this context~~, SIGTRAN is used to RELAY the SS7 ~~(MTP2)~~ to the peer using either M2UA or M3UA-SG~~. There is no ISUP or SCCP~~ processing ~~on the gateway itself~~.		In the above example, SIGTRAN is used to RELAY the SS7 to the peer using either M2UA or M3UA-SG, without local processing.

			<br />

	A termination corresponds to a link between two unique end-points. An example is provided below.		A termination corresponds to a link between two unique end-points. An example is provided below.
Line 11:		Line 13:
	[[Image:Sigtran_Termination.jpeg\|600px]]		[[Image:Sigtran_Termination.jpeg\|600px]]

	The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for ISUP ~~processing~~, ~~or to connect to M3UA-IPSP peer(s~~) ~~for SCCP processing~~.		The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for local processing (ISUP,SCCP,MTP3 routing).

	<br>		<br>

Sylvain Fontaine at 16:59, 2 August 2012

2012-08-02T16:59:59Z

← Older revision		Revision as of 12:59, 2 August 2012
Line 1:		Line 1:
	Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination~~, with a license required for each termination. A termination corresponds to a link between two unique end-points. An example is provided below~~.		Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of SS7 relay and termination.

	[[Image:~~Sigtran_Termination~~.jpeg\|600px]]		The relay concept is where the SS7 signaling received from MTP2 links is forwarded directly to SIGTRAN peer(s).

			[[Image:Sigtran_Relay.jpeg\|600px]]

			In the above example, a single TMedia is connected to one SIGTRAN peer. In this context, SIGTRAN is used to RELAY the SS7 (MTP2) to the peer using either M2UA or M3UA-SG. There is no ISUP or SCCP processing on the gateway itself.

	~~In the above example, a single TMedia is connected to two other SIGTRAN peers. Each connected stream~~ corresponds to a ~~'termination'. These are identified as Termination #1 and Termination #2. A single Termination can be multi~~-~~homed or not~~. ~~The SIGTRAN termination in this context~~ is ~~used to receive SS7 signaling on the gateway for ISUP processing~~.		A termination corresponds to a link between two unique end-points. An example is provided below.

	[[Image:~~Sigtran_Relay~~.jpeg\|600px]]		[[Image:Sigtran_Termination.jpeg\|600px]]

	~~In the above example, a single TMedia is connected to one~~ SIGTRAN ~~peers, a soft switch~~ in ~~this case. In~~ this context~~, SIGTRAN~~ is used to ~~RELAY the~~ SS7 ~~(MTP2) to~~ the ~~peer using either M2UA~~ or M3UA~~. There is no ISUP~~ processing ~~on the gateway itself~~.		The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for ISUP processing, or to connect to M3UA-IPSP peer(s) for SCCP processing.

	<br>		<br>

	== Other details ==		== Other details ==
			* The SIGTRAN Relay software license enables: 64 M2UA links, up to 20 M3UA-SG links and 64 IUA links. (SS7 links must be purchased separately)
	*~~TelcoBridges' pricing model for~~ SIGTRAN ~~does not distinguish between [[M2PA]], [[~~M2UA]], ~~or [[~~M3UA~~]]. All three of these protocols are included in the association license~~.		* The SIGTRAN Termination software license enables: 64 M2PA links and up to 20 M3UA-IPSP links.
	**Due to network design considerations specific to the use of M3UA, it may be necessary to ~~purchase additional~~ M3UA ~~associations for a given pair of endpoints~~.
	*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.		*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.

Sylvain Fontaine at 17:08, 14 November 2011

2011-11-14T17:08:24Z

← Older revision		Revision as of 13:08, 14 November 2011
Line 1:		Line 1:
	Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination, with a license required for each termination. An termination corresponds to a link between two unique end-points. An example is provided below.		Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination, with a license required for each termination. A termination corresponds to a link between two unique end-points. An example is provided below.

	[[Image:Sigtran_Termination.jpeg\|600px]]		[[Image:Sigtran_Termination.jpeg\|600px]]

	In ~~this~~ example, a single TMedia is connected to two other SIGTRAN peers. Each connected stream corresponds to an 'termination'. These are identified as Termination #1 and Termination #2. A single Termination can be multi-homed or not. The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for ISUP processing.		In the above example, a single TMedia is connected to two other SIGTRAN peers. Each connected stream corresponds to a 'termination'. These are identified as Termination #1 and Termination #2. A single Termination can be multi-homed or not. The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for ISUP processing.

	[[Image:Sigtran_Relay.jpeg\|600px]]		[[Image:Sigtran_Relay.jpeg\|600px]]

	In ~~this~~ example, a single TMedia is connected to one SIGTRAN peers, a soft switch in this case. In this context, SIGTRAN is used to RELAY the SS7 (MTP2) to the peer using either M2UA or M3UA. There is no ISUP processing on the gateway itself.		In the above example, a single TMedia is connected to one SIGTRAN peers, a soft switch in this case. In this context, SIGTRAN is used to RELAY the SS7 (MTP2) to the peer using either M2UA or M3UA. There is no ISUP processing on the gateway itself.

	<br>		<br>

Sylvain Fontaine at 16:57, 14 November 2011

2011-11-14T16:57:18Z

← Older revision		Revision as of 12:57, 14 November 2011
Line 1:		Line 1:
	Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination, with a license required for each termination. An termination corresponds to a link between two unique end-points. An example is provided below.		Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination, with a license required for each termination. An termination corresponds to a link between two unique end-points. An example is provided below.

			[[Image:Sigtran_Termination.jpeg\|600px]]

	~~[[Image:SIGTRAN_Relay~~.~~jpeg\|600px]]~~		In this example, a single TMedia is connected to two other SIGTRAN peers. Each connected stream corresponds to an 'termination'. These are identified as Termination #1 and Termination #2. A single Termination can be multi-homed or not. The SIGTRAN termination in this context is used to receive SS7 signaling on the gateway for ISUP processing.

	~~In this example, a single SIGTRAN host (IP address~~: 192.128.1.1) is connected to two other SIGTRAN hosts via primary connections (for a total of 2 connections). Each connection corresponds to an 'association'. These are identified as Association #1 and Association #2. An association may be thought of as a 'link-equivalent' to borrow the terminology used by other vendors in the marketplace.		[[Image:Sigtran_Relay.jpeg\|600px]]

	~~Association #3 corresponds~~ to the ~~use of a redundant IP link between two existing endpoints~~.		In this example, a single TMedia is connected to one SIGTRAN peers, a soft switch in this case. In this context, SIGTRAN is used to RELAY the SS7 (MTP2) to the peer using either M2UA or M3UA. There is no ISUP processing on the gateway itself.

			<br>

	== Other details ==		== Other details ==
	*TelcoBridges' pricing model for SIGTRAN does not distinguish between [[M2PA]], [[M2UA]], or [[M3UA]]. All three of these protocols are included in the association license.
	**Due to network design considerations specific to the use of M3UA, it may be necessary to purchase additional M3UA associations for a given pair of endpoints.		*TelcoBridges' pricing model for SIGTRAN does not distinguish between [[M2PA]], [[M2UA]], or [[M3UA]]. All three of these protocols are included in the association license.
			**Due to network design considerations specific to the use of M3UA, it may be necessary to purchase additional M3UA associations for a given pair of endpoints.
	*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.		*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.

			<br>

			== References ==

	~~== References ==~~
	*[[SIGTRAN]]		*[[SIGTRAN]]

Sylvain Fontaine at 16:45, 14 November 2011

2011-11-14T16:45:25Z

← Older revision		Revision as of 12:45, 14 November 2011
Line 2:		Line 2:


	[[Image:~~SIGTRAN pricing schematic~~.~~jpg\|px~~\|600px]]		[[Image:SIGTRAN_Relay.jpeg\|600px]]


	In this example, a single SIGTRAN host (IP address: 192.128.1.1) is connected to two other SIGTRAN hosts via primary connections (for a total of 2 connections). Each connection corresponds to an 'association'. These are identified as Association #1 and Association #2. An association may be thought of as a 'link-equivalent' to borrow the terminology used by other vendors in the marketplace.		In this example, a single SIGTRAN host (IP address: 192.128.1.1) is connected to two other SIGTRAN hosts via primary connections (for a total of 2 connections). Each connection corresponds to an 'association'. These are identified as Association #1 and Association #2. An association may be thought of as a 'link-equivalent' to borrow the terminology used by other vendors in the marketplace.

Sylvain Fontaine: Created page with 'Pricing for TelcoBridges' implementation of SIGTRAN is based on the concept of termination, with a license required for each termination. An termination corresponds to a link…'

2011-11-14T16:43:10Z

Created page with 'Pricing for TelcoBridges' implementation of SIGTRAN is based on the concept of termination, with a license required for each termination. An termination corresponds to a link…'

New page

Pricing for TelcoBridges' implementation of [[SIGTRAN]] is based on the concept of termination, with a license required for each termination. An termination corresponds to a link between two unique end-points. An example is provided below.

[[Image:SIGTRAN pricing schematic.jpg|px|600px]]

In this example, a single SIGTRAN host (IP address: 192.128.1.1) is connected to two other SIGTRAN hosts via primary connections (for a total of 2 connections). Each connection corresponds to an 'association'. These are identified as Association #1 and Association #2. An association may be thought of as a 'link-equivalent' to borrow the terminology used by other vendors in the marketplace.

Association #3 corresponds to the use of a redundant IP link between two existing endpoints.

== Other details ==
*TelcoBridges' pricing model for SIGTRAN does not distinguish between [[M2PA]], [[M2UA]], or [[M3UA]]. All three of these protocols are included in the association license.
**Due to network design considerations specific to the use of M3UA, it may be necessary to purchase additional M3UA associations for a given pair of endpoints.
*The SIGTRAN pricing model does not feature any restrictions on the number of messages or transactions per second. Users are only limited in their use of SIGTRAN by the capacity of the underlying IP link and the telecommunications hardware used in the system. Increasing the capacity of the IP link or the hardware will enable the user to achieve higher message counts per second without requiring additional SIGTRAN associations.

== References ==
*[[SIGTRAN]]