FAX--Store and Forward

Unanswered Question
Feb 27th, 2008

Hi,

I have configured store and forward fax on one of my 3845 gateways (ios C3845-ADVIPSERVICESK9-M) :

================================

fax receive called-subscriber $d$

fax interface-type fax-mail

mta send server A.B.C.D (ip address of the mail server)

mta send with-subject both

mta send mail-from hostname akl-core01.turnstone.net.nz

mta send mail-from username fax-mail

!

application

service faxmail_onramp flash:app_faxmail_onramp.2.0.1.3.tcl

!

service fax_detect flash:app_fax_detect.2.1.2.2.tcl

!

dial-peer voice 139770089 pots

service faxmail_onramp

information-type fax

incoming called-number 39770089

direct-inward-dial

!

dial-peer voice 239770089 mmoip

service fax_on_vfc_onramp_app out-bound

destination-pattern 39770089

information-type fax

session target mailto:[email protected]

image encoding MH

image resolution super-fine

!

=============================

ISDN PRA is the connection to PSTN. Debug isdn q931 is as follows:

----------------

409726: Feb 28 11:03:35.059: ISDN Se0/3/0:15 Q931: RX <- SETUP pd = 8 callref = 0x1F70

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18383

Preferred, Channel 3

Calling Party Number i = 0x2183, '21856588'

Plan:ISDN, Type:National

Called Party Number i = 0xC1, '39770089'

Plan:ISDN, Type:Subscriber(local)

High Layer Compat i = 0x9181

Sending Complete

409727: Feb 28 11:03:35.071: ISDN Se0/3/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9F70

Channel ID i = 0xA98383

Exclusive, Channel 3

409728: Feb 28 11:03:35.075: ISDN Se0/3/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x9F70

Cause i = 0x8083 - No route to destination

409729: Feb 28 11:03:35.151: ISDN Se0/3/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x1F70

409730: Feb 28 11:03:35.155: ISDN Se0/3/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x9F70

---------------------------------

I can telnet to the server on port 25 from this router. Why did I get a 'No route to destination' message? How to solve the problem?

p.s. One other router has exactly the semilar configuration and working fine.

Thanks.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Zin.Karzazi Thu, 02/28/2008 - 09:56

Please post the output from "show dial-peer voice summary". Also remove the "infomation-type fax" under your pots dial peer.

Chuan Liu Thu, 02/28/2008 - 13:00

Hi Zin,

I tried removing the "information-type fax" command. No luck. Here is the summary: I removed the ip addresses.

=======================

sh dial-peer voi su

dial-peer hunt 0

AD PRE PASS OUT

TAG TYPE MIN OPER PREFIX DEST-PATTERN FER THRU SESS-TARGET STAT PORT

10 pots up up .T 0 up 0/3/0:15

39770- voip up up 3977009. 0 syst ipv4:

09

39770- voip up up 39770076 0 syst ipv4:

076

39770- voip up up 39770077 0 syst ipv4:

077

39770- voip up up 39770078 0 syst ipv4:

078

39770- voip up up 39770079 0 syst ipv4:

079

39770- voip up up 39770084 0 syst ipv4:

084

39684- voip up up 3968463. 0 syst ipv4:

63

39680- voip up up 3968002. 0 syst ipv4:

02

13977- voip up up 3977008. 1 syst ipv4:

008

13977- voip up up 39770075 3 syst ipv4:

0075

23977- voip up up 39770075 2 syst ipv4:

0075

39612- voip up up 3961299. 1 syst ipv4:

29

39770- pots down down 0 down 0/3/0:15

080

23977- voip up up 39770080 1 syst ipv4:

0078

13977- pots up up 0 down

0089

23977- mmoip up up 39770089 0

0089

============================

Thanks.

heiberfrancisco Wed, 11/19/2008 - 13:20

hi, Now I have the tcl file, but whit this configuration dont work the fax to mail;

application

service fax_on flash:faxmail_onramp.tcl

!

!

!

fax receive called-subscriber $d$

fax interface-type fax-mail

mta send server 192.168.0.246 port 25

mta send subject "Servicio de Fax AEC.S.A."

mta send with-subject $s$

mta send origin-prefix "AEC.S.A."

mta send postmaster [email protected]

mta send mail-from hostname cisco.midominio.com.co

mta send mail-from username $s$

dial-peer voice 12 pots

description --------------FAX

service fax_on

incoming called-number 3279659

direct-inward-dial

port 1/5:D

dial-peer voice 11 mmoip

service fax_on_vfc_onramp_app out-bound

destination-pattern 3279659

session target mailto:[email protected]

this is the show call history voice brief

F18 : 108377 152975920ms.93875 +-1 +40 pid:10 Answer 17420719

dur 00:00:00 tx:0/0 rx:0/0 1 (unassigned number (1))

Telephony 1/5:D (108377) [1/5.24] tx:0/0/0ms None noise:0dBm acom:0dBm

long duration call detected:n long dur callduration :n/a timestamp:n/a

thanks a lot.

Chuan Liu Wed, 11/19/2008 - 13:57

Hi,

You may need the fax detect tcl. Here is my working config:

application

service faxmail_onramp flash:app_faxmail_onramp.2.0.1.3.tcl

!

service fax_detect app_fax_detect.2.1.2.2.tcl

!

You can use "show call hist fax" to chech the fax infor.

Regards.

heiberfrancisco Tue, 12/16/2008 - 13:52

Hi, thanks a lot, now is working, but in some many call, give me this error

show call fax history voice brief

1F6 : 209228 238019430ms.178911 +1000 +21150 pid:105 Originate [email protected]

dur 00:00:20 tx:7250/0 rx:0/0 6F :0 (protocol error (111):)

MMOIP 192.168.0.246 AcceptedMime:0 DiscardedMime:0

1F6 : 209205 238003890ms.178912 +10 +36730 pid:305 Answer 56644538

dur 00:00:36 tx:13/168 rx:47/940 6F :6F (protocol error (111):protocol error (111): Receive communication)

Telephony 1/4:D (209205) [1/4.17] tx:0/0/0ms 9600 noise:-83dBm acom:57dBm

long duration call detected:n long dur callduration :n/a timestamp:n/a

?

Chuan Liu Tue, 12/16/2008 - 18:08

Hi,

If the problem happens randomly, I would say the configs are OK, and then focus on the digital interface and packet loss.

Rgds.

Nicholas Matthews Tue, 12/16/2008 - 18:38

It's also possible to get protocol errors when you're using T37 if there is a fax-layer problem that fails. This can happen if we send fax tones and we're ready for page data, but no page data comes. If any of the number of fax timers expire, we will disconnect with 111 protocol error.

Actions

This Discussion