Hi Greg,
Thanks for sharing. I found a input to yours based on a KB article on MultiTech's website:
Resolution 5031541: FaxFinder Inbound Routing and Cisco Unified Communication Servers - Problems Detecting DTMF
http://www.multitech.com/en_us/support/help/resolutions/res5031541.aspx
Resolution 5031541: FaxFinder Inbound Routing and Cisco Unified Communication Servers - Problems Detecting DTMF
FaxFinder inbound fax routing is not working as desired. FaxFinder reports a DTMF timeout (DID:T). Incoming faxes are being delivered to the Line destination instead of the desired Recipient destination.
The DTMF routing information generated by the Cisco system is heard when testing, listening with an analog phone connected to the Cisco fax line, but is not detected by the FaxFinder when connected to the same Cisco fax line.
This problem can be been solved by configuring the Cisco Analog port(s) to use "600 ohm Complex Impedance". Specifying "complex" impedance is very important, which addresses line capacitance variables.
This may require you to update your version of Cisco ISO Release.
- Product(s) affected: FF200,FF420,FF220,FF130,FF230,FF430,FF830,FF120,FF820,FF100
|
|
They also have a post on their site on how to set this up with an Avaya system. Here is an interesting paragraph from that document
For each user on Avaya IP Office desiring to use fax, a virtual fax extension and user is created with calls forwarded to the fax hunt group. Incoming fax calls to the virtual fax extensions are forwarded to the fax hunt group, and delivered to MultiTech FaxFinder via available fax ports. When Avaya IP Office detects that a fax call has been answered, the virtual fax extension associated with the DID number is out-pulsed via DTMF digits to MultiTech FaxFinder.
So I will try configuring the "600 ohm Complex Impedance" on the analog ports and hope this takes care of it. I wish there would be better documentation from MultiTech in combination with Cisco out there but that does not seem to be the case.
Mike
