<?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: CU Command: Fax modem check in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724954#M945958</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;If I were you I would look into a utility call 'Pcomm+' available at a modest cost from:&lt;BR /&gt;&lt;A href="http://www.rtr.com/Ready-to-Run_Software/communication_readypak.htm." target="_blank"&gt;http://www.rtr.com/Ready-to-Run_Software/communication_readypak.htm.&lt;/A&gt; Pcomm+ is part of their 'CommPak for UNIX'.&lt;BR /&gt; &lt;BR /&gt;It has a scripting language which can timeout, look for regular expressions (more or less), and send/receive characters from a tty line. It will handle all the dialing and handshake stuff for you. You can also return status codes to an external program (in this case a shell script). You will have to write a sqlplus command to extract the phone numbers and then let your shell script build a pcomm+ batch file 'on the fly'. &lt;BR /&gt;&lt;BR /&gt;I have used this method to build rather complex&lt;BR /&gt;modem transfer programs.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 15 May 2002 21:17:37 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2002-05-15T21:17:37Z</dc:date>
    <item>
      <title>CU Command: Fax modem check</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724953#M945957</link>
      <description>Hi all. I have a sort of odd request from my project manager. It seems the customers (users) from another division have been getting a number of reports of missing or failed fax transactions (through our 3rd party VSIFax program). Sometimes the fax numbers stored in the database are busy or non-functioning, so the only way to check is for us to check them one at a time (and we are talking nearly 500+ fax numbers overall). VSIFax has failed to point us to a method of 'pre-checking' the numbers/lines so I am turning here.&lt;BR /&gt;&lt;BR /&gt;Is it possible to use the 'cu' command to do the following (?):&lt;BR /&gt;&lt;BR /&gt;From a Oracle database, extract a fax number. Then using a function in the script, plug in the fax number into a command like: 'cu -l ttyd1p0 -m dir $1'... Where the cu program will connect to the MUX (where the modem is located) and dial the number. &lt;BR /&gt;&lt;BR /&gt;If the modem connects with the fax tone, it could be drop the connection and return 'Fax Ready'. If it returned a busy tone, the result would be 'Busy'. Otherwise it just returns NO CARRIER.&lt;BR /&gt;&lt;BR /&gt;-- M&lt;BR /&gt;</description>
      <pubDate>Wed, 15 May 2002 20:55:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724953#M945957</guid>
      <dc:creator>Michael Worsham</dc:creator>
      <dc:date>2002-05-15T20:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: CU Command: Fax modem check</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724954#M945958</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;If I were you I would look into a utility call 'Pcomm+' available at a modest cost from:&lt;BR /&gt;&lt;A href="http://www.rtr.com/Ready-to-Run_Software/communication_readypak.htm." target="_blank"&gt;http://www.rtr.com/Ready-to-Run_Software/communication_readypak.htm.&lt;/A&gt; Pcomm+ is part of their 'CommPak for UNIX'.&lt;BR /&gt; &lt;BR /&gt;It has a scripting language which can timeout, look for regular expressions (more or less), and send/receive characters from a tty line. It will handle all the dialing and handshake stuff for you. You can also return status codes to an external program (in this case a shell script). You will have to write a sqlplus command to extract the phone numbers and then let your shell script build a pcomm+ batch file 'on the fly'. &lt;BR /&gt;&lt;BR /&gt;I have used this method to build rather complex&lt;BR /&gt;modem transfer programs.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 May 2002 21:17:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724954#M945958</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-05-15T21:17:37Z</dc:date>
    </item>
    <item>
      <title>Re: CU Command: Fax modem check</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724955#M945959</link>
      <description>Several years ago I have used kermit to do very similar things. It has a scripting language and can do commans via stdin and stdio.  Kermit is well supported and comes free with HPUX.&lt;BR /&gt;&lt;BR /&gt;I have used it to check and reset locked modems, send system error messages via pager and download edi like transmissions over Phones lines and ethernet.  &lt;BR /&gt;&lt;BR /&gt;At first, It seems scary to use.  but once you find a few examples.  You will quickly learn that your task can be easily accomplished. &lt;BR /&gt;Rory&lt;BR /&gt;</description>
      <pubDate>Fri, 17 May 2002 14:14:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cu-command-fax-modem-check/m-p/2724955#M945959</guid>
      <dc:creator>Rory R Hammond</dc:creator>
      <dc:date>2002-05-17T14:14:29Z</dc:date>
    </item>
  </channel>
</rss>

