- VoiceOps - lists.voiceops.org

"Scam Likely" list of DIDs
by anakaoka＠trinet-hi.com May 13, 2017

May 13, 2017

T-mobile changes the cnam of a call to "Scam Likely" based on incoming DID. Does anyone know what list they are using and where to get it? Aryn H. K. Nakaoka anakaoka at trinet-hi.com Direct: 808.356.2901 Fax: 808.356.2919 Tri-net Solutions 518 Holokahana Lane Suite #200 Honolulu, HI 96817 http://www.trinet-hi.com https://twitter.com/AlohaTone Aloha Tone PBX https://www.youtube.com/watch?v=96YWPY9wCeU Aloha Tone (HA) High Availability http://youtu.be/rJsr4k0RBH8 A Better Solution https://www.trinet-hi.com/abettersolution.pdf <https://www.trinet-hi.com/abettersolution.pdf> CONFIDENTIALITY NOTICE: The information contained in this email and any attachments may be privileged, confidential and protected from disclosure. Any disclosure, distribution or copying of this email or any attachments by persons or entities other than the intended recipient is prohibited. If you have received this email in error, please notify the sender immediately by replying to the message and deleting this email and any attachments from your system. Thank you for your cooperation.

6 5

Vonage Business
by mgraves＠mstvp.com May 11, 2017

May 11, 2017

Afraid not. I'm inquiring for a mutual customer. Spent a while talking to their tech support team. My calls to them got dropped several times. Had tons of echo from one CSR. No-one there seems to be able to tell me anything much. Michael Graves mgraves at mstvp.com http://www.mgraves.org o(713) 861-4005 c(713) 201-1262 sip:mgraves at mjg.onsip.com skype mjgraves --------- Original Message --------- Subject: Re: [VoiceOps] Vonage Business From: "Mark R Lindsey" <mark at ecg.co> Date: 5/11/17 2:33 pm To: mgraves at mstvp.com They have a lot of internal platforms; do you know which one you're on? > On May 11, 2017, at 3:31 PM, mgraves at mstvp.com wrote: > > Hi All, > > Does anyone here know if Vonage Business customers are allowed to dial by SIP URI from a company issued phone? > > Thanks, > > Michael Graves > mgraves at mstvp.com > http://www.mgraves.org > o(713) 861-4005 > c(713) 201-1262 > sip:mgraves at mjg.onsip.com > skype mjgraves > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops

3 3

Vonage Business
by mgraves＠mstvp.com May 11, 2017

May 11, 2017

Peter, Thanks for that. It's great info. Unfortunately, I cannot reach the customer's end-point using that approach. I must infer that, in this case at least, they are not on the Broadsoft platform. Or it is in some way defeated. Michael Graves mgraves at mstvp.com http://www.mgraves.org o(713) 861-4005 c(713) 201-1262 sip:mgraves at mjg.onsip.com skype mjgraves --------- Original Message --------- Subject: Re: [VoiceOps] Vonage Business From: "Peter Rad." <peter at 4isps.com> Date: 5/11/17 4:08 pm To: mgraves at mstvp.com so BSFT has the capability to do it: BroadWorks calls it ?URL Dialing?: calling from your hosted PBX VoIP phone or SIP Trunking device to a random SIP URI. And VB is on BSFT. Vonage consumer: When I was a vonage user people could dial me by calling: sip:{Vonage_Phone Number 10 digits}(a)sip.vonage.net. This is a SIP URI but it would be much more clean if they had created SRV records for vonage.com. On 5/11/2017 4:41 PM, mgraves at mstvp.com wrote: Vonage Business customers are allowed to dial by SIP URI

1 0

Vonage Business
by mgraves＠mstvp.com May 11, 2017

May 11, 2017

Hi All, Does anyone here know if Vonage Business customers are allowed to dial by SIP URI from a company issued phone? Thanks, Michael Graves mgraves at mstvp.com http://www.mgraves.org o(713) 861-4005 c(713) 201-1262 sip:mgraves at mjg.onsip.com skype mjgraves

1 0

FCC Numbering Authorization Application?
by ryan＠finnesey.com May 11, 2017

May 11, 2017

