Re: [VoiceOps] Alarm panels and how they dial DTMF digits - pots migration from DMS to Metaswitch issue

Jheeze, what an event ya poor bugger Paul! Granted I operate in an entirely different country, but when my school looses either or both of their dual fire monitoring channels (IP & cellular), the monitoring company calls my cellphone to let me know. The alarm does not trip! Heh :) Also a

Re: [VoiceOps] Bandwidth East Coast Issues

Right, yes, sorry - I should have been more explanative :) I simply meant to say "perhaps it's not just Bandwidth (or Voip.MS) that are the targets; perhaps it's the wider VoIP industry, and perhaps it's not quite over just yet..." > On 27/09/2021, at 3:33 AM, Mike Hammett wrote: > > That

Re: [VoiceOps] Bandwidth East Coast Issues

Not sure if Slashdot does... https://tech.slashdot.org/story/21/09/26/0014216/voipms-battles-week-long-sustained-ddos-for-ransom-attack > On 26/09/2021, at 12:47 PM, Peter Beckman via VoiceOps > wrote: > > BW Considers the incident resolved. ___

Re: [VoiceOps] Call Quality

I can attest to them being non-zero as I have handled multiple of these tickets myself! I don't believe they do it through arrogance or malice though - just plain ignorance. > On 15/06/2021, at 9:46 AM, Mike Hammett wrote: > > God, I hope customers don't hold their carriers responsible

Re: [VoiceOps] Call Quality

Not sure how useful it is Mike, but thought of a couple of examples: Dropped packets (eg from radio interfaces) NAT (eg one-way audio caused by broken ALGs, or lost signalling due to state table timeouts) Pete > On 14/06/2021, at 6:11 AM, Mike

Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data

Precisely. And those "NAT table entries" eventually time out. On CG-NAT they often time out aggressively; <60 seconds. Hence sending OPTIONS over SIP over UDP regularly keeps the NAT table entries refreshed and active and therefore the UDP 'connection' open. I've come across firewalls with 30

Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data

49 seconds... how trusting! ;-) We use 25. Pete (it's true, but said tongue-in-cheek as I'm sure you have your data to show where the bulk of NATs expire) > On 11/06/2021, at 12:46 AM, Dovid Bender wrote: > > (we send SIP OPTIONS every 49 seconds) to ensure that the session > stays

Re: [VoiceOps] AT Verizon to block text messaging

I am surprised that less than 10 distinct recipients per day is considered atypical! It's certainly not on my phone. Then agian, I only really txt my wife :) > On 8/03/2021, at 9:30 AM, Peter Beckman wrote: > > Page 10: Typical Consumer Operation (P2P) > - 15-60 messages per minute >

Re: [VoiceOps] False 911 calls and old abandoned DID

Pete > On 22/01/2021, at 1:25 PM, Mike Johnston wrote: > > On 2021-01-21 17:42, Pete Mundy wrote: >> on the PoTS equipment I'm familiar with (others can chime in and correct me >> if I'm wrong on a larger scale) the numbers are reversed > > According to Wikipedia: &g

Re: [VoiceOps] False 911 calls and old abandoned DID

So close! But on the PoTS equipment I'm familiar with (others can chime in and correct me if I'm wrong on a larger scale) the numbers are reversed (well for all except 5 :) Basically it counts down from 10. 1 pulse is digit '9', 4 pulses is digit '6', 10 pulses is digit '0'. So do dial 911

Re: [VoiceOps] ATAs compatible with fire alarm panels

+1 for Yeastar > On 16/12/2020, at 10:44 AM, Brandon Svec wrote: > > As far as ATA's go, I like Yeastar. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Got my first inbound call with a STIR/SHAKEN checkmark

I agree, and I believe it will happen somewhere around approximately the turn of the 22nd century. :) Pete Mundy PBX/hosted voip operator On 10/09/2020, at 10:23 AM, Brandon Svec wrote: > Someday though.. I think there will be a confluence of coverage, call quality and mobile dev

Re: [VoiceOps] Get ready for a weird dialplan change. 9-8-8 suicide hotline.

We play them a little audio telling them that they dialled 9 for an outside line but that they don't need to, and that the call will now be put through for them anyway (with the 9 stripped off). It adds about 4 seconds onto the setup time per call playing the audio and usually only takes 2 or

Re: [VoiceOps] RAY BAUMS Act - How are people planning on complying?

I guess different people have different interpretation of that wording :) To me it seems UNreasonable to assume that a phone or device with a sticker on it that says "This phone does not work for emergency calls" can call emergency services. > On 24/01/2020, at 6:46 AM, Carlos Alvarez

