Faxing - protocol selection

I am trying to understand the order of fax protocol selection. For example, lets take a PSTN gateway that is MGCP enabled. Fax passthrough, T38 relay and Cisco fax relay are enabled. Which protocol will be used to negotiate with the far end device first(ATA, vg248 etc) ? Is there a particular order in which negotiation takes place ?
On the mgcp gateway the follwing commands are present.
mgcp modem passthrough codec g711ulaw
mgcp modem passthrough voip mode nse
ccm-manager fax protocol cisco (default)
no mgcp t38 fax inhibit (default)

In my opinion the best fax protocol is T38 (standard) followed by CISCO Fax relay (similar to T38) and the last option is fax pass through.
ATA 188 doesn't support T38. You can find more info about ATA MGCP here:
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administration_guide_chapter09186a00805fe011.html
Info about VG248 here:
http://www.cisco.com/en/US/products/hw/gatecont/ps2250/products_configuration_example09186a008020160d.shtml
On your gateway you can configure T38 as first option. If T38 negotiation fail the second option will be CISCO or pass through:
fax protocol {t38 [nse [force]] [ls-redundancy value [hs-redundancy value]] [fallback {cisco |
none | pass-through {g711ulaw | g711alaw}}]}

Similar Messages

  • MGCP fax protocol incompatible with Alcatel softswitch and GWs

    Hi
    We are using alcatel 5020 as sosftswitch and cisco 5400,5350 and Alcatel 7515 as media gateways. But there is an incompatiblity for fax protocols. When we use T38 it can be ok but some calls get hanged on. For passthru alcatel dont uses NSE mode so no fax at all. Are there any body who encounters same issues about fax. Which one is "more" universal T38 or passthru? What are the industry standars for payload types etc?
    Regards

    Some of the gateways has restrictions depending upon the IOS image loaded .
    http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087eb3.html
    http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide_chapter09186a00800b5dce.html

  • Fax protocol error

    I try to send several fax documents to different numbers. i have connection, then "sending" message. It stops at the end with message "hold until xxx". Any solution ?

    For the longest time I used FAXstf in OS9 and all was more than beautiful. Then they sold to SmithMicro, it went to pot. So I was very happy to see Apple include FAX capability in the OS. If only it worked. It seems to be one of those peripheral applications that they include for looks not function. I have had a couple of successful FAXes go through, from the other room. But when I need it to really work it seems to just does its own thing. I set it to pick up on two rings and the phone is still ringing 6 later, but the menu bar is saying "answering . . . ". I activate it manually and it still takes longer than the sending machine will allow for a wait to pick up. I'm not real sure where the problems may lie, because I also use PageSender (Great App) that use to work flawlessly until the later OS's. So I'm beginning to think that Apple has changed something in the way the modem operates that makes it hard for this kind of software to do its job. When it works, It works great. But . . .
    So I agree that it is an Apple thing that there are problems in this area. And what with them abandoning old technologies, I don't see much, if any support, or further development on this. After all, the new laptops don't come with modems anymore.
    If FAXing is important, you might look into PageSender. It has many nice features that the Apple software doesn't. Like access to other address books other than Apples, FAX to eMail, and more.

  • Problem with fax t38 protocol

    hi
    i have an mpls nework with equipment cisco 2821, 2901 and 2801, and i have problems with fax calls, i configured the fax protocol t38 in all routers but when i want to send a fax to the 2821 equipment from either 2801 and 2901, the protocol t38 is not working and the fax call use cisco protocol (although t38 is configured in all routers). the calls betwen 2801 and 2901 works ok, and from 2821 to 2801/2901 works ok too.
    any idea of whats happens? do you think is a problem of ios version?
    these are de ios version
    2821 .-c2800nm-spservicesk9-mz.124-3i.bin
    2801 .- c2801-spservicesk9-mz.150-1.M6.bin
    2901 .-c2900-universalk9-mz.SPA.150-1.M7.bin

    hi
    this is the configuration on the 2821:
    voice service voip
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
    dial-peer voice 10037 voip
    description CONEXION CELAYA DISTRITO XV
    destination-pattern 561.
    session target ipv4:172.16.200.37
    incoming called-number .
    dtmf-relay h245-alphanumeric
    codec g729r8 bytes 50
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
    ip qos dscp ef signaling
    no vad
    this is the configuration on 2801
    voice service voip
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
    dial-peer voice 10016 voip
    description CONEXION VOZ A FAXES
    destination-pattern 300[1-6,8]
    session target ipv4:172.1.1.51
    incoming called-number .
    dtmf-relay h245-alphanumeric
    codec g729r8 bytes 50
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
    ip qos dscp ef signaling
    no vad
    i want to use T38 because the bandwidth of the fax call is 16K, if i use cisco protocol the bandwidth reaches up 24k, and the router start to drop voice packets
    thanks

  • OfficeJet 4630 Defaults to Network Fax when user has selected Network Printer Instead on WIN XP

    Hi, just installed the OJ4630 and selected the "Network Printer" as the default.  When choosing to print an MS Word document in "My Documents" the "Network Printer" correctly appears as the default.  But when choosing to print a picture in "My Pictures" the "Network Fax" becomes the default, which is an error.  Please advise, thanks!

    Hi 
    Thanks for reporting the issue. Here is the way to fix it.
    Go to windows->Control panel-> Printers and devices
    Right click on the 4630 Fax Printer, select the option Set as default printer and you'll see two choices there: one is printer driver and other one is fax driver.   You choose print driver to set as default.
    Done
    Hope it will help you.
    happy Printing!!!
    Click on the "Thumbs up"button on the left to say "Thanks"
    Please mark the post that solves your problem as "Accepted Solution"
    (Although I am employed by HP, I am speaking for myself and not for HP)

  • B-channel oos and protocol error 510

    Dear all,
    I have some some issue couple of days ago. The telephony system of my client worked well and suddenly the cannot make external calls via E1. I checked the config and for me it seems to be ok. When I checked the SDL file, I can see the B channel out of service error message following by the
    "MGCP PROTOCOL ERROR: <S1/SU1/DS1-0/[email protected]> CRCX error code: 510". They have A CUCM 6.0 and Cisco 2821 as gateway with 12.4 (25f) advance IP service IOS.
    I perform the following actions without success:
    -From the CUCM in the advance service I forced the Bchannel to bring it in service,
    - no mgcp/mgcp, -reboot the CUCM and the Gateway,
    -reset the controller throug CUCM,... in vain.
    They contacted telco and has confirm that everything seems to be ok. Find below the information that can help you to undestand better
    #sh run brief
    Building configuration...
    Current configuration : 4859 bytes
    version 12.4
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    service sequence-numbers
    hostname ATD-CCM-GW
    boot-start-marker
    boot-end-marker
    security authentication failure rate 3 log
    security passwords min-length 6
    logging buffered 51200 debugging
    aaa new-model
    aaa authentication login default local
    aaa authentication login local_authen local
    aaa authorization exec default local
    aaa authorization exec local_author local
    aaa session-id common
    clock timezone A 1
    network-clock-participate slot 1
    network-clock-select 1 E1 1/1/0
    ip cef
    ip domain name xx.xxxx.xxx
    ip host ATD-CCM1 10.10.10.100
    ip auth-proxy max-nodata-conns 3
    ip admission max-nodata-conns 3
    isdn switch-type primary-net5
    isdn logging
    voice-card 0
    dspfarm
    dsp services dspfarm
    voice-card 1
    no dspfarm
    no voice call carrier capacity active
    voice rtp send-recv
    voice class codec 1
    codec preference 1 g711ulaw
    codec preference 2 g711alaw
    codec preference 3 g729br8 bytes 40
    voice class h323 1
    h225 timeout tcp establish 3
    crypto pki trustpoint TP-self-signed-635937996
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-635937996
    revocation-check none
    rsakeypair TP-self-signed-635937996
    crypto pki certificate chain TP-self-signed-635937996
    certificate self-signed 01
    application
      service alternate Default
    controller E1 1/1/0
    framing NO-CRC4
    pri-group timeslots 1-31 service mgcp
    interface GigabitEthernet0/0
    description to_CCM
    ip address 10.10.10.254 255.255.255.0
    duplex auto
    speed auto
    interface GigabitEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface Serial1/1/0:15
    no ip address
    encapsulation hdlc
    isdn switch-type primary-net5
    isdn overlap-receiving
    isdn incoming-voice voice
    isdn bind-l3 ccm-manager
    isdn bchan-number-order ascending
    isdn sending-complete
    no cdp enable
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 10.10..253
    ip http server
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    logging trap debugging
    control-plane
    voice-port 1/0/0
    timing hookflash-out 50
    voice-port 1/0/1
    signal groundStart
    timing hookflash-out 50
    voice-port 1/0/2
    signal groundStart
    timing hookflash-out 50
    voice-port 1/0/3
    signal groundStart
    timing hookflash-out 50
    voice-port 1/1/0:15
    ccm-manager fallback-mgcp
    ccm-manager mgcp
    no ccm-manager fax protocol cisco
    ccm-manager music-on-hold
    ccm-manager config server ATD-CCM1 
    ccm-manager config
    mgcp
    mgcp call-agent 10.10.10.100 service-type mgcp version 0.1
    mgcp dtmf-relay voip codec all mode out-of-band
    mgcp rtp unreachable timeout 1000 action notify
    mgcp modem passthrough voip mode nse
    mgcp modem passthrough voip redundancy
    mgcp package-capability rtp-package
    mgcp package-capability sst-package
    mgcp package-capability pre-package
    mgcp default-package fxr-package
    no mgcp package-capability res-package
    no mgcp timer receive-rtcp
    mgcp sdp simple
    mgcp fax t38 inhibit
    no mgcp explicit hookstate
    mgcp rtp payload-type g726r16 static
    mgcp bind control source-interface GigabitEthernet0/0
    mgcp bind media source-interface GigabitEthernet0/0
    mgcp profile default
    dial-peer voice 999101 pots
    service mgcpapp
    port 1/0/1
    forward-digits all
    dial-peer voice 999102 pots
    service mgcpapp
    port 1/0/2
    forward-digits all
    dial-peer voice 999103 pots
      service mgcpapp
    port 1/0/3
    forward-digits all
    dial-peer voice 1 pots
    service mgcpapp
    incoming called-number .
    direct-inward-dial
    port 1/1/0:15
    forward-digits all
    dial-peer voice 999100 pots
    service mgcpapp
    port 1/0/0
    gateway
    timer receive-rtp 1200
    scheduler allocate 20000 1000
    ntp clock-period 17180351
    ntp update-calendar
    ntp server 10.10.10.9 source GigabitEthernet0/0
    end
    #sh controller e1
    E1 1/1/0 is up.
      Applique type is Channelized E1 - balanced
      No alarms detected.
      alarm-trigger is not set
      Version info Firmware: 20090113, FPGA: 20, spm_count = 0
      Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
       Current port master clock:recovered from backplane
      Data in current interval (225 seconds elapsed):
         0 Line Code Violations, 0 Path Code Violations
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
      Total Data (last 3 15 minute intervals):
         0 Line Code Violations, 0 Path Code Violations,
         0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
         0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    #sh ccm-manager
    MGCP Domain Name: ATD-CCM-GW.xx.xxxx.xxx
    Priority        Status                   Host
    ============================================================
    Primary         Registered               10.10.10.100
    First Backup    None                    
    Second Backup   None                    
    Current active Call Manager:    10.10.10.100
    Backhaul/Redundant link port:   2428
    Failover Interval:              30 seconds
    Keepalive Interval:             15 seconds
    Last keepalive sent:            15:31:24 UTC Oct 19 2012 (elapsed time: 00:00:09)
    Last MGCP traffic time:         15:31:24 UTC Oct 19 2012 (elapsed time: 00:00:09)
    Last failover time:             None
    Last switchback time:           None
    Switchback mode:                Graceful
    MGCP Fallback mode:             Enabled/OFF
    Last MGCP Fallback start time:  None
    Last MGCP Fallback end time:    None
    MGCP Download Tones:            Disabled
    TFTP retry count to shut Ports: 2
    Backhaul Link info:
        Link Protocol:      TCP
        Remote Port Number: 2428
        Remote IP Address:  10.10.10.100
        Current Link State: OPEN
        Statistics:
            Packets recvd:   11
            Recv failures:   0
            Packets xmitted: 18
            Xmit failures:   0
        PRI Ports being backhauled:
            Slot 1, VIC 1, port 0
    Configuration Auto-Download Information
    =======================================
    Current version-id: 1350042385-8bfc9ed0-f85e-4435-8baf-3ad1ceefb55c
    Last config-downloaded:00:00:00
    Current state: Waiting for commands
    Configuration Download statistics:
               Download Attempted             : 1
                 Download Successful          : 1
                 Download Failed              : 0
                 TFTP Download Failed         : 0
               Configuration Attempted        : 1
                 Configuration Successful     : 1
                 Configuration Failed(Parsing): 0
                 Configuration Failed(config) : 0
    Last config download command: New Registration
    Configuration Error History:
    controller E1 1/1/0
    no pri-group timeslots 1-31
    FAX mode: disable
    #debug isdn q931
    #debug mgcp packet
    009112: Oct 20 12:48:50.374: MGCP Packet received from 10.10.10.100:2427--->
    CRCX 2359 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    X: 1f
    L: p:20, a:PCMU, s:off, t:00
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    009113: Oct 20 12:48:50.382: MGCP Packet sent to 10.10.10.100:2427--->
    200 2359 OK
    I: 8
    v=0
    c=IN IP4 10.10.10.254
    m=audio 18274 RTP/AVP 0 100
    a=rtpmap:100 X-NSE/8000
    a=fmtp:100 192-194
    <---
    009114: Oct 20 12:48:50.386: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 64
    009115: Oct 20 12:48:50.386: ISDN Se1/1/0:15 Q931d: data =
    009116: Oct 20 12:48:50.386:           4636A628000000030240043800010000
    009117: Oct 20 12:48:50.386:           0802000105A104038090A31803A9839F
    009118: Oct 20 12:48:50.386:           280B526F6C616E64202D2049546C0601
    009119: Oct 20 12:48:50.386:           81313232307009803636393332313933
    009120: Oct 20 12:48:50.386:
    009121: Oct 20 12:48:50.434: MGCP Packet received from 10.10.10.100:2427--->
    MDCX 2360 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    I: 8
    X: 1f
    L: p:20, a:PCMU, s:off, t:b8, fxr/fx:t38
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    009122: Oct 20 12:48:50.438: MGCP Packet sent to 10.10.10.100:2427--->
    510 2360 fx: setting cannot be supported
    <---
    009123: Oct 20 12:48:50.438: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 25
    009124: Oct 20 12:48:50.438: ISDN Se1/1/0:15 Q931d: data =
    009125: Oct 20 12:48:50.438:           4636A628000000030240043800010000
    009126: Oct 20 12:48:50.438:           0802000145080280AF
    009127: Oct 20 12:48:50.462: MGCP Packet received from 10.10.10.100:2427--->
    DLCX 2361 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9aa000000F500000001
    I: 8
    X: 1f
    S:
    <---
    ATD-CCM-GW#
    009128: Oct 20 12:48:50.478: MGCP Packet sent to 10.10.10.100:2427--->
    250 2361 OK
    P: PS=0, OS=0, PR=0, OR=0, PL=0, JI=0, LA=0
    <---
    009129: Oct 20 12:48:50.478: ISDN Se1/1/0:15 Q931d: srl_send_l3_pak:
    source_id = CCM MANAGER 0x0003, dest_id = Q.921 0x0000, prim = DL_DATA_REQ 0x0240
    priv_len = 4 int_id = 0x4636A628 datasize = 21
    009130: Oct 20 12:48:50.478: ISDN Se1/1/0:15 Q931d: data =
    009131: Oct 20 12:48:50.478:           4636A628000000030240043800010000
    009132: Oct 20 12:48:50.478:           080200015A
    ATD-CCM-GW#
    009133: Oct 20 12:49:03.002: MGCP Packet received from 10.10.10.100:2427--->
    CRCX 2362 S1/SU1/DS1-0/[email protected] MGCP 0.1
    C: D000000001fbf9ac000000F500000002
    X: 1e
    L: p:20, a:PCMU, s:off, t:b8, fxr/fx:t38
    M: recvonly
    R: D/[0-9ABCD*#]
    Q: process,loop
    <---
    #sh mgcp statistics
    UDP pkts rx 270, tx 270
    Unrecognized rx pkts 0, MGCP message parsing errors 0
    Duplicate MGCP ack tx 0, Invalid versions count 0
    CreateConn rx 10, successful 1, failed 9
    DeleteConn rx 1, successful 1, failed 0
    ModifyConn rx 1, successful 0, failed 1
    DeleteConn tx 0, successful 0, failed 0
    NotifyRequest rx 0, successful 0, failed 0
    AuditConnection rx 0, successful 0, failed 0
    AuditEndpoint rx 61, successful 61, failed 0
    RestartInProgress tx 4, successful 4, failed 0
    Notify tx 193, successful 193, failed 0
    ACK tx 63, NACK tx 10
    ACK rx 197, NACK rx 0
    IP address based Call Agents statistics:
    IP address 10.10.10.100, Total msg rx 270,
                      successful 260, failed 10
    System resource check is DISABLED. No available statistic
    DS0 Resource Statistics
    Utilization: 0.00 percent
    Total channels: 34
    Addressable channels: 34
    Inuse channels: 0
    Disabled channels: 0
    Free channels: 34
    sh controller e1
    #sh network-clocks
      Network Clock Configuration
      Priority      Clock Source    Clock State     Clock Type
         1          E1 1/1/0        GOOD            E1         
        10          Backplane       GOOD            PLL        
      Current Primary Clock Source
      Priority      Clock Source    Clock State     Clock Type
         1          E1 1/1/0        GOOD            E1     
    Thanks for your help

    The explanation for your syslog message is " The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include: Taking the channel out of service intentionally to perform maintenance on either the near- or far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager (Unified CM); MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway"
    Recommended action:
    Check the Unified CM advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

  • Fax outdial retries consume all voice channels on SIP 484 error (Cisco 2911)

    I've been seeing a nasty fax/VoIP problem on a 2911, running  IOS 15.0(1r)M12.  Any suggestions would be welcome.
    I have a 2911 which is set up to do T.37 offramp fax delivery (SMTP message is sent to 2911, which places a VoIP call over SIP/RTP/T.38 to deliver the fax).  The mainline case is set up, and working correctly - faxes are delivered without issue.  If a destination address is selected such that the VoIP switch returns a SIP 484 error, then everything fails in a spectacular fashion:
    The outdial is immediately retried, placing another SIP INVITE to the switch, with the same destination address, which obviously also gets the same 484 response.
    Each time the outdial takes place, it consumes voice channels on the DSP, which are not released on receipt of the 484.
    When there are no free voice channels, a no circuit (0x22) error is returned, and all the voice channels are finally released.
    The MTA that submitted the SMTP message retries every minute (it doesn't get a permanent failure report when the 2911 fails to place the call)
    This leads to a situation where no fax calls can be placed, as all the voice channels are being used up by retrying this call that can never succeed.
    Some other relevant information:
    The VoIP switch does not return a 484 immediately.  First it sends a SIP 183, and plays early media (an announcement about how the call isn't allowed).
    It takes 8 seconds before the 484 is returned.  The 2911 sends a new SIP INVITE every 8 seconds (as soon as it gets a 484 for the previous attempt).
    The "sip-ua" statistics show that the INVITE retry counter is not  being incremented (i.e. this is not a retry at the scope of the SIP stack).
    The T1 cable is looped-back to the 2911, so that the complete path for fax delivery looks like this:
        MTA ---SMTP---> 2911 ---T1---> 2911 ---SIP---> VoIP switch
    If I set "mta receive generate permanent-error", then I still see this retry behaviour, with all the voice channels being consumed.  Once that has happened (after about 3 minutes) the MTA does get the error response, and no longer retries every minute after that (although this setting has other negative effects that I'd like to avoid).
    Does anyone have any idea how I can get the 2911 to return a permanent failure to the MTA after just a single outdial has failed with a SIP 484?
    Here is the dial-peer config:
    dial-peer voice 1 voip
     translation-profile incoming IncomingVoip
     incoming called-number .
     voice-class codec 1
     dtmf-relay rtp-nte
     fax protocol t38 version 0 ls-redundancy 3 hs-redundancy 0 fallback pass-through g711ulaw
     no vad
    dial-peer voice 2 pots
     destination-pattern ^0005
     port 1/1:23
     forward-digits all
    dial-peer voice 3 pots
     translation-profile incoming IncomingPRI_1_0
     service onramp-app
     incoming called-number ^0005
     direct-inward-dial
     port 1/0:23
    dial-peer voice 4 mmoip
     service fax_on_vfc_onramp_app out-bound
     destination-pattern .
     information-type fax
     session target mailto:$m$@<DOMAIN NAME>
     image encoding MH
    dial-peer voice 101 mmoip
     translation-profile incoming IncomingMMoIP
     service offramp-app
     information-type fax
     incoming called-number .
    dial-peer voice 102 pots
     destination-pattern .
     port 1/0:23
     forward-digits all
    dial-peer voice 103 pots
     translation-profile incoming IncomingPRI_1_1
     incoming called-number ^0007
     direct-inward-dial
     port 1/1:23
    dial-peer voice 104 voip
     translation-profile outgoing OutgoingVoip
     destination-pattern ^0008
     session protocol sipv2
     session target ipv4:<VoIP SWITCH IP ADDRESS>
     voice-class codec 1
     dtmf-relay rtp-nte
     fax protocol t38 version 0 ls-redundancy 3 hs-redundancy 0 fallback pass-through g711ulaw
     no vad

    Hi Ellad.
    Why don't try to use the 2811 as a SIP signalling proxy only?
    In this way the media (RTP or T.38) will be handled only from the two MERA SoftSwitch.
    To do this you must enable CUBE on your 2811 and use these special commands:
    voice service voip
         media flow-around
         allow-connections sip to sip
         signaling forward unconditional
         sip
           rel1xx disable
           header-passing
           midcall-signaling passthru
           pass-thru headers unsupp
           pass-thru content unsupp
           pass-thru content sdp
    I don't remember if we have already try this solution.
    Regards.

  • Vg 224 fax receive intermittant smudged lines

    We have a vg 224 configured as sccp to connnect to fax machine and the incoming PRI was controlled by Cucm 8.5 via MGCP. And tried all combinations, the RICOH machine still gets smudged lines intermittantly. Here is the configuration of vg224. Please help:
    Building configuration...
    Current configuration : 4727 bytes
    ! Last configuration change at 22:17:44 est Tue Jan 31 2012 by cdi-admin
    ! NVRAM config last updated at 22:17:45 est Tue Jan 31 2012 by cdi-admin
    version 12.4
    no service pad
    service timestamps debug datetime localtime show-timezone year
    service timestamps log datetime localtime show-timezone year
    service password-encryption
    hostname VG-ANALOG04
    boot-start-marker
    boot-end-marker
    logging message-counter syslog
    logging buffered 4096
    no logging console
    enable secret 5 $1$..wF$
    no aaa new-model
    clock timezone est -5
    clock summer-time edt recurring
    ip source-route
    ip cef
    no ip domain lookup
    no ipv6 cef
    voice service voip
    fax protocol pass-through g711ulaw
    modem passthrough nse codec g711ulaw
    voice-card 0
    username cdi-admin password 7 1326333B462C0027222A
    archive
    log config
      hidekeys
    interface FastEthernet0/0
    ip address 10.100.205.84 255.255.255.0
    duplex auto
    speed auto
    interface FastEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 10.100.205.1
    ip http server
    ip sla responder
    control-plane
    voice-port 2/0
    no vad
    timeouts ringing infinity
    voice-port 2/1
    no vad
    timeouts ringing infinity
    voice-port 2/2
    no vad
    timeouts ringing infinity
    voice-port 2/3
    no vad
    timeouts ringing infinity
    voice-port 2/4
    no vad
    timeouts ringing infinity
    voice-port 2/5
    no vad
    timeouts ringing infinity
    voice-port 2/6
    no vad
    timeouts ringing infinity
    voice-port 2/7
    voice-port 2/8
    voice-port 2/9
    voice-port 2/10
    voice-port 2/11
    voice-port 2/12
    voice-port 2/13
    voice-port 2/14
    voice-port 2/15
    voice-port 2/16
    voice-port 2/17
    voice-port 2/18
    voice-port 2/19
    voice-port 2/20
    voice-port 2/21
    voice-port 2/22
    voice-port 2/23
    no mgcp timer receive-rtcp
    sccp local FastEthernet0/0
    sccp ccm 10.100.205.10 identifier 3 version 7.0
    sccp ccm 10.100.205.11 identifier 2 version 7.0
    sccp ccm 10.100.205.12 identifier 1 version 7.0
    sccp
    sccp ccm group 1
    associate ccm 1 priority 1
    associate ccm 2 priority 2
    associate ccm 3 priority 3
    switchback method graceful
    dial-peer voice 200 pots
    service stcapp
    fax rate disable
    port 2/0
    dial-peer voice 201 pots
    service stcapp
    fax rate disable
    port 2/1
    dial-peer voice 202 pots
    service stcapp
    fax rate disable
    port 2/2
    dial-peer voice 203 pots
    service stcapp
    fax rate disable
    port 2/3
    dial-peer voice 204 pots
    service stcapp
    fax rate disable
    port 2/4
    dial-peer voice 205 pots
    service stcapp
    fax rate disable
    port 2/5
    dial-peer voice 206 pots
    service stcapp
    fax rate disable
    port 2/6
    dial-peer voice 207 pots
    service stcapp
    shutdown
    port 2/7
    dial-peer voice 208 pots
    service stcapp
    shutdown
    port 2/8
    dial-peer voice 209 pots
    service stcapp
    shutdown
    port 2/9
    dial-peer voice 210 pots
    service stcapp
    shutdown
    port 2/10
    dial-peer voice 211 pots
    service stcapp
    shutdown
    port 2/11
    dial-peer voice 212 pots
    service stcapp
    shutdown
    port 2/12
    dial-peer voice 213 pots
    service stcapp
    shutdown
    port 2/13
    dial-peer voice 214 pots
    service stcapp
    shutdown
    port 2/14
    dial-peer voice 215 pots
    service stcapp
    shutdown
    port 2/15
    dial-peer voice 216 pots
    service stcapp
    shutdown
    port 2/16
    dial-peer voice 217 pots
    service stcapp
    shutdown
    port 2/17
    dial-peer voice 218 pots
    service stcapp
    shutdown
    port 2/18
    dial-peer voice 219 pots
    service stcapp
    shutdown
    port 2/19
    dial-peer voice 220 pots
    service stcapp
    shutdown
    port 2/20
    dial-peer voice 221 pots
    service stcapp
    shutdown
    port 2/21
    dial-peer voice 222 pots
    service stcapp
    shutdown
    port 2/22
    dial-peer voice 223 pots
    service stcapp
    shutdown
    port 2/23
    line con 0
    line aux 0
    line vty 0 4
    privilege level 15
    password 7 050A0A03285F590C1509
    login local
    transport input all
    ntp server 192.5.41.40 prefer
    end

    Paolo,
        Thank you for your reply.
    here is the PRI setup
    Current configuration : 4713 bytes
    version 15.1
    service timestamps debug datetime localtime show-timezone year
    service timestamps log datetime localtime show-timezone year
    service password-encryption
    service sequence-numbers
    hostname XXXXXX
    boot-start-marker
    boot-end-marker
    card type t1 0 0
    card type t1 0 1
    logging buffered 2500000
    no logging rate-limit
    no logging console
    enable secret 5 $1$..wF$krGZQpcpPZa6xLyTY0
    no aaa new-model
    clock timezone EST -5 0
    clock summer-time EST recurring
    clock calendar-valid
    network-clock-participate wic 0
    network-clock-participate wic 1
    network-clock-select 1 T1 0/1/0
    no ipv6 cef
    ip source-route
    ip cef
    no ip domain lookup
    multilink bundle-name authenticated
    isdn switch-type primary-4ess
    crypto pki token default removal timeout 0
    crypto pki trustpoint TP-self-signed-4191480364
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-4191480364
    revocation-check none
    crypto pki certificate chain TP-self-signed-4191480364
    certificate self-signed 01
      3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 34313931 34383033 3634301E 170D3132 30323031 31323034
      32335A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 31393134
      38303336 3430819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100C8AC 23369B3A 104D7D1D 50889B56 6FAFC0FC 679B1E8B FD127B9B 4A864E18
      C735C30C 1EC275CE AB0A461E CAC485BC 9225797F 4F02B8F6 4D1DD74B 97186BB7
      ED5C5069 4570C67E D092B24D E8DFE7F8 6E88E427 A352CA22 788226D9 79163767
      8095234E 91431356 FB065855 64070AAA 525C426D 406F9378 159D1695 16AEEF0D
      5DC10203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
      551D2304 18301680 14800A1E 7753AD8D C4D17569 2A7F98A8 B9CD89B2 B5301D06
      03551D0E 04160414 800A1E77 53AD8DC4 D175692A 7F98A8B9 CD89B2B5 300D0609
      2A864886 F70D0101 04050003 8181009C 54D470DD F3B6A8F3 B23C896B 3302631C
      24677CA3 35A2AD93 C6BE0C35 B621480F 9005D468 894F0B32 69CBBC7C 85F933AB
      33AC2811 3868E409 5127CC8A DA01B6BF 724945A2 FAF521C7 95799F41 D706EFBD
      DC4DD9AC D9D70C70 3A1D7E89 9DA17124 CFF9ECD9 86A0D5C8 FB2FEA90 21D488E3
      130F7C8A 2A28ED14 4F04A4AF 117F67
            quit
    voice-card 0
    voice service voip
    fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
    license udi pid CISCO2901/K9 sn FTX151300FK
    hw-module pvdm 0/0
    username admin password 7 1326333B462C0027222A
    redundancy
    controller T1 0/0/0
    shutdown
    cablelength long 0db
    controller T1 0/0/1
    shutdown
    cablelength long 0db
    controller T1 0/1/0
    cablelength long 0db
    pri-group timeslots 1-24 service mgcp
    controller T1 0/1/1
    shutdown
    cablelength long 0db
    interface GigabitEthernet0/0
    description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
    ip address 10.100.105.86 255.255.255.0
    duplex auto
    speed auto
    interface GigabitEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface Serial0/1/0:23
    no ip address
    encapsulation hdlc
    isdn switch-type primary-ni
    isdn incoming-voice voice
    isdn bind-l3 ccm-manager
    no cdp enable
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip route 0.0.0.0 0.0.0.0 10.100.105.1
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    voice-port 0/1/0:23
    echo-cancel coverage 64
    ccm-manager redundant-host 10.100.105.12
    ccm-manager mgcp
    no ccm-manager fax protocol cisco
    ccm-manager music-on-hold
    ccm-manager config server 10.100.105.11
    ccm-manager config
    mgcp
    mgcp call-agent 10.100.105.11 2427 service-type mgcp version 0.1
    mgcp dtmf-relay voip codec all mode cisco
    mgcp rtp unreachable timeout 1000 action notify
    mgcp modem passthrough voip mode nse
    mgcp package-capability rtp-package
    mgcp package-capability sst-package
    mgcp package-capability pre-package
    mgcp package-capability fm-package
    mgcp default-package fxr-package
    no mgcp package-capability res-package
    no mgcp timer receive-rtcp
    mgcp sdp simple
    mgcp profile default
    gatekeeper
    shutdown
    line con 0
    login local
    line aux 0
    line vty 0 4
    exec-timeout 60 0
    privilege level 15
    password 7 050A0A0F590C1509
    login local
    transport input all
    line vty 5 15
    exec-timeout 60 0
    privilege level 15
    login local
    transport input telnet ssh
    scheduler allocate 20000 1000
    ntp server 192.5.41.40
    end

  • Fax T.38 support on TDM/IP GW

    Hello gents,
    I have a customer which I need to provide a Trunk SIP to Service Provider. The connection to PBX (Alcatel OXE R10) will be done using E1 interfaces (alcatel is not IP Enable).
    I have a Cisco 3945 ISRG2 that make conversion between E1 (ISDN) interfaces and SP SIP network.
    Fax is an important subject for the customer and I have some questions on this item:
    - for T.38 fax support, I need to have DSP configured  (T.38 is medium complexity codec).
    - T.38 work in fax-relay mode, correct?
    - They have SG3 fax. To enable fax calls at SG3 speed, I need to support T38 v3.0 (on all endpoints / GW) and enable fax pass-through. Correct?
    Issue is that I don't support fax pass-through on SP Voice network.
    So final question is: do I support SG3 fax calls (maybe by lowering speed to G3) if I configure T38 fax-relay on my GW? Is there any consideration I need to take into account (DSP, Codec...)?
    For example, on my GW, I will have 240 simultaneous voice calls and 80 fax calls.
    for DSP calculation, I have take 320 low complexity calls and added 80 transcoding sessions to medium complexity.
    Is it correct or do I need to select 240 low complexity calls and 80 medium complexity calls and no transcoding (DSP for transcoding included in medium complexity calls)?
    Thanks for your help.

    Hi,
         You can try the follow lines of config on your ISR, these are for a gateway running H.323.  what is your current DSP/PVDM ration? -
    voice service voip
    allow-connections h323 to h323
    fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback cisco
    h323
    modem passthrough nse codec g711ulaw
    mgcp sdp simple
    mgcp fax t38 ecm
    mgcp fax t38 inhibit
    mgcp fax t38 gateway force
    I almost always force my SG3 fax calls back to G3.  If you want to do this as well add the following
    voice service voip
    fax-relay sg3-to-g3
    Thanks,
    Tony
    Please rate helpful posts!

  • HP 1240 FAX Setup

    I inherited a HP 1240 FAX machine; I would like to print a printer self-test report.It has the ink cartriges installed and the paper tray loaded.  When I plug it in and turn it on it displays 'Initializing'; then 'Phone Number'.  Whether I enter a phone number or not, when I press the 'OK' or 'Setup' button I hear 3 quick beeps and nothing happens.  I cannot find where this is discussed in the manual or the Setup Poster.Perhaps I need to be connected to a phone line and this is the number of that line.

    Hi , Welcome to the HP Support Forums! I see that you would like to get your HP Officejet 7612 Wide Format e-All-in-One faxing and would like to print a test report. I would like to assist you. When the printer is initializing, it needs to complete that process before you can do anything else. If the printer is stuck in that mode, I would try a Hard Reset. It goes through initialization to calibrate the cartridges, for best print quality. I would do a Hard Reset to see if that will resolve the issue.
    Leave the printer on and unplug the power cable from the printer and wall outlet for 60 seconds.
    Then reconnect the power cable to the printer and wall outlet rather than a surge protector.
    This ensures the printer is receiving full power and may help this situation.
    In order to fax from the HP Officejet 7612, it requires an active phone line. Preferably a dedicated phone line. I would try the steps within this guide, HP Officejet 7610 Wide Format e-All-in-One Printer Series (H912) - Cannot Send or Receive Faxes.The printer cannot send or receive faxes.
     Try the following solutions in the order presented to resolve the issue. Solution one: Print a fax test report Run a fax test report to determine the faxing status on the printer and whether or not it is configured correctly to send and receive faxes.From the Home screen on the printer control panel, touch the Right Arrow (), and then touch Setup ().Touch the Down Arrow (), and then touch Tools.Touch the Down Arrow (), and then touch Run Fax Test. The printer prints a fax test report.Touch OK.Review the report.If the fax test indicates that it does not detect a phone line or dial tone, continue to the next solution.If the results of the fax test are All Pass, skip to the Configure the fax for sending and receiving section in this document.Solution two: Check the fax connectionsUse the following steps to check the physical connections, and then test the fax. Step one: Check the physical connectionsDisconnect the telephone cord from the printer and wall jack, and then examine the connector on the end of the cord. Make sure that the cord has only two wires. If you see four wires, replace the cord with one containing only two wires.Figure : Example of a two-wire connectorFigure : Example of a four-wire connectorReconnect the telephone cord to the wall jack, and then reconnect the other end of the telephone cord to the port labeled 1-LINE on the rear of the printer.Figure : Connect the phone cord directly to the wall jackWall jackTwo-wire phone cordRemove the plug from the port labeled 2-EXT on the rear of the printer, and then connect a single-line telephone to this port.Figure : Connect the single-line phone to the 2-EXT portWall jackTwo-wire phone cordSingle-line telephoneIf other devices need to use the same wall jack, make sure that they are connected to the 2-EXT port on the rear of the printer.Figure : Connect other devices to the 2-EXT portWall jackTwo-wire phone cordAnswering machineSingle-line telephone NOTE: Click here to review detailed setup instructions for other connection configurations.Pick up the telephone receiver, and then listen for a dial tone. Make sure that you can dial out using the telephone keypad.If you hear a dial tone and you can dial out using the telephone, the printer is connected correctly to a working telephone cord and telephone jack.If you do not hear a dial tone, check the configuration again and make sure that it is set up correctly.Step two: Try to send and receive a faxTry to send and receive a fax.Show me how to test fax functionalityIf these steps resolved the issue, you do not need to continue troubleshooting.If the issue persists, continue to the next solution.Solution three: Configure the fax for sending and receiving Use the following steps to configure the fax for sending and receiving.Step one: Configure the fax for sending and receivingChoose one of the following options depending on your fax connection.Option one: Configure for a Voice over Internet Protocol (VoIP) systemOption two: Configure for a Digital Subscriber Line (DSL) Step two: Change the Rings to Answer settingFrom the Home screen on the printer control panel, touch the Right Arrow (), and then touch Setup ().Touch Fax Setup, touch Basic Fax Setup, and then touch Rings to Answer.Touch the Down Arrow () until the Rings to Answer setting is either 1 or 2 rings. Select at least one more ring than the phone answering machine setting, if connected.Touch Done.Step three: Change the Distinctive Ring setting NOTE: Only set a distinctive ring pattern if your phone service features the distinctive ring service. For more information, contact your telephone service provider.From the Home screen on the printer control panel, touch the Right Arrow (), and then touch Setup ().Touch Fax Setup, touch Advanced Fax Setup, and then touch Distinctive Ring.If prompted, touch Yes.Select the ring pattern assigned by the telephone company.If you know the ring pattern that the telephone company assigned to your fax number, select that ring pattern.If you do not know the ring pattern assigned by your telephone company, touch Ring Pattern Detection, and then follow the on-screen instructions.Step four: Try to send and receive a faxTry to send and receive a fax.Show me how to test fax functionalityIf these steps resolved the issue, you do not need to continue troubleshooting.If the issue persists, continue to the next solution.Solution four: Temporarily remove any other devices from the telephone line, and then reset the printerUse the following steps to remove any other devices from the telephone line, and then reset the printer. Step one: Remove any other devices from the telephone lineIf any other devices, such as a telephone, a telephone answering machine, or a modem, are connected to the telephone line, remove each device. NOTE: Remove each device even if the device is in another room connected to another wall jack or connected using a line splitter.Connect the telephone cord to the wall jack, and then reconnect the other end of the telephone cord to the port labeled 1-LINE on the rear of the printer.Figure : Connect the phone cord directly to the wall jackWall jackTwo-wire phone cordStep two: Reset the printerPress the Power button to turn on the printer.With the printer turned on, disconnect the power cord from the rear of the printer, and then unplug the power cord from the power source or electrical outlet.Disconnect the USB or Ethernet cable from the rear of the printer, if you have a cable connection to the printer.Wait 60 seconds.Reconnect the power cord to the rear of the printer, and then reconnect the USB or Ethernet cable.Reconnect the power cord to the wall outlet. Bypass any surge protectors.If the printer does not turn on by itself, press the Power button to turn it on.Try to send and receive a fax.Show me how to test fax functionalityIf these steps resolved the issue, you do not need to continue troubleshooting.If the issue persists, continue to the next solution.Solution five: Service the printer If you have completed all the solutions listed above and are still experiencing a problem, continue to the Service the printer section at the end of this document. Print a Printer Status ReportTo make sure that the hardware functions correctly, print a Printer Status Report as a test page.Load plain white paper in the tray.From the Home screen on the printer control panel, touch the Right Arrow (), and then touch Setup ().Touch the Down Arrow (), and then touch Reports.Touch Printer Status Report. The test page prints.Figure : Printer Status ReportIf these steps resolved the issue, and the test page prints, there is no need to continue troubleshooting.If the issue persists, continue with the next solution.If the test page does not print, continue with the next solution.
    Hope this answers your question. Thank you for posting!

  • FAX Error

    The configuration below is for SIP Trunk, but having issues with Faxing. It dials fine, but then sender receives an error, and it doesn't even get connected.
    Can someone shed some lights.
    See Attached Config

    Under your sip dial-peers you don't specified a fax protocol transmission method so the voip service voip fax method is use. Nothing is specified in voice service voip and so the default is use:
    Defaults
    cisco fa relay for all other platforms
    none for the Cisco AS5350, Cisco AS5400, and Cisco AS5850
    Does destination sip peer support Cisco fax relay?
    If no try to use t38 standard method:
    codec g711alaw
    fax rate 9600
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
    no vad
    If no relay method is supported try to configure pass-through:
    codec g711alaw
    fax rate disable
    fax protocol pass-through g711alaw
    no vad
    see these commands also:
    "bearer-cap speech" command under each voice-port;
    "network-clock-select 1 T1 0/0/0" enter this command for each interface that is to receive faxes specifying a different priority;

  • Re: newer iMac (mid-2010 w/Snow Leopard) fax operation w/o external fax machine

    Noting that Apple no longer offers an external USB fax modem product, are similar kinds of devices (like, for example, USRobotics5637 or Zoom3095) reliable for sending (via the print menu in OS X 10.6.x applications) and receiving? 
    An existing "automatic fax switch" is already connected to the landline, and it routes incoming calls now to the phone handset (after initially listening for incoming fax handshaking signals, which it is assumed would be routed to the iMac -- where they are archived and displayed is yet to be determined) or to the voice answering machine if the handset isn't picked-up after a few rings.  This has been serving admirably as a way to screen incoming calls, BTW!)).  My Internet connection is an ISP DSL, which wouldn't come into play if I'm sending/receiving fax via landline, at "dial-up" speeds and protocols through te external USB fax modem, as I understand it. 
    My understanding is that the USB external fax modem would be connected to a USB port (USB keyboard or rear panel of the iMac) and the RJ11 connector on the other end of that fax modem would be connected to RJ11 "fax modem" receptical on the existing "automatic fax switch".  I'm guessing that the "automatic fax switch" would go off-hook and dial up the phone number of the distant fax machine, from phone number data provided in the "send a fax" set-up invoked when "send a fax" is selected as a "print" option in an OS X 10.6.x application.
    Please advise if the equipment and scenario described, and elaborate on anything I'm missing, will work for the intended goal.
    thanks,
    dL 

    Gaston,
    This is not the correct Feedback venue for your issue.
    Please select an appropriate product from those displayed HERE and use the corresponding form to communicate to the correct department.
    ali b

  • Faxes are aborted after communication is established.

    I used to successfully send faxes using the fax function in the print window. However, for the last few months, and for no apparent reason, the fax function has been aborting all attempted transmissions after apparently beginning transmission.
    The function successfully makes contact with the receiving number, and then appears to start faxing. It then stops faxing, without stating whether it has finished faxing successfully.
    The aborted fax then remains in the queue, with "hold until xxxx", i.e. a period of 5 minutes which is when it will automatically try again. When it re-tries, the same failure occurs.
    It also displays a fax protocol error.
    The intended recipient does not receive a fax.
    My iMac has a v.92 modem. Nevertheless, I did try faxing with the v.90 modem script (which can be selected in Network Preferences), but faxes were still aborted in the same way.

    Juan,
    I will find out from our programmers if we can implement the suggestions. I have came across the Paid solution earlier today, but will have to investigate further.
    I will let you know what option was taken and what the outcome was.

  • Fax is not working on H323

    Hello All,
    I have an issue with fax, it is connected to an fxs port on my h323 gateway. When a call comes from PRI and get connected to fax after I hear the fax tone the fax drops. IOS is Version 15.0(1)M4, and DSP is PVDM3.
    My analysis:
    The external calls hit gateway and it matches the pots dialpeer where my fax connected to. From the "debug voip vtsp all", I see Primary Fax Protocol=CISCO_FAX_RELAY, which is not enabled and we are using T38 relay and modem passthrough method for faxing. I believe PVDM3 does not work with Cisco Relay and couldn't allocate any dsp resources for the call and it drops. But still I wonder how gateway takes cisco relay.
    Config:
    voice service voip
    allow-connections h323 to h323
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
    h323
      emptycapability
    modem passthrough nse codec g711ulaw
    dial-peer voice 1001 pots
    tone ringback alert-no-PI
    description PSTN Incoming, Pattern:.
    translation-profile incoming PSTN-to-PhoneDN
    incoming called-number .
    direct-inward-dial
    dial-peer voice 999030 pots
    tone ringback alert-no-PI
    destination-pattern 3027898
    progress_ind setup enable 3
    port 0/3/0
    Output of vtsp debug
    Oct  4 20:30:07: //6824/97F0D7BD8350/VTSP:(0/1/0:15):7:1:1/vtsp_dsm_save_fax_config: 
       Fax Relay=ENABLED
       Primary Fax Protocol=CISCO_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY
       Fax Relay CM Suppression :=ENABLED, Fax Relay ANS Suppression :=DISABLED
       Fax Parameters Set By=Dialpeer, Peer=999030 (this is the peer where my fax connected to)
    I have converted the port to MGCP and found its working, while faxing I see vtsp outputs
    Oct  4 23:57:29: //7181/8FE17FEF8379/VTSP:(0/3/0):-1:1:2/vtsp_dsm_save_fax_config:
       Fax Relay=DISABLED - MGCP Application
       Primary Fax Protocol=IGNORE_FAX_RELAY, Fallback Fax Protocol=IGNORE_FAX_RELAY
       Fax Relay CM Suppression :=ENABLED, Fax Relay ANS Suppression :=DISABLED
       Fax Parameters Set By=MGCP Call Type --> I believe MGCP disabled the cisco fax relay and switch over to T38.
    Oct  4 23:57:40: //7181/8FE17FEF8379/VTSP:(0/3/0):-1:1:2/vtsp_dsm_save_fax_config:
       Fax Relay=ENABLED
       Primary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY
       Fax Relay CM Suppression :=ENABLED, Fax Relay ANS Suppression :=DISABLED
       Fax Parameters Set By=MGCP Call Type
    Can some one kindly suggest how to make it work on H323, also how we can force disabling cisco fax relay?

    As I mentioned earlier, we are using MGCP for that particular fax port and the gateway we use as H323.
    Even I'm not pretty sure about using mixed protocol, I believe this gateway gonna used to support call center calls. SInce MGCP is easy for configs they might have confiugred only the port as MGCP endpoint.
    Now its not working with both the cases, not in mgcp as well as fallback mode. Can you reveiw the debugs and see why I have to remove "modem passthrough" command from voice service voip section which of our standard config and works well with all other gateway of ours. Please help here.

  • Can't receive fax LaserJet Pro MFP M127fw

    While I can send faxes on my LaserJet Pro MFP M127fw, I can't receive them.  I've downloaded the newest software & drivers, and the LaserJet Firmware Update utility, and run the fax test, with the report indicating it passed.

    Hello @V122,
    I'm sorry to hear that the reset made no difference.
    Because your fax machine will manually answer faxes we know that the fax modem in your printer is functioning properly. In saying that, I did a bit more research into the Fios phone line that you're using and I do believe that your issue lies with your digital fiber-optic phone line.
    Faxing is old analog technology. Nowadays many phone providers offer digital phone lines (like your Fios line). These digital phone lines should work OK with your fax machine. However, there is a lot more static noise and interference on those digital phone lines that cause fax receiving issues. Because your fax can manually answer we know, as I previously stated, that the fax modem is functioning. However, the fax signal isn't strong enough (probably due to digital interference) to prompt your machine to wake up and automatically answer the fax. Simply stated, your machine does not detect a fax coming through.
    According the the User Guide for your printer: "HP products are designed specifically for use with analog phone services."  Source: User Guide: Page 110 (120-128)
    Because Fios operates like Voip (Digital internet based phone line) we could try to lower your Fax Speed to Slow on your printer to give your fax machine more time to 'listen' and 'connect' as the digital signals transfer much faster than analog signals.
    How to Lower Fax Speed:
    Select the Setup button on your printer
    Right arrow to Fax Setup
    Right arrow to Advanced Fax Setup
    Select Fax Speed and alter this to Slow
    Once the Fax Speed has been changed to slow, please try to receive a fax automatically again to see how your printer responds.
    Please let me know if the Fax Speed adjustment resolves your issue. Good luck!
    X-23
    I work on behalf of HP
    Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
    Click the "Kudos, Thumbs Up" on the right to say "Thanks" for helping!

Maybe you are looking for