Problems with incomplete faxes using onramp

Unanswered Question
Oct 27th, 2009

Hi,

I'm experiencing problems with incomplete faxes coming through a UC500 with BRI connections using onramp fax-to-email. Below is the configuration used (more relevant parts). I would appreciate any ideas as I couldn't find proper troubleshooting guides for this problem.

network-clock-participate wic 1
network-clock-select 1 BRI0/1/0
!
ip domain name hub.com.mt
ip name-server 194.158.37.196
ip name-server 194.158.37.211
!
stcapp ccm-group 1
stcapp
!
stcapp feature access-code
!
multilink bundle-name authenticated
isdn switch-type basic-net3
!
!
trunk group  ALL_BRI
hunt-scheme longest-idle
!
!
trunk group  ALL_FXO
max-retry 5
voice-class cause-code 1
hunt-scheme longest-idle
!
!
voice call send-alert
voice rtp send-recv
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
sip
  no update-callerid
!
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
!
!
!
!
!
!
!
voice class cause-code 1
no-circuit
!
!
!
!
!
voice register global
max-dn 56
max-pool 14
!
!
!
voice-card 0
no dspfarm
!
fax interface-type fax-mail
mta send server mail.server.net port 25
mta send with-subject both
mta send postmaster [email protected]
mta send mail-from hostname xyz.com.mt
mta send mail-from username info
!
application
  service onramp flash:/app_faxmail_onramp.2.0.1.3.tcl
  !
!
!
!
!
interface BRI0/1/0
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
isdn static-tei 0
trunk-group ALL_BRI 64
!
interface BRI0/1/1
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
shutdown
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
isdn static-tei 0
trunk-group ALL_BRI 64
!
!
!
!
voice-port 0/1/0
compand-type a-law
bearer-cap Speech
!
voice-port 0/1/1
compand-type a-law
bearer-cap Speech
!
voice-port 0/2/0
trunk-group ALL_FXO 64
connection plar opx 51
!
voice-port 0/2/1
trunk-group ALL_FXO 64
connection plar opx 51
!
voice-port 0/2/2
trunk-group ALL_FXO 64
!
voice-port 0/2/3
trunk-group ALL_FXO 64
!
!
dial-peer voice 70 pots
description ** incoming fax-to-email dial peer **
service onramp
incoming called-number 01
direct-inward-dial
port 0/2/1
!
dial-peer voice 2500 mmoip
service fax_on_vfc_onramp_app out-bound
destination-pattern 01
information-type fax
session target mailto:[email protected]
!
!
no dial-peer outbound status-check pots
!
!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
simon.vella Wed, 10/28/2009 - 06:38

Thanks. I had gone through this document already.

My configuration is such that the MTA server is an SMTP server, not through CUE. I don't need to use CUE functionality in this case.

The problem is either in the incoming fax through the BRI links, or else in the fax-to-doc conversion itself. However, I couldn't isolate the problem properly.

This afternoon I hope to connect a faxmachine directly to an FXO port and use fax-to-email, in order to isolate the BRI out of the system.

Any comments appreciated.

Saurabh Verma Wed, 10/28/2009 - 07:09

So looks like the faxes are coming through, but they are incomplete (not all pages)?? This may be caused due to errors in the fax reception (from the BRI lines). Can you check to see if there are any errors on the BRI interface? I think the FXO test will be critical in isolating the problem.

-Saurabh

dlob Fri, 01/22/2010 - 07:13

Hi, I'm having this same exact problem receiving faxes using fax onramp trough ISDN BRI lines. Is there any solution???

simon.vella Fri, 01/22/2010 - 07:23

Hi,

Faxes were coming in fine on the FXO port but with problems (blurred pages, etc) on the ISDN BRI ports (which didn't have errors nor clock-sync issues, etc).

The problem seems to have been the IOS packaged with the UC500 7.0.3 package.

We had resolved the problem after we upgraded to uc500-advipservicesk9-mz.124-22.YB4.

regards

Simon

Actions

This Discussion