Re: [VoiceOps] Old PA System setup

Can't see why not! Just be sure to turn it down before plugging it in and make sure it doesn't get turned up later. > On 20/04/2019, at 12:47 AM, Darin Steffl wrote: > > the snom should still work if I put in a line level adapter? Can't I just > turn the output way down on the speaker

Re: [VoiceOps] Old PA System setup

You can still use the Snom PA1 I would think. Just reduce the PA1's output levels to line level for input into the Valcoms and use a regular 24VDC power supply to send power. The wires can be terminated directly into each:

Re: [VoiceOps] Request for Opinions: High density ATA's

Good on ya for doing the right thing in calling them out on it anyway Nathan! Great story :) I've only used the single and dual port versions of these Yeastar boxes but I also discovered they were linux & Asterisk and I've found them to be quite reliable in the small numbers I've used. Pete

Re: [VoiceOps] 911 testing

> On 22/01/2018, at 6:47 AM, Jay Hennigan wrote: > > On 12/28/17 10:47 AM, Ken Mix wrote: >> We allow customers to toggle “E911 Test Mode” via our portal so that they >> can dial 911 without calls routing to the PSAP, which we’ve found works >> better than dialing a test number

Re: [VoiceOps] VoIP Testing

> On 24/05/2017, at 9:20 am, Shripal Daphtary wrote: > > Mark, what type of device are you using as the sensor? > > I've been looking for a raspberry pi with two Ethernet interfaces but I can't > seem to find one. > > I'm assuming we need on port for port mirror traffic

Re: [VoiceOps] Ideas for Building Inbound Redundancy

> On 8/02/2017, at 7:58 am, Nick Olsen wrote: > > Thanks for sharing your Config and thoughts with the community, It's given me > some Lab Ideas! +1! Thanks Markus, it was interesting to consider the config and it provided good food for thought :) Pete smime.p7s

Re: [VoiceOps] Hotel IP phones

Get one of each and give them a try. I prefer the Yealink over the Snom and Grandstream. I find the styling more to my taste and prefer the UI and underlying OS. But each to their own :) > On Wed, Jan 4, 2017 at 5:17 PM, Ernesto Miro Cons >

Re: [VoiceOps] Hunt Group "as a Service"

Hi Rafael I'm pretty sure these guys are do what you need, using their 'Locate Me' feature: http://2talk.com I'm not affiliated in any way; just a happy customer. Pete > On 12/08/2016, at 4:26 am, Rafael Possamai wrote: > > Hi all, > > Not sure if this has been

Re: [VoiceOps] Recommended Website/IP monitoring tool

This is all sounding _very_ familiar! We do quite similar things using RPis here too, right down to the reverse SSH tunnels. Incredibly useful for remote diagnosis, visibility and proactive response. Our sample size isn't huge, only just over 3X what you've mentioned, but thus-far we've had

Re: [VoiceOps] Recommended Website/IP monitoring tool

Yep! :) We used the controllable built-in LED to flash out the pi's IP(v4) address so our engineers can discover it and connect to it across the LAN without needing any sort of display. We also used to have it 'speak' it's IP address out the earphones port (using espeak), but ended up

Re: [VoiceOps] Recommended Website/IP monitoring tool

I can recommend uptimerobot.com. I tried their free-tier service after an earlier recommendation which was either on this list or NANOG; I forget which. The service has been very reliable other than a few blips with IPv6 to some local hosts (we're down in New Zealand and it's likely related to

Re: [VoiceOps] Yealink's new "E2" hardware variants

etter cpu. For example t19 wont accept > sha256 signed certificates, because of memory constrains or at least > that what I've been told from yealink. > > On 03/11/15 01:58, Pete Mundy wrote: >> Hi list, >> >> Does anyone here have any information they can share on what

Re: [VoiceOps] Need service provider to transfer numbers to.

on such a large number of concurrent ports. They may do you a deal! They have other whitebox and reseller options which may work out cheaper for this number of DDIs too. Hope this helps :) Pete Mundy Nelson, NZ On 1/11/2015, at 12:14 AM, nanog <na...@wjp.net> wrote: > I know thi

Re: [VoiceOps] WiFi SIP phones recommendations

I think that part of the problem is that underlying wired backbone layer II network also needs to catch up on the port-change (possibly even switch-change) when the client is (invisibly) handed over to the new radio.  Think along the lines o 30-second MAC table timeout before broadcast occurs