[VoiceOps] Seeking phone system recommendations

Tue Sep 29 12:27:08 EDT 2015

Also you can route these SIP PUBLISH messages to any RFC 6035  compliant
report collector supporting VQ Collector functionality. It doesn¹t have to
be the VQmon GUI. For example you could route them back to Palladion/
Communications Operations Monitor/COM  and then it would correlate this
information from the leg of the call to the VoIP phone into the other
SIP/RTP legs /streams that the monitor platform is monitoring directly

Then you get the full picture and on which leg quality may have broken down

Regards,

Richard Jobson

Teraquant Corporation
2400 Central Avenue, Suite P-2
Boulder, CO 80301 USA

E-mail: richard at teraquant.com
Web: www.teraquant.com

Phone: +1 (719) 488-1003 x101

From:  VoiceOps <voiceops-bounces at voiceops.org> on behalf of "Aryn Nakaoka
808.356.2901" <anakaoka at trinet-hi.com>
Date:  Monday, September 28, 2015 at 2:46 PM
To:  Anthony Caiozzo <anthony.caiozzo at telchemy.com>
Cc:  "VoiceOps at voiceops.org" <voiceops at voiceops.org>
Subject:  Re: [VoiceOps] Seeking phone system recommendations

> Also easy enough to monitor yourself :
> 
> - Monitor WAN traffic / cpu / latency on remote firewalls
>      - Cacti / Smokeping / Zabbix - lots of options
> 
> - Monitor SIP registration over time
>      - You should monitor all trunks and analog ports as well (that don't have
> VQmon)
> 
> 
> 
>    
> 
> 
> 
> 
> 
> 
> 
> 
> 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
>  <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 Mon, Sep 28, 2015 at 9:34 AM, Anthony Caiozzo
> <anthony.caiozzo at telchemy.com> wrote:
>> Graham - I can speak (in volumes) to the 6th point in your list - will keep
>> this brief.
>> 
>> Assuming you stick with your Polycom endpoints - those devices feature an
>> integrated MOS scoring/signaling analysis/SIP reporting function that is
>> described at a high level in the attached solutions brief.  Your customer
>> can run/operate this platform on their own - independently of their carrier
>> of choice or leverage the functionality that their carrier has implemented
>> to deliver this to them as a managed service (a number of the providers on
>> this list are Telchemy customers - leveraging the SQmediator platform to
>> deliver exactly this type of a managed service).
>> 
>> Feel free to contact me privately to dig deeper-
>> 
>> -anthony
>> 
>> Anthony Caiozzo
>> Telchemy - www.telchemy.com <http://www.telchemy.com>
>> m: 617-312-5189 <tel:617-312-5189>  f: 678-387-3008 <tel:678-387-3008>
>> e: anthony.caiozzo at telchemy.com
>> support: 1-866-TELCHEMY
>> Skype: acaiozzo
>> 
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Graham
>> Freeman
>> Sent: Monday, September 28, 2015 2:28 PM
>> To: <voiceops at voiceops.org> <voiceops at voiceops.org>
>> Subject: [VoiceOps] Seeking phone system recommendations
>> 
>> Hi, folks,
>> 
>> Can you recommend a managed telephony vendor?
>> 
>> Client characteristics:
>> * Several locations in the US, in multiple states.
>> * Total of a few hundred seats.
>> * High tens or low hundreds of thousands of minutes.
>> * Prefer to trunk to vendor via existing reliable multi-hundred-megabit
>> and/or gigabit internet connections. Dedicated link is a possibility if
>> necessary.
>> * Ideal to continue using existing Polycom SIP phones.
>> * Vendor should have monitoring that is as proactive as possible.  SIP
>> packet loss?  Call drops?  Call completion failing?  Low MOS scores?  To the
>> extent technically and commercially feasible (IMO, it's feasible), vendor
>> should be the first to notify client about these issues and path/timeline to
>> resolution, instead of waiting for client to complain.
>> * Operator panel that is at least as capable as Shoretel Communicator
>> (version 13).   Ideally modern HTML5 web-based, not based on ancient
>> vulnerable tech (such as Flash or Java).
>> 
>> Client has a good IT team, including folks with telecom experience, but
>> would rather have a managed telephony vendor instead of staffing up more
>> telecom expertise internally.   Client prefers to handle end-user tier-1
>> (and sometimes tier-2) helpdesk issues internally, and have in-house
>> IT/telecom staff talk to telephony vendor about any issues that can't be
>> handled internally.  (In other words, this is a great client for a telephony
>> vendor that can build and maintain a reliable and properly monitored
>> telephony infrastructure.)
>> 
>> Client is accustomed to deploying phones with LLDP-MED, putting phones on a
>> separate voice VLAN with a vendor-managed router handling that VLAN.
>> 
>> Client would love to see provisioning (e.g. new phone) and management (e.g.
>> password resets) as automated as possible.  Current vendor has a very manual
>> (and time-intensive and error-prone) process.
>> 
>> If you respond via email off-list, I'll summarize the responses on-list in a
>> few days.   (Please, don't call or text me about this unless we've made an
>> appointment to discuss.)
>> 
>> thanks,
>> 
>> Graham Freeman, Principal Nerd
>> NerdVentures.com
>> graham at nerdventures.com
>> https://www.linkedin.com/in/grahamfreeman
>> Twitter: @get_nerdy
>> 
>> _______________________________________________
>> 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
>> 
> 
> _______________________________________________ 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/20150929/4278ced2/attachment.html>