<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with register]]></title><description><![CDATA[A list of topics that have been tagged with register]]></description><link>https://forum.netgate.com/tags/register</link><generator>RSS for Node</generator><lastBuildDate>Tue, 12 May 2026 10:28:23 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/tags/register.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[PPPoE and VOIP Web base phone registration issue pfsense 2.7.2]]></title><description><![CDATA[Ok I don't know why but when testing it this weekend it was working. I did not change anything neither did I reinstall and fresh setup.
Would this have to do with the static routing that was setup previously but the device it was pointing to was removed the same day it was setup till recently when the client went over to the new system and was installed again. I mean it makes sens that the pbx server was speaking to the firewall and the firewall was pointing to a device on the network that was not available.
NAT is now disabled and siproxd is kinda setup.
I'll arrange to test the DNS rebinding check to disable and the preferred work around and the same for Browser HTTP_REFERER enforcement and get back if it works now. Though the client registration  check for the App was an issue even before static routing was setup.
Please let me know if there is clarity needed.
]]></description><link>https://forum.netgate.com/topic/190419/pppoe-and-voip-web-base-phone-registration-issue-pfsense-2-7-2</link><guid isPermaLink="true">https://forum.netgate.com/topic/190419/pppoe-and-voip-web-base-phone-registration-issue-pfsense-2-7-2</guid><dc:creator><![CDATA[IT Kyle]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[TAC Support Expired - Can&#x27;t re-register with new token]]></title><description><![CDATA[@dylanc23
Did that and was helped very quickly! Thank you very much! This thread can be locked if you have those permissions.
]]></description><link>https://forum.netgate.com/topic/183213/tac-support-expired-can-t-re-register-with-new-token</link><guid isPermaLink="true">https://forum.netgate.com/topic/183213/tac-support-expired-can-t-re-register-with-new-token</guid><dc:creator><![CDATA[dlarmore]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>