[cisco-voip] Faxing Issues... revisited

Kevin Dunn cheesevoice at gmail.com
Fri Mar 28 10:30:42 EDT 2008


Well, now that is just embarassing, BUT we had all the MGCP T38 inhibit
commands and NONE of the H323 pass through stuff set on teh gateway, AND the
PRI is H323...guess I need to look closer at that sort of thing.

The client is testing now, I should know soon.

Thanks for the help Craig (and everyone)

Kevin


On 3/28/08, Craig Staffin <cmstaffin at gmail.com> wrote:
>
> Make sure that T.38 is disabled all the way through.  Otherwise the
> automatic fax machine on the otherend will try T.38 the gateway will
> accept it and raise the call to T.38 and then need to do relay to the FXS
> port.
>
>
>
> On Thu, Mar 27, 2008 at 3:00 PM, Kevin Dunn <cheesevoice at gmail.com> wrote:
>
> > I have not done any debug, I should mention as well the Fax line was
> > analog at the old facility and is now a DID on the PRI at the new facility,
> > a num-exp command points the DID to the FXS port.  not sure that makes any
> > difference or not.  Also the Gateway is H323 and not MGCP... not sure that
> > makes a difference either.
> >
> > I will try a ccapio inout debug and isdn q931 to see what I get.
> >
> > Thanks
> >
> > Kevin
> >
> >
> > On 3/27/08, Paul <asobihoudai at yahoo.com> wrote:
> > >
> > > Have you looked at any debug CCAPI output regarding
> > > this matter? If so, are you seeing any timing issues?
> > > I once had a credit card processor that would wait 9s
> > > before sending data.
> > >
> > > Paul
> > >
> > > --- Kevin Dunn <cheesevoice at gmail.com> wrote:
> > >
> > > > Okay, I want to preface this with "my users are
> > > > fluent at 'vague' and fond
> > > > of BSoD (Blanket Statements of Disaster)"
> > > >
> > > > Their gateway is MGCP, and their fax machine has 2
> > > > lines going into it.
> > > >
> > > > without boring you with details of configurations
> > > > the issue is so WEIRD I am
> > > > just going to put it out there....
> > > >
> > > > When a client faxes us (incoming) manually the
> > > > system works just fine, when
> > > > the client faxes us (incoming) with an automated
> > > > system (auto-dialer, right
> > > > fax etc) the faxes do not connect.  When I test the
> > > > fax after hours it works
> > > > great (manually).  I don't have a way to test from
> > > > an automated system.
> > > >
> > > > Anyone ever hear of anything like this?
> > > >
> > > > Kevin
> > > >
> > > > PS:  I THINK the issue MIGHT be the primary incoming
> > > > fax line (FXS 0) is set
> > > > to busy trigger at one call.  The clients auto
> > > > senders are used to some sort
> > > > of cue and not a busy signal so they are reporting
> > > > "error" when in fact they
> > > > are getting "busy".
> > > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > >
> > >
> > >
> > >
> > >
> > > ____________________________________________________________________________________
> > > Never miss a thing.  Make Yahoo your home page.
> > > http://www.yahoo.com/r/hs
> > >
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080328/ee957f20/attachment-0001.html 


More information about the cisco-voip mailing list