Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Fax issue - cannot fax from RightFax server to Internal fax machine

I have the following gear:

RightFax server version 9.32 w/SP2

2851 Version 12.4(24)T

CUCM version 6.1.2.1119-1

VG224 version 12.4(20)T1

The RightFax server is connected to the 2851 via ser1/0/0 (PRI).

The 2851 is H323 with a SIP trunk to the PSTN

The VG224 is SCCP-controlled by CUCM

2851 config snippet for interface used to connect RightFax to 2851:

*** RightFax PRI ***

controller T1 1/0/0
clock source internal
pri-group timeslots 1-16,24

interface Serial1/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn protocol-emulate network
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
no cdp enable


In CUCM, the VG224 is defined as a SCCP device.  The fax mode for the VG224 is "Fax Relay"

There are over 20 fax machines in the environment.  For the purpose of this discussion, I will only focus on a single VG224 (although the fax machines are spread across 6 VG224s).  Here's the issue.  There are 2 fax machines (DN 6872 and 6876) on this VG224.  I can send a fax from RightFax to 6872 but not to 6876  Both fax machines can send and receive faxes to/from the PSTN.  The error I see in RightFax for the fax I'm trying to send to 6876 is "Dial err: No loop current".  If I compare the "show voice port 2/x" output for the two ports, they are identical.  I performed two test faxes to each DN.  I captured the following debug on the first test: debug voip ccapi inout.  The debug output was exactly the same, line by line for each call, until I got to here:

Good call:

Oct 17 14:49:32.667: //157839/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
   Interface=0x63E7660C, Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1)
Oct 17 14:49:32.667: //157839/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
Oct 17 14:49:35.479: //157839/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:

Bad call:

Oct 17 14:56:03.855: //157842/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
   Interface=0x63E69D28, Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1)
Oct 17 14:56:03.855: //157842/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
Oct 17 14:56:06.875: //157842/xxxxxxxxxxxx/CCAPI/ccCallFeature:                  <------  What is feature type 34 and which device is requesting this?
   Feature Type=34, Call Id=157842
Oct 17 14:56:06.875: //157842/xxxxxxxxxxxx/CCAPI/ccCallDisconnect:

On the second test, I had sever vtsp debugs enabled.  Again, the output of the debugs was the same, line for line, until here:

Good call:

Oct 17 15:12:40.157: //157861/xxxxxxxxxxxx/VTSP:(2/12):-1:1:1/act_setup_pend_progress:
   Progress Indication=8, Signal Indication=2, cdb->answer_supervision=0
Oct 17 15:12:40.161: //157861/xxxxxxxxxxxx/VTSP:(2/12):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_TSP_ALERT]
Oct 17 15:12:40.161: //157861/xxxxxxxxxxxx/VTSP:(2/12):-1:1:1/act_setup_pend_alert:
   Progress Indication=8, Signal Indication=1
Oct 17 15:12:40.161: //157861/xxxxxxxxxxxx/VTSP:(2/12):-1:1:1/act_setup_pend_alert:
   Ringback Indication=TRUE, Ring Timeout=-1(s)
Oct 17 15:12:42.873: //157861/xxxxxxxxxxxx/VTSP:(2/12):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_TSP_CONNECT]

Bad call:

Oct 17 15:12:03.381: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/act_setup_pend_progress:
   Progress Indication=8, Signal Indication=2, cdb->answer_supervision=0
Oct 17 15:12:03.385: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_TSP_ALERT]
Oct 17 15:12:03.385: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/act_setup_pend_alert:
   Progress Indication=8, Signal Indication=1
Oct 17 15:12:03.385: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/act_setup_pend_alert:
   Ringback Indication=TRUE, Ring Timeout=-1(s)
Oct 17 15:12:06.413: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_CC_FEATURE]                                         <------  Again, what is feature type 34???
Oct 17 15:12:06.413: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/act_call_feature:
   Feature Type=34
Oct 17 15:12:06.413: //157860/xxxxxxxxxxxx/VTSP:(2/7):-1:1:1/vtsp_process_event:
   [state:S_SETUP_REQ_PROC, event:E_CC_DISCONNECT]

References to feature type 34 appear in the debugs of the test calls that didn't work and it doesn't appear in the test calls that did work.  I'm not familiar with feature type 34 and I cannot find any explanation of it anywhere.  Is that something that the receiving fax machine is requesting?  Any ideas on what might be causing this issue?

Thanks a ton,


Steven

3 REPLIES
Cisco Employee

Re: Fax issue - cannot fax from RightFax server to Internal fax

Can you provide the dial-peer configuration for call routing between the gateway that connects to rightfax? You'll need to verify that all VOIP endpoints are configured to handle the fax calls the same way (relay or passthrough, protocol or nse based switchover).

If you can provide the configurations for all 3 devices, I can point out what needs to be changed.

-Felipe

Community Member

Re: Fax issue - cannot fax from RightFax server to Internal fax

Steven - did you figure this one out?  Think I am running into this for one of my customers.

Thanks,

Dan

Hall of Fame Super Silver

Fax issue - cannot fax from RightFax server to Internal fax mach

Fax relay is Cisco proprietary protocol and would not work well with 3rd party fax server. You need to have the same end to end fax protocol ideally protocol-based T.38, but that is not supported with SCCP ports so your best bet here would be to use passthrough if RightFax can negotiate passtrhough switchover.

I would reconfigure the ports to either MGCP or H323 and use T.38.

HTH,

Chris

3167
Views
0
Helpful
3
Replies
CreatePlease to create content