What would cause TTY ports to DSBL?

[chippowell]

So two of my TTY ports (one for CDR, one for my SEB modem) suddenly disabled over the weekend. Coincidentally or not, two days prior to the TTY ports disabling, my auxilliary site - fiber connected - had to be removed from the network for a couple hours. Everything seemed to come back up fine, and I got CDR data for almost 48 more hours.

However, at the main site, the two TTY ports were disabled: not manually by me, my tech, or my channel partner. Took me a day or so to discover this, and easy to turn back in on LD 37.

Any theories on why this may have happened? Anyone else ever see TTY ports mysteriously DSBL?

Thanks!

 

[Tman45]

Ours are doing the same thing and I have a vendor onsite now to investigate!

 

[Tman45]

It seems to have started after we did recent 7.5 patches. Our last patching was done in October-ish and it had been fine. We had to do recent patch lavels to prepare a site conversion from 4.5 CS1000S to 7.5 CS1000E - Wooot! That'll be nice to have it completed.

I will let you know what we can find, if anything. Very strange for sure!

 

[Tman45]

We found that all the TTY/COM ports on the back of the Media Gateways are not responding. We know that they started failing when the patching was done. So, we are first going to reboot our PBX and see if that resolves it (maybe Avaya left out some 'special instructions') and if it doesn't work Avaya gets to figure out why

 

[Tman45]

We INI'd our system and our TTY ports work properly. So, if you are doing patching, FYI that it could cause TTY issues.

 

[KCFLHRC]

If you run the deplist check tool before you do your patching it will tell you what patches will be added and if they require an INI or SYSLOAD.

 

[KCFLHRC]

You might want to also check and see if your MGC loadware is up to date.