<html 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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[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:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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 bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Has there been any new service parameter change to allow Prefix
of an access code for calls coming from the phone directory? I cannot prefix 91
in the caller-id from the gateway because of our CRM integration. I want to
prefix 91 when a user dials from the missed call log. I am looking for
something similar to application dial rules with CUPC. In fact it works fine
from CUPC because I prefixing 91 when I call out from it but some users still
want to use the hard phone. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Wes Sisk<br>
<b>Sent:</b> Friday, April 17, 2009 12:50 PM<br>
<b>To:</b> FrogOnDSCP46EF<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] prefix access code 0 in ccm service parameter
upsetting unity VM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>In 7.x those parameters were split out by protocol type so
you could select to prefix on SCCP, h323, SIP, and MGCP indepenendently.
However, both phones and unity use SCCP.<br>
<br>
one possible creative solution would be to use SCCP to register phones but use
SIP to register unity (or vise versa). Then you could use the protocol
specific parameters to get the desired behavior.<br>
<br>
/Wes<br>
<br>
On Friday, April 17, 2009 12:32:04 PM, FrogOnDSCP46EF <a
href="mailto:ciscoboy2006@gmail.com"><ciscoboy2006@gmail.com></a> wrote:<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>I have got a production ccm-v6 and when I prefix 0 for
missed calls in ccm service parameter it works fine. the phones are able to
prepend '0'/access code and dial missed call directly.<br>
The problem is when call coming from PSTN to a DN and DN doesn't answer then it
goes to VM - that also work but the problem is when the DN checks voicemail -
the Cisco lady speaks out "Message received from "0"+8 digit
local number blah".<br>
Is there in Unity or Unity connection some parameter which makes cisco lady to
speak only 8 digit ANI and not the prepended '0' (ccm service parameter)?<br>
<br>
I have found this a normal behaviour but just want to know if there is any
option to fix this.<br>
i've tried putting ANI xxxxxxxx on Hunt pilot but it is not accepteble solution
as there are mobile 10 digit and national 11 digits numbers too.<br>
<br>
however, if i remove my pstn access code from ccm service parameter and then
pstn user calls to a DN >goes to VM > then it's all working as expected
(e.g. cisco lady only speaks out 8 digit local DN).<br>
<br>
any idea?<br>
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog<br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre><pre style='text-align:center'>
<hr size=4 width="90%" align=center>
</pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>