[cisco-voip] Fax Server

[Turpin, Mark]

The second port is a voice t1 (pri) port right?  If so, yes you can use
MGCP, you're going to be the telco in this scenario.  Your calls coming
from the PSTN will hit your router and then you will have a route
pattern pointing it back out the second PRI to the Brooktrout.  I got it
to work with 4ESS and Network emulation (you'll see this in your router
and CCM gateway configuration).  I think the 8 in the part number means
8 channels licensed, but you can ignore that.  You can setup a full T1
(d channel on 23) and be fine.
 
Just make sure you're setup to do g.711 & pass-through, your life will
be much easier when it comes time to troubleshoot.
 
Lastly, Ethernet is still an option for you.  The h.323 portion only
applies to the Brooktrout portion of the call leg.  You can still have
your PSTN facing PRI controlled by MGCP.
 
hope this helps,
Mark

________________________________

From: Gary L. Pate [mailto:gpate at kenttech.com] 
Sent: Wednesday, October 11, 2006 11:47 AM
To: Turpin, Mark; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Fax Server



I have a Brooktrout TR1034-P8H-T1-1N card, and my PRI currently connects
to my router which is MGCP back to CCM.. All fax numbers and regular DID
numbers come through that PRI, so I will not have a PRI plugging into
the T1 interface on the Brooktrout. I was hoping to use the Ethernet
port on the Brooktrout card, but it looks like I may have to convert to
H.323 if I go that route using option 1. I was hoping to use option 3,
but I'm not sure about the signaling piece of it. Can I connect the
Brooktrout card T1 to the second port on the router module and still use
MGCP?

 

________________________________

From: Turpin, Mark [mailto:mark.turpin at Calence.com] 
Sent: Wednesday, October 11, 2006 12:34 PM
To: Gary Pate; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Fax Server

 

In my experience with Rightfax, I set it up using the brooktrout t1 card
(although IP was touted as being easier, I didn't think so).  It was
connected to a 6500 with a cmm/pa-6t1 (but any pri supporting router
will do) and the brooktrout.  We were doing pass through (not relay),
and everything worked like a champ once we got the circuit up.

 

Just ignore what they're saying about MGCP and fax relay, you don't have
to do relay.

 

By the way, I used 4ess, network side, and internal clock for the 6500
side of the t1.  We couldn't get it up with the 6500 being the customer
side.

 

Brooktrout has excellent customer support, too.

 

-mark

 

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Gary L. Pate
Sent: Wed 10/11/2006 9:20 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Fax Server

I'm doing my first Fax Server install (Rightfax) version 9.0, and I
looking for some guidance. According to the Installation Guide
Supplement for Cisco Fax server, there are three deployment methods. 

 

IP T.38 Fax Relay

All traffic to brooktrout card is via IP. The T1 interface is not used.
The Ethernet on the MCS server uses SIP for call control, and the
Ethernet port on the Brooktrout card is used for media (FOIP UDP
packets). - H.323 must be used on router.

 

ISDN E1/T1 Direct. 

T1 connects directly to T1 port on Brooktrout card.

 

ISDN/MGCP Cisco Fax Relay Mode

Used where mixed voice and fax traffic share same trunk and uses ISDN
overlap sending for signaling. When deployed in this mode, all fax
traffic to the fax server uses the Brooktrout card ISDN interface. Call
signaling for the fax call setup will first traverse the Callmanager
using MGCP. For this configuration either an additional ISDN interface
is required on the router and this plugs directly into the T1 interface
on the Brooktrout card.

 

My router is currently using MGCP, so to me the last model looks like
the way to go, but most the document refers to E1 versus T1, and I'm not
sure about the ISDN overlap signaling.

 

Can anyone offer any advice on the best way to proceed?

 

Gary

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061011/b249d626/attachment.html