Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-04-2017, 02:14 PM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Question Paging Causes One-way Audio Silence

Hi Everyone,

I have this issue we or our third party Avaya supporters can't seem to completely fix. The issue intermittently occurs when anyone user page causes any call that are already connected to lose audio one way (from customer to us) for as long as the page is active. When they lose audio the call becomes completely silent and the other part is not heard. Then when the page ends the call resumes audio both ways. So the call isn't lost at all just the audio one way momentarily until the page stops. My one QoS change to the 46xxx settings txt file helped allot because those settings weren't implemented yet since they were in use with our old Mitel PBX. Any help or suggestions would be deeply appreciated. Our IP Office vs is Version 9.1.8.0 Build 172 and we have about 50-100 extensions in use with most of them being on premise and 25% or less being remote workers. The phones in use are 1608's and 9608's. The system codec in place are g711 and g729.
Reply With Quote
  #2  
Old 04-05-2017, 05:47 AM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Post More info

One more detail the paging is going to a group of 25 extensions that's all.
Reply With Quote
  #3  
Old 04-06-2017, 05:39 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 443
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

What's the VCM capacity of your IPO system? A group page to 25 extensions would cause a sudden spike in VCM resources. Use System Status to monitor VCM usage when paging is invoked.
Reply With Quote
  #4  
Old 04-06-2017, 06:28 AM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Question

Good point I'll check that out with a test and get back you. I know how to check this but my question is are the VCM channels linked to the PRI channels our are they seperate unrelated resources?
Reply With Quote
  #5  
Old 04-06-2017, 07:03 AM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Default

I tested and i see that the total channels are 250 and we've only ever used up to 27 in the past day or 2 and never above that. I'll check during high call volume to see if i see the same thing.
Reply With Quote
  #6  
Old 04-06-2017, 08:15 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 443
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

Quote:
Originally Posted by cruz278 View Post
Good point I'll check that out with a test and get back you. I know how to check this but my question is are the VCM channels linked to the PRI channels our are they seperate unrelated resources?
VCMs are your call resources. When a phone goes off-hook, a VCM is used. VCM is also used for any TDM to IP conversion, such as when an IP endpoint is interfacing with a PRI. VCMs and PRIs are separate resources but used together.

250 sounds like adequate resources for a 25 phone page but if you find usage is high during peak hours, consider using shuffling (I think IPO calls this direct media) to enable two IP endpoints to exchange RTP directly to free up VCMs after call setup.
Reply With Quote
  #7  
Old 04-06-2017, 10:36 AM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Default

direct media has been enabled for those in the office's that can access the PBX on a local network. From what my search found is that direct media on those that are remote user's wont be or are not needed as they don't impact this, is that true?
Reply With Quote
  #8  
Old 04-17-2017, 07:03 AM
cruz278 cruz278 is offline
Member
 
Join Date: Apr 2017
Location: Fairfield NJ 07004
Posts: 6
cruz278 has 10 reputation points
Solution Confirmed

I checked the codec bit usage and compared it to my current P2P pipe between PBX and office. Anything above 23 exts on a page list would supersede pipes capacity. I always had my mind on this just never looked at it in depth since we already have our replacement P2P up which is a fiber 10mb pipe. I just haven't set it up yet. I reduced the page list to 21 exts and no complaints of current conversations being effected.
Reply With Quote
Reply

Tags
audio, ip office 500, paging

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 07:55 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.