Cisco 8851 8865 voice mail prompt

on firmware version 11.5 and below, when a user has a vm on lines other than the primary line, they'll need to press the line button for the vm prompt to show up. did some testing and firmware 12 fixed that issue. firmware 12 essentially make the phone vm prompt the same as in the 796x series phone.

Cisco 8851

Just upgraded from 7960s to the new 8851 and 8865 phones. After the upgrade we found out that users with multiple lines have issue where if they dial out from their phone, the phone will pick the last line used as the calling number instead of primary line. Easy fix, set "Always use primary line" to "On". But that introduced another problem. Now they have to select the line when picking up the phone instead of just pressing the speaker or pickup up the handset like they always used to do on the 7960s. Opened ticket with Cisco and they said that's the way it is on the 8851. Really?!! 

Not being convince I started testing all the setting on the phone that I can find that potentially sounds like it can be the fix. Long story short, the fix was to set  "Always use prime line" back to Default and change "Show All Calls on Primary Line" to "Enabled" and that fixed the issue.

UPDATE: setting everything to default and just enable "Enhanced Line Mode" will accomplish the same

CUCM 11.5 cannot change PIN for user with no mailbox in CUC

CSCva90519

Description

Symptom:
Unable to change the PIN for an End User in CUCM that does not have a voicemail box configured in CUC, and Enable End User Pin Synchronization under System -> Application Server.

Error: Pin update failed to update on Unity Connection Server. User Not Found

Refer to the "PIN Synchronization" Section of the guide below:
PIN Synchronization

The impact here is that users without mailboxes might still need to change their PIN in CUCM (for Extension Mobility, etc) on the end user account, and they are unable to do this with the End User Pin Synchronization enabled.

Conditions:
CUCM 11.5
CUC 11:5
User has no voicemail box in CUC
Enable End User Pin Synchronization is checked under System -> Application Server

Workaround:
You will have to do one of the following to allow the PIN to be changed from the End User page in CUCM:
1) Add a voicemail box to the user in CUC
2) Disable "End User Pin Synchronization"

We have found that we are able to update the PIN by logging into Extension Mobility and updating the PIN from there. However this will not do a PIN Sync to Unity connection even if the End User has a voicemail box configured or not.

Further Problem Description:

Customer Visible

Was the description about this Bug Helpful?

(0)

Details

Last Modified:

Aug 9,2017

Status:

Open

Severity:

6 Enhancement

Product:

(1)

Cisco Unified Communications Manager (CallManager)

CUCM 9.1.2 Backup issue

we had a lot of failed CUCM backup on version 9.1.2 but since we upgraded to 11.5 the backup issue was resolved using the same sftp software which is not on Cisco's approved sftp software list.

cisco 8831 with firmware 9.3.3 to 10.3.1 directly

need this to upgrade to this firmware sip8831.9-3-3-TO-10-3-1-v2

Phone running 9-3-3 FCS load can not be upgraded to 10-3-1 load directly

CSCur37664

Description

There is a bug exists in existing 9-3-3 images: fail to upgrade to non-9-3-3 versions like 10-3-1 directly.

we would like to fix it in code on 9-3-3 FCS branch as well so that further more SR/ES based on 9-3-3 would be able to upgrade to 10-3-1 directly.

Symptom:
There is a bug exists in existing 9-3-3 images: fail to upgrade to non-9-3-3 versions like 10-3-1 directly.

Conditions:
There is a bug exists in existing 9-3-3 images: fail to upgrade to non-9-3-3 versions like 10-3-1 directly.

Workaround:
The workaround for upgrade from existing 9-3-3-5 FCS load to 10-3-1 MR release load would be via an intermediate version like 9-3-3-TO-10-3-1.

Further Problem Description:
customer visible bug for 8831 10.3(1)

Customer Visible

Was the description about this Bug Helpful?

(0)

Details

Last Modified:

Jun 14,2017

Status:

Fixed

Severity:

3 Moderate

Product:

(35)

Cisco Unified IP Phone 6900 Series

Cisco Unified IP Phone 9951

Cisco Unified IP Phone Expansion Module 7914

Cisco Unified IP Phone 7962G

Cisco Unified IP Phone 7945G

