A basic VoIP scenario, to ensure VoIP is operational in the event of Frame Relay failure, you simply need to point your session target IP addresses to the loopback interfaces on R1 and R4, which will still be reachable in the event of a failure over the ISDN. If you have configured this correctly as shown in Example 3-66 and Example 3-67, you have scored 2 points. Example 3-66. R1 VoIP Configurationdial-peer voice 1 pots destination-pattern 01256 port 1/0/0 ! dial-peer voice 01189 voip destination-pattern 01189 session target ipv4:10.4.4.4 Example 3-67. R4 VoIP Configurationdial-peer voice 1 pots destination-pattern 01189 port 1/1/0 ! dial-peer voice 1256 voip destination-pattern 01256 session target ipv4:10.1.1.1
To create a hunt group, you need to configure an additional pots dial-peer statement on R4 for the same number of 01189; by assigning preference values to each dial-peer you can manipulate which port answers the call first and that the secondary answers when the primary is in use. The lower the preference value is the higher the priority will be. If you have configured this as shown in Example 3-68, you have scored 2 points. Example 3-68. R4 Hunt Group Configurationdial-peer voice 1 pots preference 1 destination-pattern 01189 port 1/1/0 ! dial-peer voice 2 pots preference 2 destination-pattern 01189 port 1/1/1
By assigning a voice-class codec on R4's VoIP dial-peer, you can define which codec is used. If the first codec fails, you can define what the fallback codec is by assigning preferences. If you have configured this correctly as shown in Example 3-69, you have scored 3 points. Example 3-69. R4 Hunt Group Configurationvoice class codec 1 codec preference 1 g728 codec preference 2 g729r8 ! dial-peer voice 1189 voip destination-pattern 01189 voice-class codec 1 session target ipv4:10.4.4.4 |