Call backup configuration example, Network requirements, Configuration procedure – H3C Technologies H3C MSR 5600 User Manual
Page 120
110
[RouterA-voice-dial-entity3000] address sip ip 20.1.1.2
[RouterA-voice-dial-entity3000] match-template 3000
[RouterA-voice-dial-entity3000] quit
# Configure the local number as 1000 for POTS entity 1000, and bind FXS interface line 1/0 to
the POTS entity.
[RouterA-voice-dial] entity 1000 pots
[RouterA-voice-dial-entity1000] line 1/0
[RouterA-voice-dial-entity1000] match-template 1000
2.
On Router B, configure the local number as 2000 for POTS entity 2000, and bind FXS interface
line 1/0 to the POTS entity.
[RouterB] voice-setup
[RouterB-voice] dial-program
[RouterB-voice-dial] entity 2000 pots
[RouterB-voice-dial-entity2000] line 1/0
[RouterB-voice-dial-entity2000] match-template 2000
3.
On Router C, configure the local number as 3000 for POTS entity 3000, and bind FXS interface
line 1/0 to the POTS entity.
[RouterC] voice-setup
[RouterC-voice] dial-program
[RouterC-voice-dial] entity 3000 pots
[RouterC-voice-dial-entity3000] line 1/0
[RouterC-voice-dial-entity3000] match-template 3000
Call backup configuration example
Network requirements
As shown in
, Router A and Router B are connected through two IP links. One of the two links
has a higher priority and serves as the primary link. Configure call backup so when the primary link goes
down, the backup link can take over.
Figure 46 Network diagram
Configuration procedure
1.
Configure Router A:
# Create VoIP entity 2000 with a priority of 1, configure the destination IP address as 10.1.1.2,
and configure the called number as 2000.
[RouterA] voice-setup
[RouterA-voice] dial-program
[RouterA-voice-dial] entity 2000 voip