sending Fax to OCS users thru CUCM
I am using GW Fax connected via SIP trunk to CUCM 7.x which also has a SIP trunk going to OCS mediation server.
My users on OCS are enterprise voice enabled and have voicemail boxes configured on Exchange 2007 with SP1.
I am trying to send a fax from the Fax GW thru CUCM to an OCS user's mailbox on outlook.
For example user SimRingThree is configured on exchange with EUM extension 60053 and is enabled for UM, it's associated to UM dial Plan (OCS) that has (OCS-Policy) and points to a UM IP GW with the OCS pool FQDN. The same user is also enabled for Enterprise voice on OCS, and has the following line URI: +14085260053. It's email address and sign-in name is SimRingThree@pbxocs.com.
I have read that in order to receive fax on an enterprise enabled user you need to use a separate extension for fax and route fax calls to this extension directly to Exchange 2007 SP1 UM outside of OCS 2007. The reason being that OCS 2007 Mediation Server does not currently support T.38.
So I added a secondary extension (61053) for fax to my user in ExUM that points to a secondary UM Dial Plan (FAXOCS) with UriType=TelExtn. And have a new UM Mailbox policy associated with this UM Dial Plan called (FAXOCSPolicy). The new dial plan points to IP Gateway that has the same IP address as CUCM. The UM server hosts both dial plans. Also I added a SIP trunk directly to ExUM 2007 on CUCM, with a route pattern for 6105X.
I have configured the SIP profile in CUCM to allow the T.38 dual m line and applied this to the SIP trunk to exchange such that the t.38 is recognized.
Also I have enabled inbandfaxdetection on Exchange and double checked all the required items in exchange to ensure faxing is enabled on the dial plan and user's box.
When I dial the secondary extension (61053) from the GW fax, I get the general greeting on Exchange and Fax is not detected.
Has anyone else done this before? Have you seen this issue and can provide some insight to what might be going on?
Thanks.
All Replies
- When you say you get the general greeting, do you mean you get the general greeting for the mailbox associated with 61053 or the general Exchange 2007 UM greeting like it doesn't integrate to a mailbox?
I know you said you tried to dial the extension 61053, but did you try to send a fax to that number? CUCM or Exchange 2007 UM will route the call just like any other voice call unless it detects the fax tone the fax machine is sending, then will convert the call to T.38. - The call must be directed to the pilot identifier and the user's extension (EUM address) must be contained in a diversion header since Exchange UM only understands diverted calls to identify the correct mailbox.
Johann
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 - I get the general ExUM 2007 greeting, so it doesn't integrate to the mailbox.I did try to send a fax to 61053, It did not work.
- So in the scenario above the pilot identifier is generated automatically when I add the UM IP GWs for the OCS pools. This is tied into the UM Dial Plan created for the location profile of those pools.When I add a secondary um dial plan for the fax, there is no pilot identifier created, should there be one?From the wireshark trace, the following happens:INVITE sent from CUCM to ExUM 2007 to ext. 61053, it is sent to 61053@<IP Address of ExUM> (there is no diversion header included)100 Trying sent from ExUM to CUCM302 Moved temporarily sent from ExUM to CUCM (no diversion header included)ACK sent from CUCM to ExUMINVITE sent from CUCM to ExUM 2007 to ext. 61053100 Trying sent from ExUM to CUCM180 Ringing sent from ExUM to CUCM200 OK, with session description sent from ExUM to CUCM
- So you will first need to get a call to integrate to the mailbox before moving on to getting the fax feature to work. Without a diversion or reason code I don't think UM will integrate to a mailbox because it will appear as if the dialed number was a direct call to UM (like a pilot number).
- How can I get the extension number to be sent in the diversion header? In this scenario there is a Direct SIP connection to ExUM so the call is not diverted to the fax number instead it is directly going to it. Not sure how I can make this work? Any suggestions?
- Thank you for your responses,I was able to send the extension number in the diversion header, it now hits the mailbox of the user instead of general greeting, but the Fax still does not work.In the diversion header, the extension number appears as such:61053@<IP Address of CUCM>Should this be 61053@<IP Address of ExUM>?Your feedback is appreciated.
So when you send a fax to that number what happens? Does it hang up the call, does UM take and record the call as a voicemail? Is the logging turned up on the UM to see if it tries to negotiate T.38 with Cisco?
- >> Should this be 61053@<IP Address of ExUM>?
Could you document the full diversion header? It normally does not include IP address
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 When I send a fax to that number the UM records the call as voicemail. I was able to capture on the UM a wireshark trace that plays back the voicemail box greeting and the fax tones recorded as a voicemail on that mailbox. I enabled tracing on the UM and captured an .etl file but not sure how to view it or analyze it, any suggestions??
Here is the wireshark trace capture from the CUCM sip trunk, and shows the diversion header:
INVITE sent from CUCM (172.20.109.254) to Exchange server (172.20.85.254):
Request-Line: INVITE sip:61053@172.20.85.254:5060 SIP/2.0
|
|
Message Header
|
|
From: <sip:4302@172.20.109.254>;tag=5cdb14b1-1460-4949-b512-34e4d3322dc0-22628415
|
|
Diversion: "TELUGU-01[ALERT]" <sip:61053@172.20.109.254>;reason=unconditional;privacy=off;screen=yes
Remote-Party-ID: <sip:4302@172.20.109.254>;party=calling;screen=yes;privacy=off
|
|
To: <sip:61053@172.20.85.254>100 Trying sent from Exchange server (172.20.85.254) to CUCM (172.20.109.254)
302 Moved Temporarily sent from Exchange server (172.20.85.254) to CUCM (172.20.109.254)
ACK sent from CUCM (172.20.109.254) to Exchange server (172.20.85.254)
INVITE sent from CUCM (172.20.109.254) to Exchange server (172.20.85.254):
Request-Line: INVITE sip:61053@172.20.85.254:5065;transport=TCP SIP/2.0
|
|
Message Header
|
|
From: <sip:4302@172.20.109.254>;tag=5cdb14b1-1460-4949-b512-34e4d3322dc0-22628415
|
|
Diversion: "TELUGU-01[ALERT]"<sip:61053@172.20.109.254>;privacy=off;reason=unconditional;screen=yes
Remote-Party-ID: <sip:4302@172.20.109.254>;party=calling;screen=yes;privacy=off
|
|
To: <sip:61053@172.20.85.254>100 Trying sent from Exchange server (172.20.85.254) to CUCM (172.20.109.254)
180 Ringing sent from Exchange server (172.20.85.254) to CUCM (172.20.109.254)
180 Ringing sent from CUCM (172.20.109.254) to Gateway Fax (172.20.109.201)
200 OK with SDP sent from Exchange server (172.20.85.254) to CUCM (172.20.109.254)
ACK sip:exchangepbx.pbxocs.com:5065;maddr=172.20.85.254;transport=Tcp, with session description sent from CUCM (172.20.109.254) to Exchange server (172.20.85.254)
183 Session Progress, with session description sent from CUCM (172.20.109.254) to Gateway Fax (172.20.109.201
200 OK, with session description sent from CUCM (172.20.109.254) to Gateway Fax (172.20.109.201
- Also after the ACK with SDP from CUCM to UM, the UM sends an RTP packet to CUCM with unknown RTP version 0 (00.. .... = Version: Old VAT Version (0))
What does this mean?
Do I need to worry about the VoIP security setting on the UM Dial Plan for the fax? It is now set to unsecured, and it has a URI type: telephone extension. - You are really close now! :-)
Somebody has to detect fax cng tone - either gateway or Exchange. To enable that in Exchange 2007 UM you have to edit globcfg.xml in bin-directory of Exchange Server:
<!--
EnableInbandFaxDetection: Specifies whether inband fax detection is enabled
or not. The default setting is false and UM relies on the IP Gateways to
perform the FAX detection.
-->
<EnableInbandFaxDetection>true</EnableInbandFaxDetection>
Exchange UM service must be restarted after this change.
CUCM must be able to handle T.38 reINVITE from Exchange - may depend on version.
Johann
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 - Inband Fax Detection is already enabled on ExUM, and ExUM has been restarted, this still does not work, and I never get a reINVITE from Exchange to CUCM.
- Take a wireshark trace at Exchange UM, pack it together with globcfg.xml in a ZIP archive and mail it to me, address: myfirstname@mylastname.de - substitute according to my signature :-)
Johann
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 - Indeed there is no reINVITE - is fax enabled at all in Exchange UM settings?
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 - I beleive so. The Dial Plan has Allow users to receive fax checked. The UM server has max concurrent fax calls set to 100. The User's mailbox has under Mailbox features, Unified Messaging set to Allow user to receive fax.
Anything else needs to be set? - Interesting problem...
Try using eventlog, set it to highest level in mgmt shell:
Get-EventLogLevel *um* | Set-EventLogLevel -Level expert
and see if eventlog gives you more information
Johann Deutinger | MCTS Exchange 2007 / OCS 2007 - I get an error from source MSExchangeTransport that says:Microsoft Exchange couldn't find a certificate that contains the domain name exchangepbx.pbxocs.com in the personal store on the local computer. Therefore it is unable to support the STARTTLS SMTP verb for the connector Default EXCHANGEPBX with a FQDN parameter of exchangepbx.pbxocs.com.......
