[VoiceOps] Unsecured conference lines

[Aryn Nakaoka 808.356.2901]

Would you be OK with 100 channels incoming used 24/7 ? Do you have a soft
cap?

If not, how much do you charge per channel ;)







Aryn H. K. Nakaoka
anakaoka at trinet-hi.com

Direct: 808.356.2901
Fax : 808.356.2919

Tri-net Solutions
733 Bishop St. #1170
Honolulu, HI 96813
http://www.trinet-hi.com

https://twitter.com/AlohaTone

Aloha Tone PBX <https://www.youtube.com/watch?v=96YWPY9wCeU>
https://www.youtube.com/watch?v=96YWPY9wCeU <http://youtu.be/27v2wbnFIDs>

Aloha Tone (HA) High Availability <http://youtu.be/rJsr4k0RBH8>
http://youtu.be/rJsr4k0RBH8

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.







On Thu, Jun 2, 2016 at 9:13 AM, Carlos Alvarez <caalvarez at gmail.com> wrote:

> We have outbound conferencing also, they don't want that.  They already do
> have HD conferencing and some web control of conferences.  This is purely
> about their standard inbound conferencing not having a PIN.  Alex's
> suggestion about ANI made me think of a compromise where their internal
> callers (80% of callers) would have no PIN.  This still exposes their board
> conversation to random peons in the company, but at least it doesn't affect
> our side of it and stops the random outside users.
>
> There would be no exorbitant billing opportunity here, since they are
> locked to 100 channels and pay a flat usage fee for them.
>
>
>
> On Thu, Jun 2, 2016 at 12:01 PM, Garrett Smith <garrett at pitchpivot.com>
> wrote:
>
>> Hi Carlos,
>>
>> Check out ZipDX - they have a patented identity based conferencing that
>> eliminates the need for pins by calling out to the meeting attendees. The
>> system is used primarily for sensitive calls - investors, market research,
>> executives and was developed to stop the inconveniences of pins and
>> unsecured conference calls.
>>
>> Can be customized to needs and they've also got a partner program.
>>
>> You can learn more here: www.ZipDX.info or I'd be happy to put you in
>> touch with someone their.
>>
>> Garrett
>>
>> *Garrett Smith*
>> Founder
>>
>> *Pitch + Pivot, LLC*
>> Website: PitchPivot.com
>> Email: garrett at pitchpivot.com
>> Office: 716-322-3101
>> Cell: 716-903-9495
>> LinkedIn: /in/garrettsmith <http://www.linkedin.com/in/garrettsmith>
>> Twitter: @garrettsmith <http://www.twitter.com/garrettsmith>
>>
>> On Thu, Jun 2, 2016 at 2:54 PM, Carlos Alvarez <caalvarez at gmail.com>
>> wrote:
>>
>>> We have a customer who has been nagging us to remove the PIN from their
>>> conference lines.  They are getting more insistent.  We've said no, for the
>>> obvious security reasons, and explained them all clearly.  On top of it,
>>> this is a medical-related company having sensitive conversations on
>>> conferences.  They keep pushing us.  What would you do?  On the one hand I
>>> think we have no liability in the matter, but on the other, we're more of a
>>> consulting ITSP than just a generic service provider.  We specialize in
>>> helping people not do stupid things with their phone system.  There's also
>>> the matter of just eating up a bunch of channels by people using it as
>>> their own conference.
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160602/90504537/attachment.html>