7975 for CCM6.0

Dear All
I have CCM6.0 but it does not have 7975 phoone in its list.
how can I add 7975 into CCM6.0 phone list?
thank you

Hi Amir,
When you don't find the IP Phone model listed in the Device defaults you can either install the required Device Pack (which adds the Firmware as well) or upgrade to a supported later CCM Version. Here is the minimum required device Pack for the 7945,7965 and 7975 and CCM 6.0
6.0(1) cmterm-devicepack6.0.1.1102-1
From these release notes;
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7975g/firmware/8_3_2/english/release/notes/75832.html
The latest Device Pack for CCM 6.0 is
cmterm-devicepack6.0.1.2134-2.cop.sgn
http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=6.0(1.2134)&mdfid=280968161&sftType=Unified%20Communications%20Manager/CallManager%20Device%20Packages&optPlat=null&nodecount=2&edesignator=null&modelName=Cisco%20Unified%20Communications%20Manager%20Version%206.0&treeMdfId=278875240&treeName=Voice%20and%20Unified%20Communications&modifmdfid=null&imname=null&hybrid=Y&imst=N&lr=Y
Here is the ReadMe;
Cisco Unified CallManager Device Package 6.0.1 (2134-2)
Release Notes
http://www.cisco.com/web/software/282074299/18327/cmterm-devicepack-6_0_1_2134-2_readme.html
Installation Instructions
Note: Cisco recommends that you apply this Device Package during a maintenance window.
Procedure
NOTE: Apply this patch to all of your Cisco Unified CallManager servers, beginning with the publisher server and TFTP server.
When applying this Device Package to enable new device support, a cluster-wide reboot is required for those devices to register successfully. A clusterwide reboot IS NOT required when running to update existing firmware/support.
For Cisco Unified CallManager 6.0, you must do all software installations and upgrades by using the Software Upgrades menu options. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 6.0.
Using your web browser, login to the Cisco Unified Communications Operating System Administration web page
Under the Software Upgrades menu, select Install/Upgrade.
Fill in the appropriate values in the Software Location section for the file you downloaded above, and click Next.
In the Available Software drop-down box, select the file you downloaded above, and click Next.
After validating the MD5 has the correct value, click Next.
In the Warning box, verify you have selected the correct firmware, then click Install.
Check that you received a Success message.
Note: In order to change the loads manually, you do NOT need to reinstall this Device Package. The new files will be present in the TFTP folder. Go to CCMAdmin->Device->Device Settings->Device Defaults and manually change the name of the load file (for specific device(s)) to the new load and click UPDATE.
Note: If you are rebooting the cluster, the next step does not need to be done.
The Cisco TFTP service now must be stopped and restarted on the TFTP server, then reset the affected devices for them to upgrade to the new load.
Hope this helps!
Rob

