Access Points

Reply
Occasional Contributor II
Posts: 77
Registered: ‎07-10-2009

Strange AP105 behaviour with voip

I've installed some AP105 in the office. When I tested them with the voip handsets it seems that even the handsets are roaming there is no audio when I am under a concrete AP. I roam from AP60 (the name not the model) to AP61 (both model AP105) with an ongoing call. When I am under AP60 (name) it is all fine, but then when I go to AP61 (name) the audio starts to chop and eventually stops.
I have some other AP105 in the buiding and they don't have this kind of problem.

In those positions i had previously normal AP61 (now the model) APs that were only G. With those it was working fine. I've tried to disable HT troughtput mode in the VOIP SSID but that didn't work.
Also I've mesured with an spectrum analyzer if there is any interference in the channel of AP61 but there is nothing remarkable.

I would like to know if somebody had a similiar problem. Maybe i have to disable HT-mode in all the ssids.

Here are the debug logs:

Time

Event

Description



Jun 30 17:12:14

stm

Sending Call Status Message to Auth 34:7e:39:8b:ef:e5-1



Jun 30 17:12:14

stm

send_sta_on_call_message 3114 Sending Call Status Message to Mobility for client ip: 84.89.233.4 cname: s:5071 sname: pbxserver.cells.es reg dur: 3600



Jun 30 17:28:25

stm

Sending Call Status Message to Auth 34:7e:39:8b:ef:e5-0



Jun 30 17:28:25

stm

send_sta_on_call_message 3114 Sending Call Status Message to Mobility for client ip: 84.89.233.4 cname: s:5071 sname: pbxserver.cells.es reg dur: 3600



Jun 30 17:28:30

stm

Sending Call Status Message to Auth 34:7e:39:8b:ef:e5-1



Jun 30 17:28:30

stm

send_sta_on_call_message 3114 Sending Call Status Message to Mobility for client ip: 84.89.233.4 cname: s:5071 sname: pbxserver.cells.es reg dur: 3600



Jun 30 17:28:58

stm

Disassoc from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 Reason STA has left and is disassocisted



Jun 30 17:28:58

stm

Disassoc from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 Reason STA has left and is disassocisted



Jun 30 17:28:58

stm

Station 34:7e:39:8b:ef:e5: Clearing state



Jun 30 17:28:58

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:28:58

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received disassociation on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP60 Group default BSSID d8:c7:c8:a8:39:f1, phy g, VLAN 233



Jun 30 17:28:58

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Mobility trail, on switch 84.89.232.250, VLAN 233, AP AP60, cells_VoIP_ap/d8:c7:c8:a8:39:f1/g



Jun 30 17:28:58

authmgr

MAC=34:7e:39:8b:ef:e5 Station DN: BSSID=d8:c7:c8:a8:39:f1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP60



Jun 30 17:28:58

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ce (tunnel 78), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:28:58

stm

Station 34:7e:39:8b:ef:e5: Clearing state



Jun 30 17:28:58

stm

Assoc request @ 17:28:58.459875: 34:7e:39:8b:ef:e5 (SN 649): AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:28:58

stm

Assoc request @ 17:28:58.380981: 34:7e:39:8b:ef:e5 (SN 649): AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:28:58

stm

Assoc success @ 17:28:58.440151: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:28:58

stm

Assoc success @ 17:28:58.463495: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:28:58

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:28:58

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received association on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP61 Group default BSSID d8:c7:c8:a8:39:e1, phy g, VLAN 233



Jun 30 17:28:58

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Mobility trail, on switch 84.89.232.250, VLAN 233, AP AP61, cells_VoIP_ap/d8:c7:c8:a8:39:e1/g



Jun 30 17:28:58

authmgr

MAC=34:7e:39:8b:ef:e5 Station UP: BSSID=d8:c7:c8:a8:39:e1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP61



Jun 30 17:28:58

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ad (tunnel 45), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:28:58

authmgr

MAC=34:7e:39:8b:ef:e5 def_vlan 233 derive vlan: 0 auth_type 0 auth_subtype 0



Jun 30 17:29:03

stm

Disassoc from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61 Reason STA has left and is disassocisted



Jun 30 17:29:03

stm

Disassoc from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61 Reason STA has left and is disassocisted



Jun 30 17:29:03

stm

Station 34:7e:39:8b:ef:e5: Clearing state



Jun 30 17:29:03

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:29:03

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received disassociation on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP61 Group default BSSID d8:c7:c8:a8:39:e1, phy g, VLAN 233



