Wireless Access

last person joined: 20 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Aruba controller 7210 & AP 135 : Voice quality is very poor with Wireless Phones

This thread has been viewed 0 times

  • 1.  Aruba controller 7210 & AP 135 : Voice quality is very poor with Wireless Phones

    Posted Jan 23, 2015 06:17 AM

    Hi ,

     

    I have set-up with spectralink phones (8440) with Aruba controller 7210 & AP135 .

     

    Users are facing lot of issue with voice quality.

    (un-una-usola1-arubawlc1) #show voice call-quality

    Voice Client(s) Call Quality Reports
    ------------------------------------
    Client(IP)      Client(MAC)        Client(Name)  ALG  Orig Time        Direction  Called to     Duration  Codec  Delay    Jitter  Pkt Loss  R-Value  Band    BSSID              ESSID        AP Name
    ----------      -----------        ------------  ---  ---------        ---------  ---------     --------  -----  -----    ------  --------  -------  ----    -----              -----        -------
    1xx.xx.217.53   xx:xx:xx:12:10:77  xxxx18       sip  Jan 23 05:33:45  IC        x1             68        G711   24.486   6.067   5.168     79       YELLOW  9c:1c:12:xx:xx:x1  voice        AP123
    1xx.xx.217.219  xx:xx:xx:12:21:fb  xxxx24       sip  Jan 23 03:25:18  OG         x2            3         G711   0.000    0.000   0.000     NA       NA      9c:1c:12:xx:xx:x2  voice        AP123
    1xx.xx.217.219  xx:xx:xx12:21:fb  xxxx24       sip  Jan 23 02:01:57  OG         x4             30        G711   47.425   4.950   8.750     69       YELLOW  9c:1c:12:xx:xx:x3  voice         AP123
    1xx.xx.217.219  xx:xx:xx:12:21:fb  xxxx24       sip  Jan 23 01:21:28  IC         x5            38        G711   40.089   7.679   14.565    69       YELLOW  9c:1c:12:xx:xx:x4  voice         AP204
    1xx.xx.217.219  xx:xx:xx:12:21:fb  xxxx24       sip  Jan 23 01:21:03  OG         x6             1         G711   0.000    0.000   0.000     NA       NA      9c:1c:12:xx:xx:x5  voice        AP204
    1xx.xx.217.219  xx:xx:xx:12:21:fb  xxxx24       sip  Jan 23 01:11:23  OG         x7            373       G711   12.987   6.856   0.855     89       GREEN   9c:1c:12:xx:xx:x6  voice          AP204
    1xx.xx.217.53   xx:xx:xx:12:10:77  xxxx18       sip  Jan 23 01:17:24  OG        x8              4         G711   0.000    0.000   0.000     NA       NA      9c:1c:12:xx:xx:x7  voice          AP123
    1xx.xx.217.219  xx:xx:xx:12:21:fb  xxxx24       sip  Jan 23 01:05:27  OG        x9             40        G711   44.723   10.768  1.283     86       GREEN   9c:1c:12:xx:xx:x8  voice           AP204
    1xx.xx.217.53   xx:xx:xx:12:10:77  xxxx18       sip  Jan 22 23:25:37  IC        x10            16        G711   71.479   3.208   0.130     91       GREEN   9c:1c:12:xx:xx:x9  voice           AP123

     

    If I see the above output I see Jitter greater than 3  and delay more than  20 , I am not sure the standard value to be consider in this case however I need to know about upstream and downstream standard value which can be accepted .

     

    I tried to debug the since client mac address and found below output :

     

    Jan 22 15:09:52 :501106:  <NOTI> |AP AP163@<ip address> stm|  Deauth to sta: 00:90:7a:xx:xx:xx: Ageout AP <ip address>-9c:1c:12:xx:xx:xx-  AP163 handle_sapcp
    Jan 22 15:09:52 :501080:  <NOTI> |AP AP163@<ip address> stm|  Deauth to sta: 00:90:7a:xx:xx:xx: Ageout AP <ip address>-9c:1c:12:xx:xx:xx-  AP163 Tx fail reached maximum
    Jan 22 15:09:52 :501105:  <NOTI> |stm|  Deauth from sta: 00:90:7a:xx:xx:xx AP <ip address>-9c:1c:12:xx:xx:xx- AP163 Reason Tx fail reached maximum
    Jan 22 15:09:53 :501106:  <NOTI> |AP un-una-usola1-AP161@<ip address> stm|  Deauth to sta: 00:90:7a:12:10:95: Ageout AP <ip address>-9c:1c:12:xx:xx:xx-AP161 handle_sapcp

     

    where I could see that many times client(station) is frequently  deauthenticating .. 

     

    I have fetched the client trail info as well where i could see the reason for Deauth is as : "station has moved to another AP "

     

     

     

     

     

    Arubawlc#show ap client trail-info 00:90:7a:xx:xx:xx

    Client Trail Info
    -----------------
    MAC                BSSID              ESSID        AP-name              VLAN  Deauth Reason                 Alert
    ---                -----              -----        -------              ----  -------------                 -----
    00:90:7a:xx:xx:xx 9c:1c:12:xx:xx:xx  voice          AP213                302   STA has roamed to another AP  STA has roamed to another AP

    Deauth Reason
    -------------
    Reason                        Timestamp
    ------                        ---------
    STA has roamed to another AP  Jan 22 22:27:08
    STA has roamed to another AP  Jan 22 20:29:31
    STA has roamed to another AP  Jan 22 15:37:07
    STA has roamed to another AP  Jan 22 15:12:43
    Tx fail reached maximum       Jan 22 15:10:15
    Tx fail reached maximum       Jan 22 15:10:15
    Tx fail reached maximum       Jan 22 15:10:14
    Tx fail reached maximum       Jan 22 15:10:11
    Tx fail reached maximum       Jan 22 15:10:11
    Tx fail reached maximum       Jan 22 15:10:11
    Num Deauths:10

    Alerts
    ------
    Reason                        Timestamp
    ------                        ---------
    STA has roamed to another AP  Jan 22 22:27:08
    STA has roamed to another AP  Jan 22 20:29:31
    STA has roamed to another AP  Jan 22 15:37:07
    STA has roamed to another AP  Jan 22 15:12:43
    Tx fail reached maximum       Jan 22 15:10:15
    Tx fail reached maximum       Jan 22 15:10:15
    Tx fail reached maximum       Jan 22 15:10:14
    Tx fail reached maximum       Jan 22 15:10:11
    Tx fail reached maximum       Jan 22 15:10:11
    Tx fail reached maximum       Jan 22 15:10:11
    Num Alerts:10

    Mobility Trail
    --------------
    BSSID              ESSID        AP-name Timestamp
    -----              -----        -------              ---------
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 22:27:08
    9c:1c:12:aa:aa:aa  voice AP216  Jan 22 22:27:08
    9c:1c:12:aa:aa:aa  voice AP216  Jan 22 20:29:31
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 20:29:31
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 15:37:07
    9c:1c:12:bb:bb:bb  voice AP215  Jan 22 15:37:07
    9c:1c:12:bb:bb:bb  voice AP215  Jan 22 15:12:43
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 15:12:43
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 15:10:15
    9c:1c:12:xx:xx:xx  voice AP213  Jan 22 15:10:15
    Num Mobility Trails:10

     

    This is the issue within LAN itself where clients are calling internal user only to another spectralink phone .

     

    Can anybody please guide me on this and put light on the above mentioned output like debug and voice quality as well client trail info?

     

    It would be really great help if somebody could help me since this we are facing since long time .

     

     

     


    #7210


  • 2.  RE: Aruba controller 7210 & AP 135 : Voice quality is very poor with Wireless Phones

    EMPLOYEE
    Posted Jan 23, 2015 07:43 AM

    - If you have not opened a TAC case and this is an important deployment, please open a TAC case now

    - Did you follow the configuration guidelines for Spectralink phones in the Roaming VRD here?  http://www.arubanetworks.com/wp-content/uploads/DG_Roaming.pdf

    - Who designed this network?

     


    #7210


  • 3.  RE: Aruba controller 7210 & AP 135 : Voice quality is very poor with Wireless Phones

    Posted Jan 24, 2015 01:34 PM

    Hi  Colin , 

     

    I have not understood the context of your question that who designed this network ? 

     

    is there any issue you find in designing network ?


    #7210


  • 4.  RE: Aruba controller 7210 & AP 135 : Voice quality is very poor with Wireless Phones

    EMPLOYEE
    Posted Jan 24, 2015 03:12 PM

    VoiP deployments, and specifically vendors of WLAN phones have very specific parameters and settings they expect for optimal WLAN performance with their designs. It usually has to do with coverage models and minimum SNR coverage rates, specific settings of AP power, rates, etc. 

    The link Colin linked to is one of our Roaming Devices VRDs, however, Spectralink should have their own as well.

    The reason for asking who the installer was, is to know whether a qualified partner or company did the installation, configuration, and validation of the WLAN to meet the above criteria.

     

    Still need to open TAC case though so they can look at ways to imrpove your users' experience.


    #7210