Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Rightfax and Session Manager - Can I cut out CM?

Status
Not open for further replies.

Steve K

Technical User
Nov 29, 2018
2
GB
I have inbound/outbound SIP trunks from Verizon, these are delivered to Session Manager, and then routed using System Mgr to CM.
I then have a SIP trunk from CM to route traffic back to Rightfax etc.
This is the documented configuration that ALL of the Avaya docs reference under the impression that ALL inbound PRI are terminated on a CM gateway.
I want to remove the CM link and just have Session Mgr and Rightfax talking directly.
I have created a Rightfax entity in System Mgr, set routing via dial patterns and inbound faxes connect to the server..
Problem is outbound i get 407 Proxy Authentication and 400 bad Request (missing user name in response digest)errors.
Any suggestions
thanks
 
Your entity link is wrong. Maybe Rightfax is doing UDP and your link is TCP or something.
SM can register sets and have trunks. Your request is first analyzed as matching source/dest IP/port of a known entity link - if so, your call is processed as being from that entity.

If your INVITE doesn't match any known entity link, well, you must be a phone with a username and a password, so when you send SM that INVITE, it's going to respond with 407 Proxy Authentication Required and expect you to send that INVITE again with a digest/hash/response to the nonce provided in the 407 message. That second invite is then allowed to pass. But if you got to this point, something about your routing made it not match as an entity.

Can you put Rightfax directly on your SIP trunks and cut out CM? Sure. You could go RightFax-->SM-->CM-->SM-->SBC-->PSTN or RF-->SM-->SBC. It's more of a Verizon question to be honest. Having CM in the middle lets you play with dedicated trunk groups where you can tweak codecs and DSPs if that suits you. The Session Manager part isn't terribly relevant - it's just a proxy. Heck, you could probably put RightFax right on the SBC if you wanted to.

What are you running in the RightFax for a SIP stack? Is it one of those Brooktrout cards? I'm sure you can tweak it really good if you wanted to. And if you happen to be a RightFax wizard, maybe that's easier for you. For me, CM's comfy.

Besides. Faxing over SIP trunks? Sure, but popping that number in CM to ARS to use a PRI for that one number you can never get to work right on SIP is nice to have.
 
The company only has SIP trunks and at present the fax calls are being processed by the IP-Codec's and these are set to pass-through. I am experiencing issues with this and T.38 & T.30 compatibility with certain external clients. The G711 compatibility option in the IP-codec doesn't work. Thought that cleaning up this connection and getting Rightfax just talking T.38 would simplify matters.
 
It might. I'd figure you should be able to do CM properly to do t38 and fallback to G711 toward the pstn and only do t38 to rightfax.

Pretend for a second that I for a telco and debug stuff like this :)

Maybe all my media gateways in my PSTN support t38. Maybe they don't.
Supposing they did, and you happened to call a PRI customer on the same carrier, we know that's going to be G711 on the last leg to them, and because we know you're my SIP trunk customer, my media gateways facing PRI land that support t38 will happily do that conversion for you.

Maybe your next fax thru my SIP trunk is to another carrier who I happen to link up with via SIP and the far end doesn't support t38 - they just return G711 as a media offer. Does my service with you include t38 to g711 conversion? If not, then that call won't pass.

Even if you're just SIP trunks, having those certain external clients in ARS to another trunk group to SM with a different far end network region and different codec set would let you juggle around CM's possibilities depending on dialed number. My advice would be that if you're able to get that part done right, you'd be just as good as t38 Rightfax to PSTN with the added flexibility of being able to juggle certain numbers out different paths if they happen to be problems.
 
Yes, You should be able to go from SBC to SM to Rightfax. CM doesnt need to be involved.
 
Yes, You should be able to go from SBC to SM to Rightfax. CM doesnt need to be involved.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top