UCCX 8 VOIP Monitor Subsystem - Out of Service

All,
Upgraded CCX 701(SR5) to CCX 8.0.2 Premium HA enabled. Both Servers were IN SERVICE. Did a Patch upgrade to UCCX 8.0.2SU1. Noticed that VOIP Monitor Subsystem on both servers showing as OUT OF SERVICE. Downgraded to CCX 8.0.2, still get this Subsystem OUT OF SERVICE.
From RTMT, it shows the following error:
%MIVR-SS_VOIPMON_SRV-3-VOIP_OPERATION_ERROR:VOIP Subsystem Operation Error: Module Name=LRMConnection.readMSG, A specific description for a trace=erroris: ,Exception=java.io.EOFException
Anyone kows how to fix this problem???
Thanks.

Hi all,
I had this same problem and similar/same versions.
Restarting Cisco DESKTOP VoIP Monitor Service (on sub - which had VoIP Monitor Service showing 'OOS') made no impact. I don't think there is any real relationship between DESKTOP VoIP monitor service and VoIP monitor service?
Anyway, restarted the same service on Pub - no change.
Tried restarting various sub services including CCX Engine - no change.
I found I had to restart publisher Cisco Unified CCX Engine, then go to sub and do the same once pub was back to all 'in service'.
I then found that my sub's 'Log Manager' under 'Cisco Unified CCX Serviceability' had gone to PARTIAL SERVICE.
I restarted 'Cisco Unified CCX Serviceability' on sub - which had to be done via CLI.
It appeared to restart no issue - but refreshing the list of services in the GUI several times - it still was in PARTIAL.
Restarted Sub appliance (bounced the server) from CLI, after reboot - all services were back up and IN SERVICE.
Thankfully I didn't have to restart my Pub - all services... IN SERVICE on pub & sub
Resolved.
PS. No calls were dropped for us.

Similar Messages

Unified CM Telephony Subsystem OUT OF SERVICE

CM 8.03
CCX 8.0.2
Data Check - everything is ОК.
Data Resync - i've done anyway
Status Cisco JTAPI Resync is completed
Cisco JTAPI Client
Node ID: 1 -- Cisco JTAPI Client versions are consistent
Node ID: 2 -- Cisco JTAPI Client versions are consistent
I've rebooted one CCX recently
Status of CCX Engine on both servers is the same:
Cisco Unified CCX Engine PARTIAL SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Manager Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Expression Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Document Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Bootstrap Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
File Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Socket Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Log Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Config Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Cluster Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Session Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
User Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Script Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
RTP Port Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Prompt Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Channel Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Grammar Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Application Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Contact Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Executor Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Archive Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Database Manager IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Subsystem Manager PARTIAL SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
MRCP ASR Subsystem NOT CONFIGURED Not Started Not Started
Unified CM Telephony Subsystem OUT OF SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Core RTR Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
CMT Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
eMail Subsystem NOT CONFIGURED Not Started Not Started
RmCm Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
MRCP TTS Subsystem NOT CONFIGURED Not Started Not Started
Voice Browser Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
HTTP Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Outbound Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
VOIP Monitor Subsystem IN SERVICE FRI DEC 2 11:00:04 2011 00 Days 00:02:27
Database Subsystem NOT CONFIGURED Not Started Not Started
Here is what I find in RTMT System Logs messages. I don't know if it refers to Unified CM Telephony Subsystem OUT OF SERVICE
: SDIDBConfigData:Read failed. odbc:SQLException = Failed to connect to datasource: [Informix][Informix ODBC Driver][-11302] Insufficient Connection information was supplied, ProcessNodeId=Failed to connect to datasource: [Informix][Informix ODBC Driver]
Help me to troubleshoot

