onramp fax problems

Answered Question

Hello,


I'm currently working on configuring onramp Fax on a Cisco 3825 with IOS 12.4(15)T9. We have Cisco CallManager Express 4.1 and Cisco Unity Express 3.1(NME-CUE module)


I got some questions:


I've configured the necessary dial-peers, one inbound pots and one mmoip.We have a faxmachine here in our office, so when I send a fax to 00765724099 it doesn't work. It dials the string but after 40 seconds it just disconnects with I think a busy tone.


With show dial-peer voice 2000, I get Last Disconnect Text is "no user answer (19)",


With show dial-peer voice 3000, I get disconnect-cause = `no-service'



What am I doing wrong here?


If you need more information about my configuration, just ask.


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


Below part of my configuration:


fax interface-type fax-mail
mta send server 192.x.x.x port 25
mta send with-subject both
mta send mail-from username gb
!
application
  service onramp flash:app_faxmail_onramp.2.0.1.3.tcl
  !


voice-port 0/0/0
translate calling 1
compand-type a-law
cptone NL
!


dial-peer voice 2000 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number 765724099
direct-inward-dial
port 0/0/0


dial-peer voice 3000 mmoip
description FAX
service fax_on_vfc_onramp_app out-bound
destination-pattern 765724099
information-type fax
session target mailto:[email protected]
!




Thanks,


~Grant

Correct Answer by paolo bevilacqua about 7 years 7 months ago

T.37 does not requires AAA or radius. I think your config is correct, not sure why is failing.


Try "debug foip on-ramp" or other debugs from: http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dtfaxcom.html#wp1007025


You can also try a different IOS, eg 12.4(22)YB4

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
paolo bevilacqua Mon, 12/21/2009 - 06:43
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Begin taking "debug isdn q931" with "term mon".

I get the following output:


004428: *Dec 21 15:52:52.179 WEST: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/1, TEI 0 changed to up
004429: *Dec 21 15:52:52.243 WEST: ISDN BR0/1/1 Q931: RX <- SETUP pd = 8  callref = 0x1C
        Sending Complete
        Bearer Capability i = 0x9090A3
                Standard = CCITT
                Transfer Capability = 3.1kHz Audio
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0x81
                Preferred, B1
        Progress Ind i = 0x8083 - Origination address is non-ISDN
        Calling Party Number i = 0x2181, '765209327'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '765724099'
                Plan:ISDN, Type:National
004430: *Dec 21 15:52:52.255 WEST: ISDN BR0/1/1 Q931: TX -> CALL_PROC pd = 8  callref = 0x9C
        Channel ID i = 0x89
                Exclusive, B1
004431: *Dec 21 15:52:52.271 WEST: ISDN BR0/1/1 Q931: TX -> CONNECT pd = 8  callref = 0x9C
        Channel ID i = 0x89
                Exclusive, B1
004432: *Dec 21 15:52:52.311 WEST: ISDN BR0/1/1 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x1C
004433: *Dec 21 15:52:52.311 WEST: %ISDN-6-CONNECT: Interface BRI0/1/1:1 is now connected to 765209327 N/A
004434: *Dec 21 15:52:58.311 WEST: %ISDN-6-CONNECT: Interface BRI0/1/1:1 is now connected to 765209327 N/A
004435: *Dec 21 15:53:32.455 WEST: %ISDN-6-DISCONNECT: Interface BRI0/1/1:1  disconnected from 765209327 , call lasted 40 seconds
004436: *Dec 21 15:53:32.455 WEST: ISDN BR0/1/1 Q931: TX -> DISCONNECT pd = 8  callref = 0x9C
        Cause i = 0x8093 - User alerting, no answer
004437: *Dec 21 15:53:32.659 WEST: ISDN BR0/1/1 Q931: RX <- RELEASE pd = 8  callref = 0x1C
        Cause i = 0x8093 - User alerting, no answer
004438: *Dec 21 15:53:32.659 WEST: ISDN BR0/1/1 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x9C

paolo bevilacqua Mon, 12/21/2009 - 07:04
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Do you have the .tcl file copied into flash ?

Can you take "debug voice application script"

Yes, I do.


CMUC01#show flash
-#- --length-- -----date/time------ path
1     51823948 Aug 18 2009 13:23:20 +00:00 c3825-advipservicesk9-mz.124-15.T9.bin
........
44       12262 Dec 18 2009 09:57:10 -01:00 app_faxmail_onramp.2.0.1.3.tcl



Output:

004539: *Dec 21 16:06:25.439 WEST: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up
004540: *Dec 21 16:06:25.483 WEST: //304//TCL :/tcl_PutsObjCmd:
Authentication control is 0
004541: *Dec 21 16:06:25.483 WEST:
004542: *Dec 21 16:06:25.483 WEST: //304//TCL :/tcl_PutsObjCmd:
Accounting control is 0
004543: *Dec 21 16:06:25.483 WEST:
004544: *Dec 21 16:06:25.487 WEST: //304//TCL :/tcl_PutsObjCmd:
Authentication method is 0
004545: *Dec 21 16:06:25.487 WEST:
004546: *Dec 21 16:06:25.487 WEST: //304//TCL :/tcl_PutsObjCmd:
Default password is
004547: *Dec 21 16:06:25.487 WEST:
004548: *Dec 21 16:06:25.487 WEST: //304//TCL :/tcl_PutsObjCmd: Accounting method is fax
004549: *Dec 21 16:06:25.487 WEST:
004550: *Dec 21 16:06:25.487 WEST: //304//TCL :/tcl_PutsObjCmd:
destination is 765724099
004551: *Dec 21 16:06:25.487 WEST:
004552: *Dec 21 16:06:25.543 WEST: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 765209327 N/A
004553: *Dec 21 16:06:31.543 WEST: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 765209327 N/A
004554: *Dec 21 16:07:05.703 WEST: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1  disconnected from 765209327 , call lasted 40 seconds
004555: *Dec 21 16:07:16.015 WEST: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down

Thanks for the reply. Good to know that RADIUS isn't needed.



But I fixed it. It's working now.First I enabled debug fax mta all and went through it step by step and I saw:


007330: *Dec 24 14:29:45.165 WEST: //-1/F762056680C4/SMTPC/esmtp_client_engine_work_routine:
   error in response to MAIL FROM


I added the mta send mail-from hostname WORD command and it worked

paolo bevilacqua Thu, 12/24/2009 - 05:53
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

I did not remembered which commands are mandatory and which are not.

Good to know you have it working.


Please remember to rate useful posts with clicking on the stars below.

paolo bevilacqua Thu, 12/24/2009 - 06:11
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Thanks for the nice rating.


Now most likely you need:


network-clock-participate wic 0

network-clock-select 1  BRI 0/1/1

paolo bevilacqua Thu, 12/24/2009 - 09:17
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Yes they are really necessary.

Alright.


I stumbled upon a major issue here. Once serivce onramp is configured on dial-peer voice 2000 pots, people aren't able to reach us anymore. debug isdn q931 gives the following output:



000213: *Dec 25 23:16:28.779 WEST: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed
000214: *Dec 25 23:16:28.831 WEST: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x55
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0x81
                Preferred, B1
        Calling Party Number i = 0x2181, '618016387'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '765724030'
                Plan:ISDN, Type:National
        High Layer Compat i = 0x9181
000215: *Dec 25 23:16:28.839 WEST: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8  callref = 0xD5
        Channel ID i = 0x89
                Exclusive, B1
000216: *Dec 25 23:16:28.855 WEST: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8  callref = 0xD5
        Cause i = 0x8081 - Unallocated/unassigned number
000217: *Dec 25 23:16:29.087 WEST: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8  callref = 0x55
        Cause i = 0x8081 - Unallocated/unassigned number
000218: *Dec 25 23:16:29.087 WEST: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0xD5


I also did a debug voip ccapi inout and saw when service onramp was configured that the calls always went through dial-peer voice 2000 pots which had the service onramp configured on it.


We have 3 more dial-peer voice pots configured for incoming ISDN calls.


This is the config WITH onramp configured. But I took it out for now, because we need to be reachable for our customers.


dial-peer voice 2000 pots
description Binnenkomende gespreken ISDN

service onramp
incoming called-number .T
direct-inward-dial
port 0/0/0
!
dial-peer voice 2001 pots
description Binnenkomende gespreken ISDN
incoming called-number .T
direct-inward-dial
port 0/0/1
!
dial-peer voice 2002 pots
description Binnenkomende gespreken ISDN
incoming called-number .T
direct-inward-dial
port 0/1/0
!
dial-peer voice 2003 pots
description Binnenkomende gespreken ISDN
incoming called-number .T
direct-inward-dial
port 0/1/1


How can I configure this so that it works with service onramp? I'm thinking the issue lies with DID, not sure tho. Not an expert



Thanks,


~Grant

Just tried something.


When dial-peer voice 2000 pots is configured the following way:


dial-peer voice 2000 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number 765724099
direct-inward-dial
port 0/0/0



It works just fine. Incoming ISDN calls work fine. As soon as I configure dial-peer voice pots the following way:


dial-peer voice 2000 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number .T
direct-inward-dial
port 0/0/0



Like this, incoming ISDN calls fail.



We have 3 numbers that will use the onramp faxing. I thought if I configure .T on dial-peer voice 2000 pots, the router would recognize the call as fax and use that dial-peer etc. Guess I was wrong. The 3 numbers that will be used for onramp fax all begin the following way: 7657240xx .




How can I do this?


Thanks,


~Grant

paolo bevilacqua Sat, 12/26/2009 - 04:22
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

The configuration depends on what you want to do with the other numbers.

paolo bevilacqua Sat, 12/26/2009 - 05:10
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

You need to configure one DP with service onramp for each number.

For the remaining numbers, you need to specify exactly what do you want to do with them.

So if I understand this correctly, I need 3 dial-peers in total for the onramp fax?


Onramp fax:

dial-peer voice 2000 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number 765724099
direct-inward-dial
port 0/0/0


dial-peer voice 2001 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number 765724038
direct-inward-dial
port 0/0/0


dial-peer voice 2002 pots
description Binnenkomende gespreken ISDN
service onramp
incoming called-number 765724039
direct-inward-dial
port 0/0/0



Normal calls(DP 2003 - .....)

dial-peer voice 2003 pots
description Binnenkomende gespreken ISDN

incoming called-number .T
direct-inward-dial
port 0/0/0



Is this a correct configuration? Also, what about the port . Can I use port 0/0/0  for all 3 onramp dial-peers?



Thanks,


~Grant

paolo bevilacqua Mon, 12/28/2009 - 07:25
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

You need as many DPs for as many patterns you have. In fact you could merge DP 2001 and 2002 with called-number 76572403[89]


Port does not matter for incoming DP on ISDN and you can omit it.


The DP for other calls should use called-number .+

Actions

This Discussion