UCM62XX - FAX Intelligent Route


#1

hi,
Has anyone managed to make the “FAX Intelligent Route” function work on the Trunk?
It doesn’t work for me, maybe I miss a few steps.


#2

How does the call come in? What answers the call, so the system can determine that it is a fax?


#3

hi Larry,

Test scenario:

  • UCM with fax VFAX 695
  • Extension 201 for the item
  • on the trunk I enable the voice “intelligent fax” and send to fax 695
  • In the incoming path of the trunk imposed 201

Any incoming call to the trunk, whether it’s a fax or a voice call, UCM will divert it to 201.
So the recognition does not take place and an incoming fax instead of going towards 695 still goes to 201.


#4

So what answered the call?
Try to an IVR and then 201 and see.

You can see if that routes and then adapt as needed.


#5

Unfortunately I tried to put an IVR, but any incoming voice or fax calls still go to 201.
For that I ask if anyone has tried and knows exactly step by step how to solve.


#6

Let me see if I can set up a test today.

ps- I HATE FAX


#7

tnx

Damiano


#8

I started to engage on this yesterday, but got called out to a client.

In any event, as you know, I hate fax. I wish it would die a quick death. I started to investigate your query and in doing so, referred to the manual (yes, i know, not very manly). What I came across from the very start was -

FAX Intelligent Route
The UCM6200 can automatically detect Fax and phone signal coming from the FXO port, and then forward Fax or phone signal to the right destination. For example, when a regular phone call is coming, the UCM6200 will be able to detect the phone signal and forward it through the correct inbound route to the destination; if Fax signal is coming, the UCM6200 will be able to forward it to the FXS extension where the Fax machine is connected.

You indicated- “on the trunk I enable the voice “intelligent fax” and send to fax 695”. So, there is a slight conundrum as the UCM VoIP trunk settings have a setting for intelligent fax routing, but the manual makes no mention of such a setting for the VoIP trunks. I have a earlier Beta of UCM software that is currently in development and this version has no fax settings at all in the trunk settings. However, this is a Beta and may not represent what finally gets released. I reverted back to 19.27 for testing.

Additionally, when hovering over the description for intelligent fax in the trunk settings, it indicates that the connection must be to a fax extension or an FXS extension with a fax machine connected.
As you have indicated you have it set to a fax extension, I assume this to be acceptable.

So, in my initial test I -

  1. Set up VoIP trunk for fax detect and intelligent fax routing with a destination of 7200 which is a UCM fax extension.
  2. Set up the inbound rule to my extension with no fax settings in the route. Voicemail is disabled but t.38 is enabled.

Sent a fax and captured the call. The call came in as a voice call and was immediately routed to my extension. As I suspected, it does not appear that unless the call is answered, the UCM is not able to detect that the call is a fax as there is no re-invite. The call is always treated as voice.

I then changed the inbound route to an IVR, which if after 10 seconds no response, it would send the call to my extension.
I sent another fax and while monitoring the fax via the UCM active call page, it indicated no calls, yet the fax was active. I then examined the pcap file, and indeed a call had come in.

The call flow shows the Invite coming from the provider, and the UCM answers the call and there is a subsequent re-invite from the UCM seeking a t.38 exchange. The provider responds with a 100 trying followed by an immediate bye and a busy here, which seems odd. The reason for the bye was:
Reason:Q.850;cause=27;text=“DESTINATION_OUT_OF_ORDER”

I will do some more checking, but the INVITE is correct and the ports are forwarded for fax 4000-5000UDP.

You might try on your end and see what happens if you do a IVR and get the call answered. I will likely have to file a ticket.


#9

hi Larry,

Meanwhile, thank you for your attention (I think the topic interests many readers here),

“In any event, as you know, I hate fax. I wish it would die a quick death.” -> I hate it as much as you do, except that every now and then customers bring out this request, it bothers me to see that UCM has the fax server integrated and does not always work (for mysterious reasons).

In my personal experience a PDF is usually sent regularly, a PDF created by a scan almost always fails.

“However, this is a Beta and may not represent what is eventually released. I’m back at 7:27 p.m. for testing.” -> not about the post but can I ask you if they have generally implemented other import/export functions?

“I’ll do some more checking, but the INVITE is correct and the ports are forwarded by fax 4000-5000UDP.” -> do you want to tell me that in addition to the classic range RTP 10.000-20.000 UDP should also make the NAT ports with range 4.000-5000 UDP?

“You might try on your end and see what happens if you do a IVR and get the call answered. I will likely have to file a ticket.” -> I tried it normally and it fails 100%, I tried it with IVR and 1 time out of 10 it recognizes the fax and forwards it correctly inside the fax. 10% I think I can say that the fax recognition of UCM is not much use.

Damiano