Author Topic: One-way voice  (Read 1290 times)

Offline VinceWhirlwind

  • Hero Member
  • *****
  • Posts: 899
  • Country: au
  • Karma: +31/-0
    • View Profile
One-way voice
« on: July 19, 2016, 10:51:36 PM »
What steps can I take to determine whether an intermittent one-way voice issue affecting outgoing calls is a problem on the controller, or can be referred upstream to the provider?
 
I've asked for times and destination numbers and there is nothing in the normal logs for those times indicating any error.


Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5741
  • Country: us
  • Karma: +468/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: One-way voice
« Reply #1 on: July 20, 2016, 08:18:10 AM »
What kind of calls?

I'm dealing with the exact same issue now on SIP calls.
We've noticed in the VQ logs the far end IP is always 0.0.0.0

Ralph

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: One-way voice
« Reply #2 on: July 20, 2016, 06:29:47 PM »
We've noticed in the VQ logs the far end IP is always 0.0.0.0

Ralph
Is that after a call is taken off hold, or come out the other side of an IVR?

Offline VinceWhirlwind

  • Hero Member
  • *****
  • Posts: 899
  • Country: au
  • Karma: +31/-0
    • View Profile
Re: One-way voice
« Reply #3 on: July 20, 2016, 08:34:24 PM »
Thanks Ralph, I used the Voice Quality statistics form on the controller, exported it to a spreadsheet.

I cut out all the relevant lines based on the user's IP address to have a look through them.
 
I highlighted all the calls that lasted about 5-15 seconds on the assumption they were most likely the one-way voice calls.
 
I then deleted all the columns where the recorded statistics were the same regardless of whether it was a good or bad call.
 
I ended up with a list of calls from my user to an IP address which I assume is the DSP card on the controller. The only things that were different from call to call were the signalling TCP ports (the signalling obviously at least mostly OK, as the call is setup) and the voice UDP ports. The kind of thing I looked for here was, assuming for example the firewall was set to allow all ports 50000-50400, calls using UDP ports <504001 succeed, calls using UDP ports >50400 fail.
I didn't see any kind of pattern like that.
 
The only thing I can't see is any indication of which DSP card resources are assigned to each call - could be something faulty on the DSP card.
 
But mostly, I'm going to tell them it's their provider. See where that gets me.

Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5741
  • Country: us
  • Karma: +468/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: One-way voice
« Reply #4 on: July 21, 2016, 08:15:12 AM »
We've noticed in the VQ logs the far end IP is always 0.0.0.0

Ralph
Is that after a call is taken off hold, or come out the other side of an IVR?

They're usually outbound calls so they're not using IVR or AA on those calls.

Ralph

Online ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5741
  • Country: us
  • Karma: +468/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: One-way voice
« Reply #5 on: July 21, 2016, 08:18:13 AM »
Vince,
 
Quote
I ended up with a list of calls from my user to an IP address which I assume is the DSP card on the controller. The only things that were different from call to call were the signalling TCP ports (the signalling obviously at least mostly OK, as the call is setup) and the voice UDP ports. The kind of thing I looked for here was, assuming for example the firewall was set to allow all ports 50000-50400, calls using UDP ports <504001 succeed, calls using UDP ports >50400 fail.
I didn't see any kind of pattern like that.

That's something I haven't thought of.  I need to check that too.  Thanks.

Ralph


 

Sitemap 1 2 3 4 5 6 7 8 9 10