cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2085
Views
0
Helpful
3
Replies

SIP Publish Trunk error msg in CUPS 8.0 Troubleshooter

Ginger Dillon
VIP Alumni
VIP Alumni

Hi all -

New deployment of CUPS 8.0 and CUCM 8.5, have been attempting to fix the following error in CUPS System Configuration Troubleshooter,"Currently SIP Publish is configured on the Cisco Unified Presence server, but not on the Cisco Unified Communications Manager".  Found the following two bugs out on Bug Toolkit you may be interested in:

- CSCti19329 Bug Details (appears to be cosmetic at this point)

You have this bug saved in the following group(s): CUPS .
(Bolded group names are subscribed to email notifications.)
Incorrect message in troubleshooter for Presence Engine
Symptom:
CUP Troubleshooter says "Currently SIP Publish is configured on the Cisco Unified Presence
server, but not on the Cisco Unified Communications Manager"

Conditions:
CUP 8.0.2
CUCM 8.5

Workaround:
Unknown

- CSCti19018 Bug Details  (in testing for the previous error, I toggled the checkbox and did not restart the Presence Engine.  I did after finding this bug.)

You have this bug saved in the following group(s): CUPS .
(Bolded group names are subscribed to email notifications.)
PE deadlocked when toggling ENABLE SIP PUBLISH ON CUCM
Symptom:
No Presence

Conditions:
CUP 8.0.2
CUCM 8.5
Toggle the checkbox "Enable SIP Publish on CUCM" from CUPAdmin > Presence > Settings

Workaround:
Restart PE

Hope this helps someone else troubleshooting same!  Sincerely, Ginger

3 Replies 3

Any update on first bug (CSCti19329) ?

Thanks,

Arash

any update on this Bug?  any further information available?

Hey Guys,

The Defect: CSCti19329, indeed is cosmetic as long as the contacts in the contact list show correct "Available/Away/On The Phone" status as we utilize SIP Trunk for Presense Status.

This is cosmetic because of a DB schema change with CUCM 8.5.  Even though CUPS 8.0(x) is supported with CCM 8.5, due to DB Schema change, that error message in generated in the System Troubleshooter.

If you were to upgrade to any version 8.5 or higher, that error message will go away.

Hope that helps clarify info on this defect.

Regards,

Jas