atcomsystems.ca/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems sx-50 call forwarding problem

I have recently acquired a motel and it seems the phone system has been somewhat neglected. I have had a tech come in and sort out many of the problems, but several more have cropped up since his visit.

In particular, when transferring a call from the console to a room, the call will be transfered back to the console after a certain number of rings.
When this occurs, the display on the console blinks the message "recall".

I would prefer that the system does not transfer the call back to the console at all.

I am hoping that this small problem could be resolved by a change made via the console. And if I must connect directly to the sx-50, how is that done? I am currently connected to the sx-50 via a serial port on this computer. Although I am unable to receive any output from the PBX when running HyperTerminal. So I am not sure whether the connection is active or if I have over looked something.

Thanks for any assistance.

Ok, Kim (?), First have your tech ensure that register 2, Bit C is 0 and Bit F is 1. FOR ALL TRUNKS. It sounds as if the caller hangs up and the system does not recognize the fact. It may not be getting the information from the telephone company, but that is something that you tech will have to determine. Also 'recall on no answer' may be set a little 'quick'. Command 100, Register 11, Bit D chnages the time before recall. Multiples of 10 seconds from 10 to 70 seconds. All this is assuming that your software is MS55.
After all that, unless you are familiar with SX50 programming, better stay away from it. And you cannot program the system through the serial port. You must program through either a console or a SuperSet. You can save a copy of the program to disc and reload it if the system loses it for some reason. I've never been successful at it, even in the shop under controlled conditions, but the book says you can!
What you CAN get from the serial port, if all the programming is done correctly, is call records for each extension, as they happen, all it shows is the extension number, the line it used, the number that was dialed and how long the call lasted. It does NOT price the call or have any sort of toll cutoff when they've spent more than some amount of cash deposit. (There are add-on devices that can do that, but those are for a different, new post.) You can also get wake-up call set confirmation, attempt(s) with result(s), and various alarms. All of this depends on the programming.

Most important, if the memory battery has not been replaced in the last 2 years, DO IT! If it is MS53, MS54, 0r MS55 software, it uses a CR2032 "coin" battery, available a LOT of places. Even Wal-Mart carries it. A lot of things use it. This is not a UPS or battery support system battery, this is inside the SX50. If it's more than 3-4 years old and you lose power for several hours,or less depending on the condition of the memory battery, you'll lose the program partially or completely. It won't be pretty and you'll have to have the system defaulted and reprogrammed. Most phone systems of any brand have this problem, so don't 'cuss' your Mitel. John C. (Not Garand)

replace battery with power on. if system is turned
off to replace it, all programing will be lost

Lightninghorse, thanks a lot for the extremely informative post. And TDS, thanks for the extra tip.

Lightninghorse, your suggestion to resolve the ten second recall time, seems like the correct solution, and you have provided enough information to allow me to look into it further.

I will definitely look into getting a new battery for the unit, since after servicing the unit, the tech left it off and unplugged for several hours.

Lightninghorse, if I understood your post correctly, I should be able to receive SMDR data via serial, assuming the PBX is programmed correctly. The serial port used to be connected to a Xiox Summa Pro (and worked). However, recently lightning struck the PBX, and seemingly rendered the Xiox unresponsive.
I did some reading on these forums and had the impression that I should be able to receive basic call information via serial at the HyperTerminal prompt (with the settings 9600,8,N,1). But I have been unable to receive anything. So I assumed the serial port on the PBX was also damaged by lightning.
However, after connecting a rs232 mini tester to only the PBX, I observed low on RD. Then connecting the other side of the tester to the computer brings up two more lights, and when connecting with HyperTerminal, the RTS and DTR become high. Finally, after placing a phone call, the call being picked up, and me hanging up the call, a second or two later the RD light will flicker between high and low for around a second. I don't know what this means, but it would seem there is some life on the cable, but maybe not enough? Should the TD light be flickering instead?
Or am I overlooking something?

Again, thank you for taking the time to help me.

Kim (?), RD is ok, you might want to try a Null Modem cable/Connector. And make sure you are connecting to a serial port, not a parallel port, on the computer. (Seen It!) And keep in mind that the SX50 can send/receive at baud rates from 110(!) to 9600, and could be set at any of those speeds. Probably 300, 1200, or 9600. Even if baud rate and speed are all wrong, you should get some sort of garbage, if the computer is connected correctly and Hyperterm is monitoring the correct serial port.

And a tip of the hat to TDS! I cannot believe I left out that little tidbit! John C. (Not Garand)

FOR TESTING PURPOSES ONLY,,,,,,,,
Set your comm port (hyperterminal or procomm, etc) to 9600 8N1, and connect to the serial port.
Toggle switch #4 (top) forward, then back.
If you see a prompt which asks for a 'debug password', the serial port is physically OK.
If you get no output, the port is bad.
Once you've determined wheter or not the port is OK, change the settings back to match the programing and continue your troubleshooting via the software settings.

Problem Solved.

It seems the combination of the last two posts led me to a solution. Thank you Lightninghorse and Fifty5footer.

If you guys are interested, here is what I did:

I toggled switch #4, received a "debug password" string.
From here, I simply set the baud rate to 300, made a call, and was greeted with output in HyperTerminal.

Thank you, to everyone who contributed.

Thanks for checking back. You must have been brought up right! A lot of folks don't bother until they want help again.
And please excuse my manners for not giving you a BIG WELCOME. John C. (Not Garand)