TIPS Polycom 330 being wonky

[rossiv]

I just moved a Polycom 330 from a WiFi bridge to a network drop and ever since then it has been dropping the connection to the PBX every 10 seconds consistently. I have also tried it on several known-good network drops and the same thing happens on every drop, so it isn't the wiring. In the logs, I see this:

[2012-02-29 00:11:30] NOTICE[4239] chan_sip.c: Peer '204' is now UNREACHABLE!  Last qualify: 144
[2012-02-29 00:11:30] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201 (queued)
[2012-02-29 00:11:30] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201 
[2012-02-29 00:11:40] NOTICE[4239] chan_sip.c: Peer '204' is now Reachable. (9ms / 2000ms)
[2012-02-29 00:11:40] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Idle for Notify User 201 (queued)
[2012-02-29 00:11:40] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Idle for Notify User 201 
[2012-02-29 00:12:44] NOTICE[4239] chan_sip.c: Peer '204' is now UNREACHABLE!  Last qualify: 9
[2012-02-29 00:12:44] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201 (queued)
[2012-02-29 00:12:44] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201 
[2012-02-29 00:12:54] NOTICE[4239] chan_sip.c: Peer '204' is now Reachable. (9ms / 2000ms)
[2012-02-29 00:12:54] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Idle for Notify User 201 (queued)
[2012-02-29 00:12:54] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Idle for Notify User 201 
[2012-02-29 00:13:58] NOTICE[4239] chan_sip.c: Peer '204' is now UNREACHABLE!  Last qualify: 9
[2012-02-29 00:13:58] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201 (queued)
[2012-02-29 00:13:58] VERBOSE[4187] chan_sip.c:   == Extension Changed 204[ext-local] new state Unavailable for Notify User 201

But it isn't every 10 seconds that it goes out but it is out for 10 seconds each time it goes out and a minute or so apart for each outage. So strange to me. I am provisioning the phone through t*f*t*p if it matters. I've even tried resetting to factory defaults and that didn't help.

Thoughts?

Thanks

 PBX in a Flash PURPLE Status
 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────


                                    ┌────────────────────────System Information───────────────────────────┐
                                    │  Asterisk   = ONLINE  | Dahdi     = ONLINE  | MySQL     = ONLINE    │  
                                    │  SSH        = ONLINE  | Apache    = ONLINE  | Iptables  = ONLINE    │  
                                    │  Fail2ban   = ONLINE  | Internet  = ONLINE  | Ip6Tables = ONLINE    │  
                                    │  BlueTooth  = ONLINE  | Hidd      = ONLINE  | NTPD      = ONLINE    │  
                                    │  SendMail   = ONLINE  | Samba     = OFFLINE | Webmin    = ONLINE    │  
                                    │  Ethernet0  = ONLINE  | Ethernet1 = OFFLINE | Wlan0     = N/A       │  
                                    │                                                                     │  
                                    │  PBX in a Flash Version   = 1.7.5.6 Running on *HARDWARE*           │  
                                    │  FreePBX Version          = 2.8.1.4                                 │  
                                    │  Running Asterisk Version = 1.8.6.0                                 │  
                                    │  Asterisk Source Version  = 1.8.6.0                                 │  
                                    │  Dahdi Source Version     = 2.5.0.2+2.5.0.2                         │  
                                    │  Libpri Source Version    = 1.4.12                                  │  
                                    │  IP Address               = 192.168.4.2 on eth0                     │  
                                    │  Operating System         = CentOS release 5.6 (Final)              │  
                                    │  Kernel Version           = 2.6.18-238.9.1.el5 - 32 Bit             │  
                                    │                                                                     │  
                                    └─────────────────────────────────────────────────────────────────────┘  
                                                                                                             




root@pbx:~ $

Status To File (Sanitized of course): http://pastebin.com/aP3AwwsM --And yes, I know that my internal IP is not censored. You can't do anything with it anyway from where you are.

 

[rossiv]

Bump..........

 

[Fortel]

Hmmm....

Was the WiFi bridge part of the same LAN as the phone's current network drop?

Is the phone on the same network as the PBX?

I don't imagine it's anything to do with the PBX. But I have seen Polycoms that apparently retain some of the programming so, even though you might changed settings via the GUI, the old are cached. But I don't guess anything was re-programmed in the phone at the time the WiFi bridge was replaced by a physical cable.

Are there other Polycoms in that environment? I'd like to see how another phone behaves...

Anything else change on that network?

Peter

 

[rossiv]

Hmmm....

Was the WiFi bridge part of the same LAN as the phone's current network drop? Yep.

Is the phone on the same network as the PBX? Yep.

I don't imagine it's anything to do with the PBX. But I have seen Polycoms that apparently retain some of the programming so, even though you might changed settings via the GUI, the old are cached. But I don't guess anything was re-programmed in the phone at the time the WiFi bridge was replaced by a physical cable. Correct.

Are there other Polycoms in that environment? I'd like to see how another phone behaves... Just the one and I even formatted its file system through the menus.

Anything else change on that network? Nope. Not at all.

Peter

fillerrrrrr

 

[atsak]

Port problem (ie switch, cable etc)?

On the switch can you see if the port is flapping or any dx info?

Also did you reboot the server? Try clearing the ARP cache on it.

 

[ErikU]

Try a different port and different patch cords.

Reboot the phone.

Reflash the bootloader and firmware.

 

[rossiv]

Port problem (ie switch, cable etc)?

On the switch can you see if the port is flapping or any dx info?

Also did you reboot the server? Try clearing the ARP cache on it.

Tried it on two different switches with many different cables.
Yep rebooted the server - and all other phones are fine.

 

[rossiv]

Try a different port and different patch cords.

Reboot the phone.

Reflash the bootloader and firmware.

Did that.
That too.
And that when a formatted its file system - it pulled new everything.

 

[Fortel]

I'd be tempted to plug it back into the WiFi bridge and see if the problem continues, or if the bridge somehow "fixes" the registration timeouts.

If it works correctly with the WiFi bridge this time, then possibly there's something in the router / firewall associated with the bridge's MAC- keeping some NAT pinhole open... just a guess.

 

[rossiv]

I'd be tempted to plug it back into the WiFi bridge and see if the problem continues, or if the bridge somehow "fixes" the registration timeouts.

If it works correctly with the WiFi bridge this time, then possibly there's something in the router / firewall associated with the bridge's MAC- keeping some NAT pinhole open... just a guess.

I don't think it would be a NAT issue as they are on the same network - FWIW, I put a 7960 behind the bridge and it experienced the same problem but not on a wired connection. I have tried plugging it back into the bridge with the same issues.