Cisco Unified IP Phone 7971G-GE

Cisco Unified Wireless IP Phone 7920

Cisco Unified IP Phone 7961G-GE

Cisco Unified IP Phone 6961

Cisco Unified Wireless IP Phone 7925G

Cisco Unified IP Phone 7941G

Cisco Unified IP Phone 6941

Cisco Unified IP Phone 7911G

Cisco Unified IP Phone 8961

Cisco Unified IP Phone 7940G

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone 7975G

Cisco Unified IP Phone 7942G

Cisco Unified IP Phone 8945

Cisco Unified IP Phone 9971

Cisco Unified IP Phone 8941

Cisco Unified IP Conference Phone 8831

Cisco Unified IP Phone 7931G

Cisco Unified IP Phone 6945

Cisco Unified IP Phone 7912G

Cisco Unified IP Phone 7970G

Cisco Unified IP Phone 6921

Cisco Unified IP Phone 7965G

Cisco Unified IP Phone 7960G

Cisco Unified Wireless IP Phone 7921G

Cisco Unified SIP Phone 3951

Cisco Unified IP Phone 7941G-GE

Cisco Unified SIP Phone 3911

Cisco Unified IP Conference Station 7937G

Cisco Unified IP Phone 7961G

Support Cases:

21

<CiscoIPPhoneError Number="6" />

apparently this means the phone is in the process of upgrading

UPGRADING CISCO UNITY CONNECTION FROM 9.1 TO 11.5

There is another  bug that affect this upgrade, found out the hard way

Unity Connection Upgrade to 11.5(1)SU1 fails

CSCvb02774

Description

Symptom:
Unity Connection upgrade to 11.5(1)SU1 fails

Issue seen on both L2 and RU upgrades (upgrades from 8.X, 9.X, 10.X, and 11.X).

Conditions:
Issue occurs when there is an admin user created using the Administrator Template.
Run this command to check for such users,
run cuc dbquery unitydirdb SELECT displayname FROM tbl_user WHERE objectid NOT IN (SELECT subscriberobjectid FROM tbl_subscribertimelastcall) AND readonly=0 AND istemplate !=1

Workaround:
1) Delete the users returned by the command output.
2) Cop file "ciscocm.cuc_11.5SU1_pre_upgrade.cop.sgn" released for the defect fix.
Please refer to upgrade guide for 11.x:
"For successful upgrade to Unity Connection 11.5.1 SU 1, make sure to download and install an additional COP file ciscocm.cuc_11.5SU1_pre_upgrade.cop.sgn. To install the COP file, you must follow the instructions given in the ReadMe of the COP file available at http:/?/?www.cisco.com/?web/?software/?282204704/?18582/?CUC_?CSCvb02774_?ReadMe.docx?
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/11x/install_upgrade/guide/b_11xcuciumg/b_11xcuciumg_chapter_010.html

Further Problem Description:
Unity Connection upgrade to 11.5(1)SU1 fails due to the presence of new columns in tbl_subscribertimelastcall.
The system attempts to update the last call time of admin users and it fails

From cuc import logs,


