Attendant Console Night Service

[McGruff753]

We have one 2250 console phone here. The DN that points to it is 7000 and is direct to it, no prompting. I am in the process of trying to run 7000 through prompting in the Aspect system to make the main number more automated in hopes of alleviating some types of calls that can be handled by announcements. So I moved 7000 from LDN0 in LD 15 to a DSC in LD 87 and put 7005 as LDN0 in it's place. I also created a Voice Services DN in Meridian Mail for 7005 with the same night announcement 4350 as 7000 has. When I select 0 in the Aspect CCT to connect to the operator, and the 2250 is not on 'night service', it connects to the operator with no problem. When the 2250 is in 'night service', I get a message from Meridian Mail stating 'Your session cannot be continued at this time. Please try again later, goodbye' instead of the system night message. I reversed everything that I did and the system works like it used to prior to my changes. Can you think of what step I missed in this to have the night message play when LDN0 is 7005? Thanks.

Mike

 

[acewarlock]

Did you change the NIT1 in the CDB to the new number?

 

[cmawbey]

LD 22
prt NIT

to change

LD15
NIT_DATA

NIT1 xxxx (night number)
Colin

 

[McGruff753]

LD 22 errored but LD 21 showed the NIT1 as 7979. My voicemail system access DN is 7979 so I didn't think that had to change it.

Mike

 

[acewarlock]

when you dial 7005 on your phone what do you get?

 

[McGruff753]

With the console in night, I get the proper night message. With the console in idle, I get the operator. It's just when the console is in night and I select '0' fron the 7000 CCT in Aspect, Meridian Mail states the 'your session cannot be continued' error message and hangs up.

I have a work around for non-business hours in the CCT itself, but if the operator leaves her station, the night service will not give the normal message. Which, in one sense, may not be a bad thing since the night message gives our hours of operation. So within those hours, if the operator is not there, all we are doing is playing a message to the caller that we should be open and we're not.

The challenge I see is they may want to re-record the night message in Meridian Mail for those instances. I also just found out I am piloting this project for all of our centers once I work out the bugs in this center. Oh, what fun.

Mike

 

[acewarlock]

You should leave the LDN0 to 7000 like it was.
you should prt the CDB to see what the nite number is.
Then change this nite number to a new number that takes it to the Aspect, then the Aspect can send (dial "0&quot to the old nite number to get the original recording before you made the changes.

 

[Reusser]

Look at your revert dn in the night menu - this may need to be changed. Also check the restrictio permission tables to verify revert dn can be dialed

 

[McGruff753]

Reusser,

Where would I check this? I thought I found it in Meridian Mail under voice services DN (Options 3, then 4, then 5) and added 7005 to match 7000. It still gave me the error message.

Mike

 

[McGruff753]

Okay, so maybe this isn't an issue after all, unless someone out there has done something different. Something I didn't try was to dial '0' when the console phone was in night service. I just assumed it would play the night message. I get the same "Your session cannot be continued at this time. Please try again later. Goodbye." Does anyone else have something different on their systems for dialing 0 after hours? Thanks.

Mike

 

[acewarlock]

When someone gets to MM and uses "0" if you don't have "0" defined in MM where it's supposed to go ie: (7005) then you will get the recording because the MM doesn't know what to do.

 

[McGruff753]

You guys ROCK! I finally have it all configured correctly. I needed to define '0' in the voice services DN in MM. Thank you so much for all of your help.

Mike