<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IP phone works abnormal. in Unified Communications Infrastructure</title>
    <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420006#M82916</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hailey.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out what caused the problem. it is CTI Manager service. when I stop CTI manager. all things are normal.&lt;/P&gt;&lt;P&gt;and only when I start CTI manager, it works wrong.&lt;/P&gt;&lt;P&gt;do you know what CTI manager is and is it nessasary to keep starting ? or&lt;/P&gt;&lt;P&gt;is it ok to stop the service ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Apr 2010 02:40:48 GMT</pubDate>
    <dc:creator>sang-bong.lee</dc:creator>
    <dc:date>2010-04-13T02:40:48Z</dc:date>
    <item>
      <title>IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420002#M82912</link>
      <description>&lt;P&gt;Hi there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not good at eng , so please understand me. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;since several weeks ago,. ip desk phone is working abnormal.&lt;/P&gt;&lt;P&gt;I called to someone and he got a call. then he can hear hold sound even tough I didn't push hold button.&lt;/P&gt;&lt;P&gt;it got back to normal after I turned off CUCM publish server and it's working abnormal again after few minutes or few days.&lt;/P&gt;&lt;P&gt;I haven't found anything wrong in config in CUCM and&lt;/P&gt;&lt;P&gt;there was no setting which make phone on hold automatically.. I'm using CUCM 4.1(3) version..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyone who can help me ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 07:42:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420002#M82912</guid>
      <dc:creator>sang-bong.lee</dc:creator>
      <dc:date>2019-03-19T07:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420003#M82913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the status of the DB replication within the cluster using the DBHelper app or directly within SQL Enterprise Manager.&amp;nbsp; Post back on the status of DB replication and we'll go from there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hailey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Apr 2010 13:30:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420003#M82913</guid>
      <dc:creator>David Hailey</dc:creator>
      <dc:date>2010-04-02T13:30:34Z</dc:date>
    </item>
    <item>
      <title>Re: IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420004#M82914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hailey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I excuted SQL Server Enterprise Manager. but I don't know where I should check&lt;/P&gt;&lt;P&gt;when I look at replication status. it's idle status . do I need to start it ?&lt;/P&gt;&lt;P&gt;could you please refer attached file ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Apr 2010 01:03:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420004#M82914</guid>
      <dc:creator>sang-bong.lee</dc:creator>
      <dc:date>2010-04-07T01:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420005#M82915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your replication is good.  The "Replication Monitor" icon is green.  If replication were bad, it would have a red X over it.  The next step, with 4.1(3), would be to reset the cluster.  When you rebooted the Publisher, that was a good idea.  But, your phones should be homed to the Subscriber and it may have things cached in memory that only a reboot will resolve.  Personally, I would schedule some downtime - reboot the Publisher again and let it come online and confirm server health.  Then, reboot the Subscriber and once it comes back online then verify replication, phone registration, etc.  Then, try to recreate the issue again on the phone after the cluster reset.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hailey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Apr 2010 13:33:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420005#M82915</guid>
      <dc:creator>David Hailey</dc:creator>
      <dc:date>2010-04-07T13:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420006#M82916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hailey.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out what caused the problem. it is CTI Manager service. when I stop CTI manager. all things are normal.&lt;/P&gt;&lt;P&gt;and only when I start CTI manager, it works wrong.&lt;/P&gt;&lt;P&gt;do you know what CTI manager is and is it nessasary to keep starting ? or&lt;/P&gt;&lt;P&gt;is it ok to stop the service ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Apr 2010 02:40:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420006#M82916</guid>
      <dc:creator>sang-bong.lee</dc:creator>
      <dc:date>2010-04-13T02:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: IP phone works abnormal.</title>
      <link>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420007#M82917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CTI = Computer Telephony Integration.&amp;nbsp; I don't think that this is the actual cause of your problem unless there is something I don't know about your situation.&amp;nbsp; Here is what the CTI Manager Service does:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;The CTI Manager contains the CTI components that&amp;nbsp; interface with applications. With CTI Manager, applications can access&amp;nbsp; resources and functionality of all Cisco CallManagers in the cluster and&amp;nbsp; have improved failover capability. One or more CTI Managers can be&amp;nbsp; active in a cluster, but only one CTI Manager can exist on an individual&amp;nbsp; server. An application (JTAPI/TAPI) can have simultaneous connections&amp;nbsp; to multiple CTI Managers; however, an application can only use one&amp;nbsp; connection at a time to open a device with media termination. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CTI Manager is required in a cluster for applications that use TAPI or&amp;nbsp; JTAPI Computer Telephony Integration (CTI). The CTI Manager acts as a&amp;nbsp; broker between the CTI application and the Cisco CallManager Service. It&amp;nbsp; provides authentication of the application and enables control or&amp;nbsp; monitoring of authorized devices. The CTI application communicates with a&amp;nbsp; primary CTI Manager and, in the event of a failure, will switch to a&amp;nbsp; backup CTI Manager. The CTI Manager should be enabled only on call&amp;nbsp; processing subscribers, thus allowing for a maximum of eight CTI&amp;nbsp; Managers in a cluster. Cisco recommends that you load-balance CTI&amp;nbsp; applications across the various CTI Managers in the cluster to provide&amp;nbsp; maximum resilience, performance, and redundancy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the primary CTI Services on the CCM:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="pBl_BlockLabel"&gt;&lt;STRONG&gt; Cisco IP Manager Assistant &lt;/STRONG&gt;&lt;/P&gt;&lt;P class="pBl_BlockLabel"&gt;&lt;/P&gt;&lt;A name="wp1063730"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;When activated, Cisco IP Manager Assistant enables managers and their&amp;nbsp; assistants to work together more effectively. Cisco IPMA supports two&amp;nbsp; modes of operation: proxy line support and shared line support. The&amp;nbsp; Cisco IPMA service supports both proxy line and shared line support in a&amp;nbsp; cluster. Refer to the&lt;SPAN style="color: black; font-style: italic; font-weight: normal;"&gt; Cisco CallManager Features and Services Guide&lt;/SPAN&gt;.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;A name="wp1063732"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;The feature comprises a call-routing service, enhancements to phone&amp;nbsp; capabilities for the manager, and desktop interfaces that are primarily&amp;nbsp; used by the assistant.&lt;/P&gt;&lt;A name="wp1063734"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;The service intercepts calls that are made to managers and routes them&amp;nbsp; to selected assistants, to managers, or to other targets on the basis of&amp;nbsp; preconfigured call filters. The manager can change the call routing&amp;nbsp; dynamically; for example, by pressing a softkey on the phone, the&amp;nbsp; manager can instruct the service to route all calls to the assistant and&amp;nbsp; can receive status on these calls.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;A name="wp1063736"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Cisco CallManager users comprise managers and assistants. The routing&amp;nbsp; service intercepts manager calls and routes them appropriately. An&amp;nbsp; assistant user handles calls on behalf of a manager. Cisco IPMA&amp;nbsp; comprises features for managers and features for assistants.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;STRONG&gt;&lt;A name="wp1042704"&gt;&lt;/A&gt;&lt;A name="wpmkr1059549"&gt;&lt;/A&gt;&lt;A name="wpxref34211"&gt;&lt;/A&gt;&lt;/STRONG&gt;&lt;P class="pBl_BlockLabel"&gt;&lt;STRONG&gt; Cisco WebDialer Web Service &lt;/STRONG&gt;&lt;/P&gt;&lt;P class="pBl_BlockLabel"&gt;&lt;/P&gt;&lt;A name="wp1042705"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;Cisco WebDialer provides click-to-dial functionality. It allows users in&amp;nbsp; a Cisco CallManager cluster to initiate a call to other users inside or&amp;nbsp; outside the cluster by using a web page or a desktop application. Cisco&amp;nbsp; WebDialer provides a web page that enables users to call each other&amp;nbsp; within a cluster. Cisco WebDialer comprises two components: WebDialer&amp;nbsp; servlet and Redirector servlet.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;A name="wp1042706"&gt;&lt;/A&gt;&lt;P class="pB1_Body1"&gt;The Redirector servlet provides the ability for third-party applications&amp;nbsp; to use Cisco WebDialer. The Redirector servlet finds the appropriate&amp;nbsp; Cisco CallManager cluster for the WebDialer user and redirects the&amp;nbsp; request to the WebDialer in that cluster. The Redirector functionality&amp;nbsp; only applies for HTTP/HTML-based WebDialer client applications because&amp;nbsp; it is not available for Simple Object Access Protocol (SOAP)-based&amp;nbsp; WebDialer applications.&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;If starting/stopping the CTI service seems to resolve your problem, then I would ask if these phones are being controlled or monitored by any CTI applications (ex: IPCC/IPCCX)...if not, then I would be suspicious of a bug or something else at play.&amp;nbsp; Do you have up-to-date TAC support for your system?&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;Hailey&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;Please rate helpful posts!&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P class="pB1_Body1"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Apr 2010 03:09:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/unified-communications-infrastructure/ip-phone-works-abnormal/m-p/1420007#M82917</guid>
      <dc:creator>David Hailey</dc:creator>
      <dc:date>2010-04-13T03:09:05Z</dc:date>
    </item>
  </channel>
</rss>

