10-09-2010 09:06 PM
10-09-2010 09:30 PM
One method to view this is : On the WEBUI, navigate to Clients, and select the phone from the list of clients. The select the STATUS button for this client (the phone). Next, scroll down on the resulting screen and observe the traffic as seen at the controller for the phone under User Firewall State. Notice the right most column... allow or deny. If there are 1 or more protocols or destinations in the deny state that could explain your situation.
A packet capture (and subsequent comparitive analysis) of one of these same phones(HW/SW/Firmware/Config) booting 'behind' a RAP-2 and one that is on your local LAN would be a good comprehensive method to debug as well.
10-10-2010 07:33 PM
I have managed to get the Shoretel Phones to work successfully over the RAP-2WG ...in our case talking via a 620 controller.
It was, in our case, getting its IP from the "Enterprise DHCP".
As an observation I found that if we ran the RAP 2 remotely through a 3G modem/router and the network latencies were ok then there was no issue with dialtone etc. If there were significant delays (as sometimes happens with the high traffic 3G periods) then no dialtone was evident through the phone. As well as that , there was a significant delay in the phones returning dialled digits (as they were entered) it seems that the Shoretel phones do "Everything " in realtime to the SG boxes. this is not an ideal situation when VPNing in a less than perfect environment. Otherwise there was Very little to complain about , as long as the latencies were respectable.
Check that you have a return path for the RTP coming from the core.
10-10-2010 07:50 PM
If the Shoretel is configured as SIP you will be wanting to view randomized UDP ports for the RTP payload (as seen in the Monitoring/Clients/Status/Firewall State table mentioned previously).
If, instead, the phones are NOT configured to use SIP, then look for a fixed port UDP 5004 for the Shoretel inband(voice, tones etc) communications.
10-21-2010 10:49 AM
I knew it was some basic but necessary settings I had missed. Being new to Aruba, I'm finding I do that a lot with the controller.
Thanks again for your help everyone!