Unity Connection transferring calls to CUCM

I have posted here before, continuing my learning in my lab.
CUCM 9 and CUC 9. 4 IP Phones registered and all have mailboxes. I have a System Call Handler configured to answer calls coming from a CTI Route Point.
I have been playing with a scenario trying to learn all the capabilities of the various call handlers.
Im currently trying to allow the caller to transfer to a phone number that is registered in CUCM - but does NOT have a mailbox.
My CUC Configuration
     Call Handler Basics
          Callers Hear -> My Personal Recording
          During Greeting -> Allow Transfers to Numbers Not Associate with Users or Call Handlers
          After Greeting -> Conversation -> Caller System Transfer
     System Settings -> Restriction Tables
          Default Transfer
               I added a new entry and specifically entered the DN that I was trying to transfer to (123)
               I unchecked the "blocked" for all entries
     Call Management -> Call Routing -> Forwarded Routing Rules
               Attempt Forward Routing Rule -> Send Call to -> Conversation -> Attempt Forward
From an IP Phone, I dial the CTI RP and get forwarded to the main / opening call handler. I traverse a couple of menu tree levels to get to my call handler where I am attempting to transfer back to CUCM. I hear my recorded personal greeting instructing me to enter my number. Whether I wait for the recording to end or whether I enter the digits during the greeting, the results are the same. The result is that nothing happens. No recorded message telling me that I cant be transferred to that number - nothing at all. The call just terminates.
I started up Connection Remote Port Status monitor and I can watch the sequence of the call. When I enter the digits of the target phone (123), I see in the Remote Port Status Monitor that it sees and receives the DTMF digits, but then nothing happens.
I next tested by adding a test user in CUC with the same DN of 123. As soon as I did that, I repeated the attempted call and when I dialed "123", I get the recorded message "Wait while I transfer that call" and then the call completes successfully.
This is my home lab so I can make any changes that you suggest with no user implications.
Jeff

Hi Jeff,
That is weird! It is still shown in this 9.x doc
Overview of Default Restriction Tables in Cisco Unity
Connection 9.x
Default Fax
Restricts numbers for fax delivery.
Default Outdial
Restricts numbers for message notifications
Default System Transfer
Restricts numbers that can be used for
Caller system transfers, which allow
unidentified callers to transfer to a
number that they specify. For example,
callers may want to dial a lobby or conference room phone that is not
associated with a Connection user. By default, the table does not allow
Connection to dial any numbers.
Default Transfer
Restricts numbers for call transfers.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx/9xcucsag110.pdf
Cheers!
Rob
"May your heart always be joyful
And may your song always be sung
May you stay forever young "
- Dylan

Similar Messages

Unity Connection Transfer calls across ICT

I am working on a system where they have a unity connection 8.6(2) server that has a system call handler configured for external voice mail access. They would like to be able to have the users call in and enter the extensions of users on a remore CUCM cluster and be routed across the Inter Cluster trunk to the remote cluster. I have the system setup to allow the caller to enter the extension of users not associated with a mailbox and I have configured the transfer rules to allow the pattern defined for the extensions. However it still fails.
Any help would be greatly appreciated.
Thanks,
Michael

Michael,
Ensure the CSS assigned of the SIP trunk (if using UCXN SIP integration) or voicemail ports (if using SCCP) has access to a partition that the route pattern pointing to remote cluster is assigned to.
HTH,
Chris

Unity Connections remote call sign-in issue.

I have some users that when they dial there DID from outside they hit there VM press star and are prompted for their sign-in number and pin. Then I have some users that do the same thing, but the greeting just continues to play. I am sure there is a simple fix to this, but I cannot seem to find it. Hoping someone out here can lead me in the correct direction.
I am running Unity Connection 8.6.2.
Thanks in advance,
Dave

Hi Dave,
I would check the following on a "working" vs "non-working" user;
User> Edit> Caller Input> * (star)> send to Sign-in
Cheers!
Rob
Please support CSC helps Kiva
https://supportforums.cisco.com/blog/12122171/cisco-support-community-helps-kiva

