Voip Redundancy - Revision history

Sylvain Fontaine at 13:23, 21 July 2010

2010-07-21T13:23:41Z

2010-07-20T21:27:24Z

2010-07-20T20:41:27Z

2010-07-20T20:40:59Z

2010-07-20T20:30:14Z

2010-07-20T20:11:33Z

2010-07-20T20:10:50Z

2010-07-20T20:08:14Z

2010-07-20T20:07:56Z

2010-07-20T19:54:49Z

← Older revision		Revision as of 13:23, 21 July 2010
Line 1:		Line 1:
−	Redundancy of both RTP and SIP can be achieved by configuring one [[NAP]] per VoIP interface for a specific remote proxy.	+	Redundancy of both RTP and SIP can be achieved by configuring one [[NAP]] (Network Access Point) per VoIP interface for a specific remote proxy.

	[[Image:VoIP Redundancy 0.png\|400px\|VoIP Redundancy Topology]]		[[Image:VoIP Redundancy 0.png\|400px\|VoIP Redundancy Topology]]

@@ Line 9: / Line 9: @@
 == Media Redundancy  ==
-The [[NAP]] is also associated to the media by assigning an UDP&nbsp;port range for the RTP. &nbsp;When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used. &nbsp;In the above example, if the <u>'''''NAP A'''''</u> then all new outgoing calls would then be using VOIP1 ethernet interface.
+The [[NAP]] is also associated to the media by assigning an UDP&nbsp;port range for the RTP. &nbsp;When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used either. &nbsp;In the above example, if the <u>'''''NAP A'''''</u> signaling is down, then all new outgoing calls would then be using VOIP1 ethernet interface for RTP.
 == Routing ==

@@ Line 21: / Line 21: @@
 == NAP ==
-In VoIP, we normally have one [[NAP]] per remote sip proxy.  On a configuration where VoIP redundancy is used, we have two [[NAP]]s, one for each VoIP ethernet interface.
+On the VoIP side, we normally have one [[NAP]] per remote sip proxy.  On a configuration where VoIP redundancy is used, we have two [[NAP]]s, one for each VoIP ethernet interface.
 == Routes ==
 Since the number of [[NAP]]s is double for a peer SIP proxy, then the number of routes mays also be doubled.

@@ Line 13: / Line 13: @@
 == Routing ==
-In order for the routing engine to use both <u>'''''NAP A''''</u> and <u>'''''NAP A'''''</u>, we need to create one route for each [[NAP]].  All routes using unavailable [[NAP]] are ignored by the routing engine when routing takes place.
+To enable redundancy, we have to instruct the routing engine about the alternate route.  This accomplish by creating a route for a specific destination using <u>'''''NAP A'''''</u>, and another route, for the exact same destination using <u>'''''NAP A''''''</u>.
-[[NAP]] availability is a fetaure of [[Scriptable Routing Engine]].

@@ Line 2: / Line 2: @@
 [[Image:VoIP Redundancy 0.png|400px|VoIP Redundancy Topology]]
 == Signaling Redundancy  ==
 In the above example, we have configured two [[NAP]] Network Access Point that reaches the same SIP destination. &nbsp;In the event the ethernet interface VOIP0 went down, the <u>'''''NAP A'''''</u> would become unavailable, and thus routing would take place using <u>'''''NAP A''''''</u>.
 == Media Redundancy  ==
 The [[NAP]] is also associated to the media by assigning an UDP&nbsp;port range for the RTP. &nbsp;When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used. &nbsp;In the above example, if the <u>'''''NAP A'''''</u> then all new outgoing calls would then be using VOIP1 ethernet interface.

@@ Line 7: / Line 7: @@
 == Signaling Redundancy  ==
-In the above example, we have configured two [[NAP]] Network Access Point that reaches the same SIP destination. &nbsp;In the event the ethernet interface VOIP0 went down, the <u>'''''NAP A'''''</u would become unavailable, and thus routing would take place using '''<u>''NAP A'''</u>'''<u></u>''.''
+In the above example, we have configured two [[NAP]] Network Access Point that reaches the same SIP destination. &nbsp;In the event the ethernet interface VOIP0 went down, the <u>'''''NAP A'''''&lt;/u would become unavailable, and thus routing would take place using '''&lt;u&gt;''NAP A''''''</u<u></u>''.''
-−
 == Media Redundancy  ==
 The [[NAP]] is also associated to the media by assigning an UDP&nbsp;port range for the RTP. &nbsp;When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used. &nbsp;In the above example, if the <u>'''''NAP A'''''</u>&nbsp;then all new outgoing calls will be using VOIP1 ethernet interface.

@@ Line 1: / Line 1: @@
 Redundancy of both RTP and SIP can be achieved by configuring one [[NAP]] per VoIP interface for a specific remote proxy.
-[[Image:VoIP Redundancy 0.png|50%x50%px|VoIP Redundancy Topology]]
+[[Image:VoIP Redundancy 0.png|300px|VoIP Redundancy Topology]]
 <br>