It seems my Google skills have failed me today ? Where can I find the FCC Numbering Authorization Application so I can request numbers as a VoIP Provider?

8 9

Plivo Domain Outage Post Mortem (fwd)
by beckman＠angryox.com May 8, 2017

May 8, 2017

Thought the list would like to see the Plivo outage post mortem. Make sure you renew your domains people! Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- ---------- Forwarded message ---------- Date: Mon, 8 May 2017 16:11:52 EDT From: Plivo <do-not-reply at plivo.com> Subject: Plivo Domain Outage Post Mortem Plivo Domain Outage Post Mortem & Analysis Dear Valued Customer, On April 23, 2017, we experienced an outage on our primary domain (plivo.com) and related subdomains. Although we had been sharing regular updates and various workarounds during the domain outage, we would like to communicate our root cause analysis, and the steps we will take to ensure this doesn?t happen in the future. ** What happened and what was the impact? ------------------------------------------------------------ At 10:39 UTC on April 23, 2017, our team noticed that our primary domain (plivo.com) and all of its related subdomains were unresolvable from most countries, which resulted in an outage for customers across all services. Our on-call team immediately began taking action, and within the next 4 hours provided workarounds for our customers that ensured access to most of our services. Customers were communicated about these updates via Twitter, a live status update document and through their respective account managers. Over the next 18 hours, while working with our domain registrar, we isolated and corrected multiple configuration and provisioning errors. By 12:30 UTC on April 24, 2017, all of our services were back up using most DNS providers globally. However, a small percentage of our voice and sms customers had increased latency and errors during the next few hours, which were resolved immediately. ** Timeline ------------------------------------------------------------ April 23, 2017 * 10:39 UTC: plivo.com and its subdomains could not be resolved from various locations globally. The On-Call team immediately started investigating the issue. * 10:42 UTC: Our domain showed up as being expired by our domain registrar. * 10:50 UTC: Our engineers contacted our domain registrar to understand the reason and resolved it with them while in parallel start implementing a contingency action plan. * 13:30 UTC: A patch was deployed to all of our servers to temporarily provide a workaround for the unresolvable domain, and switch all of our internal tools and servers to an internal domain name. * 14:00 UTC: Our internal tools and servers were resolvable. * 14:34 UTC: We communicated a workaround to our customers with the temporary IPs of our services, which ensured that service was not disrupted. * 15:00 UTC: Outbound calls to PSTN came back online. * 15:30 UTC: We communicated new domain names to our carriers and worked to re-establish Inbound Calls. At this time we saw 60% of our voice traffic back up. * 17:00 UTC: We released alternative links to our WebSDK on the live update document. * 17:30 UTC: Our registrar (phone.plivo.com) was patched, so that it accepted direct connections using the IP Only, which allowed our customers to register. * 19:46 UTC: Inbound SMS was back in service. * 20:00 UTC: plivo.io was provisioned by setting up another cluster as a workaround. * 22:18 UTC: api.plivo.io came online as a backup for api.plivo.com. * 22:26 UTC: manage.plivo.io came online as a backup for manage.plivo.com. * 22:30 UTC: We released a new version of our WebSDK using a different domain to mitigate the issues experienced by customers. At this time 80% of our Voice traffic was back up. * 23:12 UTC: We released new plivo.io domain names for customers using custom inbound carriers. April 24, 2017 * 00:38 UTC: phone.plivo.io and app.plivo.io came online, as temporary replacements for phone.plivo.com and app.plivo.com. * 03:30 UTC: We saw some plivo.com domains starting to resolve on their original IP addresses. We kept monitoring the propagation of our nameservers. * 09:30 UTC: Around 50% of the main DNS servers have been updated. * 10:30 UTC: We asked some DNS Servers to refresh their caches for plivo.com to expedite the propagation. * 13:00 UTC: 90% of DNS Servers have been updated correctly with Plivo?s name servers. * 16:00 UTC: All Plivo services were fully operational and 99% of DNS Servers updated correctly with Plivo?s name servers. ** Root-Cause Analysis ------------------------------------------------------------ Plivo?s primary domain (plivo.com) was set to renew automatically on April 17 annually. However, due to a configuration error with our registrar, instead of automatically renewing, the domain expired. We did not see any issues with our domain until April 23, 2017, as the registrar had a grace period of 5 days upon expiration. Unfortunately, what also made this unnoticeable until the day of the incident, was that we never received any updates, warnings or notifications regarding the possible expiry of the domain. Upon further drill down by our team with the registrar, we found no notifications or alerts sent by our registrar regarding the expiry of the domain and the auto renew for the domain was never triggered. Although we still don?t have an official confirmation regarding this from the registrar, we suspect it is due to a configuration error at their end. Immediately after this we started working with the registrar to restore the domain. The first reprovisioning order for the domain was stuck in a queued state and never got executed for almost 4 hours. This was then escalated to their team and we retried the restoration manually, which also failed multiple times. The official response we received from the registrar was that "Since the name server on the domains have expired it usually takes 12-24 hours to reprovision the name servers on the domain and some more time for the changes to propagate globally." To get our services back online for our customers, we set up a temporary domain at ?plivo.io? and pointed all of our services to this new domain. Then, we published this workaround in a live document that we updated throughout the incident. After almost 18 hours of working with the registrar, at 03:30 UTC April 24 2017, the order was finally executed successfully and we started seeing the name servers update and reflected on some DNS providers. ** When will the workarounds expire? ------------------------------------------------------------ How long can customers continue to use plivo.io as a workaround domain? We will ensure that the workaround domain ?plivo.io? will remain operational until May 31, 2017. We will decommission the domain after May 31, 2017. How long can customers continue to hardcode IPs in etc/hosts? We advise customers to go back to the plivo.com domain names as soon as possible. Because of our elastic architecture, we cannot guarantee that these IPs will stay the same in the near future. It is especially critical to use api.plivo.com instead of the temporary IPs that we provided during the incident. We will send reminders to all of our customers who switched to the temporary domain to revert back to the original Plivo.com domain and IPs. ** Related Service disruptions ------------------------------------------------------------ Between April 24-27, 2017, 30% percent of our customer traffic saw irregular service degradation and disruptions in our SMS, Voice API & WebRTC/SIP service. These incidents are related to the maintenance that was originally planned for April 23, 2017. When the unexpected DNS issue hit, we were near the end of our deployment that had the purpose of strengthening our Voice platform by making phone.plivo.com more redundant. However, the new deployment created performance issues in the form of locking and latency on a specific database table that was accessed for most customers. This occurred every time when the traffic for these services started spiking. We worked on those issues and built a new internal service to optimize the volume of data processed to avoid elevated database writes and latencies. We also deployed patches on April 27, 2017 that improved the overall stability and performance of our platform, while also readying it for much higher workloads. ** What are we doing about it for the future? ------------------------------------------------------------ While this incident was due to an error in configuration and provisioning by our domain registrar, we take complete responsibility for this outage. We are responsible in ensuring uptime of our services to our customers. Clearly with better checks and thorough processes we could have avoided the whole situation in spite of the error from the domain registrar. This entire outage exposed some critical flaws in our dependency on our 3rd party service providers. To ensure we minimize impact on Plivo?s services by 3rd party errors or issues, we have outlined a set of steps that we will initiate immediately: 1. Categorize all 3rd party services into different three priority levels (i.e., P1, P2, P3), based on potential impact on Plivo?s services. Detail potential workarounds in the event of experiencing downtime from these services. Perform monthly, quarterly, bi-annual, and annual audits and reviews of all P1 and P2 services for renewal and configuration settings. 2. Plan and renew all related category of services like domain names, TLS certificates, etc., for the longest period when possible. We have already executed this for our domain by renewing it for the next 10 years. We will execute the same strategy for all of our certificates and related services. 3. Setup automated monitoring to alert and notify all stakeholders in case any of our domains or similar services get within a month of their expiry date. Stakeholders will have the authority and access to take action immediately. This will avoid dependency on vendor notifications. 4. When possible, update our SDKs to be able to dynamically update domain endpoints, so a switch is possible at the customer's end without any application code changes. Our focus has always been to provide you the best quality of service and uptime, and this disruption clearly came up short of expectation. We apologize for the disruption and the inconvenience that this has caused your business and to your customers. We will work harder to earn back your trust by execution of all the steps that follow. Sincerely, The Plivo Team https://www.plivo.com/?utm_source=Domain+Post-mortem+-+Batch+3&utm_campaign… http://twitter.com/plivo?utm_source=Domain+Post-mortem+-+Batch+3&utm_campai… http://facebook.com/plivo?utm_source=Domain+Post-mortem+-+Batch+3&utm_campa… https://plus.google.com/+Plivo?utm_source=Domain+Post-mortem+-+Batch+3&utm_… Copyright ? 2017 Plivo All rights reserved / View as Webpage (http://mailchi.mp/7bab18c30aec/plivo-update-all-services-back-up-697689?e=9…)

