Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
David Hanes is a technical expert in the area of fax over IP technologies. He has worked as a CSE in WAN, WAN Switching, and Multiservice Voice teams, a team lead for the Multiservice Voice team, and an Escalation Engineer. Q&A provided in this webca...
IntroductionRelated Information Introduction David Hanes is an engineer for the Cisco Customer Advanced Engineering (CAE) group supporting various emerging technologies through product testing and field trials. He is a technical expert in the area ...
Fax over IP Troubleshooting Basics Whenever you encounter a Fax over IP (FoIP) problem, the following troubleshooting model should always be employed to quickly hone in on the problem cause. This troubleshooting model is very basic and breaks down a ...
Fax Over IP Troubleshooting Basics - This document provides a three stage model developed by Cisco TAC for efficiently resolving FoIP issues. This document is applicable to troubleshooting passthrough, Cisco Fax relay, and T.38 fax relay.
Cisco Fax WikiGeneral FoIP Information General Fax Tech Tips and FAQ'sPassthroughRelayT.37 Store-and-Forward FaxFax ServersFoIP Training Material Cisco Fax Wiki Welcome to the Cisco Fax Wiki A repository and one-stop location for everything related t...
Hi Kevin,Good to know. I wish I had an explanation for you here but there was obviously a software defect. I have just never known one to cause the debug output that you were seeing. Thanks for the follow-up!-David
This IOS is fairly recent so it should not have the defect that I am thinking about from years ago. There is a possibility that a new but similar issue has come up again but I am not aware of it.From a troubleshooting perspective, you have a few opti...
Hi Kevin,Your scenarios sounds pretty basic so I am not sure where you would be picking up so much delay if that is the cause of your problem. Whenever I have seen the debug messages appear like yours, in my experience it has been a delay issue. Eith...