Unity Connection 8.6 call transfer to non-unity extension

I have converted from Unity to Unity Connection and am looking for a solution for transferring an incoming call to a non-unity user extension.
Here is the scenario: An PSTN caller calls in and is directed to a Unity Connection Call Handler or a Subscriber greeting. In the greeting they are advised that if they know the extension they want to call, they can dial it at any time. Here is the rub, if they dial an extension for a user listed in Unity Connection, the call gets transferred to the extension. However, if the extension dialed is to an extension that is not a Unity Connection User, the attendant comes back and say the extension is not understood.
In Unity before conversion, I would make an internet user that did not have a mailbox but was listed with an extension. However, with Unity Connection, I am using LDAP integration with Microsoft AD and I don't see a method of doing the same thing.
Is anyone else doing something like this or know of a method to do it?
Thanks in advance.
Gene Keel

In the greeting check this box:
Allow Transfers to Numbers Not Associated with Users or Call Handlers
also make sure the number entered by the call is allowed in Default System Transfer restriction table.

Unity Connection 9.1 - Call back feature

Hello,
Is there a feature that would allow a user to callback the caller from the voice message itself.
For example Calling number 123-123-1234 calls extension 2000 and leaves a voice message. When user with ext 2000 listens to the message from 123-123-1234, can they press a button that would automatically call 123-123-1234.
If anyone can point me to some documentation that would allow this, that would be great ! !
Thanks,
AK

Duplicate
https://supportforums.cisco.com/discussion/12264381/unity-connection-91-call-back-feature

Unity Connection Voice Mail Issue

