VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
March 2020
- 39 participants
- 90 messages
E911 - Working from home
by marylou@backuptelecom.com
911 has always operated on a completely separate and fully redundant
network so that 911 calls can't be blocked by regular traffic.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-03-20 07:50 AM, Hiers, David wrote:
> Agreed; 911 is a part of a much larger system, and public confidence
> in the entire emergency response system is a officially a Big Deal.
>
>
> David
>
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
> Mary Lou Carey
> Sent: Thursday, March 19, 2020 6:23 PM
> To: J. Hellenthal <jhellenthal at dataix.net>
> Cc: Voiceops.org <voiceops at voiceops.org>
> Subject: Re: [VoiceOps] E911 - Working from home
>
> Because when people have an emergency their brain cells don't work as
> well. They see a phone and expect it to work regardless. That's why
> the FCC mandated that if you can make an originating call.....you have
> to provide 911 and be able to update the location accurately!
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2020-03-19 04:57 PM, J. Hellenthal via VoiceOps wrote:
>> Just sayin but they have phones ... why do they need your 911 routing
>>
>> --
>> J. Hellenthal
>>
>> The fact that there's a highway to Hell but only a stairway to Heaven
>> says a lot about anticipated traffic volume.
>>
>>> On Mar 19, 2020, at 13:56, Izzy Goldstein - TeleGo
>>> <igoldstein at telego.net> wrote:
>>
>>> ?
>>>
>>> how messy is this needing to change many E911 locations for Remote
>>> Employees --
>>>
>>> Izzy Goldstein
>>>
>>> Chief Technology Officer
>>>
>>> Main: (212) 477-1000 x 2085 [1]
>>>
>>> Direct: (929) 477-2085 [2]
>>>
>>> Website: www.telego.com [3]
>>>
>>> [4]
>>>
>>> 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 [5]
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>> Links:
>> ------
>> [1] tel:(212)%20477-1000
>> [2] tel:(929)%20477-2085
>> [3] http://www.telego.net/
>> [4] http://www.telego.com/
>> [5] https://youtu.be/DaT8YAZ4V0w
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> ----------------------------------------------------------------------
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and
> confidential. If the reader of the message is not the intended
> recipient or an authorized representative of the intended recipient,
> you are hereby notified that any dissemination of this communication
> is strictly prohibited. If you have received this communication in
> error, notify the sender immediately by return email and delete the
> message and any attachments from your system.
March 20, 2020
Investigating random call completion issues nationwide
by voiceops@ics-il.net
This is one place the IP world (while far from perfect) is vastly superior to the PSTN. Any given IP address can have many paths to success and they can be changed on a whim. You don't have to wait forever for LERG updates.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Darren Schreiber" <darren at 2600hz.com>
To: voiceops at voiceops.org
Sent: Thursday, March 19, 2020 6:29:21 PM
Subject: [VoiceOps] Investigating random call completion issues nationwide
Hi folks,
We?ve been getting occasional, very infrequent, reports of people hitting busy signals or intercept messages when calling numbers routed to us. At first we thought the issue was between us and Peerless but we now have reports with bandwidth and Inteliquent. So, then of course naturally we thought the issue was in our systems. But again, we?ve come up empty. We also thought it may be trunk or port limitations upstream. Have checked those. No dice.
The issue seems to always be the same. Customer from cell phone or landline dials a number, reaches a busy signal or intercept message. All reports are from Verizon or AT&T callers. We check our logs, don?t see any attempt to even reach our system (we log freakin everything). So we reach out to the upstream provider, and they too claim it never reached their tandem/network.
I know everyone on earth is currently WFH so perhaps that warrants just shutting up & dealing with it but I?ve been surprised not to see any chatter on this list or elsewhere in this regard. Is anyone else having indications of capacity issues (and are y?all just not talking about it) or is it just us and we should keep looking?
- Darren
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
March 20, 2020
E911 - Working from home
by David.Hiers@cdk.com
Agreed; 911 is a part of a much larger system, and public confidence in the entire emergency response system is a officially a Big Deal.
David
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mary Lou Carey
Sent: Thursday, March 19, 2020 6:23 PM
To: J. Hellenthal <jhellenthal at dataix.net>
Cc: Voiceops.org <voiceops at voiceops.org>
Subject: Re: [VoiceOps] E911 - Working from home
Because when people have an emergency their brain cells don't work as well. They see a phone and expect it to work regardless. That's why the FCC mandated that if you can make an originating call.....you have to provide 911 and be able to update the location accurately!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-03-19 04:57 PM, J. Hellenthal via VoiceOps wrote:
> Just sayin but they have phones ... why do they need your 911 routing
>
> --
> J. Hellenthal
>
> The fact that there's a highway to Hell but only a stairway to Heaven
> says a lot about anticipated traffic volume.
>
>> On Mar 19, 2020, at 13:56, Izzy Goldstein - TeleGo
>> <igoldstein at telego.net> wrote:
>
>> ?
>>
>> how messy is this needing to change many E911 locations for Remote
>> Employees --
>>
>> Izzy Goldstein
>>
>> Chief Technology Officer
>>
>> Main: (212) 477-1000 x 2085 [1]
>>
>> Direct: (929) 477-2085 [2]
>>
>> Website: www.telego.com [3]
>>
>> [4]
>>
>> 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 [5]
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> Links:
> ------
> [1] tel:(212)%20477-1000
> [2] tel:(929)%20477-2085
> [3] http://www.telego.net/
> [4] http://www.telego.com/
> [5] https://youtu.be/DaT8YAZ4V0w
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
----------------------------------------------------------------------
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
March 20, 2020
Investigating random call completion issues nationwide
by igoldstein@telego.net
ive also had issues with DIDWW DID's in israel, being called from
israel cell phones didnt connect.
seems to be industry standard
On Fri, Mar 20, 2020 at 12:15 AM Darren Schreiber <darren at 2600hz.com> wrote:
> They have that up as an auto-responder (they sent it to me twice heh).
> Then they wrote back to try and find the calls, but did not find them
> hitting their network. That?s why I thought it was their issue at first,
> but then we had the same report on a bandwidth.com number. Then a few
> more reports. And you know for each report we get there?s 10 people that
> aren?t saying anything and just redial. Well, I guess it depends on the
> customer.
>
>
>
> Anyway, we?ll keep an eye on it. We also hit record calling this week so
> that?s another data point that it?s just high traffic. Many people seem to
> be doing remote ?check-in? meetings with all their employees daily, in the
> morning, so I suspect that?s the issue.
>
>
>
> *From: *Izzy Goldstein - TeleGo <igoldstein at telego.net>
> *Date: *Thursday, March 19, 2020 at 9:12 PM
> *To: *Darren Schreiber <darren at 2600hz.com>
> *Cc: *"voiceops at voiceops.org" <voiceops at voiceops.org>
> *Subject: *Re: [VoiceOps] Investigating random call completion issues
> nationwide
>
>
>
> i experienced the same issues
>
>
>
>
>
> Peerless says:
>
>
>
>
>
> We?re sorry for the calling issues you?re experiencing today. As you may
> know, these are extraordinary times and we are currently seeing network
> congestion industry wide ? the events of the past week have had a direct
> impact on all telecommunication carriers. Due to the sheer volume of
> individuals and businesses that are now working remotely, blocking or
> congestion outside our network is impacting call completion. peerless is
> relentlessly pursuing all options with all of our partners, and working to
> ensure that they?re aware of the call completion issues. While peerless can
> and will address some of these issues directly, our troubleshooting
> indicates that many congestion-related issues are occurring within networks
> of our carrier customers or other intermediaries which we cannot control.
> Nonetheless, we are working tirelessly to resolve capacity issues wherever
> they exist. Thanks for your understanding.
>
>
>
> On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com>
> wrote:
>
> Hi folks,
>
> We?ve been getting occasional, very infrequent, reports of
> people hitting busy signals or intercept messages when calling numbers
> routed to us. At first we thought the issue was between us and Peerless but
> we now have reports with bandwidth and Inteliquent. So, then of course
> naturally we thought the issue was in our systems. But again, we?ve come up
> empty. We also thought it may be trunk or port limitations upstream. Have
> checked those. No dice.
>
>
>
> The issue seems to always be the same. Customer from cell
> phone or landline dials a number, reaches a busy signal or intercept
> message. All reports are from Verizon or AT&T callers. We check our logs,
> don?t see any attempt to even reach our system (we log freakin everything).
> So we reach out to the upstream provider, and they too claim it never
> reached their tandem/network.
>
>
>
> I know everyone on earth is currently WFH so perhaps that
> warrants just shutting up & dealing with it but I?ve been surprised not to
> see any chatter on this list or elsewhere in this regard. Is anyone else
> having indications of capacity issues (and are y?all just not talking about
> it) or is it just us and we should keep looking?
>
>
>
> - Darren
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
> --
>
> *Izzy Goldstein *
>
> *Chief Technology Officer *
>
> Main: *(212) 477-1000 x 2085 <(212)%20477-1000>*
>
> Direct: *(929) 477-2085 <(929)%20477-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>
>
--
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>
March 20, 2020
Investigating random call completion issues nationwide
by darren@2600hz.com
They have that up as an auto-responder (they sent it to me twice heh). Then they wrote back to try and find the calls, but did not find them hitting their network. That?s why I thought it was their issue at first, but then we had the same report on a bandwidth.com number. Then a few more reports. And you know for each report we get there?s 10 people that aren?t saying anything and just redial. Well, I guess it depends on the customer.
Anyway, we?ll keep an eye on it. We also hit record calling this week so that?s another data point that it?s just high traffic. Many people seem to be doing remote ?check-in? meetings with all their employees daily, in the morning, so I suspect that?s the issue.
From: Izzy Goldstein - TeleGo <igoldstein at telego.net>
Date: Thursday, March 19, 2020 at 9:12 PM
To: Darren Schreiber <darren at 2600hz.com>
Cc: "voiceops at voiceops.org" <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Investigating random call completion issues nationwide
i experienced the same issues
Peerless says:
We?re sorry for the calling issues you?re experiencing today. As you may know, these are extraordinary times and we are currently seeing network congestion industry wide ? the events of the past week have had a direct impact on all telecommunication carriers. Due to the sheer volume of individuals and businesses that are now working remotely, blocking or congestion outside our network is impacting call completion. peerless is relentlessly pursuing all options with all of our partners, and working to ensure that they?re aware of the call completion issues. While peerless can and will address some of these issues directly, our troubleshooting indicates that many congestion-related issues are occurring within networks of our carrier customers or other intermediaries which we cannot control. Nonetheless, we are working tirelessly to resolve capacity issues wherever they exist. Thanks for your understanding.
On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com<mailto:darren at 2600hz.com>> wrote:
Hi folks,
We?ve been getting occasional, very infrequent, reports of people hitting busy signals or intercept messages when calling numbers routed to us. At first we thought the issue was between us and Peerless but we now have reports with bandwidth and Inteliquent. So, then of course naturally we thought the issue was in our systems. But again, we?ve come up empty. We also thought it may be trunk or port limitations upstream. Have checked those. No dice.
The issue seems to always be the same. Customer from cell phone or landline dials a number, reaches a busy signal or intercept message. All reports are from Verizon or AT&T callers. We check our logs, don?t see any attempt to even reach our system (we log freakin everything). So we reach out to the upstream provider, and they too claim it never reached their tandem/network.
I know everyone on earth is currently WFH so perhaps that warrants just shutting up & dealing with it but I?ve been surprised not to see any chatter on this list or elsewhere in this regard. Is anyone else having indications of capacity issues (and are y?all just not talking about it) or is it just us and we should keep looking?
- Darren
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
--
Izzy Goldstein
Chief Technology Officer
Main: (212) 477-1000 x 2085<tel:(212)%20477-1000>
Direct: (929) 477-2085<tel:(929)%20477-2085>
Website: www.telego.com<http://www.telego.net/>
[https://lh4.googleusercontent.com/Ze7NkT2QtotXfVWbpWXrpSMRIcAdqb0Ci0_RZsAjQ…]<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>
March 20, 2020
Investigating random call completion issues nationwide
by igoldstein@telego.net
i experienced the same issues
Peerless says:
We?re sorry for the calling issues you?re experiencing today. As you may
know, these are extraordinary times and we are currently seeing network
congestion industry wide ? the events of the past week have had a direct
impact on all telecommunication carriers. Due to the sheer volume of
individuals and businesses that are now working remotely, blocking or
congestion outside our network is impacting call completion. peerless is
relentlessly pursuing all options with all of our partners, and working to
ensure that they?re aware of the call completion issues. While peerless can
and will address some of these issues directly, our troubleshooting
indicates that many congestion-related issues are occurring within networks
of our carrier customers or other intermediaries which we cannot control.
Nonetheless, we are working tirelessly to resolve capacity issues wherever
they exist. Thanks for your understanding.
On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com> wrote:
> Hi folks,
>
> We?ve been getting occasional, very infrequent, reports of
> people hitting busy signals or intercept messages when calling numbers
> routed to us. At first we thought the issue was between us and Peerless but
> we now have reports with bandwidth and Inteliquent. So, then of course
> naturally we thought the issue was in our systems. But again, we?ve come up
> empty. We also thought it may be trunk or port limitations upstream. Have
> checked those. No dice.
>
>
>
> The issue seems to always be the same. Customer from cell
> phone or landline dials a number, reaches a busy signal or intercept
> message. All reports are from Verizon or AT&T callers. We check our logs,
> don?t see any attempt to even reach our system (we log freakin everything).
> So we reach out to the upstream provider, and they too claim it never
> reached their tandem/network.
>
>
>
> I know everyone on earth is currently WFH so perhaps that
> warrants just shutting up & dealing with it but I?ve been surprised not to
> see any chatter on this list or elsewhere in this regard. Is anyone else
> having indications of capacity issues (and are y?all just not talking about
> it) or is it just us and we should keep looking?
>
>
>
> - Darren
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
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>
March 20, 2020
E911 - Working from home
by richard@teraquant.com
I guess one phone dispatched to a home working location does not qualify as ?Multi-Line Telephone System? MLTS i.e. PBX with SIP trunk or ISDN PRI etc.
However, the RAY BAUM?S Act , which kicks in next year 2021, may sharpen FCC?s oversight of location, accompanying a 911 call.
The Act requires that all 911 calls to the appropriate PSAP should be a accompanied with ?dispatchable location? information. As defined in the law, dispatchable location is: ?the street address of the calling party, and additional information such as room number, floor number, or similar information necessary to adequately identify the location of the calling party.?
Many Thanks & Best Regards,
Richard Jobson
Teraquant Corporation
ph: 719 488 1003
d/l: (719) 766-8523
www.teraquant.com
Info at teraquant.com
www.linkedin.com/in/richardjobson
Network Monitoring and Service Assurance - Speech Quality Experts (PESQ/POLQA) and Active Testing - Reporting ? HPBX - Session Border Controllers ? SDN and SD-WAN - Big Data Analytics and fraud detection and protection.
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mary Lou Carey <marylou at backuptelecom.com>
Date: Thursday, March 19, 2020 at 7:24 PM
To: "J. Hellenthal" <jhellenthal at dataix.net>
Cc: "Voiceops.org" <voiceops at voiceops.org>
Subject: Re: [VoiceOps] E911 - Working from home
Because when people have an emergency their brain cells don't work as
well. They see a phone and expect it to work regardless. That's why the
FCC mandated that if you can make an originating call.....you have to
provide 911 and be able to update the location accurately!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-03-19 04:57 PM, J. Hellenthal via VoiceOps wrote:
Just sayin but they have phones ... why do they need your 911 routing
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven
says a lot about anticipated traffic volume.
On Mar 19, 2020, at 13:56, Izzy Goldstein - TeleGo
<igoldstein at telego.net> wrote:
?
how messy is this needing to change many E911 locations for Remote
Employees --
Izzy Goldstein
Chief Technology Officer
Main: (212) 477-1000 x 2085 [1]
Direct: (929) 477-2085 [2]
Website: www.telego.com [3]
[4]
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 [5]
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Links:
------
[1] tel:(212)%20477-1000
[2] tel:(929)%20477-2085
[3] http://www.telego.net/
[4] http://www.telego.com/
[5] https://youtu.be/DaT8YAZ4V0w
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
March 20, 2020
Investigating random call completion issues nationwide
by jaybinks@gmail.com
We are seeing similar things in Australia over the last few days.
I can generally get calls out of our network (being that we are so well
connected to almost every other sizeable carrier in-country),
however, we are definitely seeing some inbound traffic "go missing" as you
are talking about.
The calls simply never hit our network.
I know of one carrier in country with fairly massive confirmed capacity
issues.
Another has unofficially mentioned that if current traffic volumes continue
to increase they are going to hit issues.
I just think everyone is seeing unprecedented traffic growth.
I don't think it's just working from home.
- I think its people calling to check up on loved ones.
- People calling co-workers rather than IM while working from home. (we
are seeing an increase in this in our own staff... when in isolation people
want to talk not IM, so they get some human contact)
- Then I know for sure of "Covid 19 response lines" setup by governments
that are now carrying huge amount of calls
On that note, if I can help anyone in Australia or NZ right now.. contact
me. ( yes I'm with a smaller Tier 1 in Aus )
More than happy to help where we can.
but I hope you all get through this as best you can.
On Fri, 20 Mar 2020 at 09:40, Gavin Henry <ghenry at suretec.co.uk> wrote:
> When we pulled up our Homer traces we only saw the successful attempt,
> nothing else, nor our carriers. Same story. I reckon mobile core.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
Sincerely
Jay
March 20, 2020
E911 - Working from home
by marylou@backuptelecom.com
Because when people have an emergency their brain cells don't work as
well. They see a phone and expect it to work regardless. That's why the
FCC mandated that if you can make an originating call.....you have to
provide 911 and be able to update the location accurately!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-03-19 04:57 PM, J. Hellenthal via VoiceOps wrote:
> Just sayin but they have phones ... why do they need your 911 routing
>
> --
> J. Hellenthal
>
> The fact that there's a highway to Hell but only a stairway to Heaven
> says a lot about anticipated traffic volume.
>
>> On Mar 19, 2020, at 13:56, Izzy Goldstein - TeleGo
>> <igoldstein at telego.net> wrote:
>
>> ?
>>
>> how messy is this needing to change many E911 locations for Remote
>> Employees --
>>
>> Izzy Goldstein
>>
>> Chief Technology Officer
>>
>> Main: (212) 477-1000 x 2085 [1]
>>
>> Direct: (929) 477-2085 [2]
>>
>> Website: www.telego.com [3]
>>
>> [4]
>>
>> 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 [5]
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> Links:
> ------
> [1] tel:(212)%20477-1000
> [2] tel:(929)%20477-2085
> [3] http://www.telego.net/
> [4] http://www.telego.com/
> [5] https://youtu.be/DaT8YAZ4V0w
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
March 20, 2020
Investigating random call completion issues nationwide
by marylou@backuptelecom.com
If the calls originate from AT&T and Verizon, their SS7 network should
be able to see where the call failed. I'd have them put a trouble ticket
in with their carrier.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-03-19 06:29 PM, Darren Schreiber wrote:
> Hi folks,
>
> We?ve been getting occasional, very infrequent,
> reports of people hitting busy signals or intercept messages when
> calling numbers routed to us. At first we thought the issue was
> between us and Peerless but we now have reports with bandwidth and
> Inteliquent. So, then of course naturally we thought the issue was in
> our systems. But again, we?ve come up empty. We also thought it may
> be trunk or port limitations upstream. Have checked those. No dice.
>
> The issue seems to always be the same. Customer from
> cell phone or landline dials a number, reaches a busy signal or
> intercept message. All reports are from Verizon or AT&T callers. We
> check our logs, don?t see any attempt to even reach our system (we
> log freakin everything). So we reach out to the upstream provider, and
> they too claim it never reached their tandem/network.
>
> I know everyone on earth is currently WFH so perhaps
> that warrants just shutting up & dealing with it but I?ve been
> surprised not to see any chatter on this list or elsewhere in this
> regard. Is anyone else having indications of capacity issues (and are
> y?all just not talking about it) or is it just us and we should keep
> looking?
>
> - Darren
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
March 20, 2020