Without changing anything, one day I was able to log in to the system and the next day I couldn't. My programming computer is in a remote location from where the system is at, so I took my laptop up and plugged into it. Nothing happens when I hit ESC, but if I reboot the phone system with the Procomm window open, I'll get like a half a screen of random characters when it comes back up. I've tried both RS-232 ports. Any suggestions?
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
If some how the port got programmed as the operator port try pressing CTL O and see if it takes you out of that? Or use a modem and have someone transfer you to the system modem after calling the system and check the I/O port settings. If need help remotely send PM
Transfer 99 will transfer an outside call to the built in modem.If it's a 108 CPU then probably 1200 baud.
Check the connection from the 108 cabinet backplane and make sure the cable is securely plugged in. Random characters could indicate a baud rate mismatch. Even if it was programmed as an Operator screen,hitting ESC would refresh that screen.Tells me that you have a connection problem,port issue or a baud rate issue.
Checked the connections. The port settings look OK, but still no luck. Do those port(s) go bad? I can't seem to get anything out of either one. I am able to dial into the modem.
Rarely but yes I have seen them go bad. You did check the cable going into the back plane like pvj mentioned correct that is a very common issue. Also is there one of those I/O protection units connected. If so you may want to try to route around that. Like I mentioned if you want remote assist PM me with information and I'll take a look but it sounds like you already checked that remotely so I'm sure you know what to look for.
if you are able to get into the system via the modem. go to the "B" screen and in the middle right of the screen check your port settings. make sure port 1 or 2, installed is set to "Y",(they have been known to toggle off), XON for protocol and baud rate is at correct speed. If I recall, try toggling the SMDR from "N" to "Y" and back to get the port to spit out. AND hopefully your laptop is NOT using windows 7 with procomm plus to communicate. Tj
I will give it a try. I'm using XP with Procomm Plus. What causes things to randomly change settings? I've had issues before with key assignments changing to other things.
If your line keys are changing to a code of 5535 that is a bug and you have to apply a debug routine to correct. Let us know how the I/O port thing works out.
I will give it a try. I'm using XP with Procomm Plus. What causes things to randomly change settings? I've had issues before with key assignments changing to other things.
If the system is not grounded or properly grounded will cause these to happen.
I have seen I/O ports go bad in older IDS systems after an electrical storm. If that's the case about all you can do is replace the CPU and reprogram which will be a fair size pain.
I was finally able to get connected to my system. It seems there was a wiring issue. It still seems like there might be an issue with the com ports though. The screens that don't have any "data" on them, such as the welcome screen or the reports menu look fine. I can also get into the VXC screen fine. Any of the other screens show the text fine, but the data is in the wrong place and I obviously can't change anything. For instance, in the A screen all of the data is in a long string at the bottom of the page, but the rest of the text on the page is where it should be. I've tried both com ports. Is it possible for them to be bad even though some stuff comes through fine? I have another CPU board that I popped in and it seemed to be fine.
Sounds like the Terminal type got changed. When you first log in and the Main Menu is coming up do CTL A for select terminal type. Then enter 1 and see if that corrects it for you.
I assume your lap top is set to TVI 920 25 rows and 80 columns and all other setting haven't changed?
check the Protcol on the ports of the system, You say You can make it work with Another CPU..( Back in the Old days Tech Support would have us Back up the system, then DEFAULT it , to see if the issues went away...
What should the correct Protocol info be? Unfortunately it doesn't look like I can just reload onto the other CPU, mine is an Eclipse and the other one is ACPU. I picked it up a while back for a spare. Perhaps I can try defaulting it this weekend.
When I default the system, everything is fine afterwards. When I restore my programming, it goes back to wacky. So, I'm assuming that means that something is corrupt in my program?
That sounds correct and if you changed the Terminal type like I had suggested in previous post on both ports 1 and 2 I would say you have some corruption. But if you haven't changed terminal type I have seen in the past where someone selected (4) if I remember correctly and it painted the screen just like you were saying.
I took a bunch of screen shots and defaulted the system and started from scratch. Everything else seems to be OK now, except that the VXC auto attendant won't answer incoming calls. I have the lines set to H36 in the B screen and H36 and VMS/Attend turned on for the extensions in A. When you look at an incoming call in C, it says HRNG and then just keeps scrolling through the VXC extensions, but never tramsfers. There is no incoming activity in the VXC screen. The Voicemail key does take you to your Voicemail though. Did I miss something somewhere???
Is the forwarding screen correct in the G-Screen? I would think it would be ok if you defaulted system. What software are you running on the CPU strange that the key works but not lines set to H36 in the B-Screen. I assume the line ID's are squared up to the lines themselves? If you want send PM and I can attempt to look at it for you but it sounds like everything is set correctly.
Eclipse 2.0.0. I reloaded the old setup that is corrupt, but works, for now. I will look through the settings again and make sure I didn't miss something on my screen shots, but I don't know what else it would be.
If you answer a call and try to transfer it to VM does it do the same thing? Or program a line to ring directly to VM extension what is the result there. You do have LCR keys programmed on the VM extensions? If they don't have line keys that would cause problem.
Or try this. Use a dummy ACD group and program the line to ring to that ACD group. Then in the ACD group program first box to Delay 05 then next box to FDW to H36 see if that delay helps. With 2.0 you can program things like that even though full ACD features are not activated on CPU. And like I said send me a PM with call back number and would be glad to assist.
The more I though about this it really sounds like perhaps(?) you may have forgot to subcode your line keys on the VM extensions? 300 with subcode 100 is LCR key or if all lines are in group 1 just use subcode 1 LMK
I seem to have one other issue with one of my mailboxes. When you hit the VM key, it plays the greeting and prompts to leave a message instead of going into the mailbox. If I dial one of the VM extensions and go into it that way, it works.
It's most likely missing the # in the G-Screen programming under the VMS Box# pf Under the pf it should have a # after the voicemail box number. Ext |Box# pf| Busy |No Ans| All | Busy |No Ans| All |Busy NoAns| 3001|3001 #
What does your run dialog screen on the VXC ports say you are running. It sounds like you may be running auto attend on the ports and if so when AA answers do you have the # key for that CCR box set for subscriber entry? What happens if you dial 436 and when VM answers you enter # does it ask for mailbox number and after you enter that it says enter password? I may need to look at it to assist if you PM me a call back number I would be more that willing to take a look.
OK, so upon further checking, the problem only seems to be occurring on VM keys that have different extensions as subcodes. We have a general delivery box that is on a few phones and I've got a couple different ones on my phone. Dialing 436 and going in that way works. VXC is running SMDI.
Yes, the regular VM key for that extension works, just not ones with subcodes. The DNIS task is T AUTOS 0001. I may end up having to switch back to my old program. Having some other weird issues too like one of the phones isn't lighting up any line lights.
I can email you a picture if you want to PM an email address.
