Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Avaya Aura & Unified Communications (http://support.avaya.com/forums/forumdisplay.php?f=2)
-   -   Phone Discover Issue after reconvergence (http://support.avaya.com/forums/showthread.php?t=11027)

petilliw 02-29-2016 04:50 PM

Phone Discover Issue after reconvergence
Having an issue between a core CM 6.0.1 and LSP 6.3. The remote site uses 9611G h.323 phones. They get the list of registration IP's from DHCP. When there is a WAN outage the site goes into survivable mode with no problem and all the phones register to the local s8300. After a reconvergence the MG recovers normally and the phones do not. They are sitting in a discover state and scrolling through the IP's and never making a registration. It's only after a full phone reboot that they reconnect.

The network team ran a wireshark trace and there are RAS messages saying Gatekeeper request and then reject. This is coming from clan and the PE. No idea what would be causing this, as we have remote sites all over the world. Then a full reboot of the phone registers normally. the capture sees the phone continuously trying the same clan IP address over and over and not moving through the list it should have cached from DHCP. The team put an acl to block this specific clan IP and after about 10-12 minutes the phones then register back to the core via the PE or another clan in the list. Any help would be appreciated.

fazil3 03-07-2016 11:04 AM

Is there another MG registered to the LSP ?

petilliw 03-07-2016 12:01 PM

No. The GW re-registers to the core and the s8300 goes back inactive as it should. All registered phones to the s8300 unregister and fail to register back to the core CM.

Additionally, there was a brief WAN outage in another remote office where the system is hung off of the same core. Once the network reconverged the GW re-registered to the core, but those phones also had the same issue where they did not register back.

Wondering if I should give my CLANs a reset at this point. Makes no sense.

All times are GMT -7. The time now is 11:37 AM.