Jun 30 17:29:03

authmgr

MAC=34:7e:39:8b:ef:e5 Station DN: BSSID=d8:c7:c8:a8:39:e1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP61



Jun 30 17:29:03

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ad (tunnel 45), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:29:03

stm

Station 34:7e:39:8b:ef:e5: Clearing state



Jun 30 17:29:03

stm

Assoc request @ 17:29:03.588857: 34:7e:39:8b:ef:e5 (SN 699): AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:29:03

stm

Assoc request @ 17:29:03.544239: 34:7e:39:8b:ef:e5 (SN 699): AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:29:03

stm

Assoc success @ 17:29:03.549668: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:29:03

stm

Assoc success @ 17:29:03.591920: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61



Jun 30 17:29:03

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:29:03

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received association on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP61 Group default BSSID d8:c7:c8:a8:39:e1, phy g, VLAN 233



Jun 30 17:29:03

authmgr

MAC=34:7e:39:8b:ef:e5 Station UP: BSSID=d8:c7:c8:a8:39:e1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP61



Jun 30 17:29:03

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ad (tunnel 45), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:29:03

authmgr

MAC=34:7e:39:8b:ef:e5 def_vlan 233 derive vlan: 0 auth_type 0 auth_subtype 0



Jun 30 17:29:18

stm

Deauth to sta: 34:7e:39:8b:ef:e5: Ageout AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 handle_sapcp



Jun 30 17:29:18

stm

Deauth from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 Reason 255



Jun 30 17:29:18

stm

Deauth to sta: 34:7e:39:8b:ef:e5: Ageout AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 Denied: AP Ageout



Jun 30 17:29:18

stm

Deauth from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60 Reason 255



Jun 30 17:29:18

stm

Station 34:7e:39:8b:ef:e5: No authentication found trying to de-authenticate to BSSID d8:c7:c8:a8:39:f1 on AP AP60



Jun 30 17:29:38

stm

Assoc request @ 17:29:38.354368: 34:7e:39:8b:ef:e5 (SN 966): AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60



Jun 30 17:29:38

stm

Assoc request @ 17:29:38.333496: 34:7e:39:8b:ef:e5 (SN 966): AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60



Jun 30 17:29:38

stm

Assoc success @ 17:29:38.334348: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60



Jun 30 17:29:38

stm

Client 34:7e:39:8b:ef:e5 moved from AP AP61 to AP AP60



Jun 30 17:29:38

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:29:38

authmgr

MAC=34:7e:39:8b:ef:e5 Station DN: BSSID=d8:c7:c8:a8:39:e1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP61



Jun 30 17:29:38

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received disassociation on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP61 Group default BSSID d8:c7:c8:a8:39:e1, phy g, VLAN 233



Jun 30 17:29:38

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ad (tunnel 45), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:29:38

stm

Deauth from sta: 34:7e:39:8b:ef:e5: AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61 Reason STA has left and is deauthenticated



Jun 30 17:29:38

stm

Deauth to sta: 34:7e:39:8b:ef:e5: Ageout AP 10.50.50.61-d8:c7:c8:a8:39:e1-AP61 STA has left and is deauthenticated



Jun 30 17:29:38

stm

Station 34:7e:39:8b:ef:e5: Clearing state



Jun 30 17:29:38

stm

Assoc success @ 17:29:38.362455: 34:7e:39:8b:ef:e5: AP 10.50.50.60-d8:c7:c8:a8:39:f1-AP60



Jun 30 17:29:38

stm

Sending STA 34:7e:39:8b:ef:e5 message to Auth and Mobility Unicast Encr WPA2 PSK AES Multicast Encr Static WPA,WPA2 PSK TKIP VLAN 0xe9, wmm:1, rsn_cap:0



Jun 30 17:29:38

authmgr

MAC=34:7e:39:8b:ef:e5 Station UP: BSSID=d8:c7:c8:a8:39:f1 ESSID=cells_VoIP_ap VLAN=233 AP-name=AP60



Jun 30 17:29:38

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Received association on ESSID: cells_VoIP_ap Mobility service ON, HA Discovery on Association Off, Fastroaming Disabled, AP: Name AP60 Group default BSSID d8:c7:c8:a8:39:f1, phy g, VLAN 233



Jun 30 17:29:38

mobileip

Station 34:7e:39:8b:ef:e5, 0.0.0.0: Mobility trail, on switch 84.89.232.250, VLAN 233, AP AP60, cells_VoIP_ap/d8:c7:c8:a8:39:f1/g



