<?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: HP Opencall in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687763#M54595</link>
    <description>Hi Bill,&lt;BR /&gt;&lt;BR /&gt;    First of all, thanks for the reply. I am just wondering besides nlog/wlog, is there a simple way i can write a script to monitor the link failures. &lt;BR /&gt;&lt;BR /&gt;    I am having this link problem since we have changed to use from SIU to TSU.</description>
    <pubDate>Wed, 27 Mar 2002 08:02:25 GMT</pubDate>
    <dc:creator>Wong_3</dc:creator>
    <dc:date>2002-03-27T08:02:25Z</dc:date>
    <item>
      <title>HP Opencall</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687761#M54593</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;      Recently, I am having problems with the SS7 links. Besides the nlog and Collectinfo commands, is there any other ways to troubleshoot the signalling network from the unix system?</description>
      <pubDate>Thu, 21 Mar 2002 05:06:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687761#M54593</guid>
      <dc:creator>Wong_3</dc:creator>
      <dc:date>2002-03-21T05:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: HP Opencall</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687762#M54594</link>
      <description>there are literally hundreds of ways.&lt;BR /&gt;&lt;BR /&gt;Try&lt;BR /&gt;&lt;BR /&gt;ll /opt/HP-AIN/SS7/bin/ss7*&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you've got Xwindows bring up the 'nlog' with wlog&lt;BR /&gt;&lt;BR /&gt;Additional logs can be found with wmsg (or nmsg)&lt;BR /&gt;&lt;BR /&gt;Start with ss7TscStatus -L&lt;BR /&gt;&lt;BR /&gt;ss7diag&lt;BR /&gt;&lt;BR /&gt;ss7diag::hostname&amp;gt; help&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Thu, 21 Mar 2002 08:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687762#M54594</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-03-21T08:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: HP Opencall</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687763#M54595</link>
      <description>Hi Bill,&lt;BR /&gt;&lt;BR /&gt;    First of all, thanks for the reply. I am just wondering besides nlog/wlog, is there a simple way i can write a script to monitor the link failures. &lt;BR /&gt;&lt;BR /&gt;    I am having this link problem since we have changed to use from SIU to TSU.</description>
      <pubDate>Wed, 27 Mar 2002 08:02:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-opencall/m-p/2687763#M54595</guid>
      <dc:creator>Wong_3</dc:creator>
      <dc:date>2002-03-27T08:02:25Z</dc:date>
    </item>
  </channel>
</rss>