Hi,
I have a weird Unity Connection Voice Mail issue and would appriciate any help i can get. Many thanks in advance.
I have Unity connection 7.0 and CUCM 7.0 integrated in a lab enviroment and here is what happens.
When I place a call internally say from 2001 to 2002, things work as expected, 2002 rings and it goes to voicemail where I can leave voicemail and listen to it from 2002.
However, if I place call from the PSTN to the same number 2002 (or any other number in other sites etc) the call again rings in 2002 and goes to voicemail, unity cnx plays the greetings for 2002 and says record your message as usual. Everything up to point is fine, then when the time on the PSTN phone is showing around 14 seconds into the call unity starts playing, "to send this message press one", if I press one nothing happens.
I have rebuilt unity and cucm, even just configured the bare minimum in the lab and still getting the same result. I tried calling from E1 connection and T1 connection but with the same results.
I have run out of ideas...
===============================
Here is a call trace from an internal call:
CallData, 1, CallerId=2003, CalledId=2002, RedirectingId=2002, Origin=16, Reason=4, CallGuid=8B7859FD6C16417A9A07F507418DD25B, CallerName=, LastRedirectingId=2002, LastRedirectingReason=4, PortDisplayName=PhoneSystem-1-001
Application, 1, 2003, AttemptForward
State, 1, 2003, State - AttemptForward.cde!Dummy
State, 1, 2003, Event is [NULL]
Application, 1, 2003, PHTransfer
State, 1, 2003, State - PHTransfer.cde!LoadInfo
State, 1, 2003, Event is [TrueEvent]
Application, 1, 2003, PHGreeting
State, 1, 2003, State - PHGreeting.cde!PlayGreeting
Display, 1, 2003, Call answered if needed
Display, 1, 2003, Playing greeting for Subscriber: hq2
Display, 1, 2003, No DTMF received
Display, 1, 2003, Playing greeting for Subscriber: hq2
State, 1, 2003, Event is [RecordMsgEvent]
State, 1, 2003, State - PHGreeting.cde!RecordMsg
State, 1, 2003, Event is [NULL]
State, 1, 2003, State - PHGreeting.cde!RunEditMsg
Application, 1, 2003, -->MessageEditing
State, 1, 2003, State - MessageEditing.cde!CheckMsgMenuOpt
State, 1, 2003, Event is [EditMessageMenuEvent]
State, 1, 2003, State - MessageEditing.cde!PlayEditMenu
State, 1, 2003, Event is [HangupEvent]
State, 1, 2003, State - MessageEditing.cde!CheckMsgLength
State, 1, 2003, Event is [ManyEvent]
State, 1, 2003, State - MessageEditing.cde!SendMsg
State, 1, 2003, Event is [TrueEvent]
State, 1, 2003, State - MessageEditing.cde!ConfirmSend
State, 1, 2003, Event is [HangupEvent]
Application, 1, 2003, <--MessageEditing
State, 1, 2003, Event is [HangupEvent]
Display, 1, 2003, Idle
Display, 1, , Dialing (MWI) '2002'
Display, 1, , Idle
and here is a trace from an external (PSTN) call
Trying 142.100.64.13, 5000 ... Open
CallData, 1, CallerId=911, CalledId=2002, RedirectingId=2002, Origin=16, Reason=4, CallGuid=CA3DFD90846C4FE7B0D68298A7698287, CallerName=PSTN Emergency, LastRedirectingId=2002, LastRedirectingReason=4, PortDisplayName=PhoneSystem-1-001
Application, 1, 911, AttemptForward
State, 1, 911, State - AttemptForward.cde!Dummy
State, 1, 911, Event is [NULL]
Application, 1, 911, PHTransfer
State, 1, 911, State - PHTransfer.cde!LoadInfo
State, 1, 911, Event is [TrueEvent]
Application, 1, 911, PHGreeting
State, 1, 911, State - PHGreeting.cde!PlayGreeting
Display, 1, 911, Call answered if needed
Display, 1, 911, Playing greeting for Subscriber: hq2
Display, 1, 911, No DTMF received
Display, 1, 911, Playing greeting for Subscriber: hq2
State, 1, 911, Event is [RecordMsgEvent]
State, 1, 911, State - PHGreeting.cde!RecordMsg
State, 1, 911, Event is [NULL]
State, 1, 911, State - PHGreeting.cde!RunEditMsg
Application, 1, 911, -->MessageEditing
State, 1, 911, State - MessageEditing.cde!CheckMsgMenuOpt
State, 1, 911, Event is [EditMessageMenuEvent]
State, 1, 911, State - MessageEditing.cde!PlayEditMenu
State, 1, 911, Event is [HangupEvent]
State, 1, 911, State - MessageEditing.cde!CheckMsgLength
State, 1, 911, Event is [NULL]
Application, 1, 911, <--MessageEditing
State, 1, 911, Event is [NULL]
State, 1, 911, State - PHGreeting.cde!AfterMsg
State, 1, 911, Event is [NULL]
Display, 1, 911, Idle

Sounds like one way audio from PSTN to your Unity Connection, couple of things to check:
1. ensure your protocols are bound properly on the GW, i.e. SIP/H323/MGCP
2. Make sure IP routing is OK between Unity and the voice gateway
HTH,
Chris

Unity Connection 8.5 Outcall notification to device too agressive?

I’ve noticed the Unity Connection 8.5 outcall notification is too aggressive. Is there a way to change the outcall parameters to wait x minutes between redials?
For example Connection called my cell phone, while I am inputting my PIN I get a second call from Connection alerting me to new messages. While I’m listening to the messages I get a third call from Connection. I noticed same problem if device is my desk 7962 phone.
Unity Connection 8x Administration Guide
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagpdf.pdf

