Has anybody had a problem with voice mails being cut off on ver.6.02 software with an Inmail. Two of the customers are new installs and one was existing that I upgraded to 6.02. The existing customer never had a problem until the upgrade.
Are they cutting off while the message is being recorded??
Have at least a dozen 8100 0n 6.02 with InMail. No complaints of cut-offs... yet.
D
NTAC got back to me yesterday. They have a known bug with 6.02 software with an Inmail on a PRI. That is exactly what is happening. I have some on POTS lines with no problems.
Hopefully it gets fixed soon
If you haven't got this resolved, NEC has released a solution that "appears" to work so far for us.
For some reason I'm unable to reach our mail server this morning, but it's series/list of setting changes
Would it be 80.04 Special busy Tone settings
80.04.12 = 3 and 80.04.13 = 4 ??
paulw . . .
"Yes, it was...
It involved PRI lines and 6.02
(By the way, if your still running 6.00 on anything, upgrade it. It's a trainwreck on VM) - As of last week, they are still shipping CCPU's with 6.00 causing incredible grief for us)
I don't know if I'm supposed to or allowed to post it (the various "fixes") here, but I guess most here can just call NEC and get it sent to them.
1 more additional change was sent by NEC after the first group
Official announcement by NEC that there will be patch or update to 6.02 to correct issues with InMail cut off messages and failed Um delivery.
Got an email today from NTAC.
D
doghart, mind forwarding me that email?
[email protected]Curious to see the official announcement.
I never got the Email from NEC
per NEC's suggestion I've rolled back at least 10 clients to 5.03.
Friday I was called out to a system experiencing the InMail cut-offs. The firmware was B6.00.
I tried rolling back to 5.03, but it caused major issues. All the IP stations were acting laggy and the InMail would not pick up from pressing the VMSG key or dialing the pilot. You could leave messages, just couldn't listen to them.
I tried initializing the CPU and reloading the database, but the problem was still there.
Finally had to take it back up to 6.02 to get the mail to work.
Hope that patch gets rolled out of Japan soon.
D
6.03 is out but the doc doesn't mention Inmail issues fixed.
Interesting comments from you guys in the US. When R6.00 was rolled out here the InMail cutoff fixes 80.04 Special busy Tone settings
80.04.12 = 3 and 80.04.13 = 4 were included. I have not had any sites reported with this issue after upgrading or going in as new.
It did take some effort during the beta release phase to convince anyone in Japan that this was an issue. looks like it didn't make it into your releases..
I spoke too soon. Just got my first field complain about this. Trying to find out if it's every time or how soon after the system is reset does this happen. Couldn't reproduce it in my lab with the site dump..
Paul, I have sites that have been in for several months that are just starting to have complaints.
Very odd indeed!
Have put about 6 site now up to 6.03. Waiting for a few weeks before I do the remaining sites. Don't want to have another issue blow up in my face.
D
Just wondering, I have a newly installed 6.02 using POTS lines and have had complaints of cut offs using In-Mail. While leaving a message the caller hears something like "your message is being archived". It is archived but cuts off at the same point. It's happened at one customer maybe 4 times in about a month. Is this the same issue?
Crap, I have a customer /w POTS lines and an InMail on 6.02
I have a fix that someone gave me (changing a bunch of values in programming) that is apparently from NTAC, but I haven't tried it.
Wondering if I should just roll them back to 5.02 and be done with it...
We have discovered one issue down here with going back to C5.02 in that the IPLB card no longer works as it gets its firmware upgraded when the system boots up to R6.0X.
Anyone know how to downgrade a IPLB to work on R5.0X systems??
Originally posted by paulw:
We have discovered one issue down here with going back to C5.02 in that the IPLB card no longer works as it gets its firmware upgraded when the system boots up to R6.0X.
Anyone know how to downgrade a IPLB to work on R5.0X systems??
Remove it and install an IPLA
D
Well, NTAC replied to me and had me change some memory blocks. Made the changes to 3 systems, and none have reported cut-off messages! I was getting a report from each site every 1-2 days.
If anyone needs the fix, shoot me a PM.
Originally posted by doghart:
Originally posted by paulw:
[b] We have discovered one issue down here with going back to C5.02 in that the IPLB card no longer works as it gets its firmware upgraded when the system boots up to R6.0X.
Anyone know how to downgrade a IPLB to work on R5.0X systems??
Remove it and install an IPLA
D [/b]Good luck if you can get these now. We only get the IPLB and IPLC these days. Got a reply back from NECA TAC. No they cant be taken back to R5.0X
I have been given some PRGs to change for the InMail and they seem to be working OK..Most likely the same as the ones Derek was told. (keeps fingers crossed) :-)
IPLC??
Not seen that here.... yet.
Thanks for the email Paul, I have changed 4 sites so far and they are working properly now. Just hard sometimes to get the customers to let me do a hard reset in the middle of the day, but if that what it takes....
D
Glad to see the settings seem to work. No problems on the sites we have done the changes to here.
IPLC . Replacement for the IPLA card only used on the SV8300. We think the main differences between the IPLB and the IPLC are NAT translation.
Anyone have a copy of the changes that need to be made, been trying to resolve this since upgrading a customer to R6.00 back in the end of March.
Ignore the last post, have updated to R7.00 which seems to have resolved it.
This same Inmail messages cutoff problem has plagued me for 3 weeks on a new install with 6.03. A buddy told me that the 7.0 upgrade would fix it but after the upgrade, the customer continued to intermittently have the same problem. My buddy got instructions from NTAC and here's the complete list of things that require changes. Hope this helps.
Problem Description: Inmail Messages Cutoff
Type 3 tone "Ringback Tone For Trunks"
80-04-06 "On Minimum Time": change from 25 to 23
80-04-07 "On Maximum Time": change from 40 to 74
80-04-08 "Off Minimum Time": change from 83 to 59
80-04-09 "Off Maximum Time": change from 115 to 232
Type 4 tone "Special Busy Tone For Trunk"
80-04-03 "S/N Ratio": change 2 to 1
Type 5 tone "Special Ring Back Tone For Trunk"
80-04-05 "Pulse Count": change 0 to 2
80-04-06 "On Minimum Time": change from 0 (or 36) to 2
80-04-07 "On Maximum Time": change from 0 (or 36) to 5
80-04-08 "Off Minimum Time": change from 0 (or 36) to 2
80-04-09 "Off Maximum Time": change from 0 (or 36) to 5
80-04-13 "Frequency 2 Table": change from 0 to 2
CPU RESET IS REQUIRED
thanks ntac
@Rider71. Did it fix the problem as I'm still getting intermittent complaints down here..
The settings in Type 3 tone are new as they are quite different to what we have set now. The rest are the same..
Wish the Japs hadn't tried to be too smart and play around with this as the InMail had been working fine since R1.00