V2.1 bug list?

[IPGuru]

IS there a list of current V2.1 bugs?

Just for starters these are the ones I am aware of (thanks to all who have posted them here)

1) Time profiles delayed by 15 min.
2) Hunt Group Overflow not working correctly
3) Incomming call routing can get confused if names contain spaces
4) Default settings for CLI on analog exts are incorrect.

What other bugs are known?

 

[Morrack]

5) Huntgroup Queueing problems - phantom calls & calls queueing against wrong groups.
6) Data hub on 403 & 406 known to lock up
7) CBC cannot display individual agents
8) Assisted Transfer token doesn't work correctly
9) Reporting tab of any token, ticking "Flag call has been answered by voicemail", call does count as answered but ALSO increments lost calls counter in CBC. Not ticking simply increments lost calls and leaves answered calls unchanged.

That's as far as I got before abandoning 2.1 at all my custs and downgrading everyone to 2.0.18 until the maintenance patch comes out. Do you need any more reasons? ;-)

Peter

 

[BearTrap3]

Is anyone aware of the latest timeframe for the patch's availability?

Fred

 

[IPGuru]

last date we heard was wednesday, but who can tell?

Chears Peter I new you would have a few more.
Keep em comming so we can check they dont reappear in 3.0

 

[MTVilla]

I had a hunt group switch from "In Service" to "night Service" overnight with no user input at all. I am the only one with access so I know it wasn't someone else changing that. We use a condition in VM Pro for

I also lost my point to point connection with the Philly 406 and now have "Master CLK Fail" on my Paradyne 3160 CSU/DSU here.

Lovely day isn't it?

 

[Francis999]

VMPro 2.1.10 should be released by the end of the week which should fix the assisted transfer issue. Pretty bad issue I can say!

 

[NuggiFirst]

I'm actually shocked that a bug like that can be released! I have wasted so much time on this issue...

Looks like the "Assisted transfer" and "Route by Call status" could get an extra result in 3.1. I may finally have convinced an Avaya-guy that we need a DND-result ;-)

If someone else could request this feature, it could maybe speed things up a little!

 

[Telecomboy]

I have a customer that just called with the following issue after upgrading to 2.1. They are having an issue with their "call waiting on" feature being turned off occasionally so they can only field (1) call at a time.

 

[kristiandg]

Here's one thats killing us. I've got the IPO acting like a definity as best as possible (as far as the end-user can tell). I spent a lot of time programming it in such a way that we effectively have COR's, COS's, ARS, AAR, etc. I've now got a "default database" that has these settings so when we arrive on-site to do the install, we just have to fine tune it for their needs.

The problem we have is:
When you are prompted for an Auth Code and the primary route in LCR is down, the call can't be completed. If you disable the FORCE AUTH CODE, then the call jumps to the alternate routes.

I've got an open ticket on this one... Hopefully the maintenance release will fix it.

Kris