Hi Jason,
These timers can be changed via the User or User Template pages
User Templates New Notification Device
Revised November 16, 2010
Table 3-21 User Template New Notification Device Page
Field Description
Notification Device Type
Select a type of notification device from the list.
Display Name
Enter a descriptive name for the notification device.
Phone Number
(Applicable only to phone and pager notification devices.) Enter the phone number, including trunk access code, of the selected device. Use digits 0 through 9 and the following dialing characters in the phone number:
•, (comma) to insert a one-second pause.
•# and * to correspond to the # and * keys on the phone.
Users can change this number by phone.
Extra Digits
(Applicable only to phone and pager notification devices.) Enter any extra digits that Cisco Unity Connection dials after the phone number. The effect of the extra digits depends on the selected device. For pagers, the extra digits are shown on the pager display.
For example, the extra digits could be used to include a callback number when sending notifications to numeric pager devices. Extra digits can also be used to reach an extension, where the notification is configured to dial a public 800 access number and the extra digits would be sent at the opening greeting in order to reach the target extension.
Duration to Wait Before Dialing Extra Digits
(Applicable only to phone and pager notification devices.) Cisco Unity Connection can wait a specified number of seconds before dialing the digits in Extra Digits. Use this option if the automatic call progress detection is not reliable (for example, when phone lines are noisy or when ringing patterns are unusual).
Rings to Wait
(Applicable only to phone and pager notification devices.) Enter the number of times that Cisco Unity Connection allows the user phone to ring before ending the attempt. The setting must be at least 3 rings. Enter a higher number to give a user more time to get to the phone.
Default setting: 4 rings.
Busy Retry Limit
(Applicable only to phone and pager notification devices.) Indicates the number of times that Cisco Unity Connection tries to reach a user number that is busy. Select a higher number to reach someone who uses the phone frequently.
Default setting: 4 times.
Busy Retry Interval
(Applicable only to phone and pager notification devices.) Indicates the number of minutes that Cisco Unity Connection waits between attempts to reach a user number that is busy. Select a higher number to reach someone who has long phone conversations.
Default setting: 5 minutes.
RNA Retry Limit
(Applicable only to phone and pager notification devices.) Indicates the number of times that Cisco Unity Connection tries to reach a user who does not answer the phone. Select a higher number to reach someone who steps away from the phone briefly. Select a lower number to avoid disturbing others.
Default setting: 4 times.
RNA Retry Interval
(Applicable only to phone and pager notification devices.) Indicates the number of minutes that Cisco Unity Connection waits between attempts to reach a user who does not answer the phone. Select a higher number to reach a user who is away from the phone for long periods of time.
Default setting: 15 minutes.
Retries After Successful Attempt
(Applicable only to pager notification devices.) Indicates the number of times that Cisco Unity Connection calls the pager device after the first successful call to the device while the message that triggered the notification is still marked new. Use this setting in conjunction with the Retry Interval After Successful Attempt setting if users need additional reminders of new messages, or if users sometimes do not receive notifications even though the first call to the pager is successful.
If set to a value greater than 0 (zero), Connection makes periodic calls based on the Retry Interval After Successful Attempt until the user checks the message or the retry limit is reached. For example, if Retries After Successful Attempt is set to 2 and Retry Interval After Successful Attempt is set to 15, and the user receives a new message at noon, Connection will call the pager device at noon. If that call is answered, but the user does not check the message before 12:15 pm, Connection calls the pager device again at 12:15 pm. If the user does not check the message before 12:30 pm, Connection calls the pager device a second time at 12:30 pm.
Note This setting generates a series of notifications that is separate from the series that is generated if you enable the Repeat Notification If There Are Still New Messages setting on the Edit Notification Device page. To avoid confusing the user with multiple repeating notifications, we recommend that you use either the Retries After Successful Attempt setting or the Repeat Notification If There Are Still New Messages setting, but not both.
Enter a value between 0 and 100. A value of 0 (zero) means that Connection does not retry the notification after the first successful call to the pager.
Default setting: 0.
Retry Interval After Successful Attempt
(Applicable only to pager notification devices.) Indicates the interval at which Cisco Unity Connection retries calling the pager device after the first successful call to the device if Retries After Successful Attempt is set to a value greater than 0 (zero) and the user has not yet checked the message. Use this setting in conjunction with the Retries After Successful Attempt setting if users need additional reminders of new messages, or if users sometimes do not receive notifications even though the first call to the pager is successful.
Enter a value between 0 and 100 minutes. A value of 0 (zero) means that Connection makes additional retries as soon as a port is available to dial the device.
Default setting: 1 minute.
Phone System
(Applicable to phone and pager notification devices only.) Select the phone system that the notification device uses.
Prompt for User ID on Notifications
(Applicable only to phone notification devices.) Indicate whether Cisco Unity Connection should prompt the user to enter a user ID. The user is always asked for a PIN. Users may prefer not to enter a user ID in order to shorten the time that it takes to sign in.
Note Use this setting with caution and only if the phone is never answered by anyone other than the user.
SMPP Provider
(Applicable only to SMS notification devices.) Select the applicable SMPP provider.
To
(Applicable only to SMTP and SMS notification devices.) Depending on whether you are setting up message notification for a text-compatible mobile phone or pager, or for SMS (SMPP) devices:
•For SMTP text message notifications, enter the email address of the user text pager, text-compatible mobile phone, or another email account (such as a home email address).
•For SMS (SMPP) text message notifications, enter the phone number of the SMS-compatible device. The format and the number that you enter depends on the SMPP Provider. The provider may require that you include international country codes, beginning with a plus sign and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234). Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.
Up to 128 characters can be entered in this field.
From
(Applicable only to SMTP and SMS notification devices.) For text-compatible mobile phones or pagers, enter the phone number that the user calls to check messages, or enter alphanumeric text (as applicable) in this field. The From phone number appears in the last line of any SMTP notification. A user can press the Return Call button on many text-compatible mobile phones to dial the phone number. The mobile phone must support automatic callback in order to use this feature.
For SMS (SMPP) devices, what you enter in this field depends on the SMPP Provider:
•If the SMPP Provider requires a "source address" for the server sending the message, enter the IP address for the Cisco Unity Connection server.
•If the SMPP Provider does not require a "source address," enter the number that the user calls to check messages. The format and the number that you enter depends on the SMPP Provider. The provider may require that you include international country codes, beginning with a plus sign and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234). Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.
Note Consider that some SMPP Providers replace the number that you enter in the From field with their own phone number. For an alternative method of including a call back number, try entering the number that the user calls to check messages in the Message Text field.
Up to 40 characters can be entered in this field.
Message Header
(Applicable only to SMTP notification devices.) Enter any text you want Connection to put into the header of the notification message. For example, you might enter a legal disclaimer that you want to be sent with every notification message.
Message Text
(Applicable only to SMTP and SMS notification devices.) Enter the text message that the user wants to receive in a text notification. For example, you might enter "Urgent message for Technical Support" for a user who is on call for the technical support department. Every time a message arrives that matches the criteria selected in the message notification settings, Cisco Unity Connection sends the text you enter here.
Note To include a call back number, try entering the number that the user calls to check messages within the message text (for example, enter the number in this format: tel:2065551212).
Up to 160 characters can be entered in this field. (For SMS devices, depending on the character set you configure Connection to use, it is possible that messages that are shorter than 160 characters may be truncated.)
Message Footer
(Applicable only to SMTP notification devices.) Enter any text you want Connection to put into the footer of the notification message. For example, you might enter a legal disclaimer that you want to be sent with every notification message.
Include Message Information in Message Text
(Applicable only to SMTP and SMS notification devices.) Check this check box to include information about the new message in the text string that is sent to the notification device. This information can include caller name and caller ID (if available); the type of message (voice, email, fax); the time that the message was received; and, if the message was marked private or urgent, an indication of this status.
Include Message Count in Message Text
(Applicable only to SMTP and SMS notification devices.) Check this check box if you want the notification to include a count of the number of new messages in the mailbox.
Include a Link to Cisco PCA in Message Text
(Applicable only to SMTP notification devices.) Check this check box to include a link to the Cisco Personal Communications Assistant in the text string that is sent to the SMTP notification device.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/gui_reference/guide/8xcucgrg030.html#wp1082329
Cheers!
Rob

