[cisco-voip] Survivability for CVP VXML Standalone

[redsnapper]

Hi Ahmed, 

In our scenario, CVP is not involved with call signalling, only the VXML server component is used, but it looks like this makes it somewhat hard to manage the survivability.

PRI -> 2800 router -> VXML Script triggered from the incoming pots dial-peer -> play announcement & transfer the call to ip phone (via H.323)


  ----- Original Message ----- 
  From: Ahmed Elnagar 
  To: redsnapper 
  Cc: Cisco Voip 
  Sent: Tuesday, March 23, 2010 2:27 PM
  Subject: RE: [cisco-voip] Survivability for CVP VXML Standalone


  I did a similar setup "though I were not responsible for the CVP part" but we fallback to a local CME-SRST on the router that have the VXML script.we have a VOIP dial-peer pointing to the CVP when the WAN link is down another dial-peer takes over after the SIP message timer experies.we have the CallManager and CVP at the HQ and this setup is at the remote site.

   

  What is your setup look like??

   

   Best Regards;

    Ahmed Elnagar

    Senior Network PS Engineer

   

   

  Correction:

  service on pots dial peer is "CVPMedia" not "survive".

   

  dial-peer voice 3002 pots

  translation-profile incoming OUT

  service CVPMedia

  destination-pattern 300.

  incoming called-number 300.

  port 0/3/0:15

   

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

  From: "redsnapper" <redsnapper at gmail.com>

  To: "Cisco Voip" <cisco-voip at puck.nether.net>

  Sent: Tuesday, March 23, 2010 10:33 AM

  Subject: Survivability for CVP VXML Standalone

   

   

  > Hi,

  > 

  > We're planning using a VXML script for incoming PSTN calls, to play an 

  > announcement and make a transfer to a specific IP Phone in a branch. But, 

  > when the WAN link is down, calls are dropped with the default system error 

  > message. (critical_error.wav) We need to add survivability to this call 

  > flow, ie. if the vxml server is not reachable, it should bypass the script 

  > and directly forward to call to the IP phone specified.

  > 

  > CVP config guide says the following:

  > 

  > "On a Unified CVP Standalone call flow model, no special survivability 

  > dial-peer needs to be created. Survivability will automatically be invoked 

  > by the Unified CVP Standalone script if the "survive" service exists."

  > 

  > My configuration is:

  > 

  > application

  >  service CVPMedia flash:CVPSelfService.tcl

  >  param CVPSelfService-app IVR_Branch

  >  paramspace english language en

  >  paramspace english index 0

  >  param CVPSelfService-port 7000

  >  param CVPPrimaryVXMLServer 10.10.10.10

  >  paramspace english location flash:

  >  paramspace english prefix en

  > ...

  > ...

  > application

  > service survive flash:survivability.tcl

  > param open-hours-agent0 1200

  > param open-hours-time0 1234567:0800-20:00

  > ...

  > ...

  > dial-peer voice 3002 pots

  > translation-profile incoming OUT

  > service survive

  > destination-pattern 300.

  > incoming called-number 300.

  > port 0/3/0:15

  > !

  > ...

  > ...

  > 

  > 

  > But, survivability script doesn't seem to invoke when a call is placed 

  > when WAN link is down. So, again the system error message is played and 

  > the call is dropped.

  > 

  > Does anyone have an experience with survivability in a similar scenario?

  > 

  > Thanks,

  > 

  > Baris.

  > 

  > 

  > 

  > 

  > 

   

  _______________________________________________

  cisco-voip mailing list

  cisco-voip at puck.nether.net

  https://puck.nether.net/mailman/listinfo/cisco-voip


  Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100323/8c599c9c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1801 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100323/8c599c9c/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1806 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100323/8c599c9c/attachment-0001.jpe>