12-06-2010 11:39 AM - edited 03-21-2019 03:21 AM
Can I configure the UC500 to to have do policy based routing for failover between two ISPs, using Sub Interfaces on the WAN (F0/0) interface and then setting ip sla with tracking.
The goal is to set up a redundant path to our SIP service provider.
Solved! Go to Solution.
12-06-2010 11:48 AM
Not supported on the UC500 with CCA. Dual WAN and multiple SIP providers is on the roadmap.
12-06-2010 11:55 AM
Perhaps, or maybe an SA500 which has dual WAN. But neither will give you dual SIP providers.
12-06-2010 11:48 AM
Not supported on the UC500 with CCA. Dual WAN and multiple SIP providers is on the roadmap.
12-06-2010 11:52 AM
In the meanwhile is the solution to put an 1811 in front of the UC500?
- Pete
12-06-2010 11:55 AM
Perhaps, or maybe an SA500 which has dual WAN. But neither will give you dual SIP providers.
12-06-2010 11:58 AM
Steven:
Thank you. Not looking for dual SIP providers, just redundant paths from different ISPs.
- Pete
09-13-2011 12:59 PM
Hi Steven
Is it possible to configure dual WAN or 2 different Sip trunks on UC520 TO THIS DATE
THANKS
SHAMEER
09-14-2011 11:48 AM
It is still not possible with CCA, however it is possible in CLI (via IP SLA).
09-14-2011 03:31 PM
Hi Shameer,
The latest version of CCA should support Dual SIP trunks, but not Dual WAN.
Cheers,
David.
09-16-2011 03:11 PM
None of our clients look at the internet as business critical.
We have no need for reliable internet connectivity nor automatic failover capabilities in our Cisco UC540 products.
We dont want faxes delievered directly to our email InBox via our SIP trunks, either. We like love the tired old thermal printer in the corner and the rolls of paper it feeds on.
Thank you.
09-19-2011 10:33 AM
I have been deploying a Cisco 1811 or Cisco 891, in front of the UC540/UC560 appliance, to provide dual WAN redundancy. Essentially the goal was to have a dedicated aDSL for SIP (Provided by our SIP provider) and a dedicated connection for the remaining IP traffic. If either of the connections fail, traffic is automatically rolled over to the working connection.
I utilized the following technologies to provide seamless failover between ISP’s.
IP SLA – To send ICMP echo packets to downstream routers
PBR/Tracking – Source based routing to direct traffic out the appropriate ISP. Tracking is used to track the states of the IP SLA probes, essentially if a specified amount of time goes by without a response from the downstream router, the connection is presumed down and PBR stops sending traffic out that interface.
EEM – Used to clear the dynamic NAT entries after failover. This was a critical feature for us. Without EEM the dynamic NAT entries remained in the NAT table and caused traffic to be directed out the incorrect interface. I also typically use EEM to send an email status notification indicating the connection is down.
Note the Cisco SR500 series does NOT support EEM. I initially wanted to use the Cisco SR500 with a sub interface for each WAN connection.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide