- VoiceOps - lists.voiceops.org

AT&T Wireless contact
by nathana＠fsr.com Aug. 14, 2020

Aug. 14, 2020

This is probably a long shot, but are there any AT&T Wireless engineers here, & one who wouldn't mind contacting me off-list? I may be misinterpreting what I'm seeing, but I think you might have a small number of MMSC servers that are down... -- Nathan

1 0

issues with calls to-from verizon wireless ?
by igoldstein＠telego.net Aug. 5, 2020

Aug. 5, 2020

has anyone else noticed issues only with calls to and from Verizon Wireless cell phones ? -- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>

2 1

Recording disclaimer.
by alex.lopez＠opsys.com Aug. 5, 2020

Aug. 5, 2020

Just had a client refer to the announcement stating that calls can be recorded and or monitored as a 'Mini Miranda'. Has anyone heard it described that way before. I just may use that from now on.

3 2

One-time Bulk LRN Lookup
by voiceops＠ics-il.net Aug. 4, 2020

Aug. 4, 2020

Where's a good place to just upload a CSV with a bunch of numbers and get back the LRN information? Most places let me do one or two through a web tool or they require I use an API. Developing something to hit an API is more work than it's worth to me. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com

5 4

Trouble calling 8xx numbers
by mjohnston＠wiktel.com Aug. 3, 2020

Aug. 3, 2020

