fax capability quit working

Discussion in 'General' started by sskiba, May 27, 2009.

  1. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Hi,

    I've been using elastix 1.1-8 & having great luck with it for over a year. I had a local asterisk guy come in to help me make sure my security was in good shape as well as just checking the system over for me since I'm learning as I go along & am not sure I've done things correctly.

    My issue is that we've been using the fax aspect of the system with no problems until right after he came in to help me.

    I had 5 faxes set up through elastix & all were working well. My asterisk guy made a couple of security setting changes, mostly just looked through the system & didn't change much if anything else. He spent some time looking through elastix because he's not familiar with it.

    At this point my faxes have stopped working. I'm getting a bunch of the following message at my output screen.

    INIT: Id "fx1" respawning to fast: disabled for 5 minutes. (Same for fx1 through fx5)

    My Virtual Fax List Status changed to "on ttyIAX1" from "Running and idle on ttyIAX1"

    We're running all sip phones so don't have any additional hardware.

    Could security changes have made the difference on our fax capability?

    For awhile after the asterisk guy was here, fax emails were coming through to the specified email addresses but the pdf's were striped out. I would get a link to the fax but the system couldn't find it. Now I just get an unable to send message from any fax I try to send from.

    He also discovered that the hylafax services weren't working. He went in and (I believe) set up a user & then was able to get the hylafax services running.

    Any ideas from the community why things would have stopped working with the descriptions I provided above? Thanks for any advice or thoughts.

    Steve
     
  2. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    My commiserations:
    If faxes were flowing then hylafax , there are two services faxq and hfaxd, was indeed running, basically he was dead wrong.

    The last line of "ls -lasrt /var/spool/hylafax/log" will tell when the last fax was successfully processed.

    Your errors show a connection problem between the the Hylafax faxgetty's and the Asterisk iaxmodems, possibly an ownership/permission problem.

    In his inability to unfix his fixes, then perhaps

    rpm -q --whatprovides hylafax

    to see if it was an rpm he installed

    rpm -e --nodeps hylafax

    to remove hylafax without taking out the whole of elastix and freepbx

    and lastly

    yum install hylfax

    will reinstall it from the elastix repositories, and hopefully fix the configurations.

    A caveat is that I haven't ever needed to do it so no guarantees and you might need to reconfigure or even delete/re-add your modems.

    good luck
     
  3. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    Post here the outputs of:

    cat /etc/inittab |grep ttyIAX
    cat /etc/iaxmodem/*
    cat /var/spool/hylafax/etc/config*
    for i in `ls /var/log/iaxmodem/iaxmodem-cfg.ttyIAX*`; do tail -8 $i; done
    asterisk -rx "iax2 show peers"
    ps -aux |grep fax

    This can help us to find out what your problems are.
     
  4. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Man that's a lot of stuff. I hope this all helps & thanks for your help.

    Steve


    [root@elastix /]# cat /etc/inittab |grep ttyIAX
    fx6:2345:respawn:/usr/sbin/faxgetty ttyIAX6
    fx5:2345:respawn:/usr/sbin/faxgetty ttyIAX5
    fx4:2345:respawn:/usr/sbin/faxgetty ttyIAX4
    fx3:2345:respawn:/usr/sbin/faxgetty ttyIAX3
    fx2:2345:respawn:/usr/sbin/faxgetty ttyIAX2
    fx1:2345:respawn:/usr/sbin/faxgetty ttyIAX1



    [root@elastix /]# cat /etc/iaxmodem/*
    device /dev/ttyIAX1
    owner uucp:uucp
    mode 660
    port 40000
    refresh 300
    server 127.0.0.1
    peername 300
    secret
    cidname Advanced Hearing
    cidnumber 7196232168
    codec slineardevice /dev/ttyIAX2
    owner uucp:uucp
    mode 660
    port 40001
    refresh 300
    server 127.0.0.1
    peername 310
    secret
    cidname PreciseHearingFax1
    cidnumber 7196232158
    codec slineardevice /dev/ttyIAX3
    owner uucp:uucp
    mode 660
    port 40002
    refresh 300
    server 127.0.0.1
    peername 320
    secret
    cidname CHAP-Fax-Cstmr
    cidnumber 7193551447
    codec slineardevice /dev/ttyIAX4
    owner uucp:uucp
    mode 660
    port 40003
    refresh 300
    server 127.0.0.1
    peername 330
    secret
    cidname CHAP-Fax-Vendor
    cidnumber 7193551449
    codec slineardevice /dev/ttyIAX5
    owner uucp:uucp
    mode 660
    port 40004
    refresh 300
    server 127.0.0.1
    peername 340
    secret
    cidname PH-Support
    cidnumber 7196232157
    codec slineardevice /dev/ttyIAX6
    owner uucp:uucp
    mode 660
    port 40005
    refresh 300
    server 127.0.0.1
    peername 350
    secret
    cidname STEVETEST
    cidnumber 7196232168
    codec slinear[root@elastix /]#




    [root@elastix /]# cat /var/spool/hylafax/etc/config*
    LogFacility: daemon
    CountryCode: 1
    AreaCode: 719
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: "etc/dialrules"
    ServerTracing: 1
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7196232168
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "Advanced Hearing"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7196232158
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "PreciseHearingFax1"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7193551447
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "CHAP-Fax-Cstmr"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7193551449
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "CHAP-Fax-Vendor"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7196232157
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "PH-Support"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="
    CountryCode: 011
    AreaCode: 719
    FAXNumber: 7196232168
    LongDistancePrefix: 1
    InternationalPrefix: 011
    DialStringRules: etc/dialrules
    ServerTracing: 0xFFF
    SessionTracing: 0xFFF
    RecvFileMode: 0600
    LogFileMode: 0600
    DeviceMode: 0600
    RingsBeforeAnswer: 1
    SpeakerVolume: off
    GettyArgs: "-h %l dx_%s"
    LocalIdentifier: "STEVETEST"
    TagLineFont: etc/lutRS18.pcf
    TagLineFormat: "From %%l|%c|Page %%P of %%T"
    MaxRecvPages: 200
    #
    #
    # Modem-related stuff: should reflect modem command interface
    # and hardware connection/cabling (e.g. flow control).
    #
    ModemType: Class1 # use this to supply a hint

    #
    # Enabling this will use the hfaxd-protocol to set Caller*ID
    #
    #ModemSetOriginCmd: AT+VSID="%s","%d"

    #
    # If "glare" during initialization becomes a problem then take
    # the modem off-hook during initialization, and then place it
    # back on-hook when done.
    #
    #ModemResetCmds: "ATH1\nAT+VCID=1" # enables CallID display
    #ModemReadyCmds: ATH0


    Class1AdaptRecvCmd: AT+FAR=1
    Class1TMConnectDelay: 400 # counteract quick CONNECT response

    Class1RMQueryCmd: "!24,48,72,96" # enable this to disable V.17

    #
    # You'll likely want Caller*ID display (also displays DID) enabled.
    #
    ModemResetCmds: AT+VCID=1 # enables CallID display

    #
    # If you are "missing" Caller*ID data on some calls (but not all)
    # and if you do not have adequate glare protection you may want to
    # not answer based on RINGs, but rather enable the CallIDAnswerLength
    # for NDID, disable AT+VCID=1 and do this:
    #
    #RingsBeforeAnswer: 0
    #ModemRingResponse: AT+VRID=1

    CallIDPattern: "NMBR="
    CallIDPattern: "NAME="
    CallIDPattern: "ANID="
    CallIDPattern: "NDID="
    #CallIDAnswerLength: 4
    # Uncomment these if you really want them, but you probably don't.
    #CallIDPattern: "DATE="
    #CallIDPattern: "TIME="


    [root@elastix /]# for i in `ls /var/log/iaxmodem/iaxmodem-cfg.ttyIAX*`; do tail -8 $i; done
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-26 20:49:41] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-[2009-05-27 15:59:09] Registration completed successfully.
    [2009-05-27 16:00:04] Registration completed successfully.
    [2009-05-27 16:00:59] Registration completed successfully.
    [2009-05-27 16:01:54] Registration completed successfully.
    [2009-05-27 16:02:49] Registration completed successfully.
    [2009-05-27 16:03:44] Registration completed successfully.
    [2009-05-27 16:04:39] Registration completed successfully.
    [2009-05-27 16:05:34] Registration completed successfully.
    [2009-05-27 15:59:09] Registration completed successfully.
    [2009-05-27 16:00:04] Registration completed successfully.
    [2009-05-27 16:00:59] Registration completed successfully.
    [2009-05-27 16:01:54] Registration completed successfully.
    [2009-05-27 16:02:49] Registration completed successfully.
    [2009-05-27 16:03:44] Registration completed successfully.
    [2009-05-27 16:04:39] Registration completed successfully.
    [2009-05-27 16:05:34] Registration completed successfully.
    [2009-05-27 15:59:09] Registration completed successfully.
    [2009-05-27 16:00:04] Registration completed successfully.
    [2009-05-27 16:00:59] Registration completed successfully.
    [2009-05-27 16:01:54] Registration completed successfully.
    [2009-05-27 16:02:49] Registration completed successfully.
    [2009-05-27 16:03:44] Registration completed successfully.
    [2009-05-27 16:04:39] Registration completed successfully.
    [2009-05-27 16:05:34] Registration completed successfully.
    [2009-05-27 15:59:09] Registration completed successfully.
    [2009-05-27 16:00:04] Registration completed successfully.
    [2009-05-27 16:00:59] Registration completed successfully.
    [2009-05-27 16:01:54] Registration completed successfully.
    [2009-05-27 16:02:49] Registration completed successfully.
    [2009-05-27 16:03:44] Registration completed successfully.
    [2009-05-27 16:04:39] Registration completed successfully.
    [2009-05-27 16:05:34] Registration completed successfully.
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable
    [2009-05-27 16:05:52] Unable to pass the full buffer onto the device file. 1 bytes of 4094 written: Resource temporarily unavailable




    [root@elastix /]# asterisk -rx "iax2 show peers"
    Name/Username Host Mask Port Status
    350 127.0.0.1 (D) 255.255.255.255 40005 OK (3 ms)
    340 127.0.0.1 (D) 255.255.255.255 40004 OK (3 ms)
    330 127.0.0.1 (D) 255.255.255.255 40003 OK (3 ms)
    320 127.0.0.1 (D) 255.255.255.255 40002 OK (3 ms)
    310 127.0.0.1 (D) 255.255.255.255 40001 OK (3 ms)
    300 127.0.0.1 (D) 255.255.255.255 40000 OK (3 ms)
    6 iax2 peers [6 online, 0 offline, 0 unmonitored]
    [root@elastix /]# ps -aux |grep fax
    Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ
    adm 26570 0.0 0.0 4484 720 ? Ss 12:15 0:00 /usr/sbin/hfaxd -i hylafax
    root 29810 0.0 0.0 3908 716 pts/3 S+ 15:56 0:00 grep fax
    [root@elastix /]#
     
  5. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Hey dicko,

    Thanks for the response. Not to slight you but I'm going to hold off on doing the reinstall until you guys look at the info I just posted for ramoncio.

    Thanks again, Steve
     
  6. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    No sleight perceived, always better to fix a problem with a screwdriver rather than a hammer and of all around here ramoncio can wield that screwdriver

    It looks like 4 of your 6 modems are answering as of 5 mins ago [2345] , can you confirm?

    what does ps aux|grep -i iax look like now?


    faxstat should show status
     
  7. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    It looks like this.

    Status still says - on ttyIAX1 - (1 through 6)

    [root@elastix /]# ps aux|grep -i iax
    root 25505 0.0 0.0 2836 344 ? Ss 11:34 0:00 /usr/sbin/iaxmodem
    adm 25506 0.0 0.0 2948 892 ? S 11:34 0:00 /usr/sbin/iaxmodem
    adm 25507 0.0 0.0 2948 892 ? S 11:34 0:00 /usr/sbin/iaxmodem
    adm 25508 87.0 0.0 2948 928 ? R 11:34 289:52 /usr/sbin/iaxmodem
    adm 25509 0.0 0.0 2948 892 ? S 11:34 0:00 /usr/sbin/iaxmodem
    adm 25511 0.0 0.0 2948 892 ? S 11:34 0:00 /usr/sbin/iaxmodem
    adm 25512 0.0 0.0 2948 892 ? S 11:34 0:00 /usr/sbin/iaxmodem
    root 31009 0.0 0.0 3904 688 pts/3 R+ 17:07 0:00 grep -i iax
     
  8. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    my apologies, faxstat from bash, not in the GUI
     
  9. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Ah, You assume too much. How do I check faxstat from bash? Sorry I know next to nothing about linux commands.
     
  10. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    No problem, bash is the linux shell where you did all those commands for ramoncio from (I sent a fax to 2157, did it go anywhere?)
     
  11. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Okay, that's kind of what I thought. I typed faxstat at the root level & didn't get anything.

    All the fax lines have been forwarded to a working fax line that's outside of our elastix setup except 7196232168. It's the only one that's been left active through elastix so we can test it. Our company needs the other lines working.
     
  12. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Nothing at all?, not

    HylaFAX scheduler on xxxxxxxxx: Running (then hylafax is at least running, configured modems should follow one per line)

    or

    Can not reach server at host "localhost", port 4559. (hylafax is not running)

    then

    which faxstat

    should give

    usr/bin/faxstat
     
  13. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Nothing with faxstat but which faxstat did give me usr/bin/faxstat
     
  14. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Then I hope ramoncio can help you, I think he hosed you. Anyway good luck and I hope I'm wrong.
     
  15. sskiba

    Joined:
    Aug 4, 2008
    Messages:
    45
    Likes Received:
    0
    Bummer! Thanks for giving it a shot. I'm done for the night. Steve
     
  16. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    Ok, the hylafax config is fine. Even some of your iaxmodems are working.

    This line in /etc/inittab loads faxgetty for each iaxmodem at the system init:

    fx*:2345:respawn:/usr/sbin/faxgetty ttyIAX*


    From the error in your first message you can see
    INIT: Id "fx1" respawning to fast: disabled for 5 minutes.

    The app faxgetty starts, then exits almost immediately. So the respawn part of the entry tells init to start it again. It starts, exits ... and so on.

    So it is a problem with your iaxmodems. You can see it in the iaxmodem logs too:

    /var/log/iaxmodem/iaxmodem-cfg.ttyIAX*

    Some of your iaxmodems are registering ok:

    [2009-05-27 16:04:39] Registration completed successfully

    but ttyIAX1 and ttyIAX6 have some problem:

    Unable to pass the full buffer onto the device file.
    1 bytes of 4094 written: Resource temporarily unavailable


    I think if you remove al virtual faxes an recreate them you can solve your problem.

    But first you'll need to know fax things work with Elastix.

    When you add a virtual fax at the web interface, Elastix does the next steps:

    - Inserts the fax config into the Elastix's sqlite fax database /var/www/db/fax.db
    - Adds the faxgetty line in /etc/inittab
    - Adds the iaxmodem config into /etc/iaxmodem/ttyIAX*
    - Restarts init with command "init q". This reloads faxgetty listening to the iaxmodems in ttyIAX*
    - Restarts iaxmodem service (/etc/init.d/iaxmodem restart)
    - Restarts hylafax service. You can also do it manually with

    /etc/init.d/hylafax restart

    and you should see this output

    Shutting down HylaFAX queue manager (faxq): [ OK ]
    Shutting down HylaFAX server (hfaxd): [ OK ]
    Starting HylaFAX queue manager (faxq): [ OK ]
    Starting HylaFAX server (hfaxd): [ OK ]
    Restarting HylaFAX modem manager (faxgetty): [ OK ]


    So faxq and faxgetty should be reloaded ok.


    If you see the runing processes you should have faxq running and one faxgetty for each iaxmodem ttyIAX*

    [root@elastix ~]# ps aux |grep fax
    uucp 2489 0.0 0.1 6928 1184 ? Ss 00:05 0:00 /usr/sbin/faxq
    uucp 2492 0.0 0.1 4540 888 ? Ss 00:05 0:00 /usr/sbin/hfaxd -i hylafax
    uucp 2770 0.0 0.1 4988 1480 ? Ss 00:05 0:00 /usr/sbin/faxgetty ttyIAX2
    uucp 2771 0.0 0.1 4992 1484 ? Ss 00:05 0:00 /usr/sbin/faxgetty ttyIAX1
    root 3636 0.0 0.0 3948 744 pts/2 R+ 01:32 0:00 grep fax


    So try this: Remove all virtual faxes at the elastix interface. Not the iax extensions, just the virtual faxes.

    Also make sure all virtual faxes are removed from the sqlite database.

    You can see the configured faxes in Elastix's database with:

    sqlite3 /var/www/db/fax.db "select * from fax;"

    And you can delete them with:

    sqlite3 /var/www/db/fax.db "delete from fax;"

    After removing all virtual faxes run the commands:

    /etc/init.d/iaxmodem restart
    init q
    /etc/init.d/hylafax restart

    You should see [ok] in all starting processes

    After this recreate your virtual faxes at the web interface, and you should be done.

    I hope this helps you.

    If this doesn't work you can try dicko's solution of uninstalling and reinstalling hylafax.
     
  17. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    See I told you he could drive a screw!

    From a memory of a self inflicted injury to myself
    If your expert reinstalled hylafax from scratch using the defaults there is a good chance that faxgetty is in
    /usr/local/sbin
    and not
    /usr/sbin

    which faxgetty

    's output
    should agree with the entries in inittab.
    or you will get the respawn errors
     
  18. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    I don't think so.
    He wouldn't get the "respawning too fast" error, but something like /usr/sbin/faxgetty not found
    faxgetty crashes and respawns because there is a problem with some iaxmodems. And also does faxq.
     
  19. ramoncio

    Joined:
    May 12, 2010
    Messages:
    1,663
    Likes Received:
    0
    There is a very easy way to test if the iaxmodems are working, and the asterisk part too.
    If you call from a phone to the fax iax2 extension you should hear a fax tone.
     
  20. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Agreed, but In my case it WAS in /usr/sbin, there from the Elastix installation and /usr/local/sbin from my inept installation of hylafax. and i was calling the wrong one.

    Neither has he any output at all from /usr/bin/faxstat, so I was suspicious.
    Just my 2cents, and you know me, sometimes I don't know when to shut up :)
     

Share This Page