Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Thread Tools Search this Thread Display Modes
Old 03-01-2011, 07:04 AM
dupl dupl is offline
Hot Shot
Join Date: May 2010
Posts: 17
dupl has 10 reputation points
Default IP Phones Discovering

Hi All,

I have a problem where phones go into the discover mode when you logoff the user and try to login once again.
This happens on over 10 000 extensions and more than 7 locations World Wide all linked via WAN/ESS/IPSI etc....
It also happens on all type of phones 46xx/16xx/96xx.
Loaded the latest Firmware for IPSI and C-Lan and still the same problem.
CM 5.2.1 is currently being used with Service Pack 5, will be loading Service Pack 7 this coming weekend and see if there is any difference.
All was fine and it started approx a week ago....Customer has very good network skills on site and they confirmed that it is not a Network issue.
When I take this same problomatix phone and changes it to register to the LAB AVAYA it registers immediately....only problem with above test is that it is different CM Versions.
When phone is logged in it works 100%, not a problem.
Any Advise...
Reply With Quote
Old 03-04-2011, 01:41 AM
aa1 aa1 is offline
Join Date: Feb 2010
Location: Budapest - Hungary
Posts: 185
aa1 has 24 reputation pointsaa1 has 24 reputation points
Default Troubleshooting


I am sorry to hear that. There could be some configuration mismatch or software difficulty either on the phones or Communication Manager. Somemthings to try:

1) try disabling the TTS ( se the "Near End Establishes TCP Signaling Socket? " to N on the ip-network-region form, page 2 of the network-region the phones should be registered to.

2) search for denial events in the Communication Manager (using displaly events form and filter for the extension you tried to login).

3) a network wireshark trcae will show the RAS messages between the phone and the gatekeeper.

4) List trace ras (with IP address of the phone). Do you see any difficulty? Maybe you could paste it here and that might help

if the difficulty is still there after SP7, I suggest contacting Avaya support team and opening a ticket. Some details that would help:

a) A wireshark trace of the phone from a complete reboot of the phone to login a station and then loggoff and then try to login again where the difficulty is present then.

b) A list trace ras on the Communication Manager SAT interface.
Reply With Quote
Old 03-07-2011, 11:03 AM
rogerg's Avatar
rogerg rogerg is offline
Join Date: Jan 2010
Location: Houston, Tx
Posts: 51
rogerg has 10 reputation points

You might also take a look at the 46XXsettings.txt file. I was having the same issue on CM 5.2.1 and found that if I removed the "SET MCIPADD XXX.XXX.XXX.XXX" it corrected the issue. The phones should get the first CLAN or Proc-Ethernet address from DHCP options, so that setting should not be required.
Gary Rogerson
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 03:30 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.