<?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: Insufficient Bandwidth error in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573697#M2113</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The error is likely due to 'region' settings for bandwidth allocation and call quality: &lt;A href="https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.html#anc16" title="https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.html#anc16"&gt;https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.…&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding is that call signaling and media setups are somewhat decoupled, which may explain why you receive a brief bit of RTP...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure if there are any special considerations or handling with a HCS situation - hopefully between the customer admin and HCS support, they can review the recording architecture vs. their current config, and adjust region/bandwidth settings as needed to accommodate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 May 2018 21:09:16 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2018-05-23T21:09:16Z</dc:date>
    <item>
      <title>Insufficient Bandwidth error</title>
      <link>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573695#M2111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking at integrating our call-record platform to work with Cisco HCS, and am having difficulty with the forked audio call. I have set up a recording profile, built-in-bridge etc in CUCM but when I receive the call, it shortly clears with a BYE containing:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warning: 370 172.27.199.11 "Insufficient Bandwidth"&lt;/P&gt;&lt;P&gt;Reason: Q.850; cause=125&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is after 5 RTP packets. Am I supposed to send RTP back, or RTCP? Also, shouldn't there be a second audio stream?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Apr 2018 16:22:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573695#M2111</guid>
      <dc:creator>ShoutTelecoms</dc:creator>
      <dc:date>2018-04-24T16:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Bandwidth error</title>
      <link>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573696#M2112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Please check this url for related info - &lt;A href="https://community.cisco.com/docs/DOC-49341"&gt;Multiple RTP packets recording&lt;/A&gt;. moving your question under UC Manager SIP community for more visibility of support engineers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Geevarghese&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2018 10:52:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573696#M2112</guid>
      <dc:creator>Geevarghese Cheria</dc:creator>
      <dc:date>2018-05-23T10:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Bandwidth error</title>
      <link>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573697#M2113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The error is likely due to 'region' settings for bandwidth allocation and call quality: &lt;A href="https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.html#anc16" title="https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.html#anc16"&gt;https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/telepresence-codec-c40/119207-ts-failures-end-ccm-00.…&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My understanding is that call signaling and media setups are somewhat decoupled, which may explain why you receive a brief bit of RTP...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure if there are any special considerations or handling with a HCS situation - hopefully between the customer admin and HCS support, they can review the recording architecture vs. their current config, and adjust region/bandwidth settings as needed to accommodate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2018 21:09:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/insufficient-bandwidth-error/m-p/3573697#M2113</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2018-05-23T21:09:16Z</dc:date>
    </item>
  </channel>
</rss>

