[cisco-voip] T.38 and MGCP

[Matt Slaga (US)]

XMedius is the only company that support T38 with MGCP.  Rightfax still
requires an H323 gateway.  Even XMedius' solution is still H323 to
CallManager, but now CallManager 4.2 and later natively supports T38 and
can do the protocol conversion between the two.

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Craig Staffin
Sent: Monday, February 04, 2008 2:08 PM
To: Justin Steinberg
Cc: Cisco Voice
Subject: Re: [cisco-voip] T.38 and MGCP

 

Alright

So lets say we manage to get them on 4.2 does anyone have any
documentation on how to set this up?

I can't seem to find anything on the interwebs

Craig

On Feb 4, 2008 12:39 PM, Justin Steinberg <jsteinberg at gmail.com> wrote:

CM 4.1 doesnt support t38 with MGCP endpoints.  You will need 4.2 or 6.x
for mgcp support of t38.

If you absolutely had to stay with CM 4.1 and MGCP, you could use t38
gateway force but you would need to integrate with RightFax via T1 card
because as far as I know Rightfax doesn't support t38 negotiation via
nse.

On Feb 4, 2008 12:13 PM, Craig Staffin <craig at staffin.org> wrote:

	does callmanager support T.38 in MGCP mode yet?
	
	I have a project coming up where I will need to integrate a T.38
RightFax server with callmanager and the clients setup is CM 4.1 and
MGCP gateways
	
	Thanks for any insight
	

	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip

 




-- 
Craig Staffin
Craig at staffin.org
(H) 262-437-7313
(C) 262-613-6003 




-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080204/dc433f92/attachment.html