Return to the Comm Tips
Multitech Modem Configuration
This may be a very basic question, but are you sure the multi tech modem you are using supports SYNC rather than ASYNC comms? I'd try another modem just to see if the problem is the modem (or modem cfg) or somewhere else. If you have a UDS V3229, 3400 or 3600 around, set the modem to factory option set 9 and you will be all set.
I have used the Multitech MT2834BLK successfully - I don't know how the spec for the BLK compares with the BA model. Anyhow, my modem is at home but I will e-mail switch settings etc later when I can check it. Maybe your modem is faulty, I had to return one modem to Multitech when first purchased because it would not work.
To narrow the problem down, without a spare SYNC modem; Plug in a working ASYNC modem and use STRITF. From there do ATDT(your number).
This'll eliminate all those 272X card/cable problems.
For the line description, you'll need an ASYNc configuration, here's one I use:
CRTLINASC LIND(ASYNCMDM) RSRCNAME(CMN01) ONLINE(*NO) + INTERFACE(*RS232V24) CNN(*NONSWTPP) SNBU(*NO) BITSCHAR(8) + PARITY(*NONE) STOPBITS(1) DUPLEX(*FULL) ECHO(*NONE) + LINESPEED(9600) MODEM(*NORMAL) MODEMRATE(*FULL) + MAXBUFFER(896) THRESHOLD(*OFF) FLOWCNTL(*NO) IDLTMR(1) + DSRDRPTMR(10) AUTOANSTYP(*DTR) CTSTMR(25) RMTANSTMR(60) + CMNRCYLMT(99 99) TEXT('CMN01 9600 *NONE 8 1') CRTCTLASC CTLD(ASYNCMDM) LINKTYPE(*ASYNC) ONLINE(*YES) + SWITCHED(*NO) SNBU(*NO) LINE(ASYNCMDM) ACKTMR(35) + RETRY(7) RMTVFY(*NO) CMNRCYLMT(9 1) + TEXT('CMN01 9600 *NONE 8 1') CRTDEVASC DEVD(ASYNCMDM) RMTLOCNAME(ASYNCMDM) ONLINE(*YES) + CTL(ASYNCMDM) TEXT('CMN01 9600 *NONE 8 1') ****************** End of data **************************************If this works, I'd try the multitech in ASYNC mode.
If that works, then it's either your ECS line description or the SYNC part of the modem. So try putting up a different line configuration. If you need one these, let me know.
Thanks for checking. I called Multitech and they confirmed the switch settings for the BLK and the BA models are the same. The only difference between the two is the BLK model supports 4 wire leased line. I also found out that pin 20 is DTR. I will check to make sure the 400 is bringing that up when I very it on. It would help if I could verify the internal settings on the modem also. If it's too much trouble it's ok. I realize everyone is busy. The tech said I may need AT&D0 but he wasn't sure. In order to view the internal setting he said write down the original setting first then connect it up to a PC and change pin 8dn10u and 12dn.
Then on a terminal screen
ATL5
ATL6
ATL7
will give all the internal settings. Make sure 8,10 & 12 are returned to their original settings. I know switch 12 up is SYNC down is ASYNC.
I certainly wouldn't want you to re-type all those settings. I hope you have a way of capturing that screen. If you do have a way of capturing
the screen and zipping into a file you are welcome to email me directly. Dave doesn't like attachments. I use Snagit for all text or image captures.
It can be found at http://www.snagit.com/
Gary, the switch settings on my modem are as per the second example in your original note:
1up2up3dn4dn5through7up8&9dn10up11dn12through15up16dn
I was not using QESLINE. I'm afraid I cannot remember why I decided not to use it. It was probably so that I could have one line description for each location that I planned to dial out to. I was being helped by an Ops Supervisor when setting my machine up.
I created a new SDLC line description of my own, with a controller. I seem to remember having to make sure the STNADR parameter matched on line and controller, though I picked an arbitrary value of 66 for both.
My line description parameters are :
RSCRCNAME(CMN01) ONLINE(*NO) ROLE(*NEG) CNN(*SWTPP) AUTOCALL(*NO) MODEM(*NORMAL) SWTCNN(*BOTH) AUTOANS(*YES) AUTOANSTYP(*DTR) AUTODIAL(*YES) DIALCMD(*V25BIS) THRESHOLD(*OFF) DUPLEX(*FULL) MODULUS(8)My contoller description parameters are: LINKTYPE(*SDLC) ONLINE(*YES) SWITCHED(*YES) INLCNN(*DIAL) DIALINIT(*LINKTYPE) SWTDSC(*YES) AUTOCRTDEV(*ALL) on the controller description.
Nigel Waters
[report a broken link by clicking here]