<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.6036" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>The discussion of interoperability issues concerning
fax/modem in particular and PSTN X/modem calls in general was already
topic in the past two years in the correspondent experts groups,
like</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- ITU-T Q.14/16</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- SIP Forum FoIP Task Force</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- ANSI TR 30.1</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- ETSI TISPAN WG3</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- i3 Forum</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- MSF TC meeting and</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>- IETF MMUSIC (concerning the usage of revised SDP
Offer/Answer in SIP for T.38, V.152).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>There isn't much value in repeating the same discussions in
other groups again.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>Starting point for product implementations is to point out
their standard compliance primarily against the recommendations by the
correspondent technology owners, i.e. ITU-T Q.14/16 in case of T.38 and V.152
and IETF MMUSIC in case of SDP O/A (via SIP).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2>NGN / IMS compliant products on top must refer to 3GPP,
ETSI TISPAN, etc standards.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=781432316-16122010><FONT face="Trebuchet MS"
color=#800000 size=2></FONT></SPAN> </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>Lee
Riemer<BR><B>Sent:</B> Donnerstag, 16. Dezember 2010 16:01<BR><B>To:</B>
voiceops@voiceops.org<BR><B>Subject:</B> Re: [VoiceOps] Dynamic T1 Faxing over
IP<BR></FONT><BR></DIV>
<DIV></DIV>Can you list some devices that use the other versions and standards
you mention?<BR><BR>On 12/15/2010 11:46 PM, Schwarz, Albrecht (Albrecht)
wrote:
<BLOCKQUOTE
cite=mid:5F7BCCF5541B7444830A2288ABBEBC961D4FE529CF@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com
type="cite">
<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]-->
<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> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(128,0,0) 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> <A class=moz-txt-link-abbreviated
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</A>
[<A class=moz-txt-link-freetext
href="mailto:voiceops-bounces@voiceops.org">mailto:voiceops-bounces@voiceops.org</A>]
<B>On Behalf Of </B>Richey<BR><B>Sent:</B> Donnerstag, 16. Dezember 2010
04:53<BR><B>To:</B> <A class=moz-txt-link-abbreviated
href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</A><BR><B>Subject:</B>
Re: [VoiceOps] Dynamic T1 Faxing over IP<BR></FONT><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); 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: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'">Richey<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></SPAN></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 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'"> <A
class=moz-txt-link-abbreviated
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</A>
[<A class=moz-txt-link-freetext
href="mailto:voiceops-bounces@voiceops.org">mailto:voiceops-bounces@voiceops.org</A>]
<B>On Behalf Of </B>Jeff Anderson<BR><B>Sent:</B> Wednesday, December 15,
2010 5:54 PM<BR><B>To:</B> <A class=moz-txt-link-abbreviated
href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</A><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><PRE wrap=""><FIELDSET class=mimeAttachmentHeader></FIELDSET>
_______________________________________________
VoiceOps mailing list
<A class=moz-txt-link-abbreviated href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>