If it works in 4.2, it seems logical that is what you should be running. Because the phone reboots, there is no real way to "log" what it might be throwing that causes the reboot. It certainly sounds like a LAN issue.
You should ensure it is properly configured and running a recent firmware for the spectralink. In your current description I would suggest you put the proxy and registrar in debug, boot the phone up and and make a call that makes it fail. You should pay closest attention to what the PROXY log sees as the invite message out to see if it is priperly formatted from the phone and what error messages it sends (if any). You should also properly understand whether or not it supports registering and sending calls via SRV records or not, which means looking at the polycom manual to see. So I suspect a lan/dns configuration issue here. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Fri May 07 14:37:45 2010 Subject: [sipx-users] SpectraLink Wifi Hello - I am once again trying resolve an issue with the Spectralink ( Polycom) 8030 Wifi Handsets (SIP) . I am more than happy to pay someone for their time if they think they can resolve this issue. I have a SIPX system being installed this month with 50 Polycom and 16 8030 handsets . I would like to but in 4.2 but will install 4.02 if I can not. Wireless to wireless, wireless to wired, outside calls to wireless all work perfectly. When I tried to dial out( eg my cell phone) the 8030 displays no net found and starts to reboot but the call goes through to my cell phone, the cell phone continues to ring and when the 8030 handset comes back up I answer my cell phone and the 8030 repeats the no net access routine again. I have wireshark trace from the sipx server if this will help. I did not have this issue on 4.2 but on both 4.04 and 4.2. This is not a production system but in my test lab. Laptop= 192.168.1.100 | 8030= 192.168.1.246 | SIPX- 192.168.1.25 Bob Anderson Cyrand Corp 3-4170 Sladview Drive Mississauga, ON L5L 0A1 905-817-8208 x237 www.cyrand.com _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
