Overlay Passthru Connection Issue

[Vernst]

I am trying to open an Overlay Passthru System Terminal window to do some changes. Every time it opens I get an error message saying Connection To Host Lost.

I have checked all the physical connections and they are fine.

Does anyone know why this is happening and what I can do to stop it so I am able to get in to do some work?

 

[srmega41]

Can you ping the PBX from your workstation? Have you been able to get in before? If you can ping, then this issue is a beyond Layer 2, and might be a Server issue or config change.

Hope this helps,

Scott M.

 

[Vernst]

What IP address should I ping?

I have been able to get in before. It was working up until about an hour ago. I haven't changed any settings and thought that maybe it was just a workstation problem but a few restarts later and Im still here!

 

[srmega41]

The IP Address of the PBX. Do you have that info? If not, look under the connections profile of the PBX within OTM, and you should find it there.

Scott M.

 

[Vernst]

Oh yeah. OK I pinged the IP and it is hitting it OK. However, something else has just happened.

When I went into OTM to look for the IP, I clicked on the System Data tab and I got the error message
"An error occured while attempting to initalize the selected property page.
The page will be disabled."

And when I clicked on the Applications tab, I got
"Invalid machine/release combination."

Something isn't right!

 

[srmega41]

Sounds like you may be having server issues. I would try to reload the OTM Server.

Scott M.

 

[Vernst]

Firstly, I don't want to sound stupid so if I am doing anything wrong please tell me.

I presume the services are Windows services, so I restarted all OTM services that were running.

This seemed to rectify the other problems (Systems Data, Applications tabs) but I am still not able to access the Overlay Passthru.

Have I restarted the correct services?

 

[srmega41]

Are you running the server on your PC, or do you have a seperate OTM server? Ususlly, there is an OTM server, and the users use their PC and a client install to access the system. You can set your PC up to be the server, but that is ususally not the normal install.

If you are running from your PC, I would reboot your entire machine. If it is running from a seperate server, I would reboot the server.

Since you can access the tabs, can you now get the PBX IP Address and ping the PBX?

Scott M.

 

[Vernst]

I have already pinged the PBX and it came back OK.

I am not too sure that the OTM server is running on the PC as I have reboot it several times and it did not rectify the problem.

However, the only equipment that we have here is the Option 11c and a PC. Our telco only installed the PC with OTM about 6 months ago.

What do you reckon we have?

 

[srmega41]

Sounds like you have the server running on your PC. One thing you may want to try is re-building your site profile. We have had a few issues with database corruption, and the only way to get everything working was to delete and re-create the site.

Scott M.

 

[Vernst]

I was kind of thinking this may be the solution. Also, I have noticed myself that the databases running OTM are very ropey. As far as I can tell, most of them are running in Microsoft Access. That to me tells me that the system will not be very stable. As a web-developer, it is always a last resort using Access.

When we first had this system installed we had a very similar problem, but it seemed to rectify itself the next day. I will leave it for the weekend, and hopefully it will have resolved itself. If not, looks like I will have some work to do come Monday!

 

[srmega41]

Good luck!

Scott M.

 

[acewarlock]

Why not try a shutdown of the PC and reboot everything.

 

[boogalacker]

OK look at this
When you programmed you PTY ports you had to add somthing into the fields

Ld 17
Req> chg
Type > adan
adan > new tty
tty-type> pty
Port > #
Des > ELAN
FLOW
USER> SCH <---- try this


ADAN TTY 9
CTYP PTY
DNUM 9
PORT 0
DES OTM
FLOW NO
USER SCH
XSM NO
TTYLOG 0
BANR YES

 

[Vernst]

Just to let you know that this problem has now been resolved.

It seemed to be a back-end software problem, in that login sessions were not being closed correctly by the switch.

Several patches were installed and I just performed a Warm reboot and it has done the trick!

Thanks to everyone for their advice.

 

[srmega41]

Glad to hear it is working now.

Scott M.