Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP phone 2.8.3 firmware

Status
Not open for further replies.

Konri

Technical User
Jan 9, 2004
97
PL
Hi,
Did You use this firmware already?
I've just use this and many of my phones (4610, 4625, 4621) don't work propertly.
When I press some type of programmed buttons (directory, auto-call-back) phone is rebooted.
CM is 3.1.2 with latest patch.

Regards
K
 
Yeah, I loaded on some 4610's and now they say 'No Ethernet'. The data switch is under my desk and I can see the port go active when I power cycle the phones, but they go off during the boot process. My 4625 is working just fine. You can watch the phones connect and drop on the switch. BUT, bow that I have the new code on and they won't connect to the network, I have no way to back rev them to 2.8.
 
Wow, whew. Glad I waited - mainly because there are NO release notes attached with the firmware with the changes..
 
I have already installed R2.8.3 on a clients 4621's in London, with no issues at all, running CM 4.0.1 This was over 40 phones

I have also installed this on another client in NYC, with Cm 3.1.4 currently, and still no issues...

Mitch
 
I've just made an upgrade to 3.1.4 and I have the same issues.
 
Konri,

In your 46xxsetings.txt file, do you lock the ethernet ports to 100MB/Full? Do you have the ethernet POE switch set to lock the ports at 100MB/Full? We always do both, its just more reliable.

Here is a sample of a 46xxsettings file I use on an S8300C, we use the S8300C for both TFTP and HTTP/HTTPS for both 4600 and 9600 series phones.

your option 242 string on the DHCP server needs to look like this:

Option 242: MCIPADD=192.168.1.245,MCPORT-1719,TLSSERVER=192.168.1.245

The above IP's are an example, you MUST use TLSSERVER NOT HTTPSRVR, in the Option 242 string. You also must have a SET HTTPSRVR 192.168.1.245 [example S8300] in the 46xxsettings.txt file for the S8300 to serve out the HTTP/HTTPS files properly. Just copy your 4600 files and 9600 files to your /tftpboot directory. There are also some .tar.gz files you can install that set up the /tftpboot directory for you, available on the AVAYA website for the 9600 R1.5 and 4600 R1.8.3 firmware, mostly for CM 4.0

SET AUTH 0
SET HTTPSRVR 192.168.1.245 [this is the IP of the S8300]
SET STATIC 0
SET AGCHAND 1
SET AGCHEAD 1
SET AGCSPKR 1
SET L2Q 2
SET VLANTEST 60
SET DHCPSTD 0
SET PHY1STAT 5
SET PHY2STAT 5
SET PROCSTAT 0
SET PROCPSWD 27238
SET SNMPSTRING private
SET ICMPDU 1
SET ICMPRED 0
SET IRSTAT 0
SET APPSTAT 1
SET OPSTAT 111
SET PHNDPLENGTH 4
SET PHNLDLENGTH 10
SET PHNOL 9
SET PHNLD 1
SET PHNIC 11
SET PHNCC 1
SET SYSLANG English
SET RESTORESTAT 1
SET FTPUSERSTAT 1
SET AUDIOENV 0
SET AUDIOSTHD 0
SET AUDIOSTHS 0
SET ENHDIALSTAT 1
SET VLANSEP 0
SET BAKLIGHTOFF 120
SET RESTORESTAT 1
## SET FTPSRVR 192.168.1.245
## SET BRURI SET LANGSYS English
SET LANG0STAT 1
SET LANG1FILE mlf_S15_v14_russian.txt
SET LANG2FILE mlf_S15_v14_spanish.txt
SET LANG3FILE mlf_S15_v14_french_paris.txt
SET LANG4FILE mlf_S15_v14_german.txt
SET MSGNUM 3399
## SET MCIPADD 192.168.1.245
SET REREGISTER 20
SET CTISTAT 0
SET CTIUDPPORT 49721
SET UNNAMEDSTAT 1
SET L2QAUD 6
SET L2QSIG 6

Mitch
 
Well, I figured out the issue on my end. My test phones are statically addresses. Once I put them back to DHCP and pointed them to another TFTP server with 2.8, they are working again. Had the same issue when I statically addressed a 4621SW. But, my 4625 is still chugging along with a static address. Weird!
 
I'm quite sur that your station language is set to "user defined" - change it to English or unicode ( if unicode file is already on your CM ) and the problem will fade away....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top