Dear Anchhoudh
below is the output from data and jtapi resync.
Unified CM Telephony Users
jtapi_1 -- Ok
Unified CM Telephony Port Groups
Port Group 0
CTI ports on node 1 -- Ok
CCM Data
Device Pool--Ok
Media Resource Group List-- Ok
PresenceGroup-- Ok
Partition-- Ok
User Hold Audio Source-- Ok
Alerting Name Ascii-- Ok
Require DTMF Reception-- Ok
NetWork Hold Audio Source-- Ok
CallPickUpGroup-- Ok
VoiceMailProfile-- Ok
AAR Group-- Ok
Location-- Ok
Calling Search Space-- Ok
Unified CM Telephony Triggers
AA
AA -- Ok
CCM Data
Forward Busy Calling Search Space-- Ok
Device Pool-- Ok
Alerting Name Ascii-- Ok
PresenceGroup-- Ok
Partition-- Ok
CallPickUpGroup-- Ok
VoiceMailProfile-- Ok
Location-- Ok
Calling Search Space-- Ok
AA-1
AA-1 -- Ok
CCM Data
Forward Busy Calling Search Space-- Ok
Device Pool-- Ok
Alerting Name Ascii-- Ok
PresenceGroup-- Ok
Partition-- Ok
CallPickUpGroup-- Ok
VoiceMailProfile-- Ok
Location-- Ok
Calling Search Space-- Ok
AA-2
AA-2 -- Ok
CCM Data
Forward Busy Calling Search Space-- Ok
Device Pool-- Ok
Alerting Name Ascii-- Ok
PresenceGroup-- Ok
Partition-- Ok
CallPickUpGroup-- Ok
VoiceMailProfile-- Ok
Location-- Ok
Calling Search Space-- Ok
AutoAttendant-3
AutoAttendant-3 -- Ok
CCM Data
Forward Busy Calling Search Space-- Ok
Device Pool-- Ok
Alerting Name Ascii-- Ok
PresenceGroup-- Ok
Partition-- Ok
CallPickUpGroup-- Ok
VoiceMailProfile-- Ok
Location-- Ok
Calling Search Space-- Ok
and jtapi resync
Cisco JTAPI Client
Node ID: 1 -- Cisco JTAPI Client versions are consistent
Thanks

Cisco UCCX VOIP Monitoring Issue

Hi there,
We got a customer with Cisco CUCM 8.5 and UCCX 8.5. We have configured SPAN Port VOIP Monitoring for Agent/Supervisor. When Agent is talking, the Supervisor can click on button to hear the conversation. It takes 5 or 6 seconds till we hear the agent conversation.
I hope someone got any idea why it's taking 5 or 6 seconds till we hear the actual voice.
Thanks.
Regards,
Ysana

You don't say if this is UCCX or Enterprise
Make sure your jtapi user has "Standard CTI Allow Call Monitoring" set under permissions.
If this is UCCX then it should have set that permission when it created the jtapi user, Enterprise you will need to set it
Graham

VOIP monitor in partial service

Hi Expert
I have installede a new uccx version 8.5.1 su2 withe the cop file.
What i found that the voip monitor subsystem is in partial service.,the system is in HA
From RTMT loggs i can found that "
3853: May 14 23:28:01.414 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-VOIP_OPERATION_ERROR:VOIP subsystem operation error: Module Name=LRMConnection.readMSG: lrmHost: 20.250.185.68 , lrmPort: 3000,A specific description for a trace= error is: ,Exception=java.io.EOFException
3854: May 14 23:28:01.414 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION:java.io.EOFException
3855: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at java.io.DataInputStream.readInt(DataInputStream.java:375)
3856: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at com.spanlink.lrm.io.CRSLRMInputStream.readINT(CRSLRMInputStream.java:211)
3857: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at com.spanlink.lrm.io.CRSLRMInputStream.readMHDR(CRSLRMInputStream.java:356)
3858: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at com.spanlink.VOIPMonitor.subsystem.LRMConnection.readMSG(LRMConnection.java:156)
3859: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at com.spanlink.VOIPMonitor.subsystem.LrmVoipManager.recovery(LrmVoipManager.java:444)
3860: May 14 23:28:01.415 GMT-1000 %MIVR-SS_VOIPMON_SRV-3-EXCEPTION: at com.spanlink.VOIPMonitor.subsystem.VoipServerHeartbeatThread.run(VoipServerHeartbeatThread.java:50)
Kindly help in resolving the issue
Regards
RC

Hi RC,
Please try upgrading it to UCCX 8.5 SU3 and check if it solves this issue.
CSCts87264 -VoIP monitor device sync has no failover function
http://www.cisco.com/web/software/280840578/90779/RN_UCCX_851_SU3.pdf
Hope it helps.
Anand
Pls rate helpful posts by clicking on the stars below the right answers !!

UCCX:Secondary node is in partial service & testing the HA mode

Hi,
Running UCCX 8.5 in HA mode.
Primary UCCX services are INSERVICE status,but in Secondary UCCX service status (UCCX engine ans subsystem)shows PARTIAL SERVICE.
Let me know how to make it INSERVICE.
Also let me know any procedure to test the HA mode is working fine or not!!!
Help me out!!
Thanks & Regards,
Krishna