Similar Messages

  • 7975 firmware for call manager express

    i would like to add 7975 phone to call manager express.
    where do I get the firmware for 7975 for cme?
    i tried from software.cisco.com but it's for call manager only.

    Hi pranavluhar,
     check this link cme-153-3Mv2.rar (in 10.0 option).There is a 7975 version for CUCME.
    Hope this helps.

  • Extension mobility - can i have 2 extension mobility profiles with the same extension for a 7970 phone and a 7975 phone?

    extension mobility  - can i have 2 extension mobility profiles with the same extension for a 7970 phone and a 7975 phone? thanks

    Yes, or simply configure 1 UDP and default device profile for the other one.
    EDIT: and actually with those models, you should be able to use just one
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100_chapter_011000.html#CUCM_RF_EDCB3C30_00

  • Background Image file for 7975

    What are the file specifications for a custom background image on the Cisco 7975 Ip phone? I mean, the size, resolution, color depth and so on
    Thank you in advance

    The PNG files for background images must meet the following requirements for proper display on the Cisco Unified IP Phone:
    •Full size image-320 pixels (width) X 212 pixels (height).
    •Thumbnail image-80 pixels (width) X 53 pixels (height).
    •Color palette-Includes up to 16-bit color (65535 colors). You can use more than 16-bit color, but the phone will reduce the color palette to 16-bit before displaying the image. For best results, reduce the color palette of an image to 16-bit when you create a PNG file.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7975g/7_0/english/administration/guide/7975cst.html#wp1088046

  • UCM 9.1 7975 Sets can't restrict user preferences

    We have CallManger 9.1 installed and just noticed that we can't restrict the settings on the 7975 sets to only User Preferences - all 7 options are showing
    Is there a patch with the 9.1 for the 7975 sets?

    Mac OS X now uses the clang compiler, and it is possible the package has not been ported to work with the pickier clang compiler.
    If your system has gcc, you could maybe try hacking the Makefile to use gcc instead of cc (or maybe export CC=gcc, again assuming you have an older copy of gcc on your system).  You might also try specifying some CFLAGS to disable some compiler checks.  It is possible you will need to modify the sources to fix obnoxious coding violations that both clang and gcc will not ignore.
    Or you might check if one of the Mac OS X package managers have already ported the package:  http://MacPorts.org, http://brew.sh, http://www.finkproject.org

  • WLST Failed in Oracle BPM Enterprise for Weblogic Server

    Hi,
    I am not getting any clue of resolving the following issue. We are using Oracle BPM Enterprise for Weblogic # 100141. Error details:-
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    t3://192.68.1.3:
    Connecting to t3://192.168.1.3: with userid weblogic ...
    This Exception occurred at Tue Jul 3 :56: IST .
    weblogic.utils.NestedError: Local host not known?!
         at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:9)
         at weblogic.rjvm.JVMID.localID(JVMID.java:8)
         at weblogic.protocol.LocalServerIdentity$SingletonMaker.<clinit>(LocalServerIdentity.java:3)
         at weblogic.protocol.LocalServerIdentity.getIdentity(LocalServerIdentity.java:)
         at weblogic.server.channels.ServerChannelImpl.createDefaultServerChannel(ServerChannelImpl.java:3)
         at weblogic.rjvm.t3.ProtocolHandlerT3$ChannelInitializer.<clinit>(ProtocolHandlerT3.java:3)
         at weblogic.rjvm.t3.ProtocolHandlerT3.getDefaultServerChannel(ProtocolHandlerT3.java:4)
         at weblogic.protocol.ServerChannelManager$SingletonMaker$.getOutboundServerChannel(ServerChannelManager.java:339)
         at weblogic.protocol.ServerChannelManager.findOutboundServerChannel(ServerChannelManager.java:43)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:3)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:94)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:5)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:88)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:53)
         at weblogic.jndi.WLInitialContextFactoryDelegate$.run(WLInitialContextFactoryDelegate.java:344)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
         at weblogic.jndi.Environment.getContext(Environment.java:35)
         at weblogic.jndi.Environment.getContext(Environment.java:85)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:88)
         at javax.naming.InitialContext.init(InitialContext.java:3)
         at javax.naming.InitialContext.<init>(InitialContext.java:9)
         at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:5)
         at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
         at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:35)
         at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:3)
         at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:6)
         at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:5)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
         at java.lang.reflect.Method.invoke(Method.java:59)
         at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:6)
         at org.python.core.PyMethod.__call__(PyMethod.java:96)
         at org.python.core.PyObject.__call__(PyObject.java:48)
         at org.python.core.PyObject.invoke(PyObject.java:6)
         at org.python.pycode._pyx4.connect$(<iostream>:6)
         at org.python.pycode._pyx4.call_function(<iostream>)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyTableCode.call(PyTableCode.java:44)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyFunction.__call__(PyFunction.java:9)
         at org.python.pycode._pyx6.initConfigToScriptRun$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:5)
         at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyTableCode.call(PyTableCode.java:56)
         at org.python.core.PyFunction.__call__(PyFunction.java:69)
         at org.python.pycode._pyx6.f$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:66)
         at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyCode.call(PyCode.java:4)
         at org.python.core.Py.runCode(Py.java:35)
         at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:6)
         at weblogic.management.scripting.WLST.main(WLST.java:9)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
         at java.lang.reflect.Method.invoke(Method.java:59)
         at weblogic.WLST.main(WLST.java:9)
    Caused by: java.net.UnknownHostException: HOME-MITTAL: HOME-MITTAL
         at java.net.InetAddress.getLocalHost(InetAddress.java:353)
         at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:5)
         ... 6 more
    No server running at t3://192.168.1.3: or the user/password is wrong
    Exiting WebLogic Scripting Tool.
    Even I tried using hostname as "localhost" but still I am facing the same issue.
    Please suggest what is the resolution for the same.
    Thanks,
    Abhishek

    Hi,
    I was getting same excepction when tried to configure weblogic server (10.3.3 and 10gR3) through BPM Configuration Wizard, so I end up doing everything manually, like setting up JDBC data sources, JMS Server, JMS Modules and created DB (Directory & Engine).
    Now, I am stuck at the last step of deploying the EAR files generated using BPM Process Administrator, they EAR's are generated fine but while deploying them to Weblogic server (through BPM Process Administrator), getting following exception (for "01-eng-bpmengine.ear")
    <Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpmengine".
    fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: Invalid column type].
         at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
         at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
         at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
         at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1423)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy246.authenticateHumanParticipant(Unknown Source)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy243.connect(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
         at fuego.directory.provider.Factory.startSession(Factory.java:405)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
         at fuego.directory.Directory.startSession(Directory.java:268)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
         at fuego.ejbengine.Engine.start(Engine.java:122)
         at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.sql.SQLException: Invalid column type
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7975)
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
         at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8028)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:238)
         at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:324)
         at fuego.jdbc.FaultTolerantPreparedStatement.setString(FaultTolerantPreparedStatement.java:436)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.setStringAttribute(JDBCPersistenceManager.java:896)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1417)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy246.authenticateHumanParticipant(Unknown Source)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy243.connect(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
         at fuego.directory.provider.Factory.startSession(Factory.java:405)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
         at fuego.directory.Directory.startSession(Directory.java:268)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
         at fuego.ejbengine.Engine.start(Engine.java:122)
         at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    my assumption is JDBC Data Sources or the Directory/Engine database have some column name mismatch.
    Let me know if somebody has a solution for this, or if I am doing something wrong.
    NOTE: just found out that this happens only on Windows 2003 server, but not on OEL5 (Oracle Enterprise Linux 5).
    Thanks !!

  • Support for SPA932 with SPA525G phone on the UC520

    Will the SPA932 be supported with the SPA525G phone on the UC520 in SCCP mode?
    The command for configuring the SPA525G with a SPA932 would be similar to the following when such feature is supported:
    ephone 1
    device-security-mode none
    video
    mac-address 0021.A000.D001
    username jdoe password "jdoe"
    type 525G addon 1 932
    keep-conference
    button 1:1
    I do know that the following addon module combinations are supported on the UC520:
    796x / 7914
    797x / 7914
    7962 / 7915
    7965 / 7915
    7975 / 7915
    7962 / 7916
    7965 / 7916
    7975 / 7916

    There are no plans to support the SPA932 in SCCP mode. A new sidecar will be offered for the CP-500 series and the SPA525G in SCCP mode.
    Thanks,
    Marcos Hernandez
    Technical Marketing Engineer
    Cisco Systems, Inc.

  • 7921 - no outbound audio for pots calls

    I also posted this in IP Telephony. Not sure which section is more appropriate for my problem, but I really need help here.
    I have an odd problem.
    I have a 7921, which registers as it should in an CUCME 8.6 environment.
    4 ephones, (3) 7975G and (1) 7921. One incoming / outgoing pots line. No voip.
    My problem:
    calls made from the 7921 to internal extensions work perfectly. Audio in both directions.
    Calls made from the 7975's to internal extensions and to external numbers via pots (VIC2-2FXO) work perfectly - audio in both directions.
    Calls made from the 7921 to external numbers via pots, however, have no outgoing audio. Inbound audio works fine.
    Any ideas? Config is attached

    Duplicate post. 
    Go HERE.

  • Localization / language support for 6941/6961

    Hi,
    I have a UC540 with package 8.1.0 and several different IP-Phones.
    (509, 525, 6941, 6961, 7962, 7965, 7975)
    UC, CUE and phones are configured for germany and it works,
    only the 6941 an 6961 are still in english ...
    Firmware of the 69xx: cmterm-69xx-sccp.9-1-1-sr1.zip
    Any ideas?
    Kind regards, DetNit

    Maybe you should check database encoding...
    But, when you modify message catalog and use - lets say win-1250 encoding - you must use native2ascii tool to convert it to ascii7 (the troublemaking characters will be stored in \uXXXX form)

  • CCM6.0 with no default 50 license unit

    Hi all,
    I wanted to try out new features in CCM6.0 but I do not have a license. I read somewhere that CCM6.0 comes with 50 license units by default. I installed CCM5.1 (with 0 license) into a VMWare machine and then upgraded it to CCM6.0.1.2000-3. Is there anyway to regenerate back the default 50 license unit as I see that after upgrading, I still see 0 license? Thanks.

    Cisco Unified Communications Manager comes preinstalled with starter licenses, so a file upload is not required. Starter licenses have no expiration date and are available in limited quantities. Be aware that starter licenses are only available for fresh installations; they are not available for upgrades or migrations from previous releases. Starter licenses support only one Cisco Unified Communications Manager node and up to 50 device license units.
    Starter license units get replaced when you purchase a production license.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/cucm-rel_note-601a.html#wp45773

  • How to unbrick CISCO 7975

    Does anybody know how to unbrick a CISCO 7975? I have tried to do the factory reset wiht no success..Help!

    Hi
    The phone will do the following things:
    1) Request DHCP
    2) If it gets option 150 succesfully (or some other options, but option 150 is the common one) it will attempt to TFTP files from the option 150 IP address
    3) It will try to download term75.default.loads, which contains a list of the required firmware files (you can open that file and see them in notepad to verify you have the correct ones)
    4) It will then download each of those files and install them
    So - if you are confident you have DHCP and Option 150 set up, you can debug or monitor the logs on your TFTP server to see whether you can see the reuqests for files, and whether they are succesful.
    If you don't have DHCP/Option 150 set up, start by setting that up.
    Regards
    Aaron
    Please rate helpful posts...

  • Downloading Firmware into 7975 from CUCM

                       Hello All,
    I have Issues with a 7975 IP phone downloading firmware and registering with call manager 7.1. The IP Phone is for cts 1300 and its new whenever i connect to the cucm its shows the file SIP.75.9-0-2SR1S to be downloaded but suddenly shows Auth fail , it keeps showing the same all over. Please what do you think can be done to make me the phone register with the call manager. or is there another way that I can load the firmware into the phone without connecting to the call manager.

    Search for "Auth fail" here and you will find many similar posts.
    It is either that your current firmware is too old and you need 2 steps upgrade, or it may be ITL cert issue.
    HTH,
    Chris

  • 7975 Not showing Extension Mobility service

    I'm seeing an odd difference in behavior between 7970 and 7975 phone models surrounding Extension Mobility. This is on a UCM 6.1(2) install.
    The environment has been using 7970 as their primary production phone model for some time. Extension Mobility has been configured without issue and working as expected.
    The first batch of 7975 phones arrived last week for new users. The same process was followed to enable EM on these phones (enable Extension Mobility and subscribe the service to the device); however, when the Services button is pressed, the service does not appear as an option. There is no error displayed on the device, the list is just blank.
    Has anyone run into this or have ideas what has changed in the 7975 XML behavior?

    When you use firmware release 8.3(3) with Cisco Unified Communications Manager 6.x, you must use Cisco Unified Communications Manager engineering special release. If this is not used, you will receive an XML parse error when you login or logout of a Cisco Unified IP Phone. Take a look at this bug“CSCsj79645”.

  • What is the correct XML request for ccm 6.0

    Hi,
    i m tring to get getphone-data from my ccm6.0 with a axl call.
    here is what i have, which is a example out of the toolkit, i guess its old, so it doesnt work with my ccm6.0
    xmlhttp.Open("POST", "http://" + ccmserver + "/CCMApi/AXL/V1/soapisapi.dll", false);
    xmlhttp.setRequestHeader("Authorization", "Basic " + authstring);
    xmlhttp.setRequestHeader("Content-type", "text/xml");
    xmlhttp.Send(xmlDoc);
    can anyone help me and share the correct lines for this request?
    thanks

    yeah.. my java programm with the soap call, which works fine, is using
    http://myserver/AXL/
    i tryied it in my jva-script, but its not working, i also tried https, but in both cases i dont even get an entry in the trace files..:-((
    here is what i use in my java programm
    sAXLSOAPRequest = "POST /axl/ HTTP/1.0\r\n";
    sAXLSOAPRequest += "xxxxxxxxx:8443\r\n";
    sAXLSOAPRequest += "Authorization: Basic " + authorization + "\r\n";
    sAXLSOAPRequest += "Accept: text/*\r\n";
    sAXLSOAPRequest += "Content-type: text/xml\r\n";
    sAXLSOAPRequest += "SOAPAction: \"CUCM:DB ver=6.0\"\r\n";
    sAXLSOAPRequest += "Content-length: ";
    and in my java-script i tryied..
    xmlhttp.Open("POST", "http://" + ccmserver + "/AXL/", false);
    xmlhttp.setRequestHeader("Authorization", "Basic " + authstring);
    xmlhttp.setRequestHeader("Content-type", "text/xml");
    xmlhttp.Send(xmlDoc);
    but with no success..:-((
    can anybody help?
    thanks

  • CUCM 9.1 Phone 7975 upgradation issue

    Hi
    Recently we upgraded CUCM 7.1.5 to CUCM 9.1.
    IP Phone 7975 old firmware was 9.0.x and cucm 9.1 was loaded with firmware 9.3.x
    somehow 7975 phones didnt upgraded firmware to version 9.3.x
    Also noticed when we factory reset 7975 phones, it loaded SIP firmware....! But that phone is added as sccp.
    Once we delete and reconfigured the phone, then only phone firmware upgraded to 9.3.x.
    Any sugestion, why IP phone 7975 not taking firmware version 9.3.x? also when we did factory reset why it is loading with sip firmware ?
    we have 7911 phones, those phones taken new firmware without any problem.
    cucm ip : 192.168.17.1 and 2
    I have attached IP phone span PC wireshark capture and IP Phone console log and version screenshot.
    Pls. suggest
    Rgds
    Rajesh kumar

    Looks like this phone has a problem parsing it's configuration file, given the firmware version it should upgrade to is contained within that config that would indicate why.
    If you have a look in file 'log3' there are the following entries:
    697: ERR 14:08:30.663131 JVM: Startup Module Loader|cip.xml.ap:  - XML Parser Exception: name expected (position:START_TAG @113:2 in java.io.InputStreamReader@3a4675)  (line=113)
    698: ERR 14:08:30.664676 JVM: Startup Module Loader|cip.cfg.s:? - ERROR PARSING CONFIG file:ram/SEP1C17D337295A.cnf.xml
    699: NOT 14:08:30.666919 JVM: Startup Module Loader|cip.cfg.s:? - Config processConfigNoError() result code=CONFIG_FILE_BAD_FORMAT
    If you have a look at this post it relates to this error and should help you to resolve the issue:
    https://supportforums.cisco.com/thread/2129364
    It would appear that the config file includes a tag, if you open the config file for the phone:
    http://192.168.17.1:6970/SEP1C17D337295A.cnf.xml
    Then hopefully you can locate the null entry (should be line 113 of that file), go to UCM and set the corresponding parameter (i.e. under Common Phone Profile), that should hopefully prevent the null entry from being generated in the config file and allow the config file to be parsed correctly.
    If you are still having issues post the config file and I'll have a closer look, it wasn't in the packet capture.
    Thanks
    Stephen Welsh
    CTO
    http://www.unifiedfx.com

Maybe you are looking for