<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: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="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><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:0cm;
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:"Arial","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
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=PT link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>It’ s a SIP trunk between a Cisco GW (the one I have control) and a ZTE device… It was working with the config I have shown. Something was changed on the other side. I was trying to make it work using the options available at our side. Unfortunately I don’t have the debugs captured when this was configured so I still have a doubt. What PT should be used in this T.38 negotiation ? PT=100 or PT=101 ?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>PT=100:</span><span lang=EN-US> </span><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Designates an NSE (Named Signaling Event packet). NSE packets can signal a variety of different messages so it is helpful to know the NSE Event ID.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>PT=101: Designates an NTE (Named Telephony Event) as defined in RFC 2833.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Check this table:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><a href="https://supportforums.cisco.com/docs/DOC-1387">https://supportforums.cisco.com/docs/DOC-1387</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>I was convinced that it was PT=100 (NSE) but as you said, they are Cisco proprietary. So maybe it should be PT=101 (NTE) ?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Thanks.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Antonio Soares, CCIE #18473 (R&S/SP)<br><a href="mailto:amsoares@netcabo.pt"><span style='color:blue'>amsoares@netcabo.pt</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> matthn@gmail.com [mailto:matthn@gmail.com] <b>On Behalf Of </b>Nick Matthews<br><b>Sent:</b> segunda-feira, 17 de Janeiro de 2011 17:56<br><b>To:</b> Antonio Soares<br><b>Cc:</b> Peter Slow; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] T.38 Fax Issue<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>When you say SIP trunk, are you implying that this is going to a SIP provider? Or is this just a SIP gateway and the fax is going out a TDM interface?<br><br>If it's a SIP trunk you're sending the fax over, forget about anything using NSEs - like Pete said they're Cisco proprietary.<br><br>You'll need to configure the other device for protocol based T.38 switchover like you've got it configured on your end.<br><br>-nick<o:p></o:p></p><div><p class=MsoNormal>On Mon, Jan 17, 2011 at 10:21 AM, Antonio Soares <<a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a>> wrote:<o:p></o:p></p><p class=MsoNormal>We tried the "fax protocol t38 nse force" but it didn't work.<br><br>Now with "fallback cisco" we have something different:<br><br>--------------------------------------<br> s=VoIP d=DSP payload 0x60 ssrc 0xFFD5D4C sequence 0x291 timestamp<br>0x19A50<o:p></o:p></p><div><p class=MsoNormal> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>--------------------------------------<o:p></o:p></p></div><p class=MsoNormal> s=DSP d=VoIP payload 0x61 ssrc 0xFFE2 sequence 0x0 timestamp 0x0<br> Pt:97 Evt:0 Pkt:00 04 00 <Snd>>><br>--------------------------------------<br> s=DSP d=VoIP payload 0x60 ssrc 0x0 sequence 0x0 timestamp 0x0<br> Pt:96 Evt:0 Pkt:00 00 00 <Snd>>><br>--------------------------------------<br> s=VoIP d=DSP payload 0x60 ssrc 0xFFD5D4C sequence 0x292 timestamp<br>0x19AA0<o:p></o:p></p><div><p class=MsoNormal> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>--------------------------------------<o:p></o:p></p></div><p class=MsoNormal> s=DSP d=VoIP payload 0x61 ssrc 0x60014 sequence 0x1 timestamp 0x1<br> Pt:97 Evt:0 Pkt:01 00 00 <Snd>>><br>--------------------------------------<br> s=VoIP d=DSP payload 0x60 ssrc 0xFFD5D4C sequence 0x293 timestamp<br>0x19AF0<o:p></o:p></p><div><p class=MsoNormal> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>--------------------------------------<o:p></o:p></p></div><p class=MsoNormal> s=DSP d=VoIP payload 0x61 ssrc 0x0 sequence 0x2 timestamp 0x2<br> Pt:97 Evt:0 Pkt:01 00 00 <Snd>>><br>--------------------------------------<br> s=VoIP d=DSP payload 0x60 ssrc 0xFFD5D4C sequence 0x294 timestamp<br>0x19B40<o:p></o:p></p><div><p class=MsoNormal> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>--------------------------------------<o:p></o:p></p></div><p class=MsoNormal> s=DSP d=VoIP payload 0x61 ssrc 0x0 sequence 0x3 timestamp 0x3<br> Pt:97 Evt:0 Pkt:01 00 00 <Snd>>><br>--------------------------------------<br> s=DSP d=VoIP payload 0x7A ssrc 0xFFFFFFFF sequence 0x9EBF<br>timestamp 0x2FE4CED0<br> Pt:122 Evt:0 Pkt:52 3A 00 <Snd>>><br>--------------------------------------<br><br>Now we see:<br><br>Pt:96 Evt:136 (Sent by a voice gateway to signal a switchover to Cisco<br>fax relay)<br>Pt:97 Evt:0 (Sent by a voice gateway to confirm a successful switchover<br>to Cisco fax relay)<br>Pt:122 Evt:0 (Indicates Cisco fax relay data)<br><br>So I was expecting this would mean it was working but apparently it still<br>doesn't work.<br><br>I'm using this document as reference:<br><br>Cisco RTP Payload Types<br><br><a href="https://supportforums.cisco.com/docs/DOC-1387" target="_blank">https://supportforums.cisco.com/docs/DOC-1387</a><br><br>Any other ideas ?<o:p></o:p></p><div><p class=MsoNormal><br><br>Thanks.<br><br>Regards,<br><br>Antonio Soares, CCIE #18473 (R&S/SP)<br><a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a><br><br><br>-----Original Message-----<br>From: Peter Slow [mailto:<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>]<o:p></o:p></p></div><div><div><p class=MsoNormal>Sent: segunda-feira, 17 de Janeiro de 2011 12:16<br>To: Antonio Soares<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] T.38 Fax Issue<br><br>No, "fallback cisco" is different. You need to try the "fax protocol<br>t38 nse force" command.<br><br>-pete<br><br><br>On Mon, Jan 17, 2011 at 6:58 AM, Antonio Soares <<a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a>> wrote:<br>> It was working before so I assume the other end's configuration was<br>changed.<br>> This is a SIP trunk and we have this configuration for the T.38 fax:<br>><br>> voice service voip<br>> fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through<br>> g711alaw<br>><br>> We are now trying the following:<br>><br>> voice service voip<br>> fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco<br>><br>> This should match their PT=96 request, right ?<br>><br>><br>> Thanks.<br>><br>> Regards,<br>><br>> Antonio Soares, CCIE #18473 (R&S/SP)<br>> <a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a><br>><br>><br>> -----Original Message-----<br>> From: Peter Slow [mailto:<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>]<br>> Sent: segunda-feira, 17 de Janeiro de 2011 11:50<br>> To: Antonio Soares<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: Re: [cisco-voip] T.38 Fax Issue<br>><br>> Usually t.38 Fax relay operates by switching to t.38 based on an MGCP<br>> MDCX, a new h245 TCS/OLC etc, or a SIP re-invite. this is referred to<br>> as protocol based switchover, and is generally how people's gateways<br>> are configured for t.38 when it is being used. it would appear that<br>> the other GW you are talking to is set up for NSE based switchover,<br>> which AFAIK is a cisco proprietary method. You may be configured for<br>> protocol based switchover still, while it sounds like perhaps the<br>> other side went and changed something and is now trying to do NSE<br>> based switchover...<br>><br>> Check out this link:<br>><br><a href="http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_fax_services_over_i" target="_blank">http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_fax_services_over_i</a><br>> p_application_guide/t38.html#wp1156699<br>><br>> It is tough to help you out beyond what I've said without knowing what<br>> protocol (h.323, MGCP..) you are using for call control. More insight<br>> there, plus perhaps some asn1 or mgcp packet debugs would help, but<br>> try setting your side to use nse based switchover if it isnt set that<br>> way already.<br>><br>> -Peter<br>><br>><br>><br>> On Mon, Jan 17, 2011 at 5:48 AM, Antonio Soares <<a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a>><br>wrote:<br>>> Hello group,<br>>><br>>> A few days ago, fax stopped working on one gateway. The "debug voip rtp<br>>> session nse" gives me this:<br>>><br>>><br>><br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>>> ++++++++++++++<br>>> s=VoIP d=DSP payload 0x60 ssrc 0x509B391F sequence 0x18E<br>> timestamp<br>>> 0xF8C0<br>>> <<<Rcv> Pt:96 Evt:136 Pkt:02 80 50<br>>> s=VoIP d=DSP payload 0x60 ssrc 0x509B391F sequence 0x18F<br>> timestamp<br>>> 0xF910<br>>> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>>> s=VoIP d=DSP payload 0x60 ssrc 0x509B391F sequence 0x190<br>> timestamp<br>>> 0xF960<br>>> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>>> s=VoIP d=DSP payload 0x60 ssrc 0x509B391F sequence 0x191<br>> timestamp<br>>> 0xF9B0<br>>> <<<Rcv> Pt:96 Evt:136 Pkt:01 40 50<br>>> s=VoIP d=DSP payload 0x60 ssrc 0x509B391F sequence 0x192<br>> timestamp<br>>> 0xFA00<br>>> (...)<br>>><br>><br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>>> ++++++++++++++<br>>><br>>> Most likely, the problem is on the other end, a gateway that I do not<br>>> control.<br>>><br>>> I believe for this to work I need to receive PT=100 and EVT=200:<br>>><br>>> Payload Type 100: Designates an NSE (Named Signaling Event packet). NSE<br>>> packets can signal a variety of different messages so it is helpful to<br>> know<br>>> the NSE Event ID.<br>>><br>>> Event 200: Triggered by the detection of a V.21 fax preamble when T.38 is<br>>> configured. This message initiates the switchover of the call from voice<br>> to<br>>> T.38. This message is sent by the terminating fax gateway to notify the<br>>> originating fax gateway of the switch to T.38.<br>>><br>>> And I'm receiving PT=96 and EVT=136. PT=96 means " Sent by a voice<br>gateway<br>>> to signal a switchover to Cisco fax relay". I wasn't able to find the<br>>> meaning of EVT=136.<br>>><br>>> With this information, can I assume that the problem is on the other end<br>?<br>>> Can I do anything on my side to force the desired PT/EVT combination ?<br>>><br>>><br>>> Thanks.<br>>><br>>> Regards,<br>>><br>>> Antonio Soares, CCIE #18473 (R&S/SP)<br>>> <a href="mailto:amsoares@netcabo.pt">amsoares@netcabo.pt</a><br>>><br>>><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>><br>><br>><br><br><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>