Cisco SA520 IP alias broken after FW upgrade

Question

We have a Cisco SA520 running on a Comcast 5 IP block. We just recently upgraded the firmware from 1.1.42 to 2.1.51 and now we are unable to use our IP aliases that we setup to route one server's traffic to a particular WAN IP Alias which is different from the rest of the network. Here is what we are trying to accomplish, and yes, it was working fine before the firmware upgrade:
"Server A"-> "External IP Alias A" (Email server)
"All other traffic on same subnet" -> "Default WAN IP" (computers and other servers)
Right now I have the WAN IP setup on the router to be the same IP as the alias we were using before, just to get the server on the right IP. Unfortunately that means all other traffic is on that IP now too.
I'd really like to separate the traffic on the network so we can keep all email traffic on its own WAN IP, and all other network traffic on its own WAN IP too.
What do I need to do to fix this? We originally had an IPV4 Rule in place which worked great. See the attached picture for an example of what worked before.
Thanks for your help!!
Kevin Cantrell

Answer 1

Hi,
I have exactly the same problem ! Although on a AS5350 running c5350-js-mz.123-4.T2.bin.
tried "isdn map address . plan isdn type national" on the serial interface. Did not work.
Also tried adding "isdn calling number ........" (8 digits). Did not work.
When debugging on SIP the CLID is being received from the SIP client.
Interesting that we have the same problem on the same software ? hopefully someone will give pointer as to which software that works or a workaround command.
Regards
Lasse