I've got a problem. I have Openstage 40T (TDM) phones that are losing their display to the tune of 1-2/week. The display goes blank. Attempting to change the contrast has no effect. Putting the phones on a different port/STN has no effect. This just started 2 months ago. No other problems with the phones whatsoever. Has anyone heard of this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Openstage 40T (TDM) phone screens going blank.
- Thread starter MerlinJ
- Start date
I just posted this in another thread, but you may have said you tried it already. I have these issues sporadically, and I will go into the phone and change the pen (in software) to another empty one, wait a minute or two and then move it back. That seems to clear them up for me. My display doesn't go completely black though - the key labels stay visible but the company logo disappears - that is the first sign; then I will get calls that they cannot dial out or put calls on hold. I have never found a way to make that problem (of mine) go away except for that. DEACT/ACT has no effect - it has to be deleted off the PEN to a different one, and then you can go ahead and put it back on and it's good. Saves me a lot of travelling when it's at a remote site!
@sbcsu - do we have the latest version of OS40T firmware on Tonido? Granted I'm too lazy to look, but I was under the impression they haven't yet released a newer version than the one I have. Thanks
)
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
@sbcsu - do we have the latest version of OS40T firmware on Tonido? Granted I'm too lazy to look, but I was under the impression they haven't yet released a newer version than the one I have. Thanks
)Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
- Thread starter
- #8
System is Hipath 4000 V6
Version is V6 R1.10.7
The system has had only one small update (which I think was several years ago) since installation. The Openstage 40T phones have never been upgraded. The software in the system to push out updates to the phone does not work.
I've never had this problem before, that's why it's weird that it's so frequent now.
donb1: I have that problem you have. It shows up occasionally on my Openscape 40Ts with the logo going away, key labels still there, not able to call out, but can receive calls. I call it a "Zombie" phone state. It drove me nuts trying to make it go away because nothing I tried worked. (Even moving PENs!)
Luckily, I wrote to the others from my Siemens class (I hadn't heard of this site yet) and was able to talk to one that had seen that and had come up with a fix. He told me to hit the Menu Function key several times, or hit the left key (return?) on the 5-way navigator several time. It works like a charm by restoring the phone and only takes a few seconds. As it moves PEN to PEN for me, I'm guessing it's some glitch inside the main software. I was hoping that I was the only poor guy left that had to deal with it as my system has not been upgraded, and I was hoping it had been found and fixed.
Version is V6 R1.10.7
The system has had only one small update (which I think was several years ago) since installation. The Openstage 40T phones have never been upgraded. The software in the system to push out updates to the phone does not work.
I've never had this problem before, that's why it's weird that it's so frequent now.
donb1: I have that problem you have. It shows up occasionally on my Openscape 40Ts with the logo going away, key labels still there, not able to call out, but can receive calls. I call it a "Zombie" phone state. It drove me nuts trying to make it go away because nothing I tried worked. (Even moving PENs!)
Luckily, I wrote to the others from my Siemens class (I hadn't heard of this site yet) and was able to talk to one that had seen that and had come up with a fix. He told me to hit the Menu Function key several times, or hit the left key (return?) on the 5-way navigator several time. It works like a charm by restoring the phone and only takes a few seconds. As it moves PEN to PEN for me, I'm guessing it's some glitch inside the main software. I was hoping that I was the only poor guy left that had to deal with it as my system has not been upgraded, and I was hoping it had been found and fixed.
- Thread starter
- #9
hipath4k: I thought of that, but replacing the 40T with another one has the new phone come up A-OK with full functionality. When physically putting the phone on another port that has a good working phone, the problem follows the phone (not the STN).
Are you using the tool in Assistant (note I have V7) that scans for the TDM phones and shows you which version they are, and allows you to send out updates? On mine it is under Software Management and is TDSM. I *have* pushed out updates with it, but it is slow and painful and you want to do it at a quiet time when the phones are not likely to be in use. Up until now I didn't have a newer version of the software for the past couple of years. It takes its own sweet time scanning for the phones as well, but it seems to do the job. One of these days when i have nothing better to do I will run it again. It sends out the updates to the phones using some clunky protocol that allows it to update over that single pair it is connected to.
I'm going to try that menu key thing or the back button on the next one that pops up with the issue (of course it's usually the main phone in ER that goes first!).
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
I'm going to try that menu key thing or the back button on the next one that pops up with the issue (of course it's usually the main phone in ER that goes first!).
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
- Thread starter
- #11
Yep. It's TSDM here too. It runs for a several minutes in "Regenerate All", then I get "Network error: connection to the server has been lost". It's never done anything else since the system was installed in 2012.
Good luck with the menu button attempt. It sure saved my sanity (at least for that issue).
Good luck with the menu button attempt. It sure saved my sanity (at least for that issue).
V6 R1.10? It's probably the earliest version of V6 released. Why not do something about that? I've not seen the issue you describe but I would make sure the SLMO loadware is current at the very least. No way is it up to date if you are using R1.10. Are you not able to upgrade last version of V6 - R2.17? If not, you will be able to replace the SLMO loadware by itself, file from a V7/V8 would be fine, doesn't need to be from a V6.
- Thread starter
- #13
Thanks Moriendi. I do have one of the first V6s ever installed. I would love to update this system, and am almost to the point where I am allowed to put V7 on it. However, due to where I work, I can not update the software like normal techs.
I had a call for a wonky 40T this afternoon and I had the user try the menu thing and the back arrow thing and they claimed neither worked. Granted it was the user so you know how that goes, but it didn't seem like rocket science. I did the remote PEN flip thing on it right before I left work tonight (after forgetting for 4 hours) and asked them to let me know if that fixed the problem. If not I suppose I can go there and try it myself.
Is it possible to run TDSM on smaller batches? I don't know how many phones you have. I have about 100 T's total, and about 1100 IP phones currently, plus over 400 analog PITA phones.
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
Is it possible to run TDSM on smaller batches? I don't know how many phones you have. I have about 100 T's total, and about 1100 IP phones currently, plus over 400 analog PITA phones.
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
- Thread starter
- #16
Even though I'm in the IT department now and focus on phones, in that case I'm going to blame the firewall )
Figure out what ports it uses to communicate and make sure they are not blocked both on the network firewall and on your PC. It's slow as he!! but I've never had an issue running it so far. Sorry if this is stuff you already know, but because the TDM phones ARE digital, even though they only need 1 pair to connect they can still do data transmission using the phone line, but that transmissing either comes from the OS4K via the SLMO cards or some other way I don't know. I don't know what could be blocking it - from scanning the network for phones at the very least, but I don't know if the application runs locally and the PBX sends out the data, or the whole process runs on the processors in the PBX.
I guess if you haven't already, take a look at the loadware version you have installed on your SLMO boards and see how out of date it might be. You should be able to use the gateway manager in assistant, and youst click the setting to show ALL boards and not just the IP ones. That will allow you to see what loadware you have. Then if you post that someone here can tell you what the current version is for your system and can get the files into Tonido if necessary.
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
)Figure out what ports it uses to communicate and make sure they are not blocked both on the network firewall and on your PC. It's slow as he!! but I've never had an issue running it so far. Sorry if this is stuff you already know, but because the TDM phones ARE digital, even though they only need 1 pair to connect they can still do data transmission using the phone line, but that transmissing either comes from the OS4K via the SLMO cards or some other way I don't know. I don't know what could be blocking it - from scanning the network for phones at the very least, but I don't know if the application runs locally and the PBX sends out the data, or the whole process runs on the processors in the PBX.
I guess if you haven't already, take a look at the loadware version you have installed on your SLMO boards and see how out of date it might be. You should be able to use the gateway manager in assistant, and youst click the setting to show ALL boards and not just the IP ones. That will allow you to see what loadware you have. Then if you post that someone here can tell you what the current version is for your system and can get the files into Tonido if necessary.
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
- Thread starter
- #18
No customer net here. Plugged directly into the switch network between the host and IPDA, no firewall enabled. It's more then likely an initial bug as I am not able to update the system. Hopefully when it is finally up to date, it will work.
Iamnothere
Technical User
TDM Software Download Manager requires AMO config. Back in the early releases of V6, I believe that the TSDM AMO configuration entry was required to be MANUALLY entered. In later versions/releases, I believe that AMO CPTP, XAPPL, and ACMSM configuration exists by default, but AMO SBCSU may require manual chnages to add the "VIRTDTE" entry. Have you verified that the AMO configuration exists?
Use this next section as a guide of what to look for.
When TSDM is used to update TDM phones, the first four phones will typically be updated via the devices' "D" channel @ 16kbps. VERY SLOW. However, after that initial D-channel delivery, subsequent devices are updated via a "B" channel (from device to device) @ 64kbps. This B-channel path is enabled courtesy of AMO SBCSU - where each TDM device (to be updated) must have "VIRTDTE" as an additional setting in the AMO SBCSU --> "DVCFIG" field.
Example: ADD-SBCSU:4266,OPTI,DIR,1-1-9-14,
OPTIP500&VIRTDTE,1&2,
30,15,10,2,1,1,0,1,N,1,10,0,2,
N,0,56,N,,SBDSS1,
Y,0,Y,Y,N,Y,N,,10,
,
,,,,5,,,,N,NORMAL,
N,ENGLISH,0,TRIES,,1,,,
,,,,,,,,
,,,
,;
Also, additional AMO config is required (mixture of BP and A1 configuration).
ADD-CPTP:TYPE=DPCON,NO=93,DPPROC=HU_INTER,IPNO=192.0.2.5;
ADD-CPTP:TYPE=APPL,NO=95,EMSAPPL=TSDM_APP,DPPROC=HU_INTER,
DPAPPL=TSDM_SF,MSGBASED=YES,LOCPORT=102,FARPORT=5095,
LOCTSAP=HUI_S_0095,FARTSAP=HUI_D_0095;
ADD-XAPPL:APPLNO=95,APEPLDP=TSDM_SF,NAME=TSDM APPLICATION,TSKA=N;
CHA-XAPPL:CTYPE=SUBAPPL,APPLNO=95,SUBAPPL=D23,ADDEVT=ALL;
ADD-ACMSM:UNIT=A1,APPLNU=95,TYPE=ACLAPPL,ACLAPPL=TSDM_SF,
PBXAPPL=TSDM_APP,PROCID=HU_INTER,ACCESS=CO,PASSWD=SFTSDM,PACKAGE=N;
Note: this AMO config was correct as of HiPath 4000 V4. In later versions/releases there may be some subtle changes within these AMO commands, but all of these AMOs remain required for the TSDM feature to work as designed.
Be sure to save the AMO changes to the active controller using EXE-UPDAT:BP,ALL; and EXE-UPDAT:A1,ALL;
Good Luck!
Use this next section as a guide of what to look for.
When TSDM is used to update TDM phones, the first four phones will typically be updated via the devices' "D" channel @ 16kbps. VERY SLOW. However, after that initial D-channel delivery, subsequent devices are updated via a "B" channel (from device to device) @ 64kbps. This B-channel path is enabled courtesy of AMO SBCSU - where each TDM device (to be updated) must have "VIRTDTE" as an additional setting in the AMO SBCSU --> "DVCFIG" field.
Example: ADD-SBCSU:4266,OPTI,DIR,1-1-9-14,
OPTIP500&VIRTDTE,1&2,
30,15,10,2,1,1,0,1,N,1,10,0,2,
N,0,56,N,,SBDSS1,
Y,0,Y,Y,N,Y,N,,10,
,
,,,,5,,,,N,NORMAL,
N,ENGLISH,0,TRIES,,1,,,
,,,,,,,,
,,,
,;
Also, additional AMO config is required (mixture of BP and A1 configuration).
ADD-CPTP:TYPE=DPCON,NO=93,DPPROC=HU_INTER,IPNO=192.0.2.5;
ADD-CPTP:TYPE=APPL,NO=95,EMSAPPL=TSDM_APP,DPPROC=HU_INTER,
DPAPPL=TSDM_SF,MSGBASED=YES,LOCPORT=102,FARPORT=5095,
LOCTSAP=HUI_S_0095,FARTSAP=HUI_D_0095;
ADD-XAPPL:APPLNO=95,APEPLDP=TSDM_SF,NAME=TSDM APPLICATION,TSKA=N;
CHA-XAPPL:CTYPE=SUBAPPL,APPLNO=95,SUBAPPL=D23,ADDEVT=ALL;
ADD-ACMSM:UNIT=A1,APPLNU=95,TYPE=ACLAPPL,ACLAPPL=TSDM_SF,
PBXAPPL=TSDM_APP,PROCID=HU_INTER,ACCESS=CO,PASSWD=SFTSDM,PACKAGE=N;
Note: this AMO config was correct as of HiPath 4000 V4. In later versions/releases there may be some subtle changes within these AMO commands, but all of these AMOs remain required for the TSDM feature to work as designed.
Be sure to save the AMO changes to the active controller using EXE-UPDAT:BP,ALL; and EXE-UPDAT:A1,ALL;
Good Luck!
I'm trying to add these options on my TDM phones using CHA-SBCSU and having issues. Do I have to Regen and then delete the phone out and put it back to make the changes?
I know it all used to work in V7R1, but I'm not sure it has worked since I upgraded to V7R2 - I don't know why that config would have gotten stripped from the phones while doing an upgrade....
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
I know it all used to work in V7R1, but I'm not sure it has worked since I upgraded to V7R2 - I don't know why that config would have gotten stripped from the phones while doing an upgrade....
Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
- Status
Similar threads
- Locked
- Question