Voip Redundancy
From TBwiki
(Difference between revisions)
| Line 7: | Line 7: | ||
== Signaling Redundancy == | == Signaling Redundancy == | ||
| − | In the above example, we have configured two [[NAP]] Network Access Point that reaches the same SIP destination. In the event the ethernet interface VOIP0 went down, the <u>'''''NAP A''''' | + | In the above example, we have configured two [[NAP]] Network Access Point that reaches the same SIP destination. 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>. |
<br> | <br> | ||
| Line 13: | Line 13: | ||
== Media Redundancy == | == Media Redundancy == | ||
| − | The [[NAP]] is also associated to the media by assigning an UDP port range for the RTP. When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used. In the above example, if the <u>'''''NAP A'''''</u> | + | The [[NAP]] is also associated to the media by assigning an UDP port range for the RTP. When [[NAP]] is unavailable at the signaling level, the assigned RTP ports aren't being used. In the above example, if the <u>'''''NAP A'''''</u> then all new outgoing calls would then be using VOIP1 ethernet interface. |
Revision as of 16:10, 20 July 2010
Redundancy of both RTP and SIP can be achieved by configuring one NAP per VoIP interface for a specific remote proxy.
Signaling Redundancy
In the above example, we have configured two NAP Network Access Point that reaches the same SIP destination. In the event the ethernet interface VOIP0 went down, the NAP A would become unavailable, and thus routing would take place using NAP A.
Media Redundancy
The NAP is also associated to the media by assigning an UDP port range for the RTP. When NAP is unavailable at the signaling level, the assigned RTP ports aren't being used. In the above example, if the NAP A then all new outgoing calls would then be using VOIP1 ethernet interface.