Is anybody else having issues calling 8xx destinations with Inteliquent since last night? This is mostly being reported as credit card machines and ATMs not working. Other than acknowledging my ticket, Inteliquent has been unresponsive (I'll have to start working their escalation list soon...sigh). I am hearing that other telcos around me are having issues as well. Mike Johnston Wiktel NW Minnesota

2 1

Need Referral for help configuring Q10 and Q20 SBCs
by marylou＠backuptelecom.com Aug. 1, 2020

Aug. 1, 2020

I have a client who is searching for an independent consultant experienced in configuring Q10 and Q20 SBCs. If you have a suggestion, please contact me offline. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111

1 0

Trouble calling 8xx numbers
by mjohnston＠wiktel.com Aug. 1, 2020

Aug. 1, 2020

TL;DR: It was a fiber cut. > Subject: Inteliquent Service interruption advisory || TT # 289412 > From: Inteliquent NOC <NOC at inteliquent.com> > Date: Friday, 07/31/2020 12:48 PM > Dear customer, > Subject: Multiple DS3 outage in Minnesota > Date: 07-31-20 > Time Start: 01:17 CST > Time Resolved: TBD > > Issue and actions taken: Multiple DS3?s failing due to higher level > OC-48 issue on circuit vendor?s network. This is escalated to highest > levels with in our organization as well as the circuit provider. > Circuit vendor dispatch is already in route to facility. > > We have opened 289412 as a master level ticket. > > Additional updates will be provided as soon as they are available. > > Thank you > Inteliquent NOC > Network Operations, Inteliquent > 24-hr NOC: 800-933-1224 op 2 > www.inteliquent.come: noc at inteliquent.com 2020-07-31 13:21, they added: > Update 1: Circuit vendor technician is on site and working the issue 2020-07-31 13:40, Inteliquent updated my ticket: > Thank you for your incredible patience. We are currently experiencing > an issue with our circuit provider. Escalations are already at executive > levels and we are working to resolve this as soon as humanly possible. At 00:03 this morning, Inteliquent updated my ticket: > Our circuit vendor experienced a large fiber cut today which impacted > services. They have recently confirmed that splice crews have completed > their work and are now hands-off. We see that the affected services > have since restored. Please check and let us know if any issues persist > so that our NOC may investigate ASAP.

1 0

Production STIR/SHAKEN
by dfrigen＠wabash.net July 27, 2020

July 27, 2020

Paul, this is in reply to your question posted on July 24th: Currently there are 34 active STI-GA SHAKEN participants authorized to exchange SHAKEN tokens in the U.S. While Canada and the UK are working on SHAKEN, to my knowledge there are no PA's or CA's to operate and approve new applicants in those countries. T-Mobile, Comcast, Verizon, and AT&T were the first four carriers to adopt SHAKEN and are still temporarily using self-signed certificates (not official PA authored certificates that Transnexus and the rest of the U.S. uses). This is due to FCC expectations of having a SHAKEN platform in production at the beginning of the year and there not being a PA (Policy Administrator), nor any CA's (Certificate Authorities) at that time. Self-signing certificates were the only means of operating the SHAKEN platform in the FCC timeframe. We, as out-of-band (OOB) operators do not have the ability to exchange certs. (certificates) with the self-signers today. It goes without saying that these networks are huge and not easily converted. T-Mobile and Comcast are in the process of converting to official PA authored certificates, they are expected to be on-line in the coming month. Both AT&T and Verizon are in the engineering stages and planning to convert in the future. I reside on a board seat of the national STI-GA governance board as an NTCA representative, and have asked the self-signers to begin publishing their self-signing root addresses so every can exchange tokens in the interim regardless of whether or not they are official PA authored certs. I anticipate self-signing certs going away, and likely within the coming months. In summary, we, as out-of-band (OOB) operators, do not have the ability to exchange certs. with the self-signers today, hopefully they will agree to publish their root certificate addresses soon. I want to prequalify this next statement by congratulating any TDM provider that is adopting OOB or some sort of TDM SHAKEN technology. You're doing the right thing, because TDM isn't going away anytime soon. And all Americans deserve the right to have their calls officially authenticated and verified just like any iP network provider's calls. OOB and other technologies for use on TDM calls for SHAKEN are in the infant stages and are just now being discussed and considered for permanent TDM standards. The body that is adopting new TDM standards is the PTSC Non-IP Call Authentication Task Force, led by ATIS. Anyone is welcome to become a member of the task force. There is a nominal $250 fee for organizations that are not already an ATIS member. If you want more information on how to join the committee, I'd be glad to help. Belonging to the committee is one of many ways to comply with the FCC's mandate for TDM providers to adopt SHAKEN. As to the original question of who to test OOB with, Transnexus to Transnexus will allow for both authentication and verification testing; or Transnexus to Netnumber or Neustar. These would be OOB to OOB calls. Regarding OOB to IP, or the reverse..it's my understanding that OOB to in-band will only work one way today. OOB can authenticate a PA certificate that in-band can receive. HTTP Post software or a Call Placement Service (CPS) is required for an IP provider to post a token to an OOB provider. With that being said, Wabash is a Transnexus customer and would be more than happy to test OOB SHAKEN with any provider desiring to do so. Let me know and I'll get you in touch with our engineers. Lastly, I'd like to add that Wabash originally implemented OOB SHAKEN into a C-15 with no CapEx, just existing translations modifications. After running the Transnexus/ClearIP platform for a while, we decided to upgrade our SBC to a cloud solution for under $100 a month, but to date that is our only capital expense to be OOB SHAKEN enabled. So, don't let your switch vendor insist that you break-the-bank to operate OOB. Dave Dave Frigen Chief Operating Officer Wabash Communications CO-OP | 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/> <http://www.wabash.net/>

2 1

Area code 886
by dovid＠telecurve.com July 24, 2020

July 24, 2020

Hi, Does anyone know if area code 886 was allocated to Canada and if yes where in Canada? We were just told by an international vendor that it is a new area code in Canada yet I can't find anything on it. TIA. Dovid

6 10

Production STIR/SHAKEN
by ptimmins＠clearrate.com July 24, 2020

July 24, 2020

Is anyone but T-Mobile and Comcast (and now us) doing STIR/SHAKEN right now and want to make test calls? We're on Inteliquent if that helps. -Paul Paul Timmins Senior Network Engineer Clear Rate Communications Direct: (248) 556-4532 Customer Support: (877) 877-4799 24 Hour Repair: (866) 366-4665 Network Operations: (877) 877-1250 www.clearrate.com This message contains confidential information intended only for the use of the intended recipient(s) and may contain information that is privileged. If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, you are hereby notified that reading, disseminating or copying this message is strictly prohibited. If you have received this message by mistake, please immediately send notification by replying to the message, indicate the message was received by mistake, and then delete the original message immediately thereafter. Thank you. Clear Rate Communications, Inc. 2600 W Big Beaver, Suite 450, Troy, MI 48034.

1 0