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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hicom 150E + PhoneMail

Status
Not open for further replies.

keliew

IS-IT--Management
Feb 8, 2010
5
BE
Am having issues with connecting to PhoneMail using HiPath 3000 Manager using RS232 on COM2. Am very sure that COM2 is working fine.

The error message that is displayed is "Error: Communication system is offline. Check the cable connection."

If anyone can give me some insights as to what to look out for, please do! Am all out of ideas as to what is going on. Siemens technical team is unable to help me out due to the age of the system.

Is there a switch that I need to enable to have PhoneMail's RS232 work?
 
Sorry for a rep-post, but if anyone have a copy of "Hicom 150 E Office R 2 & 3 Installation Programming" that can be sent to me, that'd be great! Thanks in advance!
 
I don't want to make myself look stupid here, but.... :eek:)

I have 2 different PhoneMail systems - I have a freestanding node that supports my whole "network" of users, and I also have a 150E that I inherited when I bought the building that has a Hicom Office Phonemail on it. I've been doing this just over 13 years now and I have never accessed either of these PhoneMail systems without either dialing in to their system modems or direct connecting to their RS232 ports, and I've never used anything but ProComm to communicate with them (ANSI-BBS protocol, 9600 8N1). I've never used Assistant E or Manager E, etc - I wasn't even aware they had any provisions to access PhoneMail.

I would suggest using ProComm to access PhoneMail and try that - or possibly hyper-terminal from Windows, but I don't know how the screen is going to look.

I have the Siemens documentation on upgrading from 150E V2 to 150E V3 (also known as 150H V1.0) if that is what you're asking for. I can tell you that it requires a processor board upgrade because V3 needs more memory, and it also requires that you download your 2.0 database and use a conversion process to convert it into a 3.0 database. Then you have to default the system and upload your 3.0 database. The system initialization process is also different between 3.0 and the two previous versions. Basically after you default the system under 3.0 you have to enter 31994 four times, then enter a code to change the phone's language to English, then scroll to INIT and choose your country to get he right language... It's not hard to do - just a tad scary and a little time consuming...

 
Ask your installer/BP

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
@donb01 Using HyperTerminal was the first thing I've tried, but yielded no result - complete blank in the terminal even after hitting the carriage return multiple times, etc. I've also played around with the baud rate and other settings, no go. I'll see if I can give ProComm a try...

@Bas1234 I have asked our installer (Siemens) and they've stated they do not support it anymore. They have directed me to another agent that could help, but the agent insisted that we buy a new PBX system. And yes, I've also asked many others.
 
I think you need to set the port to "voicemial digit 5/6" on the extensions.

Aslo are you US based? don't think it's supported in other locales.

Also (But i think you've seen it) there is an on/off switch on the HOPE board.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
One other thought because it's been so long since I made my serial connection to PhoneMail.... You might need a null modem adapter between your computer and PhoneMail....
 
@Bas1234 am based in Europe.

@donb01 good thinking! I missed that one. A quick search shows that I need a null cable (crossover). A quick test also shows that I have a serial cable instead.

Now I have to hunt for a null cable. :) Will check back later if there's any issue.

Thanks for your help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top