Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: dmoore7648 on November 08, 2007, 08:04:09 PM
-
We are upgrading our Avaya to Communications Manager 4.1 and replacing our Map-D with the AES Server. Does anyone know if I will need to get a new Tserver version or template. We are currently using Template TServer_Deffinity_702 and TServer version 7.0.206.01.
Thanks!
-
I think the issue is more the Communication manager version rather than AES vs MAPD.
If I recall correctly I think Genesys has stated they have only certified 7.5 with CM 4.1
We had some problems with 7.5 and had to back that out -- and are still running a 7.2 T-Server -- but we upgraded Avaya..
-
T-Server 7.2 is a must for CM 4.1 - we had quite a few problems with 7.0 and 7.1 running with AES.
I am a strong proponent of upgrading to the latest version of T-Server, so I would go all the way to the latest 7.5 after doing few nights of testing.
It is amazing the jump in performance once you upgrade from AES to MAPD. We used to have a CONJ ERROR (too many events for MAPD to process) which would lead to anywhere from 1 second to 10 second event delays, but once we have upgraded to AES, I am told we can ten fold our current traffic and still be within the operating limits. Make sure you get the latest patches for your AES, since there were a few buggy releases that would crash CRV :)
Best regards,
Vic
-
Avaya Communication Manager 4.0 is supported only from Tserver 7.5.009.00 (second 7.5 GA). I totally advise against upgrading to 7.5 since it's a kick in the neck release full of bugs; we currently have 2 ERs for 7.5 Avaya Tserver for Solaris, one for a contemporary core dump of two Tservers in primary/backup pair, one for Tserver trying to release each call when 30 secs have passed since its EventEstablished. None of them is included in the last released hot fix.
Moreover 7.6 is being released, Framework has already been, so I'd wait for Tserver.
Fra
-
OffTopic: Very funny avatar lol
-
O_O actually I have not choosen it..!!!
[i][size=8pt]Added by Vic:
Sorry, I thought it would break the monotony of posts all text post. Please change it if you don't like it. You have to admit - it is cute though. :)[/size][/i]
[i][size=8pt]Added by Fra
Vic, it's pretty fun, no problemt at all, I was just wondering how that avatar had been appeared :)))
-
Well well well... this is what I heard... Genesys developed 7.5 TServer from scratch - so watch out for all those bugs and still waiting in queue at Genesys to get them fixed one by one.
Better go to 7.2 version and when 7.5 is stable in 2 - 3 yrs may be - u can upgrade to it if necessary...
-
We do not have T/S 7.5 running anywhere yet, but I was strongly pushing for upgrade. Obviously, after this post, I will need to re-think my plans. As for CM4.0 - it is running fine with T/S 7.2. No problems that I am aware of yet.
And why exactly did Genesys decide to rebuild T/S from scratch for 7.5? Haven't they learned from a huge RN they got from 5.1? Finally, just when things got stable and we can slowly relax and not spend sleepless nights testing the bejezus (is it how you spell it?) out of the system, Genesys does a 360 (yes, a full turn-around) and resets 7 years worth of work.
Speaking of quality control, is it me, or did Genesys quality control went down the drain since 7.2? I think we should demand Genesys either to stop giving us such buggy applications (don't even get me started on their SIP T/Server) or start paying us for doing their job. I heard that some of development was outsourced to some Ukrainian company and I wlecome the move. I just hope there is no correlation between the move and the number of bugs we have seen in the latest version. (E.g. Stream Manager would unexpectedly crash if user would press a digit during treatment in 7.2 - are you kidding me? Since SM is used for treatment, something this obvious should be noticed BEFORE the product was released...) I feel like it is Campaign Manager 5.1.x all over again...
Vic