Issue with transferring calls to VM for the correct DN Unity Connection 9.1.2

Hi all
I have been facing an issue with a Unity Connection Server v9.1.2. Every time an internal extension (assigned to VM profile and to Unity as a user) which is configured to be transferred to VM after 20 sec or so NoAN,is called , Unity treats the call as the extension of the calling party and not the called party. Furthermore , I dont know if this has any relation with the problem I am facing but when I check the voicemail port status in RTMT its seems like that regardless it is a direct call to the Unity from an extension (dial the pilot number or press the messages button on the IP phone) or a redirected call from an extension to Unity due to NoAN configuration, the Reason is Direct and the caller party number is always the extension initiated the call and not the one redirected to the Unity (second case).
I have changed the Use Last (Rather than First) Redirecting Number for Routing Incoming Call Unity parameter in the
System Settings > Advanced >Conversations -> checked and
Redirecting Diversion Header Delivery - Outbound CUCM parameter ->checked
in the SIP Trunk configuration used for the integraton of the CUCM with Unity but none of those seem to address this issue. Is there any guidelines you can give me to overcome this issue?
The servers I am using are
CUCM v9.1.2 BE
CUC v9.1.2 BE
Thank You in Advance

Hello again,
The Voice Mail Box Mask was blank before. However I tried XXXX (I use 4-digit extension for the VM pilot) but this did not seem to fix anything to the system....Same situation as before. Any more suggestions?
Thank you

