Buckshot

Most times, you can work on something and figure it out, but I dont think this situation would apply. Unfortunately, Symposium is NOT the type of gear you can easily fix a mistake in. If making adds-moves and changes to the users in Symposium is the short term thing, I would strongly suggest you NEVER make a change with a phone that is in symposium by not deaquiring 1st. I was talking to an engineer about Symposium and he told me the correct way to make a change to a phone in symposium, without causing any corruption is as follows:

1. Disable the phone in the PBX
2. Deacquire the set in Symposium
3. Delete the set in Symposium
4. Out the set in the PBX
5. Rebuild the set in the PBX
6. Rebuild the set in Symposium
7. Reaquire the set in Symposium

The most important thing, is to make sure you deaquire before making changes. Corruption in the database might not show up immediately, but when it does, a reboot is definitely in the future. Its been a while since I've been around it, and I think its a great piece of gear (once Nortel got it stabilized), but when it goes down, it goes down hard.

mrmike

Good advice Buckshot

James, go to class or you will lose hair!!!! :laugh: :laugh: :casstet: :casstet:

fonchick

I agree with what has been said so far. I have 3 Symposiums and a Network Symposium I support right now and whenever we call our vendor who has to escalate to Nortel, one of the first things that they question us about is our training especially in scripting. I have gone to class and gotten the certs and I can be the first to attest that Symposium is a very finaky product and I would not recommend trying to learn on your own. Since most likely you are in a call center environment, Symposium is probably something that the company can do without for a few days if it crashes. Therefore, take the safe way and go to training.

I know in the age of budget cuts, training is the first to go. However, if you try to make changes that corrupt software, you may get slapped with a hefty bill from your vendor.

Jamesestes

Thanks for the advice. I don't even have access to the switch at that location, was just wondering. Sound like it is a difficult ACD to learn, sounds like Siemens 9006 ACD, very difficult.
Thanks.

[Edited on 2/14/2003 by Jamesestes]

monkeyboy

Theres an app from Nortel called Symposium Customer Care that simulates Symposium. My copy came from Ameritec.

Panchanka

On the topic of deacquiring, Buckshot stated the following
1. Disable the phone in the PBX
2. Deacquire the set in Symposium
3. Delete the set in Symposium
4. Out the set in the PBX
5. Rebuild the set in the PBX
6. Rebuild the set in Symposium
7. Reaquire the set in Symposium

However, I am running a mixed environment. We are using Symposium Link (similar to M Link) on a Option 81 C 25.40B, however, our CTI provider is Genesys, not Symposium Call Center. Genesys 5.1 acquires the telephone sets, CDNs, queues and just about everything else.

We do not have the ability to deaquire in Genesys. Nortel tells us that Genesys 5.1 is not fully compatible with Option 25.40B. Keeping this in mind, what is the best way to make a change.

I am currently:
1. Disabling the set in the PBX
2. Deacquiring the set in the PBX
(LD 48
dacr agt TN)
3. Out the set and then rebuild it
4. I don't bother reaquiring the set, it works fine at this point, plus genesys reaquires it with their scheduled cycling of the server.

I am wondering if this is a safe procedure, that is, can it corrupt the PBX or the database? Also, besides a reboot of te PBX, what other nasty things can come of it? Is it possible that a corrupt database causes one-way static for either agents or customers?

Any comments, suggestions or snide remarks would be appreciated.

Thanks,

Dan