Nortel Meridian problems

Could we get a copy of that list?

hi everybody

Can i configure a telephone on multi queue with Northel ???

Could me too have a copy of that list?

Thanks in advance

Shashank

First time caller, had the link for a long time. Could you send me a list also.

Can I get a copy of list to please. Thanks

Could I also have a copy of the list of tricks. Many thanks

Can I have a copy of that list,

Thanks

Hi Tony,

Were you able to resolve your problems? We are running into the same problems on a Nortel Meridian 81C with Genesys 6.5. Apparantly there is a DND message that is sometimes not received by Genesys and this causes the loss of sync between the Tserver and Statserver.

It was recommended to us to upgrade from Mlink to MLS. Did you use Mlink at that stage?

Anton

Anton,

Yes still experience same issue. Running 6.5 TServer with MLS link. Heard issues are resolved in 7.0, but still waiting to hear from customers who upgraded and no longer see these issues.

Tony

Can I also have the copy of these tricks please?

Thanks in advance

Hi, you might want to check a Posted messages call “Querying StatServer”,(two page down) there is an idea to temporaly solve your problem, We 've done it with success, it use CCP with threshold.

Good Luck

Dennis

Tony, are you routing to ACDQueues, AgentGroups or PlaceGroups?

If you want to accurately target agents according to the longest wait time using the ExpandGroup function in your stratiges might improve matters.

Please send me a copy of the list if possible.

I’m late to read this forum, please send me copy too ? thanks

Don’t look at agents or anything else until you upgrade to Succession 3.0 or 4.0 and make sure your CDN’s are in CME as Rt. Pt.'s and the stuck call issues will be resolved.

Steve,

We are on a Nortel 81x (Rel 25.40b) using Symposium 4.2 (SU12). We have had significant problems with both hung agents and VTO ports. If I understood your post correctly, Sucession 3.0 or 4.0 would resolve this issue. Could you expand on how Nortel resolved this issue with Succession? We currently run a hybrid 6.5.x / 7.0.x Genesys environment and have not had much success in resloving this issue (even working directly with Nortel Engineers). Your thoughts / comments on a possible resolution would be greatly appreciated.

Thanks!

Mike

Mike,

We are also using an Option 81C and previous to our upgrade on 25.40B software and Symposium 4.2 (since upgraded to Symposium 5.0). We worked every day with the support phone clearing calls from the various call centers. We even had Nortel tell us to AST enable all the DN’s in the building and all the incoming trunks (licensing nightmare). Since we upgraded to Succession 3.0 we rarely see a stuck call (occasionally we will see a ‘call
inging’ from a set that is programmed to hunt and forward by the PBX). We also installed a new site using the latest Nortel software (I think instead of Succession 4.0 it is called Communication Server 1000 Release 4.0) and after 30,000+ calls we have not seen a single ‘stuckcall’. Our VTO would get stuck in consult; inbound, etc. as well and now we never have to monitor it. Tserver options rlsextconsult and the dta’s have to be set correctly. Anyways, if you upgrade the PBX software and use a 7.0 Tserver, I think you will resolve the issues.

If anyone could send the list being discussed , it would be much appreciated

Perhaps you could post the list. Since there are may requests for it.

• I wouldn’t mind either if that’s ok?

regards

Si