Unity Connection - Certificate from cucm no more trusted for encrypted calls after upgrade to 10.5(1)

Hello Support Community,
i have a strange problem:
after upgrading my cucm and unity connection from 9.1 to 10.5(1) enctrypted calls are no more working.
situation 1: CUCM is down, Subscriber is up: Encrypted call to Unity Connection work correctly
situation 2: CUCM is up: Encrypted Calls to Unity Connection not working.
i get the following Info in the log for the Connection Conversion Manager:
19:35:21.053 |15865,,,MiuGeneral,25,Invalid Certificate: Received Certificate -----BEGIN CERTIFICATE-----
MIID8zCCAtugAwIBAgIQc/fBdUz1Zdh4CXhcPqGVuDANBgkqhkiG9w0BAQsFADBw
MQswCQYDVQQGEwJERTELMAkGA1UEChMCSVQxGzAZBgNVBAsTEkhlbGxnYXRlIFRl
XD0oD9d5MQ==
-----END CERTIFICATE-----
doesn't match with stored Certificate: -----BEGIN CERTIFICATE-----
MIIC2DCCAkGgAwIBAgIIJWCm4bSdt+kwDQYJKoZIhvcNAQEFBQAw
-----END CERTIFICATE-----
so where does Unity Connection cache this certificate and how can i delete/replace it?
the cert shown in the logs is the one from cucm: ("CallManager"), i recreated it through cucm os administration, now i see the same error message on unity connection for the new recreated certificate.

Actually It doesn't. It says he's on a MacBook. I don't know all the different types of Macs. I was having a ton of problems with iChat. I opened DMZ to my computer, knocked down all firewalls etc and left everything exposed, still with bad results. A few weeks ago my power supply went out on my D-Link. I bought a linksys. Since I'd left all firewalls off I figured it couldn't be the router. I power cycled everything n the netork, still no luck. Today I bought a universal Power supply and started up my D-Link Router. Everything worked perfectly. My wifes computer - a laptop running Tiger worked fine with the Linksys and did my machine before the Leopard upgrade. Now that I've got the D-Link online everythings working.
Message was edited by: graphico
Message was edited by: graphico

Unity Connection 8.5 - No Diversion Header information in transfered call

We are having call failures when calls are transfered to our SIP provider from Unity Connection (AutoAttendent). We have tracked this down to Unity is sending a Refer that does not have any information regarding the number the call was transfered from. Subsequently Callmanager does not create a diversion header in the invite to the SIP provider.
The SIP provider require either a authorized number in the from header or a the same in the diversion header.
We have the rediversion headers enabled on the callmanager side of the trunk.
Does anyone have end to end SIP configuration with UCM 8.5 and Unity Connection 8.5 and can complete transfers back to the provider?
mike