1 0

Fax ATAs/devices
by caalvarez＠gmail.com April 28, 2017

April 28, 2017

Fax is dead. Long live fax. We've resisted supporting it, but customers still need it on occasion, and they hate having a separate landline carrier just for a fax line. So I'm wondering what others here use successfully to provide their customers with a "fax line" to a physical machine. We would only use a handful of them, and only with our customers who have a fully managed service (IE, 2-3ms connection directly to us over MPLS). We run Asterisk and pass T.38 to a few carriers. We currently do fax to e-mail inbound on Asterisk with no issues. Volume is very light, maybe 3-5 per day per customer, so things like the Vitelity FaxEnable don't make economic sense ($25/mo unlimited our cost).

12 26

Fax ATAs/devices
by caalvarez＠gmail.com April 27, 2017

April 27, 2017

Mike, the Obihai recommendation was great, and I've ordered one to test. It has great reviews and is damn cheap. On Thu, Apr 27, 2017 at 4:03 PM, Mike Ray, MBA, CNE, CTE < mike at commauthority.com> wrote: > Hi guys, > > > > We are a facilities-based CLEC and have a very reliable fax/POTS product > in addition to our popular SmartMail FAX fax-to-email service. Since we do > not use LCR of any sort and also handle all of our own media, fax/modem > calls are very reliable on our network using a standard ATA whether using > t.38 or ulaw. We?ve had the best luck so far with Obihai, but work with > any standard ATA out there. > > > > We also offer a VPN solution for SIP trunks to solve the NAT problem and > encrypt traffic in the middle. > > > > We have a very feature-rich portal where wholesale customers can perform > most tasks in an immediate and automated fashion. > > > > All the details are on our wholesale site wholesale.commauthority.com. > We?d love to have an opportunity to show you how well it works. Please let > me know if you?re interested. > > > > Regards, > > > > Mike > > > > Mike Ray, MBA, CNE, CTE > > Communications Authority, Inc. > > 11523 Palm Brush Trail #401 > > Lakewood Ranch, FL 34202 > > DIRECT: call or text 941 600-0207 <(941)%20600-0207> > > http://www.commauthority.com > > > > > > *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Keln > Taylor > *Sent:* Thursday, April 27, 2017 6:29 PM > *To:* Carlos Alvarez <caalvarez at gmail.com> > *Cc:* voiceops at voiceops.org > *Subject:* Re: [VoiceOps] Fax ATAs/devices > > > > Vitelity fax service is the best I know of. (With or without the FaxEnable > device.) I suspect that they are actually using some sort of modem bank to > send and receive faxes. (I would love to hear from someone who can confirm > or deny this.) > > > > You don't have to pay for the *unlimited *FaxEnable service. You can > purchase a FaxEnable device from them. (I think they are ~$100), pay a > small price for DID, and then pay per minute for faxing. > > > > All that being said, I would love to find a service that handled fax as > well as Vitelity. I only use Vitelity for fax service because I can't find > a better option. I am not a huge fan of their support or customer control > panel. > > > > > Sincerely, > > Keln Taylor > > 870-204-2121 <(870)%20204-2121> > > kelntaylor at gmail.com > > > > On Thu, Apr 27, 2017 at 4:30 PM, Carlos Alvarez <caalvarez at gmail.com> > wrote: > > Fax is dead. Long live fax. > > > > We've resisted supporting it, but customers still need it on occasion, and > they hate having a separate landline carrier just for a fax line. So I'm > wondering what others here use successfully to provide their customers with > a "fax line" to a physical machine. We would only use a handful of them, > and only with our customers who have a fully managed service (IE, 2-3ms > connection directly to us over MPLS). We run Asterisk and pass T.38 to a > few carriers. We currently do fax to e-mail inbound on Asterisk with no > issues. > > > > Volume is very light, maybe 3-5 per day per customer, so things like the > Vitelity FaxEnable don't make economic sense ($25/mo unlimited our cost). > > > > > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > > >

