10-14-2014 01:08 PM - edited 10-14-2014 01:10 PM
So I have a RAP setup and it works well for all data back to HQ, but for some reason the VOIP phone doesn't work so great. We have the phone plugged into the PoE port on the RAP 3 and we get the phone to boot up, show everything fine, can dial out and receive calls. HOWEVER, the call just goes blank when answered or picked up.
So you dial to say voicemail or another person, internal or external. It rings, and as soon as they pick up, the phone goes silent.
Internally the phone works perfectly. My best guess is that I am missing some VOIP specific configurations. This is my first RAP I have setup, and internally we have the phones connected to our switches, not going through the controller at all.
What are some things you would recommend I check?
EDIT: Running AOS 126.96.36.199
Solved! Go to Solution.
10-14-2014 03:19 PM
One thing you could do is create a UDR using the OUI 00:10:49 and then applying all your priorities and markings to VOIP role applied by your UDR
For this to you need to create AAA profile apply the UDR , then use this AAA profile on your wired ports settings and make the port "Untrusted"
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
10-15-2014 01:20 PM
The answer is yes I had VOIP trunked to my controller. HOWEVER, the person that setup the port channel specified allowed VLANS, and the VOIP VLAN was not listed as allowed.
To kind of explain the setup, we have two routes to get to the controller, 1 is more for management, but it could technically be setup to route properly. We had that set a trunk that allowed all VLANS. The Router however, only allowed VOIP on another portion of the network. (We don't need it in our Management Network) so the VOIP could originate from the controller to our VOIP Server, but anything the VOIP Server sent back would have to go through the Port Channel, but the VLAN was not allowed on the Port Channel.
So long story short. It was a trunking issue.
11-06-2015 09:03 AM
UDR = user derivation rules. It can be used to see the mac address of a phone and then apply a role with QOS in it to the ethernet interface.
For detailed information, please see the Voice VRD for Fixed Telecommuter Deployments here. http://community.arubanetworks.com/t5/Validated-Re
QOS is normally applied by a user derivation rule setting a role that has QOS firewall policies.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base