
We are getting a sudden burst of complaints concerning TCP SIP working but no UDP RTP audio flowing, specifically on T-Mobile. Is anyone else seeing this?

I'm seeing the same. I get one way audio from server to the handset. The call drops after 5 seconds due to not detecting 2 way audio. ~Jared Geiger On Thu, May 18, 2017 at 12:35 PM, Liudvikas Bukys <Liudy at bukys.org> wrote:
We are getting a sudden burst of complaints concerning TCP SIP working but no UDP RTP audio flowing, specifically on T-Mobile. Is anyone else seeing this?
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Maybe this: http://www.skyswitch.com/t-mobile-breaks-sip-ipv6-updates/ On Thu, May 18, 2017 at 5:14 PM, Jared Geiger <jared at compuwizz.net> wrote:
I'm seeing the same. I get one way audio from server to the handset. The call drops after 5 seconds due to not detecting 2 way audio.
~Jared Geiger
On Thu, May 18, 2017 at 12:35 PM, Liudvikas Bukys <Liudy at bukys.org> wrote:
We are getting a sudden burst of complaints concerning TCP SIP working but no UDP RTP audio flowing, specifically on T-Mobile. Is anyone else seeing this?
_______________________________________________ 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

Hello, I was wondering if anyone could suggest some open source testing and quality monitoring applications for VoIP. From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. Any help or tips regarding best practices would be greatly appreciated. TIA, Jamie

Hello Sir I use Homer5 to view RTCP-XR reports, statistics from RPTEngine and call tracing among a bunch of other stuff.. It's free and awesome (about to become HEPIC) https://github.com/sipcapture For network tests I use iperf, smokeping and stuff like that. Kind regards Andy On Tue, 23 May 2017 19:11 James M, <jm8269 at outlook.com> wrote:
Hello,
I was wondering if anyone could suggest some open source testing and quality monitoring applications for VoIP. From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. Any help or tips regarding best practices would be greatly appreciated.
TIA,
Jamie _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

This may not be quite what you're looking for, but 'The Test Call' has proved very helpful for us so I wanted to share it with this community (and reminds me I should probably donate). The Test Call at http://thetestcall.blogspot.com/ hosts a handful of PSTN numbers that you can call and test several functionalities: -Record and playback a message (test 2-way audio) -DTMF testing -Real-time Echo Test (test latency) -Playback music on hold (test sustained connections for drops on inbound audio) -0-4KHz audio sweep -Caller ID Readback Hope that's helpful to you or someone else on this thread, Jacob S? ? ? -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of James M Sent: Tuesday, May 23, 2017 1:11 PM To: VoiceOps <voiceops at voiceops.org> Subject: [VoiceOps] VoIP Testing Hello, I was wondering if anyone could suggest some open source testing and quality monitoring applications for VoIP. From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. Any help or tips regarding best practices would be greatly appreciated. TIA, Jamie _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.

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 and one for internet access to send the data back to voipmonitor. Thanks, Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

I currently use Celeron or Atom based single board devices. https://www.amazon.com/Jetway-Networking-Appliance-Embedded-JBC373F38W-525/d... are pretty OK. There's also a celeron model. They both have 4 interfaces. On 5/23/2017 5:20 PM, 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 and one for internet access to send the data back to voipmonitor.
Thanks,
Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

You can use a USB to ethernet dongle on a raspberry pi to bring up two NICs. I have a VoIP monitor capture node in our lab built this way and it works well. On Tue, May 23, 2017 at 5:21 PM Shripal Daphtary <shripald at gmail.com> 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 and one for internet access to send the data back to voipmonitor.
Thanks,
Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ 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

Thanks! Going to check it out! On Wed, May 24, 2017 at 10:42 AM Christopher Aloi <ctaloi at gmail.com> wrote:
You can use a USB to ethernet dongle on a raspberry pi to bring up two NICs. I have a VoIP monitor capture node in our lab built this way and it works well.
On Tue, May 23, 2017 at 5:21 PM Shripal Daphtary <shripald at gmail.com> 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 and one for internet access to send the data back to voipmonitor.
Thanks,
Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ 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

You?ll need to be aware of what level of traffic you?re trying to mirror into the Pi. The onboard NIC is riding the USB bus which you?ll then share with the external USB NIC. If the Pi is receiving too much data, it?ll drop packets. This would appear as an RTP problem even if there isn?t one since RTP packets would be lost. Also consider the packets per second that the Pi CPU can interrupt for. 20ms = 50pps From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Shripal Daphtary Sent: Wednesday, May 24, 2017 9:43 AM To: Christopher Aloi; Mark Wiater Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] VoIP Testing Thanks! Going to check it out! On Wed, May 24, 2017 at 10:42 AM Christopher Aloi <ctaloi at gmail.com<mailto:ctaloi at gmail.com>> wrote: You can use a USB to ethernet dongle on a raspberry pi to bring up two NICs. I have a VoIP monitor capture node in our lab built this way and it works well. On Tue, May 23, 2017 at 5:21 PM Shripal Daphtary <shripald at gmail.com<mailto:shripald at gmail.com>> 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 and one for internet access to send the data back to voipmonitor. Thanks, Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com<mailto:mark.wiater at greybeam.com>> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ 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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops

We track registration latency of each phone and trunk... its very helpful to see patterns. looks like this: [image: Inline image 1] Aryn H. K. Nakaoka anakaoka at trinet-hi.com Direct: 808.356.2901 Fax: 808.356.2919 Tri-net Solutions 518 Holokahana Lane Suite #200 Honolulu, HI 96817 http://www.trinet-hi.com https://twitter.com/AlohaTone Aloha Tone PBX https://www.youtube.com/watch?v=96YWPY9wCeU Aloha Tone (HA) High Availability http://youtu.be/rJsr4k0RBH8 A Better Solution https://www.trinet-hi.com/abettersolution.pdf <https://www.trinet-hi.com/abettersolution.pdf> 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 Wed, May 24, 2017 at 5:40 AM, Lee Riemer <LRiemer at bestline.net> wrote:
You?ll need to be aware of what level of traffic you?re trying to mirror into the Pi. The onboard NIC is riding the USB bus which you?ll then share with the external USB NIC. If the Pi is receiving too much data, it?ll drop packets. This would appear as an RTP problem even if there isn?t one since RTP packets would be lost. Also consider the packets per second that the Pi CPU can interrupt for. 20ms = 50pps
*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Shripal Daphtary *Sent:* Wednesday, May 24, 2017 9:43 AM *To:* Christopher Aloi; Mark Wiater *Cc:* voiceops at voiceops.org *Subject:* Re: [VoiceOps] VoIP Testing
Thanks! Going to check it out!
On Wed, May 24, 2017 at 10:42 AM Christopher Aloi <ctaloi at gmail.com> wrote:
You can use a USB to ethernet dongle on a raspberry pi to bring up two NICs. I have a VoIP monitor capture node in our lab built this way and it works well.
On Tue, May 23, 2017 at 5:21 PM Shripal Daphtary <shripald at gmail.com> 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 and one for internet access to send the data back to voipmonitor.
Thanks,
Shripal
On May 23, 2017, at 3:49 PM, Mark Wiater <mark.wiater at greybeam.com> wrote:
From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem. While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.
The collection software is open source but the gui is invaluable.
_______________________________________________ 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

On 24/05/2017, at 9:20 am, Shripal Daphtary <shripald at gmail.com> 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 and one for internet access to send the data back to voipmonitor.
Shripal, There's no off-the-shelf RPi with dual NICs, but any class-driver compliant USB NIC will work fine as a second interface, as long as you don't need more than 100mbit wire speed. We do this on multiple RPis. It's literally plug-n-play :) Pete

Thanks Pete. We're testing now. Thanks, Shripal
On May 29, 2017, at 5:25 AM, Pete Mundy <pete at fiberphone.co.nz> wrote:
On 24/05/2017, at 9:20 am, Shripal Daphtary <shripald at gmail.com> 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 and one for internet access to send the data back to voipmonitor.
Shripal,
There's no off-the-shelf RPi with dual NICs, but any class-driver compliant USB NIC will work fine as a second interface, as long as you don't need more than 100mbit wire speed.
We do this on multiple RPis. It's literally plug-n-play :)
Pete

If you need more horsepower, for about $100 extra, you can load linux on a Netgate appliance. Something like an SG-1000 https://www.netgate.com/products/sg-1000.html From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Shripal Daphtary Sent: Monday, May 29, 2017 8:01 AM To: Pete Mundy Cc: Voiceops.org Subject: Re: [VoiceOps] VoIP Testing Thanks Pete. We're testing now. Thanks, Shripal On May 29, 2017, at 5:25 AM, Pete Mundy <pete at fiberphone.co.nz<mailto:pete at fiberphone.co.nz>> wrote: On 24/05/2017, at 9:20 am, Shripal Daphtary <shripald at gmail.com<mailto:shripald at gmail.com>> 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 and one for internet access to send the data back to voipmonitor. Shripal, There's no off-the-shelf RPi with dual NICs, but any class-driver compliant USB NIC will work fine as a second interface, as long as you don't need more than 100mbit wire speed. We do this on multiple RPis. It's literally plug-n-play :) Pete
participants (12)
-
anakaoka@trinet-hi.com
-
colton.conor@gmail.com
-
ctaloi@gmail.com
-
jared@compuwizz.net
-
jm8269@outlook.com
-
jscherb@Fitzmark.com
-
Liudy@bukys.org
-
LRiemer@bestline.net
-
mark.wiater@greybeam.com
-
monkeilas@gmail.com
-
pete@fiberphone.co.nz
-
shripald@gmail.com