UTStarcom not connecting to D-link 655

Posts: 8 · New Forum Member Joined: Mar 23, 2008 Posts: 8

I just upgraded to the Dlink 655 router and now I cannot get my UTStarcom to play with it! I have seen posts about sound quality being poor and intermittent issues with Vonage adapters but not this phone specifically. I'm guessing there is a difference... We have also tried to connect a Nokia N95. The Nokia will browse the internet but will not make Voip calls so I am assuming that I am missing something obvious.

There is no option to disable SIP nor can I downgrade the firmware (two suggestions made on another forum).

Any help would be greatly appreciated!!!!

Posts: 16 · Vonage Forum Associate Joined: Mar 21, 2008 Posts: 16

Try this:
Login to your router via your webrowser: 192.168.0.1

Click on the Advanced tab at the top
Click on the Port Forwarding to the left
- Under name enter: Vonage1
- In the IP address enter the IP of your Vonage Device
- In the UDP enter: 5060-5063, 21, 53, 69, 123, 2400

- Enter Vonage2 in the next name field
- Enter IP address again
- Under UDP enter: 10000-20000

Hit Save Settings at the top
Reboot later

Now hit Advanced again, and in the left Select: Firewall Settings
Scroll down and uncheck SIP (The last checkbox on the page)

Save and reboot.

This should get you up and running.

Posts: 8 · New Forum Member Joined: Mar 23, 2008 Posts: 8

I don't have a SIP option. I'm using firmware version 1.1EU

Posts: 16 · Vonage Forum Associate Joined: Mar 21, 2008 Posts: 16

http://www.dlink.com/products/support.asp?pid=530&sec=0 (US)

That is the link to download the 1.11 firmware. That is what I am running with no problems at all.

EU Links and info:
http://www.dslreports.com/forum/r19362111-Info-DIR655-New-Firmware-Version-111-Eu

ftp://ftp.dlink.se/Products/dir-products/dir-655/drivers_firmware/DIR655A3_FW111EUB00.zip (Actual download)

Google search for the win!

Posts: 8 · New Forum Member Joined: Mar 23, 2008 Posts: 8

Thank you so much for helping me with this. Unfortunately, I am still getting the message "Couldn't connect to AP". Before I got your last message, i plugged my old Linksys router into the new Dlink (not ideal, I know...) and the phone worked connecting to the old Linksys router. This is DEFINITELY not the route I wanted to take but I needed to use the phone. Strange that it worked since the Linksys was connecting thru the Dlink. The Linksys is setup with a WEP password while the 655 is setup with WPA... if that makes a difference? Also, I set the IP address on the UTStarcom and then set up a DHCP reserve for that IP address as well.

Any other ideas?

Posts: 328 · Vonage Forum Evangelist Joined: Dec 13, 2005 Posts: 328

I don't know if this D-Link has the same problem as some others, but I have seen connection problems like this where the D-Link gives out the same association ID to all devices, then "forgets" who is who.

The way to test this out is to reboot the D-Link then have the WiFi phone be the first thing to associate with the router. If it works, then that is the problem.

Another possibility is that the D-link is putting added "security" (meaning that they block more stuff - using the same philosophy that you would use by nailing a door shut to make it more secure) on the WiFi part of the router than on the wired part, figuring that if you can plug in, then the router is likely yours while if you're on WiFi you could be "anyone". In that case, I'd suggest checking the D-Link "security" settings.

Posts: 830 · Vonage Forum Evangelist Joined: Jun 08, 2007 Posts: 830

VOIPbroke wrote:

The Linksys is setup with a WEP password while the 655 is setup with WPA... if that makes a difference? Also, I set the IP address on the UTStarcom and then set up a DHCP reserve for that IP address as well.

Any other ideas?

WPA comes in two flavors, enterprise (802.11i) and personal (PSK). I assume that the Starcom uses PSK, so verify what the Dlink is using.

Since around 2006, WPA2 became a major trend in "certified" DPA wireless devices. These include the mandatory features of 802.11i. However I would not think this is a problem as WPA is both forward and backward-compatible.

Looking at the TOC of the Manual, there are two flavors of WPA on the D-Link:

Wireless Security........................................................63
What is WEP?.........................................................63
What is WPA?.........................................................64
Wireless Security Setup Wizard.............................65
Configure WEP.......................................................68
Configure WPA-Personal (PSK)..............................69
Configure WPA-Enterprise (RADIUS).....................70

Again check that you are using "Personal"

Posts: 328 · Vonage Forum Evangelist Joined: Dec 13, 2005 Posts: 328

I would add one more item here - the UTStarcom F1000 supports only WPA-PSK (TKIP). It specifically DOES NOT support WPA-PSK (AES) nor any of the enterprise/radius based versions of WPA/WPA2.

Posts: 8 · New Forum Member Joined: Mar 23, 2008 Posts: 8

The security was set to WPA Personal. I changed it to WEP - no luck. Then I changed it to NONE - no luck.

I'm back to believing it's a setup issue. I currently have the phone working on the Linksys that is plugged into the DLink... which is rubbish.

What else can I try? I'm at my wits end!

Posts: 328 · Vonage Forum Evangelist Joined: Dec 13, 2005 Posts: 328

Does the phone's MAC show up in the DHCP Clients Table on the router (MAC starts with 00:07:). If so, then the router sees the phone but the phone does not stay linked for some reason. If the phone does not show up, then the router doesn't see it at all.

Another thing to check is what the display says - do you get "No Service Try Another AP" (which indicates that it is linking to the router, but not going past there) or do you get "Cannot Connect to AP" - which means that it is not getting an IP address or is otherwise having trouble communicating with the D-Link.