2016-08-23 16:49:12 INFO Running migration.unitydirdb.11_05_0335_update_admin_subscribertimelastcall.up() (migrate:225)
2016-08-23 16:49:12 DEBUG ('SELECT objectid FROM tbl_user WHERE objectid NOT IN (SELECT subscriberobjectid FROM tbl_subscribertimelastcall) AND readonly=0 AND istemplate !=1',) (migration:116)
2016-08-23 16:49:12 DEBUG (u"INSERT INTO tbl_subscribertimelastcall (subscriberobjectid, timelastcall, inactive, tuisessioncount) VALUES ('cb8f1c4d-205d-46e2-b00a-cd30545d194d','2016-08-23 11:19:12', 0, 0)",) (migration:116)
2016-08-23 16:49:12 Traceback (most recent call last):
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/switchover.py", line 460, in
2016-08-23 16:49:12 sys.exit(main())
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/switchover.py", line 163, in main
2016-08-23 16:49:12 start_migration(get_data_directory(), destdbnames)
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/switchover.py", line 184, in start_migration
2016-08-23 16:49:12 migrate_data(data_directory)
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/switchover.py", line 214, in migrate_data
2016-08-23 16:49:12 migration.migrate.run(data_dir, direction=get_switch_direction())
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/migrate.py", line 59, in run
2016-08-23 16:49:12 return main([__name__, base_directory], **kwargs)
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/migrate.py", line 56, in main
2016-08-23 16:49:12 MigrateDatabase(argv[1], os.path.basename(database_path), **kwargs).migrate()
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/migrate.py", line 105, in migrate
2016-08-23 16:49:12 self.run_migration_scripts()
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/migrate.py", line 229, in run_migration_scripts
2016-08-23 16:49:12 getattr(m, self.direction)()
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/unitydirdb/11_05_0335_update_admin_subscribertimelastcall.py", line 16, in up
2016-08-23 16:49:12 execute("INSERT INTO tbl_subscribertimelastcall (subscriberobjectid, timelastcall, inactive, tuisessioncount) VALUES ('%s','%s', 0, 0)" %(subscriberid[0], now))
2016-08-23 16:49:12 File "/opt/cisco/connection/lib/switchover/migration/migration.py", line 117, in execute
2016-08-23 16:49:12 return conn.execute(*args)
2016-08-23 16:49:12 sqlite3.OperationalError: table tbl_subscribertimelastcall has no column named inactive

Customer Visible

Was the description about this Bug Helpful?

(5)

Details

Last Modified:

Jun 21,2017

Status:

Fixed

Severity:

3 Moderate

Product:

(1)

Cisco Unity Connection

Support Cases:

194

Known Affected Releases:

(1)

11.0

Known Fixed Releases:

(15)

CUC.12.0(0.97123.1)

12.0(0.98997.1)

12.0(0.97000.13)

12.0(0.97000.10)

12.0(0.97000.8)

12.0(0.97000.7)

12.0(0.71)

12.0(0.58)

12.0(0.57)

12.0(0.52)

12.0(0.51)

11.5(1.12900.21)

11.5(1.12013.1)

11.5(1.11900.4)

11.5(1)ES4

Download software for  Cisco Unity Connection

Cisco Unity connection 9.1 upgrade to 11.5 failed pretest

tried to upgrade Cisco Unity connection version 9.1 to version 11.5 and when I issued the 'run cuc preupgrade test' got some errors and found this bug. with my system the Connection DB test also failed as well and not just the cluster status. will copy the vm file and try the upgrade in the lab first and see if it goes well.

Cisco Bug: CSCui08093 - PreUpgrade test CLI Command gives wrong result for Cluster State check

Last Modified

Jun 16, 2017

Product

Cisco Unity Connection

Known Affected Releases

8.6(2)ES25 9.0 9.1(2.1)

Description (partial)

Symptom:

CLI command "run cuc preupgrade test" gives wrong output for Cluster state of the Cluster though the cluster is perfect 

Expected output

===========

===========================================================================

R E P O R T    C A R D

===========================================================================

Locales Installation Test: PASS

Connection DB Test: PASS

DRS Backup History Test: PASS

Cluster State Test: PASS

Cop File Installation Test: PASS

CLI command "run cuc preupgrade test" gives wrong output for Cluster state of the Cluster though the cluster is perfect 

Observed output

===========

===========================================================================

R E P O R T    C A R D

===========================================================================

Locales Installation Test: PASS

Connection DB Test: PASS

DRS Backup History Test: PASS

Cluster State Test: PASS

Cop File Installation Test: PASS

Conditions:

While running the "run cuc preupgrade test" CLI command on 8.6(2)ES25 or later cluster

CUCM Passwords & Recovery

CUCM Passwords & Recovery

CUCM passwords

During CUCM installation, you must specify the following user names and passwords:

• Application user name and password
• Administrator Account user name and password 
• Security password

Application password

It  is used for the login on Cisco Unified CM Administration, Cisco Unified  Serviceability, Cisco Unified Reporting pages and Real Time Monitoring  Tool.

The Application User name must  start with an alphabetic character, must be at least six characters  long and can contain alphanumeric characters, hyphens and underscores.

You can reset the application username/password from CUCM OS CLI using the command

utils reset_application_ui_administrator_name

utils reset_application_ui_administrator_password

Administrator Account password

