WinSPM 9 and remote access blues

[pmcook]

I can call in to the AA, dial **xx and get the modem. So I set up the dial string as 1XXXXXXXXXX,,,**xx. It works, calls in, waits, dials **xx. I hear the modems talkin. Then nothing. What could be wrong? Other than the operator.

 

[merlinman]

If this is a "NEWER" PRI, then usually the problem is with the Carrier "COMPRESSING" the signal, thus not allowing a good transmission of the Modem Tones to be received by the Switch.

That being said, I have also had problems with the modem I was using and, rather than a tiny USB External modem, I had to switch to a "REAL" Internal modem.

Even some of those are tricky at best.

But, I'd be willing to bet it's the PRI causing your grief.

Good Luck, 'cause I still have some I can not dial into.

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[pmcook]

So it should work is that right? I am still working on the PRI project. Many delays. We're still on analog lines. But these ar MPower lines so they are not true analog.

 

[Telecomboy]

I doubt you'll be able to connect with IP lines emulating POTS lines. I have a multiple clients who have this set-up and WinSPM will not connect. One thing you can do is load WinSPM on a local PC that is directly connected to the Magix and then remote into that pc.

 

[pmcook]

I may have to bring a whole new laptop. See my laptop worked just fine connecting dorectly to the Admin port but for some reason now all of a sudden it won't. I can get an initial connection and I see the red and green S/R lights blink then it just craps out. When I plug the cable into the SMDR port and use Hyperterminal I can see the output so I know my laptop serial port (well USB serial) is working.

 

[pmcook]

Breakthrough - changing the FIFO buffers and turning off ompression seems to help. I can get a login prompt but it rejects the password. Nothing that 400 miles of driving won't fix.