FXO/T38 Fax relay issue on a CCM-controlled MGCP gateway - RigthFax9.4
I set up a Right fax server 9.4. Evry thing is working fine using a PRI link.
However, when I tried to configure FXO analog lines to accept and forward T38 faxes, I wasn't able to make things work. There is no fax tone heard when calling the analog line connected to an FXO installed on a CCM-controlled 2811 MGCP gateway.
I have added the following line to the gateway config :
no mgcp fax t38 inhibit
mgcp package-capability fxr-package
mgcp default-package fxr-package
I noted that the call succed to reach the fax server ( using the Fax Entreprise Manager ).
However thre is no fax tone detected and there is no successful fax transmission !
When I type show voice call summary during a fax call , I note
"T38" written in the CODEC column whereas it should the rate used (14400) and VSTP column contains S_CONNECT instead of S_FAX
The gateway end point and the RF gateway are also in the same Device Pool
Re: FXO/T38 Fax relay issue on a CCM-controlled MGCP gateway - R
Actually, using the command show voice call summary, I think that having t38 in the CODEC column is correct. However, I agree that the VTSP column should say S_FAX instead of S_CONNECT. Now with a t38 fax, you will see 14400 in the CODEC column if you use the 'show voice call status'.
iecucme01#sho voice call summary PORT CODEC VAD VTSP STATE VPM STATE ============== ========= === ==================== ====================== 0/3/0:23.23 t38 n S_FAX 0/1/0 *shutdown* 0/1/1 - - - FXSLS_ONHOOK
iecucme01#sho voice call status CallID CID ccVdb Port Slot/DSP:Ch Called # Codec MLPP Dial-peers 0x55 120B 0x48BED9FC 0/3/0:23.23 0/1:1 * 14400 0/0 1 active call found
iecucme01#sho call active voice compact A/O FAX T Codec type Peer Address IP R: Total call-legs: 1 88 ORG FAX T45 t38 VOIP P 10.3.254.2:17040
That being said. Which version of IOS are you running? There is a defect in the 12.4T train that I have ran into. The defect ID is CSCsy29533. It affected some 12.4(15)T trains and is fixed in 12.4(15)T12. It is also fixed in 12.4(24)T2 and I believe 12.4(20)T4. Though, there are some other defects in 12.4(20)T4 that I wanted to avoid so I did not test that version. I have tested and confirmed the defect in 12.4(20)T and 12.4(20)T4. I have also tested that it is fixed in 12.4(24)T2. Anyway, it is at least something to check. The bug is well written and you can confirm you are impacted almost immediately.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...