[cisco-voip] VoIP Failover Path

Alex ecralar at hotmail.com
Wed Feb 27 16:06:51 EST 2008


Without going into heavy-weighted solutions like Cisco Peformance Routing (where you can route VoIP traffic based on MOS http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps8787/product_data_sheet0900aecd806c4ee4.html ),
I believe you can reroute the active calls from PATH1 to PATH2 by using floating static routes with IP SLA to track connectivity and/or IPCIF/MOS across PATH1, and EEM to act on threshold-crossing events.
Rgds
Alex
  ----- Original Message ----- 
  From: Todd Simons 
  To: Alex ; cisco-voip at puck.nether.net 
  Sent: Wednesday, February 27, 2008 5:44 PM
  Subject: RE: [cisco-voip] VoIP Failover Path


  Thanks!

  I know about additional dial-peers, unfortunately you can only have one session target per dial peer.

   

   I found this about PSTN Fallback:

  http://www.cisco.com/en/US/docs/ios/12_2/12_2x/12_2xa/feature/guide/ft_pstn.html

   

  The PSTN Fallback feature and enhancement provide the following benefits: 

  .Automatically routes a call to an alternate destination when the data network is congested at the time of the call setup. 

  .Enables the service provider to give a reasonable guarantee about the quality of the conversation to its Voice over IP (VoIP) users at the time of call admission. 

  .Provides delay, jitter, and packet loss information for the configured IP addresses. 

  .Caches call values from previous calls. New calls do not have to wait for probe results before they are admitted. 

  .Enables a user-configurable cause code display that indicates the type of call rejection. 

   

  The PSTN Fallback feature has the following restrictions: 

  .When detecting network congestion, the PSTN fallback feature does nothing to the existing call. It affects only subsequent calls. 

  .Only a single ICPIF/delay-loss value is allowed per system. 

  .A small additional call setup delay can be expected for the first call to a new IP destination. 

  .PSTN fallback is supported for H.323 VoIP calls only.

   

   

   

  From: Alex [mailto:ecralar at hotmail.com] 
  Sent: Wednesday, February 27, 2008 11:32 AM
  To: Todd Simons; cisco-voip at puck.nether.net
  Subject: Re: [cisco-voip] VoIP Failover Path

   

  My memory can be rusty but I think you can do think using link-endpoint addresses as "session targets", also look into "PSTN fallback" for failover on bad quality.

  Rgds

  Alex

    ----- Original Message ----- 

    From: Todd Simons 

    To: cisco-voip at puck.nether.net 

    Sent: Wednesday, February 27, 2008 3:36 PM

    Subject: [cisco-voip] VoIP Failover Path

     

    All-

    We have two Cisco2801 routers that can connect to each other serial to serial, or Ethernet to Ethernet:

     

      /--S0--{path1}--S0--\

    GW1                   GW2

      \--E0--{path2}--E0--/  

     

    Currently PATH1 is our default path.  How can we setup PATH2 for a backup path for VoIP dialpeers?  I've investigated the preference value, but with the preference, what triggers the failover?  

     

    Will/Can active Calls be passed between PATH1 and PATH2 without dropping if PATH1 goes down?  

     

    If call quality on PATH1 is bad, will PATH2 be used, will/can active calls be moved??

     

    Thanks!

    ~Todd


    ## Scanned by Delphi Technology, Inc. ## 


----------------------------------------------------------------------------

    _______________________________________________
    cisco-voip mailing list
    cisco-voip at puck.nether.net
    https://puck.nether.net/mailman/listinfo/cisco-voip


  ## Scanned by Delphi Technology, Inc. ## 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080227/08b81119/attachment-0001.html 


More information about the cisco-voip mailing list