Hi,
Please expand the Engine under the arrow and check as to which subsystem is in partial service, this will help determine.
-Also make sure to turn on the engine debugging under UCCX serviceability.
Restart the servers during a maintenance window
-Collect the logs from the RTMT tool
-As after the restart the MIVR LOGS should clearly display the cause for which subsystem is in partial service
-Some of the most common reasons can be :
-Application manager service in partial
-CMT telephony subsystem might be in partial too
Also is the setup HAOWAN?
Please send over the CUCM version as well.
Once I know which subsystem is in partial service,I can point you in the right direction
Thanks,
Prashanth

UCCX 10.5 HA, Silent Monitoring, no devices under CDA VoIP Monitoring Device

Hi
I'm configuring Silent Monitoring, but in UCCX CDA under Settings: Services Configuration > Multiline, Monitoring & Recording > VoIP Monitoring Device, there are no devices.
Note: I have CAD agents setup with IP Phone working properly. UCCX is "IN SERVICE", Cisco Desktop VoIP Monitor Service "IN SERVICE"
UCCX 10.5.1.10000-24
Let me know if someone had the same issue.
Regards
Carlito

Hi Carlito,
you need to agregate IP Phone that you want to monitor to RmCm User (Application user), in "Device Information/Controlled devices", and save.
Let me know if this information could help you.
Regards,
Caosfox

VoIP Monitor in UCCX Admin

Hi,
We have made some changes in our environment such as CUCM upgrade etc and i have just come to configure two new agents in VoIP monitor and i get error reading from directory services.
We have updated the JTAPI client, rebooted the server etc and are now stumped.
Anyone got any ideas, we checked the logs and event viewers too.
/Jon

