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

Unity Connection Greetings

I am trying to understand how the different personal greetings get triggered as i have some users that have a standard greeting and internal greeting as well as a busy greeting.  It doesn't appear that calls are getting anything but the standard greeting?

 

Unity Connection 8.6 using SIP integration

  • Unified Communications Applications
1 REPLY
Hall of Fame Super Red

Hi ther, I tried setting it

Hi there,

 

I tried setting this up for testing a while back; ** Busy/Internal greetings must be enabled on user pages smiley

We are using a SCCP integration between CUCM & CUC

 

Here's what I found for Internal greeting;

 

- system must pass callers CLID

- CLID of caller must be a recognized CUC user

- caller must be part of the same integration so it didn't work for our PIMG

  integrated users calling a CUCM integration user

- Internal Greeting must be recorded & Enabled (had to enable via gui in our case)

 

After those checks it works like a charm

 

For Busy greeting users must be set with a Busy Trigger of 1 in CUCM

 

If this isn't working,I would use this Tool from the great suite of Unity Tools to have a look at the call flow

on a "test" call this may give us a hint as to what's actually happening here

 

Port Status Remote Monitor for Connection (rPSM)

 

http://www.ciscounitytools.com/Applications/CxN/PortStatusMonitorCUC7x/PortStatusMonitorCUC7x.html

 

Cheers!

Rob

 

Please support CSC helps Kiva yes

https://supportforums.cisco.com/blog/12122171/cisco-support-community-helps-kiva

 

"May your heart always be joyful And may your song always be sung May you stay forever young " - Dylan
59
Views
0
Helpful
1
Replies
This widget could not be displayed.