Not sure if you guys saw this or not, but 6.03 is out with a bunch of bug-fixes.


New Features:
a)NAPT Enhancement
b)IP Single Line Telephone (SIP) Enhancement
c)PC Programming outbound IP connection
d)Remote (System) Upgrade with MEMDB
e)VM8000 InMail Enhancements
f)Standard SIP Transfer
Field Complaints:
a)F110801001 - Live Monitor does not work when InMail is assigned ports 497-512.
b)F110719001 - VRS Delay Announcements stuck in a continuous loop.
c)F120126001 - Desktop Suite with DSS Console shows incorrect extensions in the DSS/BLF area.
d)F120321001 - Univerge SV8100 InMail CF is causing the phone system to reboot continuously.
e)F110630001 - When calls are made via a TAPI application (UCB, Desktop Suite, Dialer), if the dialed number ends with 911 and PRG 21-01-12 is set to 0, the number will not be dialed correctly.
f)F100415001 - Transferring a call out of UCB VM to an outside number fails when transferring out on Copper Lines.
g)F111010002 - If the VRS in a SV8100 answers an incoming analog trunk and the user dials an extension that call forwards no answer across CCIS to VM in a SV8500, the busy greeting is played instead of the no answer greeting.
h)F110322001 - IP Stations loose connection after port 5081 on the CP00 stops responding and a reset of the SV8100 is the only thing resolves it.
i)F110518002 - If an extension barges into a conference call, phantom calls are created in UCB for the extension initiating the barge it.
j)F110602003 - UCB agent extensions show "CTI Operation" in the display when UCB invokes the CTI unpark-with-callback feature to redirect a call from a UCB queue to the agent's extension.
Note: Any Field Complaints resolved in previous versions of Univerge SV8100 software are included in v6.03. Please refer to the SV8100 Release Notes Issue - 1.12.doc, SV8100 Release Notes Issue - 2.51.doc, SV8100 Release Notes Issue-3.13.doc, SV8100 Release Notes Issue-4.01, and SV8100 Release Notes Issue-5.02 for previously resolved field complaints.

No word if this contains the InMail message cut-off fix?

D

Nothing official. NEC was aware of that issue with the InMail. Considering they've acknowledge the system reboot issue when Inmail is installed, I'd assume they fixed the cutoff issue but I cannot confirm as I don't have any customers that experienced that issue directly.

I've done the 6.03 update to 3 of my InMail cut-off affected systems last week.

So far no phone calls from any of these 3 sites, so it has either helped considerably, or they just can't call out now...

D

Hey Doghart. Still no problems?? We just got R6.01 (your 6.03) for testing here to see if it fixes our problem site..

Spoke too soon. In my lab set the traces running and got it to cutoff 4 times in a row out of 8 calls on ISDN.. :-(

We are seeing InMail issues with 6.03 as well....

Back to the drawing board.

D

In my case back to C5.02. Why NECJ has to be so smart with making the Sig/noise ratio Inmail settings to be a world standard is beyond me. Set it back to what it was in R5.xx and it will work fine again.
Apparently PRG 80.04. Special Busytone For Trunks has nothing to do with trunks but has a lot to do with noise filtering in the InMail..