Jon,
The biggest thing I see is that your UCCX version (5.0(2)SR2 is not compatible with CUCM. We only support CUCM 6.0(1)a. You will need to downgrade your CUCM or upgrade your UCCX to be compatible. UCCX 8.0(2)SU3 and UCCX 8.5(1)SU1 are both compatible. The incompatilble nature of the CUCM to UCCX version is causing JTAPI not to be able to sync. Resolving that willl resolve your issues. Please rate helpful posts!!
Regards,
Robert W. Rogier
CSE -- TAC, UCC

UCCX 8.0(2) SPAN/RSPAN based VOIP Monitoring

Hi Alll,
UCCX 8.0(2) High Availability (both servers are co-located in data center, where agents and supervisors are in building across the street over fibre)
SRND for UCCX 8 describes that it supports SPAN and/or RSPAN based voip monitoring, which is a requirement for my client as they have CAD Agents running on Citrix thin client and Supervisors on Thick client PCs.
However I am struggling to find a way to achieve this solution for my client with UCCX 8.x, UCCX 7 we would not have had this problem as you can configure 2nd NIC adaptor on UCCX server to be configured as VOIP Monitoring server port/IP under PostInstall and sniff all traffic for all Agent phone devices as configured under CDA.
Desktop Monitoring is not supported for thin client environment. Customer may eventually purchase QM/WFM, but for now we urgently require the essentials of agent monitoring on UCCX.
Please has anybody successfully had this configuration described above achieved? or have any ideas?
Thank you,
Yavuz

Have you been able to get a response to this post? I am running into the exact same issue with an upgrade to UCCx 8.0. SPAN on the 2nd NIC isn't allowed, and now the customer has lost functionality.
Thanks,
Ben

Desktop Administrator - VoIP Monitor Error in UCCX 4.5(2) Server

When i run the desktop administrator and then select the VoIP Monitor under the Enterprise Data Configuration, i got this pop up message "Could not get devices from Sync Service".
Then, i click "OK" and the "Default VoIP Monitor Server" filed got dimmed.
So, i would like to know if there were any way could fixed this problem.
Thanks!
B.rgds,
Tong

Thanks for your update.
I have try your suggestion but the problem remain same.
Here are the log file content your request:
==============================================================================================================
09:34:17 05/12/2010 INFO    LC4505 SNTServiceCommon::Handler: The Windows NT service received a stop message from the Windows NT service manager.
09:34:23 05/12/2010 INFO    LC4505 SNTServiceCommon::Handler: The Windows NT service has stopped.
09:34:27 05/12/2010 INFO    LC4505 SNTServiceCommon::Initialize: The Windows NT service has started.
09:34:27 05/12/2010 INFO    VER0000 LogModuleVerInfo: : Product Version <6.2.0.19> Pri Build <6.2(1)> Special Build < > Platform <2000 Service Pack 4> Debug range <8000-8006>.
09:34:27 05/12/2010 INFO    LC0059 SplkLDAPConnectionMgr::RegWatcherThread: Waiting for registry changes.
09:34:27 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 2 is empty.
09:34:27 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 3 is empty.
09:34:27 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 4 is empty.
09:34:27 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 5 is empty.
09:34:27 05/12/2010 INFO    LC0059 LDAPConnectionMgr::EstablishConnection: Connected to LDAP server on <10.10.10.2>.
09:34:27 05/12/2010 INFO    FCSS0020 ldapInitialize: Could not connect to CM LDAP
09:34:27 05/12/2010 INFO    SS1000 DirAccessSynSvr_i::LRMThread LRM promote server to be active.
09:34:27 05/12/2010 INFO    LRM_1001 SLRMMgr::SLRMMgr(): SLRMMgr object created.
09:34:27 05/12/2010 INFO    LRM_1001 LRMThreadStartGlue(): LRM thread starting.
09:34:27 05/12/2010 INFO    LRM_1001 SLRMMgr::Initialize(): SLRMMgr object initialized.
09:34:27 05/12/2010 INFO    LRM_1001 SLRMMgr::SetLRMAvailableFlag(): LRM interface has become available.
09:34:27 05/12/2010 INFO    LRM_1001 ReacquireThreadStartGlue(): Reacquire thread starting.
09:34:27 05/12/2010 INFO    VER0000 LogModuleVerInfo: : Product Version <6.2.0.19> Pri Build <6.2(1)> Special Build < > Platform <2000 Service Pack 4> Debug range <8000-8006>.
09:34:27 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler heartbeat STOP handle is not null!
09:34:27 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler Successfully created the heartbeat thread.!
09:34:27 05/12/2010 INFO    ACMI0000 AcmiConnectionMgr::EstablishConnection: Successfully connected to server on <10.10.10.2> port <42027>.
09:34:52 05/12/2010 INFO    LC4505 SNTServiceCommon::Handler: The Windows NT service received a stop message from the Windows NT service manager.
09:34:57 05/12/2010 INFO    LC4505 SNTServiceCommon::Handler: The Windows NT service has stopped.
09:34:59 05/12/2010 INFO    LC4505 SNTServiceCommon::Initialize: The Windows NT service has started.
09:34:59 05/12/2010 INFO    VER0000 LogModuleVerInfo: : Product Version <6.2.0.19> Pri Build <6.2(1)> Special Build < > Platform <2000 Service Pack 4> Debug range <8000-8006>.
09:34:59 05/12/2010 INFO    LC0059 SplkLDAPConnectionMgr::RegWatcherThread: Waiting for registry changes.
09:34:59 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 2 is empty.
09:34:59 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 3 is empty.
09:34:59 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 4 is empty.
09:34:59 05/12/2010 INFO    LC0002 GetLDAPRegistrySettings: The LDAP host name 5 is empty.
09:34:59 05/12/2010 INFO    LC0059 LDAPConnectionMgr::EstablishConnection: Connected to LDAP server on <10.10.10.2>.
09:34:59 05/12/2010 INFO    FCSS0020 ldapInitialize: Could not connect to CM LDAP
09:34:59 05/12/2010 INFO    SS1000 DirAccessSynSvr_i::LRMThread LRM promote server to be active.
09:34:59 05/12/2010 INFO    LRM_1001 SLRMMgr::SLRMMgr(): SLRMMgr object created.
09:34:59 05/12/2010 INFO    LRM_1001 SLRMMgr::Initialize(): SLRMMgr object initialized.
09:34:59 05/12/2010 INFO    LRM_1001 ReacquireThreadStartGlue(): Reacquire thread starting.
09:34:59 05/12/2010 INFO    LRM_1001 LRMThreadStartGlue(): LRM thread starting.
09:34:59 05/12/2010 INFO    LRM_1001 SLRMMgr::SetLRMAvailableFlag(): LRM interface has become available.
09:34:59 05/12/2010 INFO    VER0000 LogModuleVerInfo: : Product Version <6.2.0.19> Pri Build <6.2(1)> Special Build < > Platform <2000 Service Pack 4> Debug range <8000-8006>.
09:34:59 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler heartbeat STOP handle is not null!
09:34:59 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler Successfully created the heartbeat thread.!
09:34:59 05/12/2010 INFO    ACMI0000 AcmiConnectionMgr::EstablishConnection: Successfully connected to server on <10.10.10.2> port <42027>.
09:44:22 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler heartbeat STOP handle is not null!
09:44:22 05/12/2010 INFO    FCCTI_1000 CAcmiBase::InitializeHeartBeatHandler Successfully created the heartbeat thread.!
09:44:22 05/12/2010 INFO    ACMI0000 AcmiConnectionMgr::EstablishConnection: Successfully connected to server on <10.10.10.2> port <42027>.
09:44:47 05/12/2010 MINOR   DA0004 GetMACList Could not get csq list, err <0>, desc<>
09:44:47 05/12/2010 MAJOR   FCSS4533 DirAccessSynSvr_i::GetMACList Could not get MAC list
==============================================================================================================
Thanks and look for your further suggestion on this issue.
B.rgds,
Tong

RE: How to monitor who has what service objectconnection?

We ran into this problem, specifically because we are using a dbsession
connection pattern and the dba's did not like loosing control over
connections. We have 8 subsystem, each with a dedicated connection that
is shared across multiple users. We also have a security pattern in
place that is token based. Since we have to pass a security token
through service objects we can track this information using a
"connection array" on the service object and a system agent to poll the
contents of the array. When a sql statement is invoked on a
persistence object we add the user to the array on the persistence
manager (SO). When the sql is complete we remove the user from the
array. Since the PO has a system agent we can ask the system agent at
anytime, who has an open connection/session with the PO. Since system
agents plug into econsole, the dba can go look any time.
Any questions, please contact
Chris [email protected] or
Gary [email protected]
MCI Systemhouse
From: ADRIAN PEGGY LYNN
To: [email protected]
Subject: How to monitor who has what service object connection?
Date: Tuesday, September 24, 1996 9:12AM
Here at Eli Lilly & Co., we have a customer that would like to know if
anyone out there has successfully
devised a method to be able to tell what user has what service object
connection. Basically, if a customer
calls the system administrator with a problem with the application, the
system administrator would like to
be able to kill certain processes. Right now, the database connections
running on the server all look the same.
Some ideas were generated internally, one referring to setting up agents
but we'd like to see if anyone
has had success in doing this already that we could use as a contact.
Thanks,
Peggy Adrian
Eli Lilly & Co.
[email protected]

Hello Peggy,
I suggest that you make contact with Paolo Sidoli at DS Data (Italy). They
have written a very nice package called DORE that includes trouble shooting
utilities, that allow you to monitor what a remote user is doing (you can
actually see their screen!).
You can contact Paolo at [email protected]
Best regards,
Richard

Portg Z30-A-1E1 - External monitor blacks out randomly

Very annoying problem - every now and then the monitor blacks out for 2 seconds and comes back.
Monitor is powered all the time.
HDMI cable changed twice and does not solve the problem.
Seems like a change of resolution or a reset - can the problem be in the graphic card? Otherwise maybe the HDMI port itself detecting strange stuff?
Please help I'm getting crazy as I work 90% of the time on external monitor.
Thanks
MAx

Originally Posted by ammtosh
I would try the French service, Toshiba is an international company. If you have a problem with your Italian car in France you go to the French workshop...
Yes maybe you are right. Still, annoying not being a fluent French speaker to have to deal with them.... and with 90% possibility that they'll say "if you bought in Italy you should talk to them". I'll try.
PS: another ridiculous thing: you buy a product that has a problem, and you need to pay to call the support service? Really not acceptable....
The dark side is strong.... actually, I start wondering which is the real dark side. Theory of relativity!

SCOM 2012 Linux Monitoring - RPCBIND, RPCIDMAP, RPCSTAT services not running

We are running SCOM 2012 SP1 and added a test Linux server running Red Hat Enterprise 6.3. SCOM is reporting that the server is in Critical health because the following three services are not running.
1) Process Rpcbind Service Health - Rpcbind Mapper Not Running
2) Process Rpcidmap Service Health - NFSv4 ID Name Mapper Not Running
3) Process Rpcstat Service Health - NSM Status Monitor Not Running
My question is that are these services required to be running in order for SCOM to monitor the Linux servers properly? If yes, can you please give brief explaination as to why so I can explain that to our Linux Administrator. The Linux Administrator
is saying that we do not run these services on any of the Linux servers because they are not needed. If infact these services are not needed, how can I have SCOM ignore the critical error messages? Thanks

