<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:x="urn:schemas-microsoft-com:office:excel" 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)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;}
@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 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'>Check the CTI Port’s CSS and calling permissions.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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 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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Kent Roberts<br>
<b>Sent:</b> Tuesday, May 29, 2007 10:30 PM<br>
<b>To:</b> Robert Kulagowski<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Transferring to Outside Lines from the IPCC ?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Just a thought, Do you
have dedicated LD circuits? If so are you routing sending that 800s via
those circuits? The 800 calls can not be sent out LD
circuits. They must go out the local.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 5/29/07, <b>Robert Kulagowski</b>
<<a href="mailto:bob@smalltime.com">bob@smalltime.com</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal>> Miller, Steve wrote:<br>
>> We have an odd problem. In our script on the CRS server, we<br>
>> transfer calls to an external number for our backup helpdesk<br>
>> vendor. This works fine when we insert their regular phone
number <br>
>> which is 404-XXX-XXXX, but when we enter the toll free number<br>
>> 800-XXX-XXXX that is forwarded to the 404 number by the carrier, we<br>
>> get a busy signal.<br>
<br>
Check your Q931 traces; does it look like this? (I'm also about to <br>
start troubleshooting this issue, so I don't have an answer).<br>
<br>
If the site dials the 800 number directly, it works, but if they use a<br>
site-wide speed dial that's a CFA on a line that's attached to a <br>
"SpeedDial" CTI port, it doesn't work. (*660 is the speed
dial)<br>
<br>
May 29 10:47:40.923: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type<br>
0xD is 0x2 0x1, Calling num 213928<br>
May 29 10:47:40.923 : ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type<br>
0xD is 0x2 0x1, Called num 18005797372<br>
May 29 10:47:40.923: ISDN Se0/1/0:23 Q931: TX -> SETUP pd =
8 callref =<br>
0x06A3<br>
Bearer Capability i = 0x8090A2
<br>
Standard = CCITT<br>
Transfer Capability = Speech<br>
Transfer Mode = Circuit<br>
Transfer Rate = 64 kbit/s<br>
Channel ID i = 0xA98382<br>
Exclusive, Channel 2 <br>
Calling Party Number i =
0x21A1, '213928'<br>
Plan:ISDN, Type:National<br>
Called Party Number i = 0xA1,
'18005797372'<br>
Plan:ISDN, Type:National<br>
Redirecting Number i = '!',
0x008F, '??*660' <br>
Plan:ISDN, Type:National<br>
<br>
May 29 10:47:41.015: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8<br>
callref = 0x86A3 Channel ID i = 0xA98382 Exclusive, Channel 2<br>
<br>
May 29 10:47:41.023: ISDN Se0/1/0:23 Q931: RX <- PROGRESS pd = 8 <br>
callref = 0x86A3<br>
Cause i = 0x80FF -
Interworking error; unspecified<br>
Progress Ind i = 0x8088 -
In-band info or appropriate now available<br>
<br>
May 29 10:47:44.935: ISDN Se0/1/0:23 Q931: TX -> DISCONNECT pd = 8 <br>
callref = 0x06A3 Cause i = 0x8090 - Normal call clearing<br>
<br>
May 29 10:47:45.015: ISDN Se0/1/0:23 Q931: RX <- RELEASE pd =
8 callref<br>
= 0x86A3<br>
<br>
May 29 10:47:45.019: ISDN Se0/1/0:23 Q931: TX -> RELEASE_COMP pd = 8 <br>
callref = 0x06A3<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck..nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>