-
1
- #1
Hi there!
We needed to upgrade one of our 81C from CP4 to CPPII, for capacity reasons, and Nortel forced us to migrate from Rls 25.40 to Succession 3.0. As a result they said we needed to change Meridian MAX SNN8.71 for SCCS
We are using Genesys 6.5 (migrating to 7 soon) for part of our call center.
To clarify, I want to show the schema:
elan clan LAN |
81C---+--SCCS-----Tserver----|
We feel our distributor isn't being very helpful because of lack of expertise.
Now we have a lot of questions:
1. Could we still use MMAX 8.71 in succession 3.0? Just for speeding up the CPU upgrade.
2. Is our schema correct or there is a better way to set it up? At the beginning we connected SCCS directly to corporate LAN and it didn't work.
3. How could we set the supervisors' access to SCCS if it's in a different LAN? We read about Symposium web client but I suppose it only works in the same LAN, because I read something regarding IP Multicast. By the way, why are the hardware specs for this server so high?
Thanks in advance,
Jaime G.
We needed to upgrade one of our 81C from CP4 to CPPII, for capacity reasons, and Nortel forced us to migrate from Rls 25.40 to Succession 3.0. As a result they said we needed to change Meridian MAX SNN8.71 for SCCS
We are using Genesys 6.5 (migrating to 7 soon) for part of our call center.
To clarify, I want to show the schema:
elan clan LAN |
81C---+--SCCS-----Tserver----|
We feel our distributor isn't being very helpful because of lack of expertise.
Now we have a lot of questions:
1. Could we still use MMAX 8.71 in succession 3.0? Just for speeding up the CPU upgrade.
2. Is our schema correct or there is a better way to set it up? At the beginning we connected SCCS directly to corporate LAN and it didn't work.
3. How could we set the supervisors' access to SCCS if it's in a different LAN? We read about Symposium web client but I suppose it only works in the same LAN, because I read something regarding IP Multicast. By the way, why are the hardware specs for this server so high?
Thanks in advance,
Jaime G.