Static NAT is more straight forward to configure so to do this you need to do the following:
When you do the NAT Translation just reference the Internal HSRP Group e.g:
ip nat inside source static tcp 10.0.0.55 3389 184.108.40.206 3855 redundancy HSRP-Internal extendable
Remember to do this on both Routers as they both must Match!
Dynamic NAT is done like the following:
You need to create a Stateful ID as you need to link the NAT pool to this ID. (Again same on both routers)
ip nat Stateful id 1
Define NAT Pool:
ip nat pool VOIP 220.127.116.11 18.104.22.168 netmask 255.255.255.192
Create the Access-List to define what matches this rule:
Extended IP access list VOIP
10 permit ip 10.5.0.0 0.0.0.255 any (35533 matches)
20 permit ip 10.15.0.0 0.0.0.255 any (5760 matches)
Now the Overload Statement:
ip nat inside source list VOIP pool VOXHUB-VOIP mapping-id 101 overload
Thats all there is too it!
If you do “Show ip nat translations” on the secondary router you will see the NAT translations replicated from the Primary!
I have used this on a PWAN project that has over 100 sites and the two main sites has VOIP phones that work on a 10.5.X.X and 10.15.X.X Network so I nat’ted them straight out using a unique public IP. Less hassle this way especially where SIP is concerned!
See Image below showing both Putty sessions open for Both Routers showing exactly the same NAT translations although only the Primary Router is active!