<?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 CUBE initiates an INVITE after 480 Refer Failure in IP Telephony and Phones</title>
    <link>https://community.cisco.com/t5/ip-telephony-and-phones/cube-initiates-an-invite-after-480-refer-failure/m-p/4187421#M393051</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm facing a problem where CUBE initiates two times INVITE after Refer Failure event with 480 Temporary unavailable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The CallFLow is Bellow :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CVP sends Refer to CUBE --&amp;gt; CUBE transfert the REFER message to the ISP with Refer-to Header&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the problem is, after CUBE receives 480 Temporary unavailable NOTIFY Message, it sends 2 times INVITES messages instead of transfering the 480 NOTIFY message to CVP to try another Refer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have any idea to avoid CUBE sending INVITE instead of transferring the 480 NOTIFY message ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Community&lt;/P&gt;</description>
    <pubDate>Mon, 23 Nov 2020 11:07:45 GMT</pubDate>
    <dc:creator>tazi mahmoud</dc:creator>
    <dc:date>2020-11-23T11:07:45Z</dc:date>
    <item>
      <title>CUBE initiates an INVITE after 480 Refer Failure</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/cube-initiates-an-invite-after-480-refer-failure/m-p/4187421#M393051</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm facing a problem where CUBE initiates two times INVITE after Refer Failure event with 480 Temporary unavailable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The CallFLow is Bellow :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CVP sends Refer to CUBE --&amp;gt; CUBE transfert the REFER message to the ISP with Refer-to Header&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the problem is, after CUBE receives 480 Temporary unavailable NOTIFY Message, it sends 2 times INVITES messages instead of transfering the 480 NOTIFY message to CVP to try another Refer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have any idea to avoid CUBE sending INVITE instead of transferring the 480 NOTIFY message ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Community&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 11:07:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/cube-initiates-an-invite-after-480-refer-failure/m-p/4187421#M393051</guid>
      <dc:creator>tazi mahmoud</dc:creator>
      <dc:date>2020-11-23T11:07:45Z</dc:date>
    </item>
  </channel>
</rss>