I don't see any problem, just don't check the option to ignore additional input when configuring caller input on digit 1
By default CUC will give you 1500 ms to dial for any other digits before trying to route the call with whatever you dialed.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Unity Connection 8.6 LDAP or CUCM Import with german special characters called "Umlaut": ä, ö, ü

Hi,
for jabber 9.1 integration i sync'ed all users at Callmanager, Presence and Unity to our LDAP (MS AD). with CUCM and Presence (both 8.6.x), it works fine, just Unity Connection sync the Users from AD, but i cannot import Users with german special characters ä, ö, ü (i.E. German Name in LDAP-su: Müller).
Jabber 9.1 need for Voicemail Integration the AD Authentication. Know somebody, if there is an Workaraound or Fix ?
This is a general issue, with or without Jabber, with sync directly from AD, or indirectly through CUCM (sync'ed with AD)
thx and regards
Jacky

I located an identical defect (CSCts28455) that was closed as unreproducible. The defect references CSCtj73444 "Add support for UTF-8 password to LDAP and RADIUS/MSCHAP" which is added to 8.4.2 with the recommendation of RADIUS/MSCHAP or LDAP only for international character support. It would make sense to go to the latest in your current train (ie: 8.4.4.1.ED) and see if the issue remains. What you want to do appears to be supported.
Matthew

Voice Mail Ports Rejected in CUCM - Unity Connection

Hi to all,
I have a CUCM v9.1 cluster (1 Pub and 2 Subs) with two device pools (DP_Site_A and DP_Site_B), each DP has a call manager group that has the Subscriber for each site as the Primary CUCM Server in order of registration: DP_Site_A -> CMGroup_A ( 1° Sub_A and 2° Sub_B) ,
DP_Site_B -> CMGroup_B ( 1° Sub_B and 2° Sub_A).
The issue that I have is that when I configure the voice ports in the CUCM with either DP_Site_A or DP_Site_B I always get those ports as "Rejected" in the registration status BUT if i leave the DP for the voice ports as default they get registered and actually work fine with voice mails.
My Unity Connection is v9.1 too.
Any ideas about what can be causing this behavior??
Thanks in advance for your help.

Hi Alfonso,
Can you check these settings in CUC for the "Secondary" CUCM (Sub) server config
to make sure the Subs are listed as part of the SCCP registration;
Step 32 On the Edit Servers page, do the following substeps if the Cisco Unified CM cluster has secondary servers. Otherwise, skip to Step 33.
a. Under Cisco Unified Communications Manager Servers, click Add.
b. Enter the following settings for the secondary Cisco Unified CM server and click Save.
# Table 6-16     Settings for the Cisco Unified Communications Manager Servers
# Field
# Setting
# Order
# Enter the order of priority for the Cisco Unified CM server. The lowest number is the primary Cisco Unified CM server, the higher numbers are the secondary servers.
# IP Address or Host Name
# Enter the IP address (or host name) of the secondary Cisco Unified CM server.
# Port
# Enter the TCP port of the Cisco Unified CM server that you are   integrating with Cisco Unity Connection. We recommend that you use the   default setting.
# TLS Port
# Enter the TLS port of the Cisco Unified CM server that you are   integrating with Cisco Unity Connection. We recommend that you use the   default setting.
# Server Type
# Click Cisco Unified Communications Manager.
http://www1.cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny050.html
Cheers!
Rob
"Talk about a dream
Try to make it real"
- Springsteen

Call forward to unity connection call handler

have the following setup:
cucm 8.6
cuc 8.6
a cti route point (DN 1000 )with forward all to unity connection call handler.
phone users who choose to have some quiet time can forward all their calls to the cti rp.
1. i need to allow only specfic DNs the ability to forward to the cti rp.
2. at times that the allowed DNs didnt choose to forward to cti rp then normal behaviour should occur - busy or unanswerd calls should go to DNs personal voice mail.
thanks

You can assign a specific partition to cti-rp and assign it to a CSS and this CSS should be assigned to those users (at call forward settings in line) only to whom you are trying to give this facility and for other users you can
or you can create a TP for it with specific partition and set the called number as per voice mail.
Suresh

Cisco Unity Connection 8.6 not getting CLID information from CUCM 8.6

Hello,
Currently Running:
Cisco Unified Communications Manager 8.6.2
Cisco Unity Connection 8.6.2
Problem:
when any outside caller leaves a voicemail, the caller number information is not being sent to unity.
example, I call with my cell phone, 817.555.1234 to my Cisco 7940 phone and it shows the CLID information that i am calling with. iDivert to voice mail, Leave a message. Playback message and just the default message information from Cisco Unity.
we currently upgraded from CUCM 6.1.3 and Unity 5. before i could press 9 and get the caller information.
I have viewed the "Playback Message Settings" and selected "After Playing Each Message, Play" and selected Sender's Information. and also selected "Include Extension and Sender's ANI"
upon playing the VoiceMail after the message i get the default message "From Cisco Unity Connection Messaging System"
I also have the message relaying to my E-mail and I get the same in the subject line.
"Message from Cisco Unity Connection Messaging System (Unknown extension)"
This tends to be a big deal with the Sales team as customers will call and say "Call me back"
But any Internal Calls show the correct information, proper greeting, extension information even on the relay to e-mail.
Any help will be appreciated.
Thanks
Tim

Found another post that referenced Cisco Bug ID CSCti37610.
CUC plays message is from Unity Connection Messaging system
Symptom:Before message playback, Unity Connection plays the message is from Unity Connection Messaging System instead sender's ANI
Conditions:Problem was observed on Unity Connection cluster and appropriate services are not rebooted after changing the SMTP domain name
Workaround:
Restart the Unity Connection servers
It should have been fixed in 8.5 but we did change the SMTP domain name on 8.6 and now see the problem. Will schedule a reboot and see if the issue goes away.

Installation CUCM 10.X & Unity Connection

Hello,
I have a question about the actual installation of both systems, so i'm not using a pre made file on the website of cisco which you convert to a floppy image.
When i installed CUCM, i made my lab switch the NTP server by giving it the following command:
- config#ntp master 1
The call manager saw all of this & the default gateway also and it al worked perfectly and the Call Manager installed. When i did the same installation for Cisco Unity it did not work, it would not reconise the NTP nor even the default gateway and the installation did not proceed. This strook me as very weird, as the installation of the call manager did succeed with no issues.
Rebooted the switch : Didn't work
Resetted it as NTP : Didn't work
Laptop as NTP: Didn't work (Registry in Windows 8), if someone knows a decent program it would be a plus
Cisco Unity Connection wasn't even able to contact the default gateway of the vlan, it was 1 switch. The vlan had an SVI and IP routing was enabled.
Does anyone have any suggestions to these kinds of problems, which approaches did work?
Kind Regards,

Hi,
So yes the virtual machines had the same network settings and were in the same IP subnet aswell.
In ESXi i configured both the network cards, 1 active & 1 backup so i didn't need to create a port channel. I put up 2 VLAN's one for the management of the ESXi and one for the UC applications, so tagging was enabled.
My switch configuration was extremely basic
Just 2 vlan's 100 for data & 200 for voice, this resembles the environment it will be later installed.
The vlan's were SVI's and ip routing was enabled, i was able to ping from one vlan to another.
It had the command:
NTP Master 1
I knew it worked because i forgot during the installation to correct the clock, it was still 1993 and i had an issue with uploading the licenses, i resolved this.
So call manager was getting all of the NTP information
But during the Unity installation it all didn't work/respond, still very weird. The ports to the ESXI were configured as Trunk

Unity Connection transferring calls to CUCM

Similar Messages

Maybe you are looking for