Prompt problem

[Nick8Noodles]

Using a KX-TD1232 with a TVS100.

Hi everyone,

Ok a weird one here . I'm replacing user prompt 371(call transferred from the voice processing system) So la-de-da used selective prompt 165#6*9985611(entered prompt # 371) after I changed it to my own voice. Saved it, tested it... I can hear its scary default voice once more! I tried a couple of other things, but it continues its relentless assault. So I took a break, ate some noodles during lunch and posted this thread.

Nick

 

[skip555]

my experiance is the prompts dont match the numbers in the manual.

nice thing is you can restore prompt 371 back to defualt

what I had to do was go thru and listen to the prompts ,one at a time untill I found the prompt number that corresponded to what I wanted to change .

 

[Nick8Noodles]

I am certain that this number is the correct prompt. Before recording my own prompt, I heard the orig. prompt that corresponds to the number just before I pushed 1 to record.

When my own prompt(with my voice) dident play and the default one did instead I checked it again. Sure enough, when it played just before recording it played the one with my own voice, which only made things more confusing.

This forced me to check the custom service menu settings to make sure that prompt for User1 was selected(which it was) instead of System. See why I dont understand how it's doing this?

 

[cwc3]

double ck i'll bet you have not told the tvs to use user
prompt one instead of system !!

 

[Nick8Noodles]

That was one of the first things I checked, simply because it made sense as to what would cause such a problem. The settings I have configured are correct, user1 is the prompt selected. The prompted in question for user1 is #371 which was rerecorded and yet it seems the default system prompt prevails. I don’t know how this is possible. I went ahead a little further and double checked all custom service just in case it might have been something funny with those as well. All the CSM's have user1 for prompt selected as well. This might be the first sign of artificial intelligence that refuses to simply die in regards to a phone system .

 

[Nick8Noodles]

ok... well... I'm just stunned. I only came across this problem at the end of last week and it hadent been corrected before the weekened. Monday morning... it's gone and seems to have fixed itself. What a wounderful start to another week.