<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: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 15 (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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>We’ve narrowed this down to calls completing on our facilities (from likely least cost routing) down an AT&T TDM/SS7 terminating trunk group. We have no contacts for this trunk group, and even turned the trunk group down for a day thinking we would get a call, but didn’t. We’re still getting two calls to a single number, one call with caller on it and the other with dead air. The dual calls are coming from various service providers on this trunk group. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anyone have any suggestions?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dave<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Dave Frigen <dfrigen@wabash.net> <br><b>Sent:</b> Friday, December 11, 2020 11:55 AM<br><b>To:</b> 'voiceops@voiceops.org' <voiceops@voiceops.org><br><b>Cc:</b> 'Rodney Young' <Rodney@wabash.net>; 'Don Ross' <deross@wabash.net>; 'Barry Adair' <barryadair@wabash.net><br><b>Subject:</b> SS7 problems<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I know SS7 is not a big part of the voice world for many of you, but for those of you still exposed to it, just curious if anyone experienced any problems with SS7 signaling in the past couple of days where Terminating signaling times out and a 2<sup>nd</sup> retry and new call set up for the call delivery occurs. The result was the phone ringing the customer, no one there. Second attempt successfully (if multiline hunt group) comes in on next line/trunk.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Trouble tickets reported: Customers complaining about phones ringing, no one on the other end.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We traced the issue upstream in the SS7 signaling. The signaling was timing out after 15 seconds, creating call retry. We had our SS7 provider look into it. No trouble found, but the “gremlins” mysteriously disappeared after the testing……concerned trouble may reoccur.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any reference to anyone else experiencing these issues recently would be appreciated.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dave<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><span style='font-size:22.0pt'>Dave Frigen<o:p></o:p></span></b></p><p class=MsoNormal><b><i><span style='font-size:12.0pt'>Chief Operating Officer <o:p></o:p></span></i></b></p><p class=MsoNormal>Wabash Communications CO-OP | <a href="http://www.wabash.net">www.wabash.net</a><o:p></o:p></p><p class=MsoNormal>Office: 618.665.3311 <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><a href="https://www.facebook.com/wabashcommunicationscoop/"><span style='color:windowtext;text-decoration:none'><img border=0 width=26 height=26 style='width:.2708in;height:.2708in' id="Picture_x0020_1" src="cid:image001.png@01D6D77F.4F3AF290"></span></a><a href="https://www.instagram.com/wabashcommunications/"><span style='color:windowtext;text-decoration:none'><img border=0 width=26 height=26 style='width:.2708in;height:.2708in' id="Picture_x0020_2" src="cid:image002.png@01D6D77F.4F3AF290"></span></a><a href="https://www.youtube.com/channel/UCWoo3wyybeYEnTpTxK2jbUg"><span style='color:windowtext;text-decoration:none'><img border=0 width=26 height=26 style='width:.2708in;height:.2708in' id="Picture_x0020_3" src="cid:image003.png@01D6D77F.4F3AF290"></span></a> <a href="https://www.linkedin.com/company/18788687/admin/"><span style='color:windowtext;text-decoration:none'><img border=0 width=24 height=24 style='width:.25in;height:.25in' id="Picture_x0020_4" src="cid:image004.png@01D6D77F.4F3AF290"></span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="http://www.wabash.net/"><span style='color:windowtext;text-decoration:none'><img border=0 width=193 height=66 style='width:2.0104in;height:.6875in' id="Picture_x0020_0" src="cid:image005.png@01D6D77F.4F3AF290" alt="WabashCom_CO-OP_RGB.png"></span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>