Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Default Greeting

I'm running CUCM 8.6.2 along with Unity.

When a user presses the Voicemail key (envelope) they are sent to extension 1000.  and then instead of entering PIN, they press the # key, they get an obsolete Welcome message.

We have a new welcome message already prepared and in use elsewhere, but I cannot seem to locate exactly where I need to be to upload the new wave file for this specific case.

 

Sounds easy enough, but I simply can't figure this one out.  Any pointers?

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Use the port status monitor

Use the port status monitor to find that out

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
2 REPLIES
Cisco Employee

Use the port status monitor

Use the port status monitor to find that out

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Went to ciscounitytools.com

Went to ciscounitytools.com and downloaded PSM.  It installed w/ no complaints.  When I attempt to run PSM 2.0.2.4 (As Administrator) on my Win7 64-bit laptop, the instructions vaguely states that I need "to "point it at the Connection server and begin monitoring".  Yeah, whatever. I wasn't prompted to enter a name or IP for a COnnection server like in the videos for previous versions. 

So if I do a System->Add Local System, presumably to instruct PSM "point to my Connection server", I get the wonderful message "Unable to open key HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvLogMgr\1.0\Diagnostic Grid for read."  In looking at my registry, there is no Active Voice Branch under HKLM\SOFTWARE, so something is missing.

I went back and retraced my steps, and wow, the download piece is really confusing.  It appears that I downloaded 2.0.2.4 which isn't as up-to-date as 2.0.0.16. ?!?!

That installed well, and it prompted me for a server.  I entered in the subscriber. I went through the process I wanted to capture which was simply Message button, followed by #, to see what happened.  Here are the results:

11:19:46, New Call, CalledId=1000,  RedirectingId=,  Origin=16,  Reason=1,  CallGuid=F9E813A754E54DB1938C4B52BA4E1885,  CallerName=CSCFitzie_2,  LastRedirectingId=,  LastRedirectingReason=1,  PortDisplayName=CUCM-1-025,[Origin=Unknown],[Reason=Direct]
11:19:46, AttemptSignIn
11:19:46, State - AttemptSignIn.cde!Dummy
11:19:46, Event is [NULL]
11:19:47, SubSignIn
11:19:47, Subscriber Sign-In
11:19:47, State - SubSignIn.cde!AnswerPhone
11:19:47, Event is [TrueEvent]
11:19:47, State - SubSignIn.cde!AuthenticateUser
11:19:47, -->SubAuthenticate
11:19:47,         State - SubAuthenticate.cde!TryCounter
11:19:47,         Event is [NULL]
11:19:47,         State - SubAuthenticate.cde!GatherID
11:19:47,         Event is [FalseEvent]
11:19:47,         State - SubAuthenticate.cde!LoadSubscriberMinimalData
11:19:47,         Event is [NULL]
11:19:47,         State - SubAuthenticate.cde!GatherPIN
11:19:47,         -->SubAuthenticatePW
11:19:47,                 State - SubAuthenticatePW.cde!ValidatePwd
               
11:19:54,                 Event is [TimeoutEvent]
11:19:54,                 State -
11:19:58,                 Event is [TT#Event]
11:19:58,         <--SubAuthenticatePW
11:19:58,         Event is [TT#Event]
11:19:58,         State - SubAuthenticate.cde!RouteToNextConversation
11:19:58,         Event is [NULL]
11:19:58, <--SubAuthenticate
11:19:58, Event is [NULL]
11:19:58, AttemptSignIn
11:19:58, State - AttemptSignIn.cde!Dummy
11:19:58, Event is [NULL]
11:19:58, PHTransfer
11:19:58, State - PHTransfer.cde!LoadInfo
11:19:58, Event is [TrueEvent]
11:19:58, PHGreeting
11:19:58, State - PHGreeting.cde!PlayGreeting
11:19:58, Call answered if needed
11:19:58, Playing greeting for Call Handler:  Opening Greeting
11:20:02, Event is [HangupEvent]
11:20:03, State - PHGreeting.cde!DoHangup
11:20:03, Event is [HangupEvent]
11:20:03, Idle
 

My attempt at analysis is as follows:  @ 11:19:46  I pressed the envelope key, which sent me to ext 1000.  OK, I knew all that beofre I started, but OK.  It asked me for a PIN and I let it time out @ 11:19:54.  I then pressed the # key, which I guess is represented by TT#Event.  OK, so far so good.  TT#Event then goes to play a Call Handler called 'Opening Greeting' at 11:20:02.

Traced that down further, to be the "Standard" greeting.  Problem solved.

88
Views
0
Helpful
2
Replies