<?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: JTAPI API for Silent and Whisper in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4123969#M2939</link>
    <description>&lt;P&gt;Actually Whisper &amp;amp; Barge are not supported in Jabber 12.9 also. Here is the Cisco doc-&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_feature-configuration-for-jabber-129/cjab_b_feature-configuration-for-jabber-129_chapter_0100.html#reference_6593FBAC29C21F27B64439EFB7614297" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_feature-configuration-for-jabber-129/cjab_b_feature-configuration-for-jabber-129_chapter_0100.html#reference_6593FBAC29C21F27B64439EFB7614297&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess you are using UpdateMonitorType. Can you try with startMonitor API and pass the monitor type value as whisper.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Umesh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jul 2020 05:11:06 GMT</pubDate>
    <dc:creator>upchaurasia</dc:creator>
    <dc:date>2020-07-23T05:11:06Z</dc:date>
    <item>
      <title>JTAPI API for Silent and Whisper</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4123960#M2938</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question regarding JTAPI usage and the following are my scenarios:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Scenario 1:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Silent and Whisper functionalities are added on a gadget on Finesse desktop&lt;/P&gt;&lt;P&gt;2. Two (2) workstations are used each for Supervisor and Agent (total of 4) .&lt;/P&gt;&lt;P&gt;3. Supervisor - Workstation 1 (laptop) has local Jabber 12.8 but doing a remote desktop to Workstation 2 to access Finesse due to limited accessibility and network structure of the client.&lt;/P&gt;&lt;P&gt;4. Agent - Workstation 3 (laptop) has local Jabber 12.8 but doing a remote desktop to Workstation 4 to access Finesse due to limited accessibility and network structure of the client.&lt;/P&gt;&lt;P&gt;5. Supervisor and Agent are both using local Jabber on Workstation 1 and 3 and using laptop speakers.&lt;/P&gt;&lt;P&gt;6. Mobile phone over PSTN is used to call the Agent.&lt;/P&gt;&lt;P&gt;7. On Silent monitoring, Mobile phone is not hearing the supervisor (expected).&lt;/P&gt;&lt;P&gt;8. On Whisper, Mobile phone can hear the supervisor (expected is Mobile phone &lt;STRONG&gt;should not &lt;/STRONG&gt;hear).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Scenario 2:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Silent and Whisper functionalities are added on a gadget on Finesse desktop&lt;/P&gt;&lt;P&gt;2. Two (2) workstations are used each for Supervisor and Agent (total of 4) .&lt;/P&gt;&lt;P&gt;3. Supervisor - Workstation 1 (laptop) has local Jabber 12.8 but doing a remote desktop to Workstation 2 to access Finesse due to limited accessibility and network structure of the client.&lt;/P&gt;&lt;P&gt;4. Agent - Workstation 3 (laptop) has local Jabber 12.8 but doing a remote desktop to Workstation 4 to access Finesse due to limited accessibility and network structure of the client.&lt;/P&gt;&lt;P&gt;5. Supervisor and Agent are both using local Jabber on Workstation 1 and 3. &lt;FONT color="#808000"&gt;Supervisor is on headset and Agent's microphone are turned off.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;6. Mobile phone over PSTN is used to call the Agent.&lt;/P&gt;&lt;P&gt;7. On Silent monitoring, Mobile phone is not hearing the supervisor (expected).&lt;/P&gt;&lt;P&gt;8. On Whisper, Mobile phone can hear the supervisor (expected is Mobile phone &lt;STRONG&gt;should not &lt;/STRONG&gt;hear).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using CiscoTerminalConnection.updateMonitorType to do the Whisper and Finesse API to do the Silent Monitoring.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Anyone have done whisper using JTAPI and Jabber and the result is the phone calling the agent doesn't hear the one monitoring the call?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2020 04:32:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4123960#M2938</guid>
      <dc:creator>liam123</dc:creator>
      <dc:date>2020-07-23T04:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: JTAPI API for Silent and Whisper</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4123969#M2939</link>
      <description>&lt;P&gt;Actually Whisper &amp;amp; Barge are not supported in Jabber 12.9 also. Here is the Cisco doc-&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_feature-configuration-for-jabber-129/cjab_b_feature-configuration-for-jabber-129_chapter_0100.html#reference_6593FBAC29C21F27B64439EFB7614297" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_feature-configuration-for-jabber-129/cjab_b_feature-configuration-for-jabber-129_chapter_0100.html#reference_6593FBAC29C21F27B64439EFB7614297&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess you are using UpdateMonitorType. Can you try with startMonitor API and pass the monitor type value as whisper.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Umesh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2020 05:11:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4123969#M2939</guid>
      <dc:creator>upchaurasia</dc:creator>
      <dc:date>2020-07-23T05:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: JTAPI API for Silent and Whisper</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4126587#M2942</link>
      <description>&lt;P&gt;Hi Umesh,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The startMonitor&amp;nbsp; method works for Jabber-Jabber and Jabber-Desk phone. We will be testing other scenarios like Desk phone - Jabber (incoming/outgoing).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By the way, any idea regarding the difference between startMonitor and updateMonitor on the code level? Not sure why effects are different.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Liam&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jul 2020 10:45:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4126587#M2942</guid>
      <dc:creator>liam123</dc:creator>
      <dc:date>2020-07-28T10:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: JTAPI API for Silent and Whisper</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4126597#M2943</link>
      <description>&lt;P&gt;Nothing mine it's PARSEC expertise in Cisco APIs (CUCM/UCCX/UCCE/CVP/Finesse). We do lot of R&amp;amp;D related to Cisco APIs.&lt;/P&gt;&lt;P&gt;I am happy that solution worked for you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Umesh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jul 2020 11:21:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-api-for-silent-and-whisper/m-p/4126597#M2943</guid>
      <dc:creator>upchaurasia</dc:creator>
      <dc:date>2020-07-28T11:21:44Z</dc:date>
    </item>
  </channel>
</rss>

