Meridian option 81C/ Genesys 6.0 CTIlink confusion

[Ramesh Pitchumani]

Hi All:

We are working on a project with Meridian option 81C, release 24, Genesys 6.0. I see a lot of conflicting reports on the Link being used. Some people say MLink and others refer to Symposium Link and some others to SCCS. I am not very clear on which CTILink would be available in the long un and supported by Nortel. As far as my knowledge goes, I didnt find any confusion with Aspect because it had the Application Bridge as the CTIlink. In the case of Lucent, I have used ASAILink. But I really get confused with the CTILinks available for Meridian 1.
Any help on this issue would be greatly appreciated.
Thanks,
Ramesh.

[Vic]

Ramesh,

here are the facts:

Nortel has two types of CTI links:
SCCS and MLink.

MLink was discontinued and is no longer in production, thus leaving us with only SCCS.

When people refer to Symposium Link, they are talking about a module inside SCCS which is a standalone server that is connected between PBX and the network.

You can find the pbx versions supported in the document titled "G6 PBX supported switches". Drop me an email if you have a question.

MLink 5C (The latest version of now discontinued MLink) is supported by Rls23 through Rls 25 in G6

Symposium Link 6.0.1 that comes with SCCS 1.5 and 3.0 is supported from Rls23 through 25 in G6

Symposium Link 6.0.2 that comes with SCCS 4.0 is supported in G6.1 even though it will run in G6.0. It also says that you will need Rls24 or 25 to be in a "supported" environment

So, to summarize it MLink was phased out and replaced by SCCS.
It is supported by Genesys and Nortel; however, MLink is no longer in production even though I would recommend MLink over SCCS any day.

Did it clear it up?
Vic

[Ramesh Pitchumani]

Hi Vic:

Your reply was so helpful in clearing my doubts..
Thank you very much.
Ramesh.

[Joel]

Vic, why do you prefer MLink over SCCS? If you have a few minutes you can email me. Thanks!
Joel
joeldup@hotmail.com

[Ed]

Just a note under SCCS4 ( Symposium Call Center Server for Win NT only) the link is provided by a NT service know as MLSM ( Meridian Link services Manager? ) this is supposed to provide services equal to the old Meridian Link 5C ( formally a mini unix processor on a card on the switch very stable ). Prior to SCCS4 SCCS3 provided Symposium Link Services ( could be purchased seperate of SCCS which is no longer true for SCCS4 ). A good reason why the old Meridian Link was superior is due to the way SCCS was written, it is not very stable and easily corrupted, not something you want in call processing. I will say that SCCS works fairly well if used as is without deviating too far into custom services.
Hope this helps

[Victor]

In May 2001 we received following message from Nortel stating that they are withdrawing Symposium Link from the market. Perhaps it is only for EMEA, I am not sure. Apparently they have released SL 6.0.2 after this message (?)

EMEA Announces Meridian Link Services (MLS) 4.0

Nortel Networks is pleased to announce Meridian Link Services (MLS) 4.0, the latest Meridian Link product, designed to provide both increased callhandling capacity as well as call control compatibility with Meridian Link 5C. Meridian Link Services 4.0 replaces Meridian Link and Symposium Link 6.01 for new sales.
In May 2000, Nortel Networks announced the retirement of the Meridian Link Application and IPE Modules due to the end of life of some of the hardware components. Symposium Link 6.01 was offered on a controlled release basis as a replacement for Meridian Link functionality. Meridian Link Services (MLS) 4.0 supersedes Symposium Link 6.01 and offers increased capacity as well as new functionality that closely matches Meridian Link Release 5C. Because MLS 4.0 has a richer feature offering, Nortel Networks recommends MLS 4.0 for new sales and is withdrawing Symposium Link 6.01 from the market.
Meridian Link Services 4.0 is embedded in Symposium Call Center Server 4.0 which has been Generally Available in EMEA since February 2001. The MLS module is automatically provisioned when ordering SCCS 4.0 with one agent increment. SCCS 4.0 can be ordered using NetPrice Version 2.2.2 or later.
Because Symposium Link 6.01 is based on Symposium Call Center Server 1.5, Nortel Networks will continue to provide support for Symposium Link 6.01 in line with SCCS 1.5. Retirement of 6.01 will follow the same dates for SCCS R1.5. For further details, please refer to the relevant EMEA Retirement Bulletin for SCCS Release 1.5 for your region.

[gabriel Taliga]

The problem is with integration of IVR Periphonics to Genesys. We have
installed IVR driver into Periphonics and Iserver. The comunication
between Iserver and driver is established. There is problem with
association DN to IVR port in CME. The IVR (behind switch) is connected
to PBX via DPNSS link. The access number (ACOD) is used to call IVR
route on PBX Meridian ( Symposium link) . The B channel is selected by
PBX. The questin is how to configure association DN if the Meridian has
ACOD and no DN suitable for registration in Tserver? We need to know
what is necessery to setup or change in Meridian. Im responsible for integrating Genesys but we don't know the Meridian. It will be nice to have more information about PBX.
Technical data:
IVR: Periphonics 2x VPS/is2 Model 9500E Response System 240 Volt,
PABX : Nortel Meriadian 1, Option 81 C, rel. 25.15.
Symposium Link 6.0.2, SMLS 4.2/SCCS 4.2.
OS: UNIX 2.6
IVR Driver for Periphonics 5.3.1.

Problem:

IVRPABX use 8 x E1 DPNSS protocol, it is working.
PABXGenesys use Symposium Link 6.0.2, SMLS 4.2/SCCS 4.2, it is working.
IVRGenesys use Driver for Periphonics, it is working.
We are not able to register DN.
G.T.