cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10633
Views
0
Helpful
12
Replies

CUCM 7.1 - Help Configuring Ricoh IP Fax

muranskycotech
Level 1
Level 1

Greetings!

I have a number of Ricoh Multifunction Printers that support H.323/SIP IP-Fax capabilities. I would like to be able to use them with my CUCM 7.1 and 2821 MGCP gateway. Currently my on-site devices use a VG224, but my off-site units use analog lines only, and as I expand my system to those sites I want to avoid putting ATA's in place due to cost and the added support complexity.

If anyone here is familiar with this process or specifically with Ricoh/Lanier/Gestetner devices in this setup, I would appreciate any guidance.

12 Replies 12

Christopher Graham
Cisco Employee
Cisco Employee

I'm not familiar with the Ricoh printers, but if they support H323/SIP, I can only assume they would functions much like a fax server (RightFax/Xmedius). As such, they would need to negotiate protocol based T38 with the PSTN gateway. 

I would envision a call flow like this:

PSTN--PRI--Gateway--MGCP--CUCM--H323--fax machine

You would configure the fax machine as an H323 gateway in CUCM, and create a route pattern for the DID of the fax machine to route to this gateway.  Then, you would need to have the following config on your MGCP gateway:

no ccm-manager fax protocol cisco

no mgcp fax t38 inhibit

mgcp package-capability fxr

mgcp default-package fxr

no mgcp

mgcp

So, once the call routes to the fax machine, T38 would be negotiated, and the T30 messages exchanged as such.

Thanks for the quick reply! I'll give it a shot tomorrow and see what I can make of it.

Did you ever get this to work? I've been testing SIP to a richo MFP, it registers but never completes the call.

Same. I was never able to get it to complete the dialing process, so I just gave up in favor of other priorities. I generally just use ATA-187 devices at this point.

If you do happen to find a solution, I'd be interested in hearing it though.

scheived
Level 3
Level 3

I can get the Ricoh to register as sip endpoint, it answeres then imediatly disconnects. Doing a monitor with Wireshark looks like it attempts to negotiate t38 but fails. Any idea why this fails?

|160.260684000|         INVITE SDP (g711U)            |                   |SIP From: <2287>

|         |(5060)   ------------------>  (5060)   |                   |

|160.338806000|         INVITE SDP (t38)              |                   |SIP Request

|         |(5060)   <------------------  (63435)  |                   |

|160.339545000|         491 Request Pending           |                   |SIP Status

|         |(5060)   ------------------>  (5060)   |                   |

|160.547894000|         406 Not Acceptable            |                   |SIP Status

|         |(5060)   <------------------  (63435)  |                   |

I got Ricoh sip fax working from gateway to ricoh using t.38. Looks like that is only thing the ricoh will do.

Do you mind sharing details on how the Ricoh units are configured and the CM SIP configuration?

Settings go something like this,

On CM set up a Third-party SIP Device with an ext, configure a Digest User.

on Ricoh IP-Fax settings, enable sip, enable server. Use the ext number for user name. Enter cm address in Registrar address. Turn on Digest Auth, and enter the username/password of the digest user used on CM.

It should register right up, you have to use t.38 relay to whatever device it is communicating for it to work.

Any chance we could see a screenshot of what you setup on the copiers ip-fax settings page? also what settings did you setup in the gateway? set it up just like an ata?

ricoh

I am working on the same configuration, the third party sip device registers but is unsuccessful in completing the transaction. 

I am using version 10.01 CUCM and MGCP gateway.  My call flow is as follows:

PSTN--PRI--Gateway--MGCP--CUCM--SIP--fax machine

Can you provide the config on the MGCP gateway that you are using to get it to work.

Thus far I am getting a 406 not acceptable message.  Below find the logs.

__________________________________________________________

Date: Thu, 29 Oct 2015 14:34:44 GMT

Call-ID: 20151029104119-T38-C-1KHzx@10.1.2.56

Supported: timer,resource-priority,replaces

User-Agent: Cisco-CUCM10.0

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 102 INVITE

Max-Forwards: 70

Expires: 180

Allow-Events: presence

Min-SE:  1800

Remote-Party-ID: <sip:97702421273@172.20.10.42>;party=calling;screen=yes;privacy=off

Contact: <sip:97702421273@172.20.10.42:5060>

Content-Type: application/sdp

Content-Length: 363

 

v=0

o=CiscoSystemsCCM-SIP 582574 3 IN IP4 172.20.10.42

s=SIP Call

c=IN IP4 172.20.10.16

t=0 0

m=image 30358 udptl t38

a=T38FaxVersion:0

a=T38MaxBitRate:14400

a=T38FaxFillBitRemoval:0

a=T38FaxTranscodingMMR:0

a=T38FaxTranscodingJBIG:0

a=T38FaxRateManagement:transferredTCF

a=T38FaxUdpEC:t38UDPRedundancy

a=T38FaxMaxBuffer:200

a=T38FaxMaxDatagram:72

 

//Fax returns 406

 

43175530.001 |10:34:44.530 |AppInfo  |//SIP/SIPUdp/wait_SdlDataInd: Incoming SIP UDP message size 373 from 10.1.2.56:[65373]:

[2111601,NET]

SIP/2.0 406 Not Acceptable

Via: SIP/2.0/UDP 172.20.10.42:5060;branch=z9hG4bK2d4054482639b

From: <sip:97702421273@172.20.10.42;user=phone>;tag=582574~1dde394d-a9da-440b-99b3-e841e0f56070-87557506

To: <sip:8227195@10.1.2.56;user=phone>;tag=Ae_'.bdFuy

Call-ID: 20151029104119-T38-C-1KHzx@10.1.2.56

User-Agent: RicohIAF Version 2.0

CSeq: 102 INVITE

Content-Length: 0

 

 

21.4.7 406 Not Acceptable

 

   The resource identified by the request is only capable of generating

   response entities that have content characteristics not acceptable

   according to the Accept header field sent in the request.

  

I tried everything per your instructions and cannot get the thing to register.  Will this example work on a Ricoh 5002?  Thanks!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: