Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Symposium Failure Rate 1

Status
Not open for further replies.

GSanalyst

Technical User
Sep 8, 2003
7
CA
Does anyone know where I could find any information on Symposium failure rates?
I have found an overwhelming amount of positive information in regards to the system and am curious how often the system goes down, what 3rd party products may cause the downtime (if any), what percentage of companies have had problems with a Symposium roll out and how often are there initial failures upgrading from MAX to Symposium?

Not sure if anyone knows where I could find this information but any reference would help.

Thanks in advance if you can help.
 
Basically, you should follow Nortel's opinions on how to set up Symposium within your company. We had a lot of issues with Symposium because we separated the SCCS server from the voicemail system/PBX and there was an distance issue. we were also connected via short haul modems, which was causing our voicemail ports to go idle instead of stay active and working. Now that we have moved the server and eliminated the distance/points of failures (short haul modems from the server to the voicemail (2) modems) we have had no issues for two months. (knock on wood). But before, we were having to reboot our systems every month. Hope that helps..
 
Hi GS,

We migrated from Max to Symposium Rel 3.0 back in 2001. We had issues especially with networking between sites (we are also using network symposium) However, when we upgraded to Symposium 4.0, we have had very few issues with Symposium. Follow Nortel's recommendations about setting up the network with the ELAN and CLAN as you do not want any network traffic hitting Symposium. That can take you down very quickly. Also make sure you follow Nortel's recommendations when changing CDNs that you deaquire before a change as not following recommendations could cause your PBX to INI.
 
We are running SCCS 4.01.07 and are considering setting up voicemiail so that customers have an option to leave a message if they do not want to wait in queue. This would work such that the system would prompt the caller to "push one (1) to be transfered to voicemail otherwise wait for the next available agent". Has anyone used this configuration before? How does it work?

Thanks,
Lenken
 
This is normally accomplished using the ACCESS link. To do that, you will need package 200 in your Symposium, as well as the ACCESS option in the Meridian Mail, plus there is a hardware setup. Then use OPEN VOICE SESSIONS in your scripts.
Or, you could use GIVE IVR to access menus in your Meridian Mail. It's not as "clean," nor do you have the variety of features offered in ACCESS, but it will do what you are asking.
In either case, though, you will need to use dedicated ports (voicemail ports in a separate queue, that are not used for any other purpose). Check your voicemail to see if you can spare some ports.
 
1. If you use the Voice Prompt Editor you should modify your script like this:

"VM_Section
OPEN VOICE SESSION ACCESS_dn
PLAY PROMPT VOICE SEGMENT menu_vm (this should be a variable directed to the VPE message)
COLLECT 1 DIGITS INTO VM_choice (a variable scope/call; Attribute DN, value 0)
INTER DIGIT TIMER 5
END VOICE SESSION

IF VM_choice = 1 THEN ROUTE CALL VMail (this should be a global ACD variable to your VM)
ELSE WAIT 2
END IF"

The VMBox created in MMail always uses the lead CDN as it's originator, so if the CDN is 7777, the VMbox should be 7777.

2. If you do not use the VPE but normal Meridian Mail then do as followed:
"GIVE IVR VMail (see above) WITH TREATMENT 123456
EXECUTE CONTINUE
CONTINUE
....(rest of the script as usual)"

The 123456 should be created in MMail in the section Voice Services Administration as a Voice Menu Definition.
Option 1 should be routed to the VMail ACD and uses the Prime CDN as originator.
The rest of the options should lead to a new CDN, which should be in your Master_Script, playing the same script as the original one.

The other modification in your script should be:
IF CDN = xxxx (the one you have used to get back from the MMail) THEN EXECUTE CONTINUE.
This would mean that the caller does not hear the same message over and over again...

Supernn
 
Thanks, I'm a new Symposium admin but I think I can work with this.

Lenana
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top