<?xml version="1.0"?>

<rss version="2.0">


<channel>
<title>Home - All Categories - Telephony &amp; Systems  - Sangoma PBXact  - Troubleshooting &amp; Diagnostics  </title>
<link>https://kb.ic.uk/category/telephony-systems/sangoma-pbxact/troubleshooting-diagnostics/28/</link>
<description>This RSS Feed contains Articles of Category in the knowledge base. You can click on the title to view its content.</description>
<item>
										<guid>https://kb.ic.uk/article/isdn-hangup-cause-codes-3.html</guid>
										<title>ISDN  Hangup Cause Codes</title>
										<link>https://kb.ic.uk/article/isdn-hangup-cause-codes-3.html</link>
										<description><![CDATA[ISDN hangup cause codes provide information as to why a call has been terminated many are shared with SIP.  The list of hangup cause codes below provides detailed information as to the underlying cause behind a call hangup: Code No. 0 This is...]]></description>

									</item>
<item>
										<guid>https://kb.ic.uk/article/wireshark-trace-for-fault-finding-45.html</guid>
										<title>Wireshark Trace for Fault Finding</title>
										<link>https://kb.ic.uk/article/wireshark-trace-for-fault-finding-45.html</link>
										<description><![CDATA[How do I perform a Wireshark trace? If you have been asked to complete a wireshark trace this is because your reported fault needs further inspection from site, these are typically asked for when the report is call quality or transfer difficulties....]]></description>

									</item>
<item>
										<guid>https://kb.ic.uk/article/sip-response-codes-178.html</guid>
										<title>SIP Response Codes</title>
										<link>https://kb.ic.uk/article/sip-response-codes-178.html</link>
										<description><![CDATA[SIP Response Codes 1xx&mdash;Provisional Responses 100 Trying ExtendedThe search being performed may take a significant time so a forking proxy must send a 100 Trying response. 180 Ringing DestinationUser agent received INVITE, and is alerting user...]]></description>

									</item>

</channel>

</rss>