<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18876"><!--[if !mso]>
<STYLE>v\:* {
        BEHAVIOR: url(#default#VML)
}
o\:* {
        BEHAVIOR: url(#default#VML)
}
w\:* {
        BEHAVIOR: url(#default#VML)
}
.shape {
        BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.5pt;
        font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue bgColor=#ffffff vLink=purple>
<DIV><FONT size=2 face=Arial>Hi Ahmed, </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>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.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>PRI -> 2800 router -> VXML Script
triggered from the incoming pots dial-peer -> play announcement &
transfer the call to ip phone (via H.323)</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=ahmed_elnagar@rayacorp.com
href="mailto:ahmed_elnagar@rayacorp.com">Ahmed Elnagar</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=redsnapper@gmail.com
href="mailto:redsnapper@gmail.com">redsnapper</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">Cisco Voip</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 23, 2010 2:27
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] Survivability
for CVP VXML Standalone</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoPlainText>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.<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>What is your setup look like??<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN
style="FONT-SIZE: 10pt"> </SPAN><SPAN style="FONT-SIZE: 10.5pt">Best
Regards;<o:p></o:p></SPAN></P>
<P style="BACKGROUND: white" class=MsoNormal><SPAN
style="FONT-SIZE: 10.5pt"> Ahmed Elnagar<o:p></o:p></SPAN></P>
<P style="BACKGROUND: white" class=MsoNormal><SPAN
style="FONT-SIZE: 10.5pt"> Senior Network PS
Engineer<o:p></o:p></SPAN></P>
<P style="BACKGROUND: white" class=MsoNormal><SPAN
style="FONT-SIZE: 10.5pt"> <IMG id=Picture_x0020_0
alt=ccie_voice_large.gif
src="cid:001801caca8b$be479e70$ee06f20a@fw.teknoloji.com.tr" width=63
height=63><IMG id=Picture_x0020_1 alt=ccvp_voice_large.gif
src="cid:001901caca8b$be479e70$ee06f20a@fw.teknoloji.com.tr" width=63
height=63><o:p></o:p></SPAN></P></DIV>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>Correction:<o:p></o:p></P>
<P class=MsoPlainText>service on pots dial peer is "CVPMedia" not
"survive".<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>dial-peer voice 3002 pots<o:p></o:p></P>
<P class=MsoPlainText>translation-profile incoming OUT<o:p></o:p></P>
<P class=MsoPlainText>service CVPMedia<o:p></o:p></P>
<P class=MsoPlainText>destination-pattern 300.<o:p></o:p></P>
<P class=MsoPlainText>incoming called-number 300.<o:p></o:p></P>
<P class=MsoPlainText>port 0/3/0:15<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>----- Original Message ----- <o:p></o:p></P>
<P class=MsoPlainText>From: "redsnapper"
<redsnapper@gmail.com><o:p></o:p></P>
<P class=MsoPlainText>To: "Cisco Voip"
<cisco-voip@puck.nether.net><o:p></o:p></P>
<P class=MsoPlainText>Sent: Tuesday, March 23, 2010 10:33 AM<o:p></o:p></P>
<P class=MsoPlainText>Subject: Survivability for CVP VXML
Standalone<o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P class=MsoPlainText>> Hi,<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> We're planning using a VXML script for incoming
PSTN calls, to play an <o:p></o:p></P>
<P class=MsoPlainText>> announcement and make a transfer to a specific IP
Phone in a branch. But, <o:p></o:p></P>
<P class=MsoPlainText>> when the WAN link is down, calls are dropped with
the default system error <o:p></o:p></P>
<P class=MsoPlainText>> message. (critical_error.wav) We need to add
survivability to this call <o:p></o:p></P>
<P class=MsoPlainText>> flow, ie. if the vxml server is not reachable, it
should bypass the script <o:p></o:p></P>
<P class=MsoPlainText>> and directly forward to call to the IP phone
specified.<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> CVP config guide says the following:<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> "On a Unified CVP Standalone call flow model, no
special survivability <o:p></o:p></P>
<P class=MsoPlainText>> dial-peer needs to be created. Survivability will
automatically be invoked <o:p></o:p></P>
<P class=MsoPlainText>> by the Unified CVP Standalone script if the
"survive" service exists."<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> My configuration is:<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> application<o:p></o:p></P>
<P class=MsoPlainText>> service CVPMedia
flash:CVPSelfService.tcl<o:p></o:p></P>
<P class=MsoPlainText>> param CVPSelfService-app
IVR_Branch<o:p></o:p></P>
<P class=MsoPlainText>> paramspace english language en<o:p></o:p></P>
<P class=MsoPlainText>> paramspace english index 0<o:p></o:p></P>
<P class=MsoPlainText>> param CVPSelfService-port 7000<o:p></o:p></P>
<P class=MsoPlainText>> param CVPPrimaryVXMLServer
10.10.10.10<o:p></o:p></P>
<P class=MsoPlainText>> paramspace english location
flash:<o:p></o:p></P>
<P class=MsoPlainText>> paramspace english prefix en<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>> application<o:p></o:p></P>
<P class=MsoPlainText>> service survive
flash:survivability.tcl<o:p></o:p></P>
<P class=MsoPlainText>> param open-hours-agent0 1200<o:p></o:p></P>
<P class=MsoPlainText>> param open-hours-time0
1234567:0800-20:00<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>> dial-peer voice 3002 pots<o:p></o:p></P>
<P class=MsoPlainText>> translation-profile incoming OUT<o:p></o:p></P>
<P class=MsoPlainText>> service survive<o:p></o:p></P>
<P class=MsoPlainText>> destination-pattern 300.<o:p></o:p></P>
<P class=MsoPlainText>> incoming called-number 300.<o:p></o:p></P>
<P class=MsoPlainText>> port 0/3/0:15<o:p></o:p></P>
<P class=MsoPlainText>> !<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>> ...<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> But, survivability script doesn't seem to invoke
when a call is placed <o:p></o:p></P>
<P class=MsoPlainText>> when WAN link is down. So, again the system error
message is played and <o:p></o:p></P>
<P class=MsoPlainText>> the call is dropped.<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> Does anyone have an experience with survivability
in a similar scenario?<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> Thanks,<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> Baris.<o:p></o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>><o:p> </o:p></P>
<P class=MsoPlainText>> <o:p></o:p></P>
<P class=MsoPlainText><o:p> </o:p></P>
<P
class=MsoPlainText>_______________________________________________<o:p></o:p></P>
<P class=MsoPlainText>cisco-voip mailing list<o:p></o:p></P>
<P class=MsoPlainText>cisco-voip@puck.nether.net<o:p></o:p></P>
<P
class=MsoPlainText>https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></P></DIV>
<DIV> </DIV>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. </BLOCKQUOTE></BODY></HTML>