cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

313
Views
5
Helpful
1
Replies
Highlighted
Beginner

Fax problem

Hi friends.

We deployed Imagicle fax server in our network and configured the router to send and receive faxes.

we received the faxes without any problem but we cant send the fax.

the connectivity to PSTN is sib trunk and my configuration is:

 

sho run | sec dial-
dial-peer voice 717430001 voip
description * Outgoing calls to CUCM *
translation-profile outgoing PSTN-Normalization
preference 1
destination-pattern 71743...
rtp payload-type cisco-fax-relay 127
rtp payload-type cisco-codec-fax-ack 126
rtp payload-type cisco-codec-fax-ind 122
rtp payload-type nte 97
session protocol sipv2
session target ipv4:192.168.202.31
session transport tcp
incoming called-number 71743...
voice-class codec 10
voice-class source interface Loopback0
dtmf-relay rtp-nte
no vad
dial-peer voice 9999 voip
description * Outgoing Call TO SBC-SIP *
destination-pattern .T
session protocol sipv2
session target ipv4:10.123.101.173
dtmf-relay rtp-nte sip-notify sip-kpml
codec g711ulaw
no vad
dial-peer voice 717430002 voip
description * Outgoing calls to CUCM *
translation-profile outgoing PSTN-Normalization
preference 2
destination-pattern 71743...
rtp payload-type cisco-fax-relay 127
rtp payload-type cisco-codec-fax-ack 126
rtp payload-type cisco-codec-fax-ind 122
rtp payload-type nte 97
session protocol sipv2
session target ipv4:192.168.202.30
session transport tcp
incoming called-number 71743...
voice-class codec 10
voice-class source interface Loopback0
dtmf-relay rtp-nte
no vad
dial-peer voice 71743700 voip
description * Incoming Fax to Imagicle- 7xx *
destination-pattern 7..
session protocol sipv2
session target ipv4:192.168.202.38
session transport udp
dtmf-relay sip-kpml sip-notify cisco-rtp
codec g711ulaw
no vad



voice service voip
no ip address trusted authenticate
callmonitor
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
no supplementary-service sip handle-replaces
redirect ip2ip
fax protocol t38 version 0 ls-redundancy 2 hs-redundancy 0 fallback pass-through g711ulaw
modem passthrough nse codec g711ulaw
h323
call service stop
sip
min-se 300
header-passing
registrar server expires max 600 min 60
midcall-signaling passthru
call-route url
no call service stop
!
voice class codec 10
codec preference 1 g711ulaw
codec preference 2 g711alaw
!
!
!
!
!
!
voice translation-rule 1
rule 1 /^71743000/ /7777/
rule 2 /^71743\([1-6]..$\)/ /+71743\1/
rule 3 /^71743\([8-9]..$\)/ /+71743\1/
rule 4 /^717437\(..$\)/ /7\1/
!

 

what is the problem? 

thanks

best regards

Everyone's tags (1)
1 REPLY 1
VIP Collaborator

Re: Fax problem

Have you looked at the Dialed Number Analyzer to see if CUCM is processing the outbound fax properly? If so, what do the SIP messages in the CUCM trace file indicate when attempting to send the call outbound?

What digits is CUCM sending to the router when an outbound fax is attempted? The reason I ask is that I see your two CUCM dialpeers having incoming called-number 71743... and the dialpeer pointing to the SBC not having an incoming-called number pattern. This means that if CUCM is sending 8-digits I don't see where that is being truncated to 3-digits to match the fax dial peer. Otherwise, if CUCM is sending 3-digits, then I don't see a dial-peer to accept that call in which case it will use dial-peer 0 which defaults to G729 which may be causing a codec mismatch problem.

Let us know what you find and we will look further.

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here