Jun 30 17:29:38

authmgr

MAC=34:7e:39:8b:ef:e5 ingress 0x10ce (tunnel 78), u_encr 32, m_encr 2056, slotport 0x1040 , type: local, FW mode: 0, AP IP: 0.0.0.0



Jun 30 17:29:38

authmgr

MAC=34:7e:39:8b:ef:e5 def_vlan 233 derive vlan: 0 auth_type 0 auth_subtype 0



Jun 30 17:29:49

stm

Sending Call Status Message to Auth 34:7e:39:8b:ef:e5-0



Jun 30 17:29:49

stm

send_sta_on_call_message 3114 Sending Call Status Message to Mobility for client ip: 84.89.233.4 cname: s:5071 sname: pbxserver.cells.es reg dur: 3600
Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Re: Strange AP105 behaviour with voip

I suggest you read Aruba's VRD on Optimizing Mobile devices here: http://www.arubanetworks.com/pdf/technology/DG_Roaming.pdf

VOIP over wifi has a great number of considerations, and the vast majority of them are covered in the VRD.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 77
Registered: ‎07-10-2009

Re: Strange AP105 behaviour with voip

Thanks for the advice.
Also I will try to make a simple test changing that AP for another one of the same
model to see if the issue persists.
Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Re: Strange AP105 behaviour with voip

Have you done all of the optimizations in the VRD?
Just because a voice device is right under an access point, does not mean that it has roamed to it.
The voip optimizations, as well as access point density, depending on the handset are crucial for proper deployment. VOIP, unlike other clients, does not always just work and it needs planning.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 77
Registered: ‎07-10-2009

Re: Strange AP105 behaviour with voip


Have you done all of the optimizations in the VRD?



I dit some optimizations one year ago when we had the only 802.11g AP models.



Just because a voice device is right under an access point, does not mean that it has roamed to it.



With the timestamps of the debugging i've tested that when i am associated to that concrete AP there is no audio.


The voip optimizations, as well as access point density, depending on the handset are crucial for proper deployment.



Totally agree.


VOIP, unlike other clients, does not always just work and it needs planning.



The voip was working fine before upgrading that ap positions to model AP105.

I've changed the AP105 of that concrete position with another one and the problem disapeared.
Then i've installed again the prolematic AP on the same position and the problem
is also gone.

Any clue? Maybe it has to be hard rebooted? Because before all this stuff i've rebooted it from the controller.
Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Re: Strange AP105 behaviour with voip

Everything related to VOIP is specific.

- What handsets are these?
- What protocol is being used?
- At what TX power is the access point? (alot of manufacturers mention a minimum and maximum power for access points)
- Is the phone being used on the same l2 LAN as other devices?
- Are you using the "show voice" statistics on the commandline to monitor call quality?
- Did you go through the "troubleshooting" portion of the document that I mentioned before?


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 77
Registered: ‎07-10-2009

Re: Strange AP105 behaviour with voip


Everything related to VOIP is specific.

- What handsets are these?



Nokia E52



- What protocol is being used?



SIP


- At what TX power is the access point? (alot of manufacturers mention a minimum and maximum power for access points)



At 20 dBm (maximum of law)


- Is the phone being used on the same l2 LAN as other devices?



We have the voice and the data devices on a separate VLANs.


- Are you using the "show voice" statistics on the commandline to monitor call quality?



I used the troubleshoot feature of the "voip clients" user interface.

- Did you go through the "troubleshooting" portion of the document that I mentioned before?



Sorry for my poor english. In the previous post problem i tried to say that the problem was already solved before going trough the trobleshooting document.
(when I re-read it I see that there is some past tenses missing)

Before going through the troubleshooting guide I exchanged the bad AP105
with another AP105 and it worked fine. So I thought it was an AP problem.
Then to give a try to the bad AP105 (and to discard a hardware issue) i
installed the "bad" AP105 again and it also worked fine.

This puzzled me because before all this thread I tried to restart the AP using the web user interface. And it didn't work.

Then I can't troubleshoot nothing because the problem seems solved.

Now I was only trying to ask if this this difference about reboot the AP from a controller and phisically disconect and connect it is normal. Maybe the CLI command for restart an AP "apboot" is better than using the web user interface.

Thanks for the followup.
Guru Elite
Posts: 21,280
Registered: ‎03-29-2007

Re: Strange AP105 behaviour with voip

I am sorry for giving you so much trouble in English. I am glad to hear you are not having the problem anymore.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: