/mcp<#root> .Jun 4 21:06:43.461: ssaSetupPeer cid(19) peer list: tag(400) called number (5074)
.Jun 4 21:06:43.461: ccCallSetupRequest (Inbound call = 0x13, outbound peer =100 , dest=, params=0x62F1CC70 mode=0, *callID=0x62F1CFD8, prog_ind = 0)
On the termination voice gateway, the first line of the debug voip ccapi inout call trace (as shown here) is a cc_api_call_setup_ind message with a peer_tag option that refers to the inbound VoIP dial peer on the termination gateway. debug voip ccapi inout - Terminating Gateway
<#root> .Jun 4 21:06:43.461: cc_API_call_setup_ind (vdbPtr=0x62F07650, callInfo={called=5074,called_oct3=0x80, calling=5075, calling_oct3=0x0,>calling_oct3a=0x83, calling_xlated=false, subscriber_type_str=Unknown,fdest=1,
peer_tag=400 , prog_ind=0},callID=0x635F72D0)
Incorrectly configured dial peers on one or both sides After you confirm that the correct dial peer is matched (in this case dial-peer 100 for the origination gateway and dial peer 400 for the termination router), confirm in the configuration that the dial-peer is configured correctly for fax. Some common errors to check for on both sides of the call are these: Fax relay is disabled (that is, the fax rate disable command has been issued on the dial peer) while a low bandwidth codec has been in use. ○ The dial peer on one voice gateway is configured for Cisco fax relay, but the other voice gateway is a Cisco 5350/5400. The Cisco 5350/5400s only support T.38, so the negotiation fails. ○ •