ip nat pool call-id-pool 192.168.201.1 192.168.201.254 netmask 255.255.255.0
ip nat inside source list 111 pool call-id-pool
At present access-list 111 permits any to the external ip so anything going there gets NAT'd.
This works fine (the call connects but I just don't get any sound) apart from one small hitch. The call comes in from the outside, gets translated, hits the router and the router connects it to our PSTN network. All is fine until the router tries to connect the media stream and 'reply' to the initial connection. My FW sees this as a reply and allows it through but when it gets to the edge router (with the SBC on it) a new connection is seemingly created and hence the FW at the client end doesn't allow this new connection through (the connection does have the correct source/destination but is just obviously not seen by the FW as part of the original conversation).
Why would unNATing a packet mean that it's no longer seen as part of the original conversation by the FW at the other end?
If I set my access list on the client FW to allow new connections then everything works and the media stream connects but I can't get customers to do that.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...