Magix internal modem

[CarGoSki]

I thought I would run this past here before I commit to pulling the battery strap and reprovisioning by hand. Magix 3.0 processor that has problems connecting. After a power cycle the modem works correctly for a small period of time. WinSPM work correctly and there are no problems. However when it acts up the login prompt sequence shows at the bottom of spm but no login window appears or is seen.

This has occurred for years so I changed out the processor with an identical unit just before Christmas and used the restore card to restore translations to the new unit.

When tested spm worked as expected so it appeared that the issue was resolved. But alas the problem is back and is a bit worse since one local user could use winspm and *10 to connect with the old processor but now can not.

I have not power cycled this unit yet but I would expect it to begin working for a few days before not working. While it is not working a local user can dial *10 from a phone and hear modem tones.

In this case would pulling the strap and rebuilding by hand be correct? Corruption?

 

[merlinman]

CarGoSki, there are better ways to reset the modem than with a Power Cycle.

I like to use the Modem Reset in Standard SPM Maintenance.

Menu > Maintenance > Port > Modem > Reset

However, there are more things that can cause this issue besides the modem itself.

Usually there are line problems that can cause this issue but I have also experienced problems with specific modems (PC side).

I find the best one (for me at least) has been the Lucent Win Modem, either in a Laptop or a Desktop.

That being said, I still have one client that I have issues with.

That I am afraid, is the nature of Modem connections.

Could your local person get a wire run installed from one of the Com Ports on his PC back to the ADMIN Port on the Magix?

That's always a good way to do it.

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

 

[merlinman]

One thing I forgot to mention:

Your local user should also double check that his modem is set up OK per the WINSPM Set up wizard.

It may have worked sporadically in in the past, but now that the modem has been replaced, he may need to re-check the setup of the modem and make sure it is in compliance with the STRINGENT requirements of WINSPM.

That could also be an issue.

Plus, does it work for you remotely?

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

 

[CarGoSki]

Modem reset had no effect. Power cycle repaired the issue. I am going to make sure that the site spms remain unused and will dial in once a day for a week to see if the modem goes awhack in that timeframe.

Is there anything during a auto backup that could cause an issue like this? There is nothing in the error log not related to the power cycle.

Grounding?

 

[merlinman]

Not that I know of.

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

 

[HiDesert]

there is the remote possibility that the system software is
corrupt...you may have to flash the software and start over
programming the processor...I would start with a different
processor and see if the modem connect problem surfaces.
it worth a shot.

 

[CarGoSki]

I suppose the possiblity exists of corrupt system software and I suppose that it would be a rare case in this case since I just replaced the processor before Christmas to repair the internal modem.

 

[HiDesert]

that said..did you use the backup flashcard or file to
reprogram the processor OR start from scratch...there is
a difference...

 

[CarGoSki]

Yes I am aware of the difference. I am try earnestly to avoid pulling the battery strap and reprogramming from scratch if possible. When I replaced the processor I simply restored the programming from the flash card.

I do know that if there is corruption then the only way to eliminate the corruption is to strap/reprogram and to talk someone else into performing the reprogramming...hehe

 

[merlinman]

If the system really needs to be wiped out and re-programmed, then pulling the battery strap is not the preferred method.

I like to use Maintenance to reset the memory.

Of course, that procedure can't be posted in this or any other Public Forum.

I have never seed Software Corruption cause a problem with the modem, however.

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

 

[HiDesert]

I see your processor is R3 magix...IF you have to start from
the beginning..I would suggest that you upgrade to a r4.7
release...MM..I have run into corrupt software in older
releases.. that did affect the modem function..by upgrading to the last known version and starting over..I did solved this issue...
This is just one path to take, if using a s/l station to
connect your pc or laptop and *10 gets you in and working...then look at the local dial tone..you didn't say
what type of DT you have connected...POTS or T1.

 

[CarGoSki]

MM: It is interesting that you have not seen corruption cause modem failures. I only have this one site where the modem has been challenging. No other sites have had issues similiar to this save the occasional pc modem setting issues.

HD: Changing out to a higher release processor is a great idea. The suits wanted to use the same release for some reason. Probably money but the cost difference can't be that great. Dialin is via PRI. The local user uses a analog station and *10. No POTS on the system.

 

[HiDesert]

Upgrading a R3 to R4.7 is only a flashcard away...and not
to expensive.
Remote Access via T1/PRI is iffy at best...I have had trouble connecting and or DL a backupfile on my PC's when
going through a Hi-Cap Ckt.

 

[phonesrus]

Just a thought on the PRI: If this is a true PRI and not a VoIP thru a Cisco or Adtran device, you should not have a problem with the modem via transfer, unless indeed you have a modem issue.
However, if you have a CBeyond or similar PRI (dynamically allocated) circuit using packet based VoIP, A modem connection will not work worth a dang and it does not matter what type of system you are trying to connect to. It will freeze up, not function correctly, or periodically just drop the connection or fail to connect. MM can testify to that!

 

[merlinman]

Amen to that.

(WinSpm) Analog to Analog is the best.

(WinSpm) Analog to PRI is problematic. It works when it wants to.

I currently have one client that my ANALOG to their PRI works reliably, but I have had others that were iffy at best!

But of course, there is always the "BAD MODEM" in the processor issue. When you have that problem, it's a very hard sell to get them to purchase a new processor, 'cause they are not having any problems with their phones.

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

 

[dagwoodsystems]

I have two Magix customers with this issue. Both express the identical behavior, which is that remote connections become impossible anytime after I use one the PBX's analog station ports to locally dial-in. Both sites have abundant analog stations, which means that I can make immediate and last minute changes without having to run all the way back to the phone room.

Once I've gained access in this manner, I lose my remote dial-in capability. Oh sure the modem answers and such, but they never quite get the handshake right. The call drops and WinSPM resets. Each time I returned to these sites, I found that I could again gain access via local station dialtone (direct-to-admin is never affected).

The only cure for this condition has been to power cycle the primary carrier. After that, remote dial-in works flawlessly for months and years without incident. But once that Magix modem handshakes/trains through an internally-placed call, I have to continue to access it that way or use the Admin port directly. The only way to go back to having remote dial-in capability is to COLD boot the switch. Performing a board renumber, system reset, modem port reset or similar techniques will not clear the problem.

The only consistancy between these two sites is that both have a CKE5 processor with an 02 hardware vintage (617X33-ML), but that's not enough to draw any definitive conclusions from.

Other than myself, you are the first to bring this subject up. I'd like to know if any of story applies to your situation. If so, tell me about your processor!

Tim Alberstein

http://www.dagwoodsystems.com

 

[CarGoSki]

Hello dagwood. Sounds identical. I'll get the details on the processor for you.

 

[HiDesert]

Dagwood..what is the release of the processors...legend or
magix...
The issue still gets back to T1/PRI Hi Cap ckts....no matter
what release you have...WinSPM with a Lucent chipset modem
will NOT always connect and I have more backup abort failures than successes...I do know what works is DOS SPM..
I know were talking about stone age software...but it works.

 

[memphisribs]

Dagwood, add me to the list, having the same as you discribed. Magix R4 CKE 5 hrw ver 2. Customer uses analog extension to *10 for admin. Also has PRI.

43 years in the business and counting.

 

[memphisribs]

Oh one other note solved my problem by adding a Digi-one to convert the admin port to ethernet. No more worries about the modem.
Good Luck

43 years in the business and counting.