Re: USR V.Everything modem fails on send

From: Logic Force (spamme_at_logicforce.com)
Date: 04/22/04 

Date: Thu, 22 Apr 2004 16:04:56 -0500

I have put in the following string which forces several different protocols
and settings, namely v.32bis is forced somehow through this string. I
believe it works, I have finally gotten more than 2 pages to go through, it
did apparently fail on one attempt, but once it tried again it appeared to
be successful. Here's the string from USRobotics support.

&F1+FCLASS=1S58=96S51=4&N6&U6
SKH

"Logic Force" <spamme@logicforce.com> wrote in message
news:%23%23u9GbIKEHA.644@tk2msftngp13.phx.gbl...
> The modem I am using is a V.Everything modem with V.92 protocol, evidently
> it's the newest one. I have called USR and received several modem strings
> to input, none of them have worked as of yet. They claim that they don't
> know enough about 2k3 to support it. I also have a list that I am
examining
> that USR tech support sent me. I have tried forcing fax class 1 and 2.
Fax
> class 1 actually lets me send 2 pages as compared to 1 with anything else.
> I can receive just fine, which makes me think that incoming fax modems are
> setting up a different protocol for their faxes. Below are the errors I
get
> from the fax software in SBS. This is insane that these modems worked the
> best with previous editions of SBS, but now they have problems. Are there
> any other modems anyone recommends?
>
> Error code in outgoing fax log: 0x40000802
> Error I get from the fax monitor: The remote fax machine did not
respond
> in time, and the call was terminated
>
> Sincerely,
>
>
> Shawn Hatcher
>
>
>
> ""Chris Ard [MSFT]"" <ChrisArd@online.microsoft.com> wrote in message
> news:GFrwugAKEHA.3564@cpmsftngxa10.phx.gbl...
> > I've been using the external V.Everything for years and it has never had
a
> > single problem. Could you describe what exactly you are doing? Are
these
> > really long faxes or are you sending broadcast faxes to a ton of people?
> >
> > Chris Ard
> > Small Business Server
> > Enterprise Platforms Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
>
>

Relevant Pages

  • Re: Recommendations on SBS 2003 External Modem
    ... Always get a modem with real chips, ... - Try different baud settings on the serial and Fifo settings ... I then disabled the high order bit for the V.17 protocol, ... that were already 0 because my modem would not support them. ...
    (microsoft.public.windows.server.sbs)
  • Re: SSHD revelaing too much information.
    ... >>'OpenSSH_2.3.0' part is required for the protocol. ... Displaying the extra version string info later on would be pointless, ... Bragging might attract the wrong types to test ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: Why are 56K Modems Limited to 44.4K
    ... >> And you will Never achieve 56K on any Modem. ... >> Phone line to your Server and the Server dose the opposite.....this all ... >> you need to Break down your String the Default string is all well and ... >> but it has Data compression on and Flow Error controls on which you do ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: save dictionary for later use?
    ... might save a list of dictionaries or a list of classobjects too if ... What about *READING THAT FUCKING MANUAL*? ... If the protocol parameter is omitted, ... file must have a writemethod that accepts a single string ...
    (comp.lang.python)
  • Re: Why are 56K Modems Limited to 44.4K
    ... > Modem but using the F1 or F&1 string by default is the best in my Opinion ... > Ok lets say your connection from your server is Rated at 33.3Kb/s you will ... > but it has Data compression on and Flow Error controls on which you do not ...
    (microsoft.public.windowsxp.help_and_support)