SIP Session Border Controller - Revision history

Dana: /* Configure Yate to be used as a SIP session border controller */

2013-05-27T07:27:13Z

‎Configure Yate to be used as a SIP session border controller

Dana: /* Configure Yate to be used as a SIP session border controller */

2013-03-22T12:50:23Z

‎Configure Yate to be used as a SIP session border controller

Dana: /* Configure Yate to be used as a SIP session border controller */

2013-03-22T12:49:30Z

‎Configure Yate to be used as a SIP session border controller

Dana: /* Why using session border controller? */

2013-03-22T11:34:24Z

‎Why using session border controller?

Dana at 11:12, 22 March 2013

2013-03-22T11:12:11Z

Dana at 10:34, 22 March 2013

2013-03-22T10:34:47Z

Dana at 14:39, 2 October 2012

2012-10-02T14:39:41Z

Dana: Created page with "== What's SIP Border Controller == So Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be u..."

2012-10-02T14:39:22Z

Created page with "== What's SIP Border Controller == So Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be u..."

New page

== What's SIP Border Controller ==

So Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be used like a '''SIP border controller'''.

You may wonder what exactly is a border controller?

A typical session border controller is used to overcome some of the problems that may appear in a VoIP communication by integrating it between the caller and the called party signaling path. Such problems can be of various types. The more important ones are like it follows:

The traversal of signal and media across a NAT or firewall border device can fail for various reasons. Let’s take them piece-by-piece.

First, there is a firewall problem, even it doesn’t apply every time and for every firewall. It is about the probability that the dynamically opening and closing of ports on incoming calls might just not work. The main problem is the Network Address Translation (NAT) one. Here is about the IP addresses that are inserted in the packets by the VoIP clients, which addresses belong to the private network behind the NAT server, and consequently can’t be routed outside it. The session border controller is positioned between the clients with these problems and solves them so that the traffic can be possible. There aren’t only the signaling packets the ones that are passing through the border controller but the media ones too.

Another reason to use a session border controller is due to different service providers for the clients, which states for a connection usually passing through many different codec hops. Here fits the border controller as a cheaper way to provide media translation and in addition also accounting information and security services.

A use for a session border controller is also to collect usage information for each session. This can be used to create Charge Detail Records (CDRs) based on various factors as media type, bandwidth used, account information, etc.

← Older revision		Revision as of 07:27, 27 May 2013
Line 29:		Line 29:
	Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support.		Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support.

−	To enable this feature you have to add in [[SIP Configuration File\|ysipchan.conf]] in section [general] ~~set~~ parameter ignorevia to yes.	+	To enable this feature you have to add in [[SIP Configuration File\|ysipchan.conf]] in section [general] parameter '''ignorevia''' to yes.

← Older revision		Revision as of 12:50, 22 March 2013
Line 29:		Line 29:
	Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support.		Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support.

−	To enable this feature you have to add in ysipchan.conf in section [general] set parameter ignorevia to yes.	+	To enable this feature you have to add in [[SIP Configuration File\|ysipchan.conf]] in section [general] set parameter ignorevia to yes.

← Older revision		Revision as of 12:49, 22 March 2013
Line 33:		Line 33:

	'''See also'''		'''See also'''
		+
		+	* [[SIP_SBC\|Yate as SIP Session Border Controller configuration]]

@@ Line 17: / Line 17: @@
 The main problem is the Network Address Translation (NAT) one. Here is about the IP addresses that are inserted in the packets by the VoIP clients, which addresses belong to the private network behind the NAT server, and consequently can't be routed outside it.
-===Why using session border controller?===
+===Why you use SIP session border controller?===
 The session border controller is positioned between the clients with these problems and solves them so that the traffic can be possible. There aren't only the signaling packets the ones that are passing through the border controller but the media ones too.
@@ Line 24: / Line 24: @@
 A use for a session border controller is also to collect usage information for each session. This can be used to create Charge Detail Records (CDRs) based on various factors as media type, bandwidth used, account information, etc.

← Older revision		Revision as of 14:39, 2 October 2012
Line 1:		Line 1:
−	== What's SIP Border Controller ==	+	== What's SIP Border Controller? ==

	So Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be used like a '''SIP border controller'''.		So Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be used like a '''SIP border controller'''.

@@ Line 1: / Line 1: @@
-Yate implements the Session Initiation Protocol for communication among others. Besides the SIP router functionality, Yate also can be used like a '''SIP border controller'''.
+Yate implements the '''S'''ession '''I'''nitiation '''P'''rotocol for communication among others. Besides the SIP router functionality, Yate also can be used like a '''SIP border controller'''.
-−
 == What's SIP Border Controller? ==
-A typical session border controller is used to overcome some of the problems that may appear in a VoIP communication by integrating it between the caller and the called party signaling path. Such problems can be of various types. The more important ones are like it follows:
+The main problem is the Network Address Translation (NAT) one. Here is about the IP addresses that are inserted in the packets by the VoIP clients, which addresses belong to the private network behind the NAT server, and consequently can't be routed outside it.
-The traversal of signal and media across a NAT or firewall border device can fail for various reasons. Let’s take them piece-by-piece.
+===Why using session border controller?===
-First, there is a firewall problem, even it doesn’t apply every time and for every firewall. It is about the probability that the dynamically opening and closing of ports on incoming calls might just not work. The main problem is the Network Address Translation (NAT) one. Here is about the IP addresses that are inserted in the packets by the VoIP clients, which addresses belong to the private network behind the NAT server, and consequently can’t be routed outside it. The session border controller is positioned between the clients with these problems and solves them so that the traffic can be possible. There aren’t only the signaling packets the ones that are passing through the border controller but the media ones too.
+The session border controller is positioned between the clients with these problems and solves them so that the traffic can be possible. There aren't only the signaling packets the ones that are passing through the border controller but the media ones too.
 Another reason to use a session border controller is due to different service providers for the clients, which states for a connection usually passing through many different codec hops. Here fits the border controller as a cheaper way to provide media translation and in addition also accounting information and security services.
 A use for a session border controller is also to collect usage information for each session. This can be used to create Charge Detail Records (CDRs) based on various factors as media type, bandwidth used, account information, etc.