Re: Pages failing before appointed deadline

[Matthias.Apitz@SOFTCON.de]

Tanya Ruttenberg wrote:
    
    Version: hylafax-v4.0pl1
    Compiler: Sun cc
    System Type: Solaris 2.5.1
    Modem: USRobotics Sportster 28800 V.34 Fax
    Supervisor rev:         6.0
    DSP rev:                11.1
    
    We use hylafax primarily for its paging capabilities.  When we upgraded to
    this version of hylafax, many pages failed where few had failed before.  I
    should not that _many_ more are succeeding than failing, but they always
    seem to fail when we need them most.  The fax daemon sends mail that says:
    
     * "Your pager job to 1-800-759-6366 could not be completed before the
       appointed deadline"
    
    The various reasons it gives are these:
    
     * "No initial ID response from paging central"
     * "Protocol failure: too many unknown responses to message block transmit"
     * "No carrier detected"
    
    All presumably problems with the paging service and not with us.  So I tried
    turning up several config parameters in the hope that hylafax will just keep
    trying, say, 10 or 20 times until the page is successful.
    
    These are the changes I've made:
    
    /var/spool/hylafax/etc/config.cua_b:
    < ServerTracing:          0x0000f
    < LocalIdentifier:      "CUC International Internet Engineering - Cambridge"
    < MaxSetupAttempts:       5
    < NoCarrierRetrys:        10
    < PagerMaxMsgLength:    256
    < IXOMaxUnknown:          6
    < IXOIDProbe:             3
    < IXOIDTimeout:           30
    < IXOLoginRetries:        6
    < IXOLoginTimeout:        20
    < IXOGATimeout:           45
    < IXOXmitRetries:         6
    < IXOXmitTimeout:         45
    < IXOAckTimeout:          45
    
    /var/spool/hylafax/etc/config:
    < ServerTracing:                0x0000f
    < SessionTracing:               11
    < MaxTries:             10
    < MaxDials:             10
    < MaxConcurrentJobs:    30
    < NoCarrierRetrys:      10
    
    Each time a page failes it indicates that it only tried 0, 1, 2, or 3 times.
    Here is an example:
    
            Status: No initial ID response from paging central
           Dialogs: 1 (exchanges with remote device)
             Dials: 0 (consecutive failed calls to destination)
             Calls: 1 (total phone calls placed)
    
    Dialogs, Calls, and Dials never exceed 3.  I've read the Troubleshooting
    sections of the web-site, looked in the mailing-list archives, and read the
    config (4) man page.  I could certainly have missed something, but this has
    been dragging on forever and I'm getting really aggravated with this.
    
    To sum up, I have two questions:
    
    1) Is there anything I can do about the errors I indicated above?  Or do
       they truly look like lousy service down at paging central and we're at
       their mercy?
    
    2) How can I increase the number of times a page is attempted?  Is there a
       "deadline" that can be set?

Read the man page of hfaxd(1M) for the parameters
KillTimeMap:
RetryTimeMap:
PriorityMap:

	matthias