1 0

Fax ATAs/devices
by caalvarez＠gmail.com April 27, 2017

April 27, 2017

The info I found on your site says FaxEnable goes with a $25 unlimited service, not the metered services. Is that correct? We *probably* want to go with a non-proprietary device that connects to us by SIP, but are considering all options. We're already a Vitelity customer for certain types of traffic/numbers. On Thu, Apr 27, 2017 at 3:56 PM, Scott Navratil <snavratil at vitelity.com> wrote: > ?Thanks for the kind words Keln. > > > We actually use a large cluster of fax servers (proprietary) to process > the HTTPS fax traffic. You are correct on the Fax Enable devices; they are > actually $109 plus shipping and then you pay for usage. They do offer full > remote management too. > > > Regards, > > > Scott Navratil > VP, Channel Sales > Inteliquent d/b/a Vitelity > 303-997-2305 <(303)%20997-2305> (DID) > 303-991-7977 <(303)%20991-7977> (vFax) > ------------------------------ > *From:* VoiceOps <voiceops-bounces at voiceops.org> on behalf of Keln Taylor > <kelntaylor at gmail.com> > *Sent:* Thursday, April 27, 2017 4:28 PM > *To:* Carlos Alvarez > *Cc:* voiceops at voiceops.org > *Subject:* Re: [VoiceOps] Fax ATAs/devices > > Vitelity fax service is the best I know of. (With or without the FaxEnable > device.) I suspect that they are actually using some sort of modem bank to > send and receive faxes. (I would love to hear from someone who can confirm > or deny this.) > > You don't have to pay for the *unlimited *FaxEnable service. You can > purchase a FaxEnable device from them. (I think they are ~$100), pay a > small price for DID, and then pay per minute for faxing. > > All that being said, I would love to find a service that handled fax as > well as Vitelity. I only use Vitelity for fax service because I can't find > a better option. I am not a huge fan of their support or customer control > panel. > > > Sincerely, > Keln Taylor > 870-204-2121 <(870)%20204-2121> > kelntaylor at gmail.com > > On Thu, Apr 27, 2017 at 4:30 PM, Carlos Alvarez <caalvarez at gmail.com> > wrote: > >> Fax is dead. Long live fax. >> >> We've resisted supporting it, but customers still need it on occasion, >> and they hate having a separate landline carrier just for a fax line. So >> I'm wondering what others here use successfully to provide their customers >> with a "fax line" to a physical machine. We would only use a handful of >> them, and only with our customers who have a fully managed service (IE, >> 2-3ms connection directly to us over MPLS). We run Asterisk and pass T.38 >> to a few carriers. We currently do fax to e-mail inbound on Asterisk with >> no issues. >> >> Volume is very light, maybe 3-5 per day per customer, so things like the >> Vitelity FaxEnable don't make economic sense ($25/mo unlimited our cost). >> >> >> _______________________________________________ >> VoiceOps mailing list >> VoiceOps at voiceops.org >> https://puck.nether.net/mailman/listinfo/voiceops >> >> >

2 1

Paging without a modem
by gmina＠connectfirst.com April 26, 2017

April 26, 2017

Does anyone know of a service or service provider that can bridge the gap between now and 1995? We have a customer doing traditional answering service functions who needs to send to alpha and two-way pagers. Thanks, Geoff -- *Geoff Mina*CEO/Founder Connect First, Inc. 720.335.5924 Website <http://www.connectfirst.com/> | LinkedIn <http://www.linkedin.com/in/geoffmina> | Email <gmina at connectfirst.com>

4 3