[VoiceOps] SS7 problems

Paul Timmins ptimmins at clearrate.com
Mon Dec 21 12:01:31 EST 2020


The part of the company to call depends on what part of the company 
those trunks come from. Contact your AT&T account manager.

If they're IXC circuits, https://primeaccess.att.com/shell.cfm?section=4343

On 12/21/20 10:56 AM, Dave Frigen wrote:
>
> 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.
>
> Anyone have any suggestions?
>
> Dave
>
> *From:* Dave Frigen <dfrigen at wabash.net>
> *Sent:* Friday, December 11, 2020 11:55 AM
> *To:* 'voiceops at voiceops.org' <voiceops at voiceops.org>
> *Cc:* 'Rodney Young' <Rodney at wabash.net>; 'Don Ross' 
> <deross at wabash.net>; 'Barry Adair' <barryadair at wabash.net>
> *Subject:* SS7 problems
>
> 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^nd 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.
>
> Trouble tickets reported:  Customers complaining about phones ringing, 
> no one on the other end.
>
> 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.
>
> Any reference to anyone else experiencing these issues recently would 
> be appreciated.
>
> Dave
>
> *Dave Frigen*
>
> */Chief Operating Officer /*
>
> Wabash Communications CO-OP | www.wabash.net <http://www.wabash.net>
>
> Office: 618.665.3311
>
> <https://www.facebook.com/wabashcommunicationscoop/><https://www.instagram.com/wabashcommunications/><https://www.youtube.com/channel/UCWoo3wyybeYEnTpTxK2jbUg> 
> <https://www.linkedin.com/company/18788687/admin/>
>
> WabashCom_CO-OP_RGB.png <http://www.wabash.net/>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1390 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1304 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1401 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1499 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 15208 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20201221/338d62f7/attachment-0009.png>


More information about the VoiceOps mailing list