It  is used for the login on Cisco Unified OS Administration, Disaster  Recovery System pages and Command Line Interface  (CLI) login.

The  Administrator Account user name must start with an alphabetic  character, must be at least six characters long and can contain  alphanumeric characters, hyphens and underscores.

To change admin password, you can run the CLI command 'set password user admin'

Note: You need to have the old password in order to change to new one

Security password

It  is used by the CUCM nodes to authorize communications with other nodes within a cluster. You  must ensure that this password is identical on all nodes in the cluster.

The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.

To change the security password, you can run the CLI command 'set password user security'

Note: You need to have the old password in order to change to new one

Password Recovery

In case you lose administrator password or security password, you can recover it using the following procedure (you don't need the old password in this procedure):

1. Login to CUCM OS CLI using the account (username:pwrecovery/password:pwreset)
2. Insert a valid CUCM DVD and press any key
3. Remove the DVD and press any key
4. You will be promoted to select whether to recover the admin password or security password.
5. Go through the instructions to complete the change

Note: In case you are recovering the security password, you need to do it in each node in the cluster and restart it

CISCO CUCM SEARCH FOR CALL FORWARD NO ANSWER, BUSY OR UNREGISTERED USING SQL

run sql select cfbdestination from numplan                    CALLFORWARD BUSY EXTERNAL
run sql select cfbintdestination from numplan                CALLFORWARD BUSY INTERNAL

run sql select cfnadestination from numplan               CALLFORWARD NOANSWER EXTERNAL
run sql select cfnaintdestination from numplan           CALLFORWARD NOANSWER INTERNAL

run sql select cfurdestination from numplan            CALLFORWARD UNREGISTER EXTERNAL
run sql select cfurintdestination from numplan        CALLFORWARD UNREGISTER INTERNAL

TO UPDATE THE CALL FORWARD NO ANSWER /BUSY NUMBER USE THE FOLLOWING COMMAND

run sql update numplan set cfbdestination[1]='0' where cfbdestination[1]='9'

here we are changing the first number for cfbdestination from 9 to 0. substitute cfbdestination with other to change that field

Unity Connection  Sub 9.1 install failed with error

I was doing a reinstall of mine Unity Connection 9.1 subscriber and it failed with the following error message.

"rpm --percent -iv --replacefiles
/common/rpm-archive/9.1.1.20000-5/RPMS/connection/cuc-9
.1.1.20000-32.i386.rpm " failed 91)

The system will now halt.


After talking to Cisco TAC it turns out to be a bug

Cluster renegotiate fails due to syscdr already present on SUB

CSCue78730

Description

Symptom:
The CLI "utils cuc cluster overwritedb" fails either on PUB or SUB.
The CLI "utils cuc cluster renegotiate" fails on SUB.
The install or upgrade fails on Subscriber server.

Conditions:
Enterprise replication was active between PUB and SUB.
Previous Replication could not be broken within a stipulated timeout as the database tables were locked internally. When replication is attempted to be recreated post overwritedb / renegotiate, it fails. The same failure is also seen during subscriber install or upgrade

Workaround:
None.

Cisco TAC did something with the database and afterward I was able to finish installing Unity Connection Subscriber to my cluster. Hope this helps someone else who run into the same issue somewhere. 

Using sql commands to update CUCM line settings

Recently we had to change the outbound PSTN access code from 9 to 0 because a lot of users were dialing 911 accidentally. It's really simple to do that in CUCM to change the dial-pattern from 9 to 0 but what about changing all the speed dial and call forward all destination. Turns out you can do that with CLI and sql commands.

To change speed dials from 9 to 0

1. verify the current speed dials with this command

    run sql select speeddialnumber from speeddial

2. use the following command to update the first number in the speed dial from 9 to 0 and only if the first number is 9

    run sql update speeddial set speeddialnumber[1] = '0' where speeddialnumber[1] = '9'

3. run the first command again to verify the change

To change call forward all destination from 9 to 0

1. verify the current call forward all destination

    run sql select cfadestination from callforwarddynamic

2. use the following command to update the first number in call forward all destination from 9 to 0 and only if the first number is 9

    run sql update callforwarddynamic set cfadestination[1]='0' where cfadestination[1]='9'

3. run the first command again to verify change