Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Rightfax SIP Trunk with CUCM 8.6

Hi,

we want to install rightfax connecting to the callmanager via a SIP trunk. the setup is as follows, however we can't send faxes through.

PSTN (PRI) ----> H323/MGCP GW--------->CUCM---------->SIP TRUCK to Rightfax

                                                          

Otherthan having T.38 rely on the gateway, route plan for the fax range to point to rightfax IP address and SIP Trunk is there anything else to be concerned about? should the fax extensions (directory numbers) also be configured in CUCM or rightfax will handle that? I also ensured that incomming and outgoing transport is set to UDP and also incoming port 5060 on the security profile.

when doing trace with whireshark, I can see the rightserver receiving the the SYN but the server is sending back (RST,SYN). does this mean the problem is with rightfax server?

another question, I have ATAs connected already as SCCP cleints and those are workign fine. will configuring T.38 relay (This is a must for rightfax) not affect the ATAs?

1 ACCEPTED SOLUTION

Accepted Solutions

Rightfax SIP Trunk with CUCM 8.6

If you have ATA 187, then those support T38 however ATA186 dont. If you configure T38 on the dial-peer to CUCM, this might cause an issue. If its possible, i would try to configure a SIP trunk directly from the gateway to the Rightfax server.

Also make sure that the SIP trunk and gateway are in the same region and there are not MTP/Transcoder being invoked.

Yes, the UCM will need to send the fax extensions to the SIP trunk so that calls come into UCM and UCM sends it to Right fax, this will not be required for outbound faxes from the Rightfax server.

Please rate useful posts.

Please rate useful posts.
3 REPLIES

Rightfax SIP Trunk with CUCM 8.6

If you have ATA 187, then those support T38 however ATA186 dont. If you configure T38 on the dial-peer to CUCM, this might cause an issue. If its possible, i would try to configure a SIP trunk directly from the gateway to the Rightfax server.

Also make sure that the SIP trunk and gateway are in the same region and there are not MTP/Transcoder being invoked.

Yes, the UCM will need to send the fax extensions to the SIP trunk so that calls come into UCM and UCM sends it to Right fax, this will not be required for outbound faxes from the Rightfax server.

Please rate useful posts.

Please rate useful posts.
New Member

Rightfax SIP Trunk with CUCM 8.6

We've got mulitple evironments where we run T38 and ATA186.  Basics of it would be to ensure that you have the fallback configured so that if it isn't able to negotiate T38 it will fallback to modem-passthrough or cisco.  We normally do this under the voice service voip global and have good success with it.

Also on the MGCP make sure that you use the correct configuration.

Some notes on this:

working on IOS 15.2.2T+ and DSP 30.3.0+

show dsp-group all

no ccm-manager fax protocol cisco

mgcp default-package fxr-package

Also make sure your ISND clock select statement is correct otherwise you will get faxes that cuts off every now and then when having more than one E1/T1 etc.

Your configuration on the MGCP gateway on the CallManager must have T38 relay enabled.

Also how to troubleshoot this:

Debug mgcp packets

debug voip vtsp all

debug isdn q931

debug fax relay t30 all-level-1



Normal output

000666: Feb 16 16:48:35.263: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8  callref = 0x001C
         Sending Complete
         Bearer Capability i = 0x9090A3
                 Standard = CCITT
                 Transfer Capability = 3.1kHz Audio
                 Transfer Mode = Circuit
                 Transfer Rate = 64 kbit/s
         Channel ID i = 0xA98386
                 Exclusive, Channel 6
         Progress Ind i = 0x8083 - Origination address is non-ISDN
         Called Party Number i = 0x81, '7800'
                 Plan:ISDN, Type:Unknown
000667: Feb 16 16:48:35.283: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x801C
         Channel ID i = 0xA98386
                 Exclusive, Channel 6
000668: Feb 16 16:48:35.287: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8  callref = 0x801C
         Progress Ind i = 0x8088 - In-band info or appropriate now available
000669: Feb 16 16:48:35.287: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8  callref = 0x801C
000670: Feb 16 16:48:35.327: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x001C
000671: Feb 16 16:48:39.051: 0/0/1:15 (39)  29163293 fr-entered=10(ms)
000672: Feb 16 16:48:39.327: 0/0/1:15 (41)  29163569 fr-entered=10(ms)
     timestamp=29165943 fr-msg-tx DIS
     timestamp=29166219 fr-msg-tx DIS
     timestamp=29169143 fr-msg-det DCS
     timestamp=29172643 fr-msg-tx CFR
     timestamp=29172649 fr-msg-tx DIS
     timestamp=29178712 fr-msg-det MPS
     timestamp=29179079 fr-msg-tx DIS
     timestamp=29180292 fr-msg-tx MCF
     timestamp=29185539 fr-msg-tx DIS
     timestamp=29191919 fr-msg-tx DIS
     timestamp=29192883 fr-msg-det EOP
     timestamp=29194463 fr-msg-tx MCF

     timestamp=29196233 FR_BAD_CRC_LS_DATA 0x0 bytes
     timestamp=29196233 fr-msg-tx  bad crc, 0 bytes
000673: Feb 16 16:49:12.091: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x001B
         Cause i = 0x8090 - Normal call clearing

Hope this helps someone.

VIP Purple

Rightfax SIP Trunk with CUCM 8.6

Hi Emmanuel,

If u are using DID number, then u need to assign/configure one number from the pool in Route patterns under Call manager pointing towards SIP Trunk.

Same number needs to be configured in Routing Code[DID/DNIS number] under  Inbound Routing --Users in RightFAx.

regds,

aman

1270
Views
0
Helpful
3
Replies