<?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: ATA 192 Not registering in IP Telephony and Phones</title>
    <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967224#M412938</link>
    <description>&lt;P&gt;As the ATA192 is a MPP device, to what type of service are you trying to get it to register with?&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2023 06:34:20 GMT</pubDate>
    <dc:creator>Roger Kallberg</dc:creator>
    <dc:date>2023-11-28T06:34:20Z</dc:date>
    <item>
      <title>ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967136#M412934</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello Community,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have a problem with an ATA 192 not registering, so I need your help!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the navigation under "Voice" -&amp;gt; "Information" it says "Registration State: Failed". &lt;/SPAN&gt;&lt;SPAN&gt;In the navigation under "Administration" -&amp;gt; "Debug Log Viewer" it says "Warning: 399 spa \'STUN Server Not Reachable\'" after it tries to register. Next thing I get is "REGISTER Reason: SIP;cause=401;text=\'CC_SIP_UNAUTHORIZED_401\'".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I can provide the full log if it's necessary.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I really would appreciate any help!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 22:31:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967136#M412934</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-11-27T22:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967224#M412938</link>
      <description>&lt;P&gt;As the ATA192 is a MPP device, to what type of service are you trying to get it to register with?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 06:34:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967224#M412938</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2023-11-28T06:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967275#M412939</link>
      <description>&lt;P&gt;I'm an end-user and trying to register the ATA at my internet service providers network. The ATA is set up in bridge mode and connected to an existing router.&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285777"&gt;@Roger Kallberg&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 08:31:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967275#M412939</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-11-28T08:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967335#M412942</link>
      <description>&lt;P&gt;So you have got the required information for how to setup it up with your service provider SIP service?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 10:11:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967335#M412942</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2023-11-28T10:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967365#M412944</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285777"&gt;@Roger Kallberg&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Yes, I got the information from the official website:&lt;BR /&gt;&lt;A href="https://www.telekom.de/hilfe/werksreset-speedport/werksreset-faq/einrichtung-sip-client" target="_blank"&gt;https://www.telekom.de/hilfe/werksreset-speedport/werksreset-faq/einrichtung-sip-client&lt;/A&gt;&lt;BR /&gt;It looks like this:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Web Oberfläche.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/203576iD058EA873BDB8173/image-size/large?v=v2&amp;amp;px=999" role="button" title="Web Oberfläche.png" alt="Web Oberfläche.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;I also port forwarded the ports 5060 - 5061 for SIP and 16384 - 16482 for RTP in my Router.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 11:07:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967365#M412944</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-11-28T11:07:23Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967418#M412946</link>
      <description>&lt;P&gt;Have a look at this excellent &lt;A href="http://ucpros.net/cube-configuration-part-1/" target="_self"&gt;blog&lt;/A&gt; for details on how to troubleshoot SIP registration. It's written for IOS and CM, but in general it is universal applicable. There is a specific part where use of a SIP client, like MicroSIP, is used to verify that the registration credentials/information is operational. That's very useful when you're dealing with issue like you're seeing as it's not always a 100% certain that the information given is absolutely correct.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 12:45:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967418#M412946</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2023-11-28T12:45:46Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967769#M412960</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285777"&gt;@Roger Kallberg&lt;/a&gt;Thanks for this promising suggestion! I will take a deeper look into it on the weekend, and will report back whether I can get it to work or not.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 23:34:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4967769#M412960</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-11-28T23:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970497#M413025</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285777"&gt;@Roger Kallberg&lt;/a&gt;Hello again!&lt;BR /&gt;I could find out what the problem is with the help of the blog article about SIP response codes. After the error 401, I get a TP Parser error: 15, which is described &lt;A href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/MPP/8800/firmware/11-3-1SR3/p881_b_8800-rn-1131sr3.html#task_E59D2EB8B52D0A479FC023DB8086B11E" target="_self"&gt;here&lt;/A&gt; as an error that appears "when tag on header in INVITE contains more than 79 characters". The tag from my ISP contains 114 characters, sometimes even 124 characters.&lt;BR /&gt;&lt;BR /&gt;It seems like I'm dependent on a patch by Cisco because, on the ATA 192, it's not fixed.&lt;BR /&gt;Do you know a way to report this bug to Cisco without a service contract since I'm just an end-user and don't have one?&lt;/P&gt;</description>
      <pubDate>Sun, 03 Dec 2023 10:48:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970497#M413025</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-12-03T10:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970514#M413027</link>
      <description>&lt;P&gt;No I don’t know how to do that, not sure if it’s even possible. I think you’re best option is to reach out to your operator and discuss this with them.&lt;/P&gt;</description>
      <pubDate>Sun, 03 Dec 2023 11:44:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970514#M413027</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2023-12-03T11:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970518#M413028</link>
      <description>&lt;P&gt;What version do you have on your ATA192? The latest version is this one from what I can tell.&amp;nbsp;&lt;A href="https://software.cisco.com/download/home/286319445/type/282074215/release/11.2.4" target="_blank"&gt;https://software.cisco.com/download/home/286319445/type/282074215/release/11.2.4&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 03 Dec 2023 11:52:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970518#M413028</guid>
      <dc:creator>Roger Kallberg</dc:creator>
      <dc:date>2023-12-03T11:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970565#M413033</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/285777"&gt;@Roger Kallberg&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;No I don’t know how to do that, not sure if it’s even possible. I think you’re best option is to reach out to your operator and discuss this with them.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;That's a bummer, but thanks anyway!&lt;/P&gt;</description>
      <pubDate>Sun, 03 Dec 2023 15:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970565#M413033</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-12-03T15:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: ATA 192 Not registering</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970566#M413034</link>
      <description>&lt;P&gt;I'm on the latest 11-2-4MPP0001-115 Aug 9 2023 and it's not patched here.&lt;/P&gt;</description>
      <pubDate>Sun, 03 Dec 2023 15:22:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/ata-192-not-registering/m-p/4970566#M413034</guid>
      <dc:creator>LveIceFire</dc:creator>
      <dc:date>2023-12-03T15:22:34Z</dc:date>
    </item>
  </channel>
</rss>

