Professional Documents
Culture Documents
Fax Communication
Fax Communication
Integrating, and
Troubleshooting Fax
Communications in
Today’s Enterprise
Networks
Gonzalo Salgueiro, Principal Engineer
David Hanes, Technical Leader
BRKUCC-2021
Agenda
• Fundamental Concepts
• Fax Transport Methods
• Design Best Practices
• Troubleshooting
• Fax Servers
Cisco Spark
Questions?
Use Cisco Spark to chat with the
speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Fundamental Concepts
Fax Over the Years…Or So It Seems
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
Fax Communications
• Fax invented by Alexander Bain in
1843 (patented 30 years before
the telephone)
• Fax is a ubiquitous form of
communication today and Fax over
IP (FoIP) is often overlooked in IP
Telephony
• Group 3 (G3) is today’s fax
standard (speeds up to 14.4 kbps)
• Super G3 is an optional extension
of G3 that allows for speeds up to
33.6 kbps
Alexander Bain’s Facsimile Apparatus,
British Patent 9745
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
G3 Fax Protocols
• Modern fax communication is based on the Group 3 (G3) fax standard, which is
composed of the ITU-T specifications of T.30, T.4, and T.6
• T.30 details the signaling, T.4 specifies the Modified Huffman (MH) and
Modified Read (MR) encoding methods, and T.6 covers Modified Modified
Read (MMR)
PSTN
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
Basic G3 Fax TransactionSending Fax Receiving Fax
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
Super G3 Fax G3 Fax Call Initiation
CNG
• Super G3 uses the V.34 Originating Terminating
modulation to achieve page Fax
CED
Fax
CJ Terminator
DIS
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
Transporting G3/SG3 Fax Protocols Over IP
PSTN
Passthrough or Relay
Transport
IP
IP
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
Relay
• The analog modulated fax data is demodulated by a Digital Signal Processor
(DSP) on the gateway and the binary information is extracted
• Binary information is passed over IP using one of several available relay
protocols
• A DSP on the destination gateway takes the binary information from the relay
packets and re-modulates it into fax data signal on telephony side
Analog Relay Protocol Analog
Modulated Data Modulated Data
Relay Relay Relay Relay
01101010 11000111 10100101 00101011
IP
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
The Switchover OGW TGW
Fax Call
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
Fax Transport Methods
Fax Transport Methods
Fax
over IP
Passthrough Relay
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
Fax Passthrough Switchover Methods
Voice
Mode
NSE-Based Protocol-Based
Switchover Switchover
Passthrough Switchover:
1. Codec upspeed
Fax Fax
Passthrough 2. VAD disabled on DSP Pass-through
3. Jitter buffer transitions from adaptive to a fixed
optimum value
Fax Passthrough
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
Passthrough Switchover Mechanisms
NSE-Based Tone
Switchover 2 RTP NSE RTP NSE RTP NSE 1 Detection
IP
OGW
Protocol-Based TGW
Switchover 3 H.323 SIP
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Named Signaling Events (NSE)
• Cisco proprietary message sent as part of the RTP stream to signal an event,
such as a switchover
• This form of signaling is call control independent
• The Event ID field uses Cisco-defined event numbers to signal a specific task
in-band
RTP Header RTP Payload
PT NSE
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
NSE Events Used for Modulated Data
• The NSE Event ID uses Cisco-defined values to signal in-band a variety of tasks
NSE Description
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
Fax Passthrough Switchover (G3)
OGW TGW
The initial VoIP call
can be setup by any
of the common call
OGW: Upspeed codec control protocols
VoIP Call (H.323, SIP, MGCP,
and switch to
Passthrough mode or SCCP)
NSE-192 CED
NSE-192
The underlying call
control protocol is TGW: Upspeed codec
unaware of the and switch to
transition to fax Fax Passthrough Call Passthrough mode
passthrough due to the
protocol independent
nature of the NSE
switchover
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Fax Passthrough Switchover (SG3)
OGW TGW
The initial VoIP call
can be setup by any
of the common call
control protocols
VoIP Call
(H.323, SIP, MGCP,
or SCCP)
NSE-192 ANSam
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
Confirming Fax Passthrough Switchover
Before Switchover: show call active voice brief
VoIP Call
After Switchover: show call active voice brief
11F1 : 10 2924510ms.1 +10530 pid:1 Originate 200 active
dur 00:00:22 tx:877/125447 rx:1040/128809
IP 1.1.1.2:17932 SRTP: off rtt:1ms pl:40/0ms lost:0/0/0 delay:60/60/60ms g711ulaw
TextRelay: off
media inactive detected:n media contrl rcvd:n/a timestamp:n/a
long duration call detected:n long duration call duration:n/a timestamp:n/a
MODEMPASS nse buf:0/0 loss 0% 0/0 last 1359s dur:0/0s
Fax Passthrough Call
Fax Passthrough Call
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 23
Fax Passthrough Configuration
SIP/H.323:
dial-peer voice 1 voip
modem passthrough nse codec g711ulaw
(Note: Can be configured globally under voice service voip or the dialpeer for
SIP and H.323. The configuration under the dialpeer takes precedence.)
MGCP:
mgcp modem passthrough voip mode nse
mgcp modem passthrough voip codec g711ulaw
SCCP:
voice service voip
modem passthrough nse codec g711ulaw
(Note: Can only be configured globally under voice service voip for SCCP.)
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 24
Fax Pass-through Switchover (G3)
OGW TGW
200 OK
The V.21 Preamble of
ACK the first T.30 message
An H.245 Request following the CED Tone
Mode for G.711 is (i.e. DIS) is the trigger
used to signal the for the transition to
Fax Pass-through Call pass-through
switchover in H.323 to
fax pass-through mode
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
Confirming Fax Pass-through Switchover
VoIP Call
After Switchover: show call active voice brief
126C : 58 11411290ms.1 +10520 pid:1 Originate 200 active
dur 00:00:41 tx:1677/252554 rx:1953/258112
IP 1.1.1.2:17620 SRTP: off rtt:4ms pl:40/0ms lost:1/0/0 delay:60/60/60ms g711ulaw
TextRelay: off
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
Fax Pass-through Configuration
SIP/H.323:
dial-peer voice 1 voip
fax protocol pass-through g711ulaw
Note: Can be configured globally under voice service voip or the dialpeer for
SIP and H.323. The configuration under the dialpeer takes precedence.
MGCP:
Fax pass-through is NOT supported for MGCP
SCCP:
Fax pass-through is NOT supported for SCCP
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 27
Fax Transport Methods
Fax
over IP
Passthrough Relay
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 28
Fax Relay Switchover Methods
Voice
Mode
Fax Relay
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
T.38 Fax Relay
• T.38 is the de facto standard for handling fax transmissions today
• Cisco has always supported the 1998 version (known as version 0) of the ITU-
T T.38 specification with UDP/UDPTL encapsulation
• In IOS version 15.1(1)T Cisco started supporting SG3 fax over T.38 (version 3)
• Cisco products can use either NSEs (proprietary) or the call control protocol
(standards-based) to switch a call to T.38 mode
T.38 Internet Fax Packets (IFP)
and optional redundancy
UDP Transport Layer
packets are carried in the
(UDPTL) header is simply
UDPTL payload
a 2 byte sequence number
IP UDP UDPTL
UDPTL Payload (T.38 IFPs)
Header Header Header
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 31
T.38 Switchover—H.323 (G3)
OGW TGW
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
T.38 Switchover—SIP (SG3)
OGW TGW
The initial VoIP call is
ANSam is sent across setup using the SIP
in the RTP media call control protocol
stream VoIP Call - SIP Signaling
200 OK
The detection of
ACK Note: CM is squelched
Calling Menu (CM) at
by the OGW DSP and
the OGW triggers the
sent over T.38. The
transition to T.38
CM/JM exchange is
T.38 SG3 Fax Relay Call done entirely over T.38
prior to T.30 negotiation
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
Confirming T.38 Fax Relay Switchover
Before Switchover: show call active voice brief
VoIP Call
After Switchover: show call active voice brief
11E2 : 4 2956390ms.1 +10500 pid:1 Originate 200 active
dur 00:00:46 tx:707/13770 rx:914/12339
IP 1.1.1.2:18496 SRTP: off rtt:3ms pl:4800/0ms lost:0/0/0 delay:60/60/70ms t38
TextRelay: off
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 34
NSE-Based T.38 Configuration
SIP/H.323:
dial-peer voice 1 voip
fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback cisco
Note: Configured globally under voice service voip or the dialpeer for SIP
and H.323. The dialpeer configuration takes precedence.
MGCP:
Enabled by default
SCCP:
Note: no mgcp fax t38 inhibit is required but is default.
voice service voip
fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback cisco
Note: Can only be configured under voice service voip for SCCP. Cisco IOS gateway
support for NSE-based T.38 fax relay with the SCCP voice signaling protocol is
introduced in Cisco IOS Release 12.4(11)T.
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 35
Protocol-Based T.38 Configuration
SIP/H.323:
dial-peer voice 1 voip
fax protocol t38 version [0|3] ls-redundancy 0 hs-redundancy 0 fallback cisco
Note: version 0 configures legacy T.38 G3 fax support, whereas version 3 enables
the newly supported SG3 over T.38 feature [as of 15.1(1)T]
MGCP:
mgcp package-capability fxr-package
mgcp default-package fxr-package
SCCP: Note: These two commands are needed to go from the
SCCP does not support default configuration of NSE-based T.38 to protocol-based
protocol-based (version 0 T.38. The command no mgcp fax t38 inhibit is required for
or version 3) T.38 both NSE and protocol-based T.38, but it is the default.
MGCP does not offer any version 3 support.
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 36
Design Best Practices
Design Best Practices
• Unified Communications Integration Methods
• Cisco Unified Communications Manager, Gateway-Controlled
• Cisco Unified Communications Manager, CA-Controlled
• Design Considerations
• QoS
• Bandwidth Utilization
• Super G3
• Protocol and Product Support
• SIP Trunking and FoIP Support
• T.38: De Facto Standard
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 38
Cisco Unified Communications Manager, Gateway-
Controlled CUCM
H.323/SIP/MGCP/SCCP H.323/SIP/MGCP/SCCP
IP
• Cisco Unified Communications Manager (CUCM) controls the setup of the initial voice call
between the gateways using standard call control signaling such as H.323, SIP, MGCP,
and SCCP
• The switchover to a fax media stream is handled by the gateways themselves without the
knowledge of CUCM
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 39
Cisco Unified Communications Manager, CA-
Controlled
CUCM
Gateway Gateway
Fax Fax
IP
• Cisco Unified Communications Manager controls the setup of the initial voice
call between the voice gateways and controls the switchover to T.38 fax relay
• T.38 support for H.323, SIP, and MGCP is available in all current versions of
Cisco Unified Communications Manager
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
Design Best Practices
• Unified Communications Integration Methods
• Cisco Unified Communications Manager, Gateway-Controlled
• Cisco Unified Communications Manager, CA-Controlled
• Design Considerations
• QoS
• Bandwidth Utilization
• Super G3
• Protocol and Product Support
• SIP Trunking and FoIP Support
• T.38: De Facto Standard
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 41
QoS Design Parameters for Fax
*Fax passthrough is very sensitive to packet loss and may be able to handle 0.1%–0.2% loss depending on
when in the fax transaction the loss occurs and if it is consecutive packets. T.38 with redundancy is the best
choice for fax calls when packet loss is occurring.
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 42
QoS Marking and Shaping Example
CLASSIFICATION & MARKING QUEUEING & DROPPING POST-QUEUING OPERATIONS
OGW TGW
Fax Fax
IP
Phone PC PC Phone
class-map match-all fax_voice
dial-peer voice 919 voip match ip dscp ef
destination-pattern 919....... class-map match-any call_signaling
session target ipv4:10.0.0.19 match ip dscp cs3
fax protocol t38 ls-redundancy 0 hs-redundancy 0 match ip dscp af31
!
fallback none
policy-map WAN
no vad class fax_voice
priority percent 33
Voice and T.38 fax traffic can share class call_signaling
the same QoS marking and shaping <snip>
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 43
FoIP Bandwidth Utilization
• Different FoIP transports use Codec Bandwidth1
varying amounts of bandwidth G.711 (64 Kbps) 83 Kbps
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 44
Methods for Handling
OGW
SG3 Fax Calls
TGW
SG3 Sending Fax SG3 Receiving Fax
CNG
ANSam
Sending fax
initiates SG3 Sg3-to-g3 spoofing Absence of SG3 CM causes
call by CM feature on OGW receiving fax to initiate G3
sending CM blocks CM message fax procedures (DIS message)
DIS
• The sg3-to-g3 spoofing feature controlled by the command fax-relay sg3-to-g3 forces
Super G3 fax calls to negotiate down to G3 speeds for compatibility with T.38 or Cisco fax
relay
• Modem passthrough will handle SG3 calls at their native speeds
• Starting in IOS 15.1(1)T SG3 over T.38 is supported for SIP and H.323 and these other
methods for handling SG3 faxes are not necessary
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
SG3 over T.38 Design Best Practices
CUCM
SIP SIP
H.323 H.323
• Endpoints must support SG3 and gateways must support the SG3 over T.38
feature (added in IOS 15.1(1)T)
• Only SIP and H.323 call control protocols are supported
• Use the same call control protocol (SIP or H.323) end to end
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 46
FoIP Call Control Protocol Support
Transport H.323 SIP MGCP SCCP
Method
T.38 (NSE-based) Yes Yes Yes Yes
*Current PVDM3 cards using LSI DSPs on the ISR platforms do not support Cisco fax relay
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
FoIP Transport Options for SIP Trunks
• SIP Trunks typically use three different methods to transport standard G3 fax
calls
• G.711 Voice - All calls (voice and fax) are always sent using the G.711 voice codec
• Pass-through - A SIP RE-INVITE message is used to up-speed to G.711 when a fax tone is
detected
• T.38 Fax Relay – Call is switched to T.38 fax relay using a SIP RE-INVITE when a fax tone is
detected
Pros Highest fax success rates can be Most widely deployed Provides bandwidth savings as G.729 voice
achieved Simplest solution call only upspeeds to G.711 if call is fax
Cleanest solution from signaling
and media point of view
Use less bandwidth than G.711
Cons Interoperability between different Consumes a large amount of Interoperability between different vendors
vendors bandwidth for all calls Sensitive to impairments, no redundancy
Not offered by some Service Sensitive to impairments, no
Providers redundancy
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 48
FoIP Best Practices for SIP Trunks
• T.38 should be your first choice, followed by G.711 voice or passthrough
• Use SIP call control end-to-end if possible (required by SG3 over T.38)
• SCCP (Skinny) endpoints do not support standards-based T.38
• Confirm your SIP trunk provider supports T.38 and be aware that
interoperability issues still exist
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 49
T.38: De Facto Standard for FoIP
Fax Pass- Fax/Modem Cisco Fax
T.38
through Passthrough Relay
Standards-Based,
Third-Party Integration
Low Bandwidth
Redundancy
SG3 Support
T.38 Should Always Be Your First Choice When Handling FoIP Traffic!
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
Troubleshooting
Packet Captures
CUCM
Capture media Capture media
and call control and call control
Capture
Voice call control Voice
Fax Gateway Gateway Fax
IP
• Packet captures are one of the best tools for troubleshooting fax problems
• Ideally captures should be made at both endpoints to ensure that both
signaling and media are seen
• Cisco Unified Communications Manager only participates in the call
control signaling
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 52
Packet Captures: VoIP Call Analysis
• For protocol-based switchovers
like fax pass-through and T.38,
the “VoIP Calls” feature in
Wireshark offers a graphical
means for analyzing the
switchover
• “VoIP Calls” also breaks down
the T.38 media stream, showing
the T.30 signaling and page
transmission
• Select “Telephony” from top of
Wireshark window, “VoIP Calls”,
click on a call, and then click
“Flow”
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
Call Troubleshooting Stages
Gateway Gateway
• Any fax call can be broken
down into three
H.323/SIP/MGCP/SCCP Call Setup
troubleshooting stages
1. Initial Voice Call
2. Switchover
3. Fax Media
Voice Media
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 54
Stage 2: Troubleshooting NSE-Based Switchovers
debug voip rtp session named-event
Jan 10 22:01:58.471: s=DSP d=VoIP payload 0x64 ssrc 0x1EF2 sequence 0x1FBD timestamp 0x20631C26
Jan 10 22:01:58.471: Pt:100 Evt:192 Pkt:00 00 00 <Snd>>>
Jan 10 22:01:58.483: s=VoIP d=DSP payload 0x64 ssrc 0x9A20101 sequence 0x18C2 timestamp 0xADA80F0A
Jan 10 22:01:58.483: <<<Rcv> Pt:100 Evt:192 Pkt:00 00 00
• Use the command debug voip rtp session named-event to view NSE-
related switchovers and events on IOS gateways, such as fax
passthrough and NSE-based T.38
• Most common cause of problems with NSE-based switchovers are an
incorrect configuration or a transcoder or proxy in the call path
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 55
Stage 2: Troubleshooting Protocol-Based
Switchover—MGCP and T.38
A NTFY containing *Feb 4 17:01:36.597: MGCP Packet sent to 172.18.110.85:2427--->
NTFY 935850485 S2/SU0/DS1-0/23@CAE-DH-3845-2 MGCP 0.1
FXR/t38(start) initiates N: ca@172.18.110.85:2427
the MGCP T.38 X: 17
O: FXR/t38(start)
switchover <---
CAE-DH-3845-2#show ccm-manager
MGCP Domain Name: CAE-DH-3845-2
Priority Status Host
==============================================
Primary Registered CAE-DH-7845 (172.18.110.85)
First Backup None
Voice Media Second Backup None
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 57
Stage 2: SIP Trunk Troubleshooting
Confirm receive CUCM If SIP service provider does not support
side sends T.38 Voice SIP delay offer and CUCM is present
SIP re-INVITE Gateway without MTP, then early offer forced
needs to be configured in CUBE
Fax SIP
IP
Service Provider
CUBE
Fax
Server MTP
For T.38, MTP Check dial- debug ccsip
needs codec peer config messages for deeper
passthrough on CUBE look at SIP signaling
• If initial voice call is not established and CUCM is present check for early/delay
offer issue
• If T.38 re-INVITE is not occurring, check terminating side support, confirm MTP
configuration, review proper dial peer config on CUBE
• Use debug ccsip messages for further call control troubleshooting
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 58
Stage 3: Troubleshooting the Fax Media - Gateway
DSP Statistics
CAE-DH-3845-2#terminal monitor
CAE-DH-3845-2#show voice call 0/1/1
0/1/1
vtsp level 0 state = S_CONNECTvpm level 1 state = FXSLS_CONNECT
vpm level 0 state = S_UP
calling number , calling name unavailable, calling time 02/03 04:20
CAE-DH-3845-2# ***DSP FAX RELAY STATISTICS***
Max Jit Depth: 36, Max Nwk RxQ Depth 3, Jitter Overflow Pkt Drops: 0
Nwk RxQ Overflow: 0, Tx Pkts: 247, Tx Pkts Drops(Nwk Busy): 0
Rx Pkts: 677, Rx Pkts Loss: 0, Rx Invalid Pkts: 0, Rx Pkts Out Of Seq: 0
Recent Hi-Speed Modulation: V.17/long/14400TX Pages: 2
Max SendInQ Depth 2, Max RecvOutQ Depth 2
Max Hi-Speed Buf Usage 54, SendInQ Overflow 0, RecvOutQ Overflow 0
fr-msg-tx
Message transmitted by DSP
• The command debug fax relay t30 all-level-1 displays T.30 messages for
T.38 and Cisco fax relay from the DSP’s perspective on the POTS/PSTN
side of the gateway
• Inbound messages are flagged fr-msg-det and messages sent by the DSP
out the telephony interface are indicated by fr-msg-tx
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 60
Stage 3: Sample Output From “debug fax relay t30
all-level-1”
Nov 2 17:19:22.928: 0/0/0 (42) 626612205 fr-entered=10(ms)
timestamp=626613325 fr-msg-det NSF
timestamp=626614305 fr-msg-det CSI
timestamp=626615005 fr-msg-det DIS
timestamp=626617385 fr-msg-tx TSI
Output from the Cisco
timestamp=626618185 fr-msg-tx DCS
voice gateway command:
timestamp=626623295 fr-msg-det CFR debug fax relay t30 all-level-1
timestamp=626648365 fr-msg-tx EOP
timestamp=626649985 fr-msg-det MCF
timestamp=626652165 fr-msg-tx DCN
Nov 2 17:20:03.208: 0/0/0 (42) 626652485 fr-end-dcn
• This debug is only valid for T.38 and Cisco fax relay as the gateway
plays an active role in modulating and demodulating the T.30 fax
messages
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 61
Stage 3: Unique T.30 Debug Signature: Corruption
Voice Voice
Gateway Gateway T.30 Negotiation
Failure With a Likely
PSTN IP Cause of a Corrupted
Training Signal
NSF/DIS
debug fax
TSI/DCS (train) relay t30 all-level1 Fax machine is receiving a
fr-entered=10(ms)
fr-msg-det NSF corrupted training signal and
FTT fr-msg-det DIS sending an FTT message
fr-msg-tx TSI
TSI/DCS (train) fr-msg-tx DCS Most common cause of a
fr-msg-det FTT corrupted training is PSTN
FTT fr-msg-tx TSI
fr-msg-tx DCS impairments, such as clock
TSI/DCS (train) fr-msg-det FTT slips
fr-msg-tx TSI
FTT fr-msg-tx DCS First step is to always confirm
fr-msg-det FTT
that any digital circuits are free
of errors
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Stage 3: Viewing Digital Circuit Errors
T1 0/1/0 is up.
Applique type is Channelized T1 Output from the Cisco
Cablelength is long gain36 0db
No alarms detected.
voice gateway command:
alarm-trigger is not set show controller t1
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20060711, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (729 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
24 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
24 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
2989 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
2989 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 63
Stage 3: Confirming the Training in T.38
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 64
Stage 3: Scan Line Corruption
Snippet from a corrupted fax page
DCS-train DCN
Page EOP
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 66
Fax Servers
Fax Server Integration With Cisco Unified
Communications Manager
H.323/SIP
H.323/SIP
Fax H.323/SIP Unified CM
Server
SIP SIP
CUBE T.38
CUCM SIP
Service Provider
Fax
Server Passthrough
CUBE is unable to receive T.38 from a fax
server and transcode it to G.711 passthrough
to be compatible with a SIP trunk provider
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 69
Complete Your Online
Session Evaluation
• Give us your feedback to be
entered into a Daily Survey
Drawing. A daily winner will
receive a $750 gift card.
• Complete your session surveys
through the Cisco Live mobile
app or on www.CiscoLive.com/us.
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Lunch & Learn
• Meet the Engineer 1:1 meetings
• Related sessions
BRKUCC-2021 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 71
Thank you