<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (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:Verdana;
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.pb1body1, li.pb1body1, div.pb1body1
{mso-style-name:pb1_body1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="pb1body1"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black"><a href="http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-config.html#wp1423763">http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-config.html#wp1423763</a><o:p></o:p></span></p>
<p class="pb1body1"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">This feature provides support for V.34 fax relay based on the ITU Specification T.38 version 3 (04/2007) and for fax pass-through at SG3 speed. Prior to Cisco IOS
Release 15.1(1)T, SG3-to-SG3 calls would fail because the V.34 modulation was not supported. A fallback solution allowed SG3-to-SG3 connections to be made, but the transmission speed was set to G3 levels.
<o:p></o:p></span></p>
<p class="pb1body1"><a name="wp1423765"></a><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">For T.38 fax sessions to operate at SG3 speeds, all the endpoints involved must support T.38 Version 3 (v3) configuration and have negotiated
T.38 v3. For example: <o:p></o:p></span></p>
<p class="pb1body1"><a name="wp1423766"></a><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Originating Gateway(T.38 v3)—IP-(T.38 v3)Cisco UBE(T.38 v3)-IP—Terminating Gateway(T.38 v3)
<o:p></o:p></span></p>
<p class="pb1body1"><a name="wp1423767"></a><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">In this context, all currently supported Cisco UBE T.38 flows (H.323-H.323, H.323-SIP and SIP-SIP) are supported in Release 15.1(1)T. However,
in topologies where at least one endpoint has a T.38 v0 configuration, the Cisco UBE configuration must be T.38 v0 (the lowest common version). Any other combination of T.38 v3 or v0 configuration involved in the Cisco UBE topologies is not supported.
<o:p></o:p></span></p>
<p class="pb1body1"><a name="wp1423768"></a><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">When two endpoints are involved in negotiating the T.38 parameter, the mandatory parameter is the "FaxVersion." That is, when one of the endpoints
supports Version 0 (v0), the resulting session operates as a v0 session. As long as Cisco UBE is configured for the lowest common version of the traffic expected, calls are completed successfully.
<o:p></o:p></span></p>
<p class="MsoNormal"><a name="wp1423816"></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I<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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Lelio Fulgenzi [mailto:lelio@uoguelph.ca]
<br>
<b>Sent:</b> Thursday, October 27, 2011 3:01 PM<br>
<b>To:</b> Nate VanMaren<br>
<b>Cc:</b> cisco-voip (cisco-voip@puck.nether.net); Erick A. Wellnitz<br>
<b>Subject:</b> Re: [cisco-voip] VG224 and vg224-i6k9s-mz.151-3.T2.bin<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">I think in pre-15 you were bang on, but v15 has had some feature enhancements for faxing.
<br>
<br>
Is SCCP w/ passthrough supported? Not sure. I'm hoping it is.<br>
<br>
It will likely be a try and call the TAC for help when it doesn't work and then argue about whether it is supported or not. ;)<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">
<hr size="2" width="100%" align="center" id="zwchr">
</span></div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">"Nate VanMaren" <<a href="mailto:VanMarenNP@ldschurch.org">VanMarenNP@ldschurch.org</a>><br>
<b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>>, "Erick A. Wellnitz" <<a href="mailto:erick.wellnitz@kattenlaw.com">erick.wellnitz@kattenlaw.com</a>><br>
<b>Cc: </b>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Thursday, October 27, 2011 4:49:20 PM<br>
<b>Subject: </b>RE: [cisco-voip] VG224 and vg224-i6k9s-mz.151-3.T2.bin<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I thought SG3 was only for T.38 and only for H.323 and SIP? (no MGCP, and SCCP t.38 is NSE based which I don’t like)</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Nate</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:-moz-use-text-color -moz-use-text-color">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
<a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto:cisco-voip-bounces@puck.nether.net]</a>
<b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Thursday, October 27, 2011 9:10 AM<br>
<b>To:</b> Erick A. Wellnitz<br>
<b>Cc:</b> cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)<br>
<b>Subject:</b> Re: [cisco-voip] VG224 and vg224-i6k9s-mz.151-3.T2.bin</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">We've had pretty good luck setting our fax machines to 14.4 ECM off when using SCCP passthrough. Or was it pass through? Or pass-through?
(Anyone remember that thread? ;)<br>
<br>
We're currently using 15.0(1)M3 on our VG224s and 15.1(3)T on our gateways. Probably look at upgrading to 15.1(3)T as well if we find some time to test SG3 speeds using passthrough which is apparently supported now.<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)</span><span style="color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">"Erick A. Wellnitz" <<a href="mailto:erick.wellnitz@kattenlaw.com" target="_blank">erick.wellnitz@kattenlaw.com</a>><br>
<b>To: </b>"Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>><br>
<b>Cc: </b>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Thursday, October 27, 2011 10:40:03 AM<br>
<b>Subject: </b>Re: [cisco-voip] VG224 and vg224-i6k9s-mz.151-3.T2.bin<br>
<br>
We're doing the same but haven't added any analog devices yet.<br>
<br>
On Oct 27, 2011, at 9:35 AM, "Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com%3cmailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com<mailto:jason.aarons@dimensiondata.com</a>>> wrote:<br>
<br>
My VG22/SCCP experience is your either have good luck or your faxing situation turns out really bad. In 2009 I went thru 6 different IOSs for VG224 before getting becoming caveat free with 12-4.15T6 and hate to repeat that situation.<br>
<br>
<br>
Combination of Faxing/Modems/Postage/Polycoms, Last very large rollout of VG224s with SCCP (for Supplementary Features) I used IOS 12.4.15T6 with very good luck, however I’m researching 151-3.T2 and wanted to know if anyone had any feedback, issues or tried
this code.<br>
<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net%3cmailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net</a>><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
===========================================================<br>
CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the Internal Revenue<br>
Service, any tax advice contained herein is not intended or written to be used and cannot be used<br>
by a taxpayer for the purpose of avoiding tax penalties that may be imposed on the taxpayer.<br>
===========================================================<br>
CONFIDENTIALITY NOTICE:<br>
This electronic mail message and any attached files contain information intended for the exclusive<br>
use of the individual or entity to whom it is addressed and may contain information that is<br>
proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you<br>
are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or
<br>
distribution of this information may be subject to legal restriction or sanction. Please notify<br>
the sender, by electronic mail or telephone, of any unintended recipients and delete the original
<br>
message without making any copies.<br>
===========================================================<br>
NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has<br>
elected to be governed by the Illinois Uniform Partnership Act (1997).<br>
===========================================================<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#666666"><br>
<br>
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original message.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</body>
</html>