Yup, generally running. I'm assuming you've done a basic install of RHEL 6. All processes listed above are enabled by default on a RHEL 6 install if you take the default settings. If someone is just getting started you can pretty much guarantee
they will do a basic install of RHEL 6 and this will not be an issue.
Could it be done better... sure but at what point do you stop? We could discover all services running on the system and start monitoring them out of the box but what are important and what are not to each customer? The idea is to give you some basic monitoring
on a default install based on what each OS provider starts on a "default" install. If this does not suite your needs SCOM is very configurable and adding a custom service monitor is very easy to configure along with disabling existing ones.
If you'd like to provide feedback on this feel free to open a support ticket with Microsoft and file what we call a 'Design Change Request' [DCR]. We go though these prior to starting each update to SCOM. No guarantee it will get fixed/changed as we do have
priorities but we are listening.
Regards,
-Steve

CSCts69270 - CCX CTI ports may stuck in out-of-service state when UCM Upgrade/Restart

Symptom:
CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.
Conditions:
During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .
This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;
The CUCM sate of down ports is "Registered".
The UCCX state of down ports is "Out of Service"
This was tested on following Release branch;
CUCM Version: 8.6.2.10000-30
UCCX Version: 8.5.1.11001-35
JTAPI Version: 8.6(2.10000)-2
CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.
UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.
Workaround:
After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.
Last Modified:
Aug 26,2013
Symptom:
CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.
Conditions:
During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .
This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;
The CUCM sate of down ports is "Registered".
The UCCX state of down ports is "Out of Service"
This was tested on following Release branch;
CUCM Version: 8.6.2.10000-30
UCCX Version: 8.5.1.11001-35
JTAPI Version: 8.6(2.10000)-2
CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.
UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.
Workaround:
After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.
Last Modified:
Aug 26,2013
Known Affected Releases:
(0)
Known Fixed Releases:
(0)

