Kind of at my wits end on this one. We have recently moved some of our customers to SIP for IB and OB calling. Along with this we have fax machines connected to ATA's. I can get IB faxes to work by changing a few things on the CUBE;
voice service voip
allow-connections sip to sip
fax protocol none
modem passthrough nse codec g711ulaw
And creating a Dial-Peer for each fax machine;
dial-peer voice 920 voip
no modem passthrough
session protocol sipv2
session target ipv4:10.x.x.x
incoming called-number +15551234567
fax-relay ecm disable
However I cannot get OB faxing to work. I have tried T.38/Fax-Passthrough, different speeds, and disabling ECM on the ATA's and the Fax machines themselves.
What model ATAs as i do know that 186s do not support T38? Also I always set the modem speed on the fax to 9600. Disable ECM. and make sure G3 is on if the fax machine supports it. Usually works like that every time with a traditional PRI or POTS lines.
I have the exact opposite problem you do, OB faxes work fine but IB faxes do not, you get about 1 sec of initial fax tone then the audio drops. You can see the call is still active but no transmission occurs if I dial in through SIP connection. I have a second CME MPLS attached and I can 4 digit dial from a fax to ATA to MPLS to CME to CME to ATA to fax, just fine both ways. Any call terminated through the SIP connection doesnt succeed.
I can send you a copy of my config if you like and I will try what you have done above to see if it resolves my issue as i can already see that the voice service voip fax protocol none is not what i have rather fax protocol pass-through g711ulaw.
I recently have had issues with RightFax servers faxing across a SIP trunk. The preferred medium for faxing across SIP trunks is T38, that being said there are several configuration considerations that come in play:
if you using T38 be sure you configure the following globally under voice service voip and or on the outgoing dial-peer to the Service provider:
the ip address of the fax server should be included in the "ip address trusted list" under voice service voip config.
Be sure you have QOS marked correctly along the fax call path, to prioritize (may match either CS5 or EF) Fax calls just like Voice calls. Be sure all your interfaces, especially closer to the ATA's trust DSCP values: using the command "mls qos trust dscp"
I should have posted earlier, but I ended up using steering digits to force OB Faxing to use a specific Dial-Peer. This is a multi-tenant environment, so I had to find some way other than sending out our PRI's. I'm not very good with Dial-peers, but this is what I did.
First off I know you would definitely need to use T.38 as fax medium when using Rightfax. and yes the config I provided above should definitely work on the CUBE for RightFax. You have two alternatives, you could directly point RightFax to the CUBE, and or for Manipulating routes using Route Patterns/List/Groups at the Callmanager level, have it point to CUCM using a SIP trunk, then another SIP Trunk from CUCM to the CUBE gateway, can get hairy, when it comes to using trunks and MTP allocations, you may or may not need to check the MTP required option on the SIP trunks, but in the scenario we have, hardware MTP's on the CUBE are being invoked, using the MRGL assigned at the Device Pool level for the SIP trunk.
Hope it helps somewhat, Good luck, maybe you can have another post when its time to actually deploy it.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...