<!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:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.6036" name=GENERATOR>
<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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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 vLink=purple link=blue>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>This discussion is just at the
surface.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>If you talk about fax over IP, then you should include
the T.38 version, and there are 6 versions so far (T.38 v0 to
v5).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>The majority of deployed ATA's seems to use T.38 v0
from year 1998, which is an issue.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>The latest one is T.38 v5
(09/2010).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>If you talk about G.711 pass-through, then you should
again discriminate between</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>a) V.152 VBDoIP with G.711 as VBD codec
and</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>b) pseudo-VBDoIP using G.711.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>The first one has a clear indication as VBD codec in
the signalling plane (like SIP, H.248, H.323, etc), which allows to
distinguish G.711 as audio codec and G.711 in VBD mode.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>The second one is just a mess ("G.711 pass-through")
due to the merge of audio with VBD (... and different media
configurations).</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>All the requirements for FoIP and VBDoIP are e.g.
summarized by <FONT face="Times New Roman" color=#000000 size=3><STRONG>ETSI TR
183 072 V3.1.1 (2010-09), </STRONG>Emulation Services for PSTN Modem
Calls.</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010><FONT face="Times New Roman" color=#000000 size=3>Which
talks also about the interop issue.</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010><FONT face="Times New Roman" color=#000000 size=3>And
one root cause are just different T.38 implementations
...</FONT> </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>Thus, any constructive discussion should address also
that level of detail.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>Regards,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000 size=2><SPAN
class=000103805-16122010>Albrecht</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Trebuchet MS" color=#800000
size=2></FONT> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> voiceops-bounces@voiceops.org
[mailto:voiceops-bounces@voiceops.org] <B>On Behalf Of
</B>Richey<BR><B>Sent:</B> Donnerstag, 16. Dezember 2010 04:53<BR><B>To:</B>
voiceops@voiceops.org<BR><B>Subject:</B> Re: [VoiceOps] Dynamic T1 Faxing over
IP<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">The
TA900s and 2431s will handle faxing, alarms, modems, etc fine IF you do two
things. One you use point to point circuits between you and the
IAD. The other thing is avoid sending these accounts across sip trunks
that traverse the internet. We use a combination of PRIs for local
and SIP trunks for LD. We route the “data lines” so that their local and
ld go out their closest PRI. If the customer wants to bring
their own bandwidth or they are offnet we won’t support any kind of data
calls.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Richey<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org] <B>On
Behalf Of </B>Jeff Anderson<BR><B>Sent:</B> Wednesday, December 15, 2010 5:54
PM<BR><B>To:</B> voiceops@voiceops.org<BR><B>Subject:</B> [VoiceOps] Dynamic
T1 Faxing over IP<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>We are experiencing a fair amount of heart burn attempting
to support faxing over our Dynamic T1 product. Some customers it works great
and others have frequent problems.<BR><BR>We currently support dynamic T1's
using both Adtran TA900 series and Cisco IAD2400 services routers. The
customers fax machines will connect to their PBX that has a PRI to an IAD/TA.
We have the IAD/TA configured for SIP signaling to an Acme SBC selecting T.38
as the preferred codec with fallback to g.711 pass-through. We can force a
slower speed, disable error correction, disabled VAD but in the end still have
very inconsistent results. From a network perspective the QoS is matching and
queuing correctly, the circuits are clean and the IP SLA gives us no reason to
believe they are having any network drops or jitter.<BR><BR>I was wondering if
others who have experience with faxing over IP could share what they have
learned works best or anything else that may be helpful.<BR><BR>Any help is
greatly
appreciated.<BR><BR>Thanks,<BR><BR>Jeff<o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>