hostarica
asked on
issues with WET610N wireless bridge and 3COM ip Phones.
Hello All,
we bought a couple of WET610N bridges in order to connect two 3COM IP Phones, the NBX is quite old and we are not able to get the phones to work.
The phone is able to connect to the NBX and it downloads the firmware but hungs after it with the message "Wait for NCP", if we check the NBX, it sees the phone "online" but the phone is not able to make/receive calls.
we have other phones connected wirelessly but using SILEX bridges which have some glitches also so we decided to try with these linksys.
Seems that the problem is that the phones register at layer 2, and the bridge sends its MAC address instead of the phone's MAC so the NBX does not registers the correct MAC address.
do you know any workaround to get it working?
we have tried several configurations with no luck.
* Model for Phone System: 3Com NBX 100
NBX® Version R6_0_59
Thank you in advance.
we bought a couple of WET610N bridges in order to connect two 3COM IP Phones, the NBX is quite old and we are not able to get the phones to work.
The phone is able to connect to the NBX and it downloads the firmware but hungs after it with the message "Wait for NCP", if we check the NBX, it sees the phone "online" but the phone is not able to make/receive calls.
we have other phones connected wirelessly but using SILEX bridges which have some glitches also so we decided to try with these linksys.
Seems that the problem is that the phones register at layer 2, and the bridge sends its MAC address instead of the phone's MAC so the NBX does not registers the correct MAC address.
do you know any workaround to get it working?
we have tried several configurations with no luck.
* Model for Phone System: 3Com NBX 100
NBX® Version R6_0_59
Thank you in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't have personal experience of this device. Like you I would have to scour the dd-wrt and similar forums for info.
First thing to try would be more recent firmware from the vendor, see http://homesupport.cisco.com/en-us/wireless/lbc/WET610N
Reading around the subject I found this :-
"Long story short, when I ran a multi-client check, both the WET6 and one of the two client machines connected to it via a switch leased the same IP address via DHCP. Although Windows did not flag an IP address collision, the duplicate-IP client was not able to communicate through the WET6, which caused my misdiagnosis.
The easy work-around (as well as good practice) is to assign a static IP address to the WET610N that is outside your router's DHCP server range."
- in case your phones are getting a duplicate IP. Or do they only work at MAC layer ? Does the WET610 give you alternative modes of operation on its GUI ?
First thing to try would be more recent firmware from the vendor, see http://homesupport.cisco.com/en-us/wireless/lbc/WET610N
Reading around the subject I found this :-
"Long story short, when I ran a multi-client check, both the WET6 and one of the two client machines connected to it via a switch leased the same IP address via DHCP. Although Windows did not flag an IP address collision, the duplicate-IP client was not able to communicate through the WET6, which caused my misdiagnosis.
The easy work-around (as well as good practice) is to assign a static IP address to the WET610N that is outside your router's DHCP server range."
- in case your phones are getting a duplicate IP. Or do they only work at MAC layer ? Does the WET610 give you alternative modes of operation on its GUI ?
ASKER
Hello yarwell,
We are using Static IPs for the phones so the issue is not with duplicate IPs. the phones has the option to assign the IP, mask, GW, and NCP statically, and in some way the phone is able to register since it downloads the firmware but then it hungs, if we look at the NBX, the NBX sees the phone as registered and online, however, is not able to send/receive calls.
If we plug a PC to the bridge, it works perfectly, I'm able to browse, check e-mail, etc. so the problem seems to be compatibility between 3COM phone<->BRIDGE<->NBX.
I would like to give a try on changing the firmware on the BRIDGE, however, I was not able to get any good information in dd-wrt about this device. I think it is because it is too new.
I think that would be the only "possible" solution so far, change the firmware and check if I'm able to do transparent bridge with it.
any other advice is highly appreciated.
Thank you.
We are using Static IPs for the phones so the issue is not with duplicate IPs. the phones has the option to assign the IP, mask, GW, and NCP statically, and in some way the phone is able to register since it downloads the firmware but then it hungs, if we look at the NBX, the NBX sees the phone as registered and online, however, is not able to send/receive calls.
If we plug a PC to the bridge, it works perfectly, I'm able to browse, check e-mail, etc. so the problem seems to be compatibility between 3COM phone<->BRIDGE<->NBX.
I would like to give a try on changing the firmware on the BRIDGE, however, I was not able to get any good information in dd-wrt about this device. I think it is because it is too new.
I think that would be the only "possible" solution so far, change the firmware and check if I'm able to do transparent bridge with it.
any other advice is highly appreciated.
Thank you.
can you ping the phones via the bridge, or access their web interface ?
in your OP you said the phones registered at the MAC layer so it may not be an IP problem.
What other modes does the bridge have ? can it act as a WDS repeater for example which is a MAC layer activity. Would need the other end to support WDS and appropriate settings of course - typically you tell each one the MAC of the other and set the encryption the same.
in your OP you said the phones registered at the MAC layer so it may not be an IP problem.
What other modes does the bridge have ? can it act as a WDS repeater for example which is a MAC layer activity. Would need the other end to support WDS and appropriate settings of course - typically you tell each one the MAC of the other and set the encryption the same.
ASKER
yarwell,
the phones are quite old and do not have web interface, however, we are able to ping them and if we daisy chain a computer to the phone I'm able to reach the PC through Remote Desktop.
I'm not sure about the WDS, I'm going to check it out and keep you updated.
the phones are quite old and do not have web interface, however, we are able to ping them and if we daisy chain a computer to the phone I'm able to reach the PC through Remote Desktop.
I'm not sure about the WDS, I'm going to check it out and keep you updated.
ASKER
unfortunately, the devices did not fit our needs, we won't be able to use them.
ASKER
do you know if it is possible to run dd-wrt or any other firmware on this device?
I google it but only found information about older models.
Any help is highly appreciated.