/mcpIP 2.1.1.2:17092 rtt:56ms pl:64730/0ms lost:0/1/0 delay:69/69/70ms g729r8
Total call-legs: 2
A common cause of fax relay problems is that the correctly configured dial peer is not the one that is matched. It is also common that there is no particular inbound VoIP dial-peer configured on the termination gateway, and Cisco IOS Software selects the first appropriate (and default) VoIP dial peer as the inbound dial peer. The parameters for this inbound dial peer possibly do not match those of the outbound dial peer on the origination gateway. It is not always required that you have identical configurations on the outbound and inbound VoIP dial-peers. When you have a fax relay problem, though, make sure you have a dedicated inbound VoIP dial-peer on the termination router and that its configuration matches the configuration of the outbound VoIP dial-peer on the origination router. This configuration for ISDN-connected routers is an example of specific, matched VoIP dial peers for the destination pattern "5..." outbound on the origination gateway and inbound on the termination gateway. Originating Gateway Terminating Gateway
!--- Incoming POTS peer:
Dial-peer voice 1 pots Incoming called number. Direct-inward-dial Port 1/0:15
!--- Outgoing VoIP peer:
Dial-peer voice 2 voip Destination-pattern 5… Session target ipv4:10.10.10.10 Fax rate 14400 fax protocol t38 ls-redundancy 0 hs-redundancy 0
!--- Outgoing POTS peer : Dial-peer voice 10 pots Destination-pattern 5… No digit-strip Port 2/0:15
!--- Incoming VoIP peer:
Dial-peer voice 20 voip Incoming called-number 5… Fax rate 14400 fax protocol t38 Ls-redundancy 0 Hs-redundancy 0