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
April 2019
- 41 participants
- 81 messages
Dealing with a spammer?
by aaron@heyaaron.com
For the last few hours I've been getting calls and texts from 800-636-7230
telling me my phone number has been compromised. When I call that number,
they answer with variations of "IRS Call Center" and then proceed to ask
for name, address, social, etc to verify my account.
I've never dealt with spammers who have an 800 number and am clueless on
locating the carrier to report it. (Not to mention I'm already bored of
queuing up 100 calls to their number and automatically conferencing them in
to an echo test or speaking clock.)
Any pointers?
-A
April 11, 2019
International (Non-US/Canada) Termination Providers
by jared@compuwizz.net
I've had pretty good luck cherry picking countries from DT ICSS, TI
Sparkle, Telefonica, TATA, PCCW, ibasis, Telia, and others where they tend
to have networks in country. Then using Verizon and Inteliquent to fill in
the gaps with their premium routes. It doesn't make for the cheapest
product to offer or the easiest to automate but quality complaints (CLI,
PDD, audio quality, FAS) dropped significantly. I'd add BT and Orange but
they want $50k plus deposits and thats just not practical for our size.
If you're looking for places to put small volumes of call center/short
duration traffic on, you'll spend considerable time trying to keep routes
open for any length of time. Which in that case, find someone with access
to Verizon's HVSD International rates and send it there. Then tell me who
it is so we can also buy from them :)
On Fri, Apr 5, 2019 at 4:44 PM Peter Beckman <beckman at angryox.com> wrote:
> We've been happy with nobody, like you, on both reachability and cost.
>
> We use Thinq for 38.1% of our international termination in the last month.
> We've had issues where a call to the destination number is not the actual
> intended endpoint. Mostly it is fine, but like I said not 100% happy. But
> maybe that's a pipe dream for any carrier.
>
> We use Onvoy/Voyant/Vitelity for another 47%, but high cost there.
>
> We are enabling the Bandwidth.com Intl deck and are looking at Inteliquent,
> but we also spend more than you do, which might be a dealbreaker for you
> and those carriers.
>
> We have a carrier that we use for International termination for 15% now and
> they are reliable but expensive and much of our termination goes through
> Inteliquent anyway, we're just paying a pass-thru premium.
>
> Beckman
>
> PS - numbers rounded, vaguely
>
> On Fri, 5 Apr 2019, Ivan Kovacevic wrote:
>
> > Hello,
> >
> > We have been struggling to find good international routes. We mostly
> handle
> > contact centre traffic in NA and do not have much traffic ($500ish per
> > month) internationally, but it has been exceedingly painful to manage.
> >
> > We've tried a couple of carriers (Level3 - expensive and bad, TATA -
> > cheaper but bad and will randomly block traffic, couple of CLECs who also
> > offer A-Z).
> >
> > Financially it's not worth the hassle and managing the providers, but our
> > contact centre clients do need to be able to make non-contact centre
> > international calls on occasion, so we have to support it.
> >
> > Any suggestions?
> >
> > <http://www.startelecom.ca>
> >
> > *Ivan Kovacevic*
> >
> > *STAR TELECOM*
> >
> > *www.startelecom.ca <http://www.startelecom.ca>*
> >
> > --
> >
> >
> > NOTE: This email message and
> > any attachments are for the sole use of the
> > intended recipient(s) and may
> > contain confidential and/or privileged
> > information. Any unauthorized review,
> > use, disclosure or distribution is
> > prohibited. If you are not the intended recipient,
> > please contact the
> > sender by replying to this email, and destroy all copies of
> > the original
> > message.
> >
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com
> http://www.angryox.com/
>
> ---------------------------------------------------------------------------_______________________________________________
> 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
>
April 8, 2019
International (Non-US/Canada) Termination Providers
by beckman@angryox.com
We've been happy with nobody, like you, on both reachability and cost.
We use Thinq for 38.1% of our international termination in the last month.
We've had issues where a call to the destination number is not the actual
intended endpoint. Mostly it is fine, but like I said not 100% happy. But
maybe that's a pipe dream for any carrier.
We use Onvoy/Voyant/Vitelity for another 47%, but high cost there.
We are enabling the Bandwidth.com Intl deck and are looking at Inteliquent,
but we also spend more than you do, which might be a dealbreaker for you
and those carriers.
We have a carrier that we use for International termination for 15% now and
they are reliable but expensive and much of our termination goes through
Inteliquent anyway, we're just paying a pass-thru premium.
Beckman
PS - numbers rounded, vaguely
On Fri, 5 Apr 2019, Ivan Kovacevic wrote:
> Hello,
>
> We have been struggling to find good international routes. We mostly handle
> contact centre traffic in NA and do not have much traffic ($500ish per
> month) internationally, but it has been exceedingly painful to manage.
>
> We've tried a couple of carriers (Level3 - expensive and bad, TATA -
> cheaper but bad and will randomly block traffic, couple of CLECs who also
> offer A-Z).
>
> Financially it's not worth the hassle and managing the providers, but our
> contact centre clients do need to be able to make non-contact centre
> international calls on occasion, so we have to support it.
>
> Any suggestions?
>
> <http://www.startelecom.ca>
>
> *Ivan Kovacevic*
>
> *STAR TELECOM*
>
> *www.startelecom.ca <http://www.startelecom.ca>*
>
> --
>
>
> NOTE: This email message and
> any attachments are for the sole use of the
> intended recipient(s) and may
> contain confidential and/or privileged
> information. Any unauthorized review,
> use, disclosure or distribution is
> prohibited. If you are not the intended recipient,
> please contact the
> sender by replying to this email, and destroy all copies of
> the original
> message.
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
April 5, 2019
International (Non-US/Canada) Termination Providers
by dovid@telecurve.com
Do you have any one country you are calling or is it just generic all over
the world?
On Fri, Apr 5, 2019 at 4:01 PM Ryan Delgrosso <ryandelgrosso at gmail.com>
wrote:
> Ill second thinq. Not really a carrier, more of a meta-carrier. Easy
> access to all the players with transparency.
> On 4/5/2019 7:30 AM, Matthew Crocker wrote:
>
> I recommend ThinQ for international. Their LCR is pretty good and they
> have some nice fraud protection.
>
> On Apr 5, 2019, at 10:17 AM, Ivan Kovacevic <ivan.kovacevic at startelecom.ca>
> wrote:
>
>
> Hello,
>
> We have been struggling to find good international routes. We mostly
> handle contact centre traffic in NA and do not have much traffic ($500ish
> per month) internationally, but it has been exceedingly painful to manage.
>
> We've tried a couple of carriers (Level3 - expensive and bad, TATA -
> cheaper but bad and will randomly block traffic, couple of CLECs who also
> offer A-Z).
>
> Financially it's not worth the hassle and managing the providers, but our
> contact centre clients do need to be able to make non-contact centre
> international calls on occasion, so we have to support it.
>
> Any suggestions?
>
> <http://www.startelecom.ca>
>
> *Ivan Kovacevic*
>
> *STAR TELECOM*
>
> *www.startelecom.ca <http://www.startelecom.ca>*
>
>
> NOTE: This email message and any attachments are for the sole use of the
> intended recipient(s) and may contain confidential and/or privileged
> information. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, please contact the
> sender by replying to this email, and destroy all copies of the original
> message.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> _______________________________________________
> VoiceOps mailing listVoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
April 5, 2019
International (Non-US/Canada) Termination Providers
by ryandelgrosso@gmail.com
Ill second thinq. Not really a carrier, more of a meta-carrier. Easy
access to all the players with transparency.
On 4/5/2019 7:30 AM, Matthew Crocker wrote:
> I recommend ThinQ for international. ?Their LCR is pretty good and
> they have some nice fraud protection.
>
> On Apr 5, 2019, at 10:17 AM, Ivan Kovacevic
> <ivan.kovacevic at startelecom.ca <mailto:ivan.kovacevic at startelecom.ca>>
> wrote:
>
>>
>> Hello,
>>
>> We have been struggling to find good international routes. We mostly
>> handle contact centre traffic in NA and do not have much traffic
>> ($500ish per month) internationally, but it has been exceedingly
>> painful to manage.
>>
>> We've tried a couple of carriers (Level3 - expensive and bad, TATA -
>> cheaper but bad and will randomly block traffic, couple of CLECs who
>> also offer A-Z).
>>
>> Financially it's not worth the hassle and managing the providers, but
>> our contact centre clients do need to be able to make non-contact
>> centre international calls on occasion, so we have to support it.
>>
>> Any suggestions?
>>
>> <http://www.startelecom.ca>
>>
>>
>>
>>
>> *Ivan Kovacevic*/
>> //
>> /*STAR TELECOM*
>>
>> /www.startelecom.ca <http://www.startelecom.ca>/
>>
>>
>>
>> NOTE: This email message and any attachments are for the sole use of
>> the intended recipient(s) and may contain confidential and/or
>> privileged information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient,
>> please contact the sender by replying to this email, and destroy all
>> copies of the original message.
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto: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
April 5, 2019
Hotel Phone
by ryandelgrosso@gmail.com
FWIW YOu need to provide per room routing but a DID per room isnt
required if you can make that happen other ways.
For example, West now offers in their NG platform to send an XML body
with the invite to provide details intra-building routing. You still
need to provide descreet callback info, but for that suite of 100 hotel
rooms, you could use a block of 5-10 numbers and assign them to each
room that dials 911 for a temporary callback period, this will give you
bi-directional reachability from a 911 perspective without managing and
provisioning hundreds of sparsley used numbers.
You could also leverage their enterprise 911 option where you send a
distinct sip URI that is statically mapped to a location (address and
room/floor etc) and they will masquerade to the PSAP with a unique phone
number.
Personally if i were designing a system today (and I am) i would take
the first option and supply the info in the outbound invite for maximum
flexibility.
On 4/4/2019 11:22 PM, Matthew Yaklin wrote:
> That is correct. A DID for every phone and listed by e911. For example
> in NH it is law schools have it now days to get their special erate
> funding. When they call 911 they see very detailed information about
> floor, room, etc.. and the phone can be called back directly. We do it
> for every customer that has that specific need.
>
> Matthew Yaklin
> Network Engineer
> FirstLight
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net | www.firstlight.net
> This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed
> not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended
> to waive any applicable privileges.
>
> ------------------------------------------------------------------------
> *From:* Colton Conor <colton.conor at gmail.com>
> *Sent:* Thursday, April 4, 2019 8:40:11 PM
> *To:* Matthew Yaklin
> *Cc:* Jason Kuylen; VoiceOps at voiceops.org
> *Subject:* Re: [VoiceOps] Hotel Phone
> So if you had e911 per room, that would be quite a bit of e911
> charges. Most hotels I have seen have a 10 to 1 ratio for rooms to
> phone lines. So a 100 room hotel gets 10 phone lines from the LEC. Are
> you saying we would have to pay bandwidth.com <http://bandwidth.com>
> or whomever we got our e911 from a separate e911 charge per room?
> Isn't e911 tied to DID? In that case you would need a DID per hotel
> room? To actuately say room 302 is on floor 3, and room 302 for example.
>
>
>
> On Thu, Apr 4, 2019 at 11:21 AM Matthew Yaklin <myaklin at firstlight.net
> <mailto:myaklin at firstlight.net>> wrote:
>
> I imagine you want to make sure E911 information is super accurate
> with actual floors and room numbers. Physical address and call
> back number is correct. By making that accurate and having the
> customer sign that phones cannot move you cover a serious base.
> Perhaps even a sticker on the phone saying such would be great to.
>
>
> *Matthew Yaklin*
> Network Engineer
> *FirstLight*
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net <mailto:myaklin at firstlight.net> |
> www.firstlight.net <http://www.firstlight.net>
> /This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed/
> /not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended/
> /to waive any applicable privileges./
>
> ------------------------------------------------------------------------
> *From:* VoiceOps <voiceops-bounces at voiceops.org
> <mailto:voiceops-bounces at voiceops.org>> on behalf of Jason Kuylen
> <kuylenj at eastex.com <mailto:kuylenj at eastex.com>>
> *Sent:* Thursday, April 4, 2019 12:08:32 PM
> *To:* VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> *Subject:* Re: [VoiceOps] Hotel Phone
>
> I?ve never heard of any other 911 requirement for hotel or
> business phones outside of not have to dial 9 to dial 911, ie
> 9911. Kari?s Law.
>
> Can anyone provide a link with more information?
>
> Thanks.
>
>
> Important/Confidential: This communication and any files or
> documents attached to it are intended only for the use of the
> person(s) or entity to which it is addressed. It contains
> information that may be confidential and exempt from disclosure
> under applicable law. If you are not the intended recipient of
> this communication, you are hereby notified that the copying,
> disclosure, distribution, storage, retransmission or other use of
> this communication is strictly prohibited. If you have received
> this communication by mistake, please notify the sender
> immediately and destroy all forms of this communication
> (electronic or paper).
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto: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
April 5, 2019
[outages] flowroute increased 2400 percent belgium ?
by beckman@angryox.com
An interesting method to avoid calls while there is a known outage.
Increase rates by 24x and hope nobody uses it! Maybe that rate puts Belgium
in a rate that will fail for everyone.
Creative, though bizarre.
Izzy -- how did you notice? Curious what monitoring you might have in place
for such major changes.
On Fri, 5 Apr 2019, Ryan Collins via Outages wrote:
> Received a notification from Voxbone this morning regarding a large network outage in Belgium:
>
> Dear Customer,
>
> We're currently investigating a network outage in Belgium and we're working on a quick resolution.
>
> We are sorry for any inconvenience this may cause. Please open a ticket and refer to superticket # 192462 if you need more information on this issue.
>
>
>
>
>> On Apr 5, 2019, at 13:53, Izzy Goldstein - TeleGo via Outages <outages at outages.org> wrote:
>>
>> One of our divisions was using flowroutes for international termination
>> and we noticed prices to Belgium increased by about an astonishment %2400
>>
>> did anyone else notice this ?
>>
>> who are you using for International Termination ?
>>
>> who else has the fraud protection like they use ?
>>
>> --
>> 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/>
>>
>> <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>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
April 5, 2019
Hotel Phone
by caalvarez@gmail.com
This probably makes sense in large installations. At less than $1 per
active 911 DID, small installs don't seem worth the effort. I'm more
asking for others' opinions that making a statement.
For open floor plan offices, or small offices where basically a scream can
be heard, I think that a ring-all group for the return number will satisfy
the requirements. I welcome any commentary on that also.
Example: Client has a call center of 50 cubicles, with 8 office phones
placed in either open desks or offices on the perimeter. The space is
small enough to have a slightly loud conversation from one end to the
other. We currently have a dedicated callback number that rings every
phone.
On Fri, Apr 5, 2019 at 11:18 AM Andy Brezinsky <andy at mbrez.com> wrote:
> There are a number of ways to do this without having a DID assigned to
> each device with address information. A number of systems also assign a
> callback number to anyone that dials 911 which tacks up a translation for
> that number for a period of time so they can call back the user directly.
>
> Example onfiguration details for AudioCodes and Sonus with skype can be
> seen here:
> https://ucvnext.org/2016/03/enhanced-911-in-skype4b-server-and-lync-server-…
>
>
> On 4/5/19 1:22 AM, Matthew Yaklin wrote:
>
> That is correct. A DID for every phone and listed by e911. For example in
> NH it is law schools have it now days to get their special erate funding.
> When they call 911 they see very detailed information about floor, room,
> etc.. and the phone can be called back directly. We do it for every
> customer that has that specific need.
>
> Matthew Yaklin
> Network Engineer
> FirstLight
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net | www.firstlight.net
> This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed
> not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended
> to waive any applicable privileges.
>
> ------------------------------
> *From:* Colton Conor <colton.conor at gmail.com> <colton.conor at gmail.com>
> *Sent:* Thursday, April 4, 2019 8:40:11 PM
> *To:* Matthew Yaklin
> *Cc:* Jason Kuylen; VoiceOps at voiceops.org
> *Subject:* Re: [VoiceOps] Hotel Phone
>
> So if you had e911 per room, that would be quite a bit of e911 charges.
> Most hotels I have seen have a 10 to 1 ratio for rooms to phone lines. So a
> 100 room hotel gets 10 phone lines from the LEC. Are you saying we would
> have to pay bandwidth.com or whomever we got our e911 from a separate
> e911 charge per room? Isn't e911 tied to DID? In that case you would need a
> DID per hotel room? To actuately say room 302 is on floor 3, and room 302
> for example.
>
>
>
> On Thu, Apr 4, 2019 at 11:21 AM Matthew Yaklin <myaklin at firstlight.net>
> wrote:
>
> I imagine you want to make sure E911 information is super accurate with
> actual floors and room numbers. Physical address and call back number is
> correct. By making that accurate and having the customer sign that phones
> cannot move you cover a serious base. Perhaps even a sticker on the phone
> saying such would be great to.
>
>
> *Matthew Yaklin*
> Network Engineer
> *FirstLight*
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net | www.firstlight.net
> *This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed*
> *not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended*
> *to waive any applicable privileges.*
>
> ------------------------------
> *From:* VoiceOps <voiceops-bounces at voiceops.org> on behalf of Jason
> Kuylen <kuylenj at eastex.com>
> *Sent:* Thursday, April 4, 2019 12:08:32 PM
> *To:* VoiceOps at voiceops.org
> *Subject:* Re: [VoiceOps] Hotel Phone
>
>
> I?ve never heard of any other 911 requirement for hotel or business phones
> outside of not have to dial 9 to dial 911, ie 9911. Kari?s Law.
>
>
>
> Can anyone provide a link with more information?
>
>
>
> Thanks.
>
> Important/Confidential: This communication and any files or documents
> attached to it are intended only for the use of the person(s) or entity to
> which it is addressed. It contains information that may be confidential and
> exempt from disclosure under applicable law. If you are not the intended
> recipient of this communication, you are hereby notified that the copying,
> disclosure, distribution, storage, retransmission or other use of this
> communication is strictly prohibited. If you have received this
> communication by mistake, please notify the sender immediately and destroy
> all forms of this communication (electronic or paper).
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> _______________________________________________
> VoiceOps mailing listVoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
April 5, 2019
Hotel Phone
by andy@mbrez.com
There are a number of ways to do this without having a DID assigned to
each device with address information.? A number of systems also assign a
callback number to anyone that dials 911 which tacks up a translation
for that number for a period of time so they can call back the user
directly.
Example onfiguration details for AudioCodes and Sonus with skype can be
seen here:
https://ucvnext.org/2016/03/enhanced-911-in-skype4b-server-and-lync-server-…
On 4/5/19 1:22 AM, Matthew Yaklin wrote:
> That is correct. A DID for every phone and listed by e911. For example
> in NH it is law schools have it now days to get their special erate
> funding. When they call 911 they see very detailed information about
> floor, room, etc.. and the phone can be called back directly. We do it
> for every customer that has that specific need.
>
> Matthew Yaklin
> Network Engineer
> FirstLight
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net | www.firstlight.net
> This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed
> not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended
> to waive any applicable privileges.
>
> ------------------------------------------------------------------------
> *From:* Colton Conor <colton.conor at gmail.com>
> *Sent:* Thursday, April 4, 2019 8:40:11 PM
> *To:* Matthew Yaklin
> *Cc:* Jason Kuylen; VoiceOps at voiceops.org
> *Subject:* Re: [VoiceOps] Hotel Phone
> So if you had e911 per room, that would be quite a bit of e911
> charges. Most hotels I have seen have a 10 to 1 ratio for rooms to
> phone lines. So a 100 room hotel gets 10 phone lines from the LEC. Are
> you saying we would have to pay bandwidth.com <http://bandwidth.com>
> or whomever we got our e911 from a separate e911 charge per room?
> Isn't e911 tied to DID? In that case you would need a DID per hotel
> room? To actuately say room 302 is on floor 3, and room 302 for example.
>
>
>
> On Thu, Apr 4, 2019 at 11:21 AM Matthew Yaklin <myaklin at firstlight.net
> <mailto:myaklin at firstlight.net>> wrote:
>
> I imagine you want to make sure E911 information is super accurate
> with actual floors and room numbers. Physical address and call
> back number is correct. By making that accurate and having the
> customer sign that phones cannot move you cover a serious base.
> Perhaps even a sticker on the phone saying such would be great to.
>
>
> *Matthew Yaklin*
> Network Engineer
> *FirstLight*
> 359 Corporate Drive ? Portsmouth, NH 03801
> Mobile 603-845-5031
> myaklin at firstlight.net <mailto:myaklin at firstlight.net> |
> www.firstlight.net <http://www.firstlight.net>
> /This email may contain FirstLight confidential and/or privileged
> information. If you are not the intended recipient, you are directed/
> /not to read, disclose or otherwise use this transmission and to
> immediately delete same. Delivery of this message is not intended/
> /to waive any applicable privileges./
>
> ------------------------------------------------------------------------
> *From:* VoiceOps <voiceops-bounces at voiceops.org
> <mailto:voiceops-bounces at voiceops.org>> on behalf of Jason Kuylen
> <kuylenj at eastex.com <mailto:kuylenj at eastex.com>>
> *Sent:* Thursday, April 4, 2019 12:08:32 PM
> *To:* VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> *Subject:* Re: [VoiceOps] Hotel Phone
>
> I?ve never heard of any other 911 requirement for hotel or
> business phones outside of not have to dial 9 to dial 911, ie
> 9911. Kari?s Law.
>
> Can anyone provide a link with more information?
>
> Thanks.
>
>
> Important/Confidential: This communication and any files or
> documents attached to it are intended only for the use of the
> person(s) or entity to which it is addressed. It contains
> information that may be confidential and exempt from disclosure
> under applicable law. If you are not the intended recipient of
> this communication, you are hereby notified that the copying,
> disclosure, distribution, storage, retransmission or other use of
> this communication is strictly prohibited. If you have received
> this communication by mistake, please notify the sender
> immediately and destroy all forms of this communication
> (electronic or paper).
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto: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
April 5, 2019
flowroute increased 2400 percent belgium ?
by igoldstein@telego.net
One of our divisions was using flowroutes for international termination
and we noticed prices to Belgium increased by about an astonishment %2400
did anyone else notice this ?
who are you using for International Termination ?
who else has the fraud protection like they use ?
--
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>
April 5, 2019