Hello r.mata, do you have a question about this bug? Regards, Wes

The agent extension is out of service. error

The agent extension is out of service.
ready state change and call control operations cannot be performed.
The agent extension is back in service.
all operations are back in service.
I get this when the agent is just sitting there in a ready state.
CUCM 7.0 UCCX 7.0
I would appreciate any help you can offer.
Dave 404 569-1752
[email protected]

The most common cause of this was the agent's phone restarted or a CTI interruption occured. This is typically something to start troubleshooting on UCM side. The CAD Troubleshooting Guide says essentially the same thing:
Problem The agent’s state changed to Not Ready for no apparent reason.
Symptom. In some situations, an agent’s state may change to Not
Ready for no apparent reason.
Cause. To determine the reason, check the reason code:
..other causes removed...
■ If the reason code is 32759, the agent’s state became Not Ready
because the phone went out of service. Check to make sure the
phone is still functional and that you can call the phone directly. If
everything seems fine, it is most likely a temporary problem and the
phone has since recovered. If the phone is still down, it is most
likely a Unified CM problem. Please consult Unified CM support.
Solution In many cases, an agent’s state becoming Not Ready is not a serious
issue. Simply click Ready to change the agent’s state to Ready.
To determine the reason code, do one of the following:
...other solutions removed...
If the reason code is 32759, the agent’s state became Not Ready
because the phone went out of service. Check to make sure the
phone is still functional and that you can call the phone directly. If
everything seems fine, it is most likely a temporary problem and the
phone has since recovered. If the phone is still down, it is most
likely a Unified CM problem. Please consult Unified CM support.

Manager Manager and Prompt Manager going out of service

Hi,
I have set up RTMT to email me syslogs so I can see if there is a problem with UCCX.
Whenever I upload a new prompt or create a new folder I am seeing error messages saying that Manager Manager and Prompt Manager are in partial service.
But when I look at Network Services in Serviceability, there's nothing there - everything is in service.
So the error messages could be incorrect, or the managers are going out of service and then back again into service quickly.
How can I track down this problem/stop it happening?
In one sense it isn't a real problem, but it is annoying as I may ignore real issues.
Thanks
Jemima
UCCX 8.0

Did you try to set it up as new device again? How to back up your data and set up as a new device

UCCX 8 VOIP Monitor Subsystem - Out of Service

Similar Messages

Maybe you are looking for