Dummy Phone Proposal for Legacy Fax Service

Unanswered Question

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

Recently migrated a client from Avaya to Cisco Call Manager System version: The client has a legacy fax number that is no longer a physical device and does not patch in anywhere. The number needs to be retained as clients still use this number The Avaya had a Call FWD applied to a virtual phone which then automatically call forwarded inbound fax messages to a Zeta Fax via a Hunt Pilot. Can this be replicated in Call Manager as the DDI is still used by some old clients.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
James Hawkins Sat, 11/28/2009 - 02:08

From the information you give I would guess that the fax system is using T.38 with Fax over IP (FoIP).

You should be able to configure the Cisco system to replicate this although Zetafax is not a Cisco certified product (lots of certified products available if needed from vendors such as Sagem, Stonevoice etc.).

Check out the link below to get started with faxing on Cisco platforms.


rob.huffman Sat, 11/28/2009 - 08:54

Hi NP,

To add a little note to the great tips from James (+5 points James)

If you are looking for a "Virtual" CFWD method for the DDI in

Communications Manager use a CTI-Route Point to term the

legacy number and Call Forward All to the Zeta Fax.




This Discussion