Topic: officeServ - CO Hung up

[kenzii]

I'm trying to help out a friend who's company who owns their phone system has gone bust and now they are without phone system support. Mainly I deal with Servers/Networking so go easy on me :)

They've just had a refurb done and I installed the phone system back in.. (A telecoms guy moved the termination box for the lines in question)... Now, they are having a problem when receiving phone calls on the first line and get a error message 702: CO hung Up... If multiple calls come in at the same time. others will work but the first call will always get that message.

from the console I've worked out that the trunk likes are 701, 702(primary line for incoming calls and 703).

Its absolutely fine for making external calls. Obviously before the refurb they did not have this issue and my knowledge of VOIP systems is limited. Alternatively, within OfficeServ is there a way to make 701 the primary line? So then at least until it is resolved the first phone call will not be hung up?

Any ideas what could be causing the phones to report that message and disconnect the call?

Cheers

[CMDL_GUY]

Welcome to myphonetechs.com   

From what I can make of your post, there is no problem with outbound (dialing out) calls.    The problem is with inbound calls.

Am I right so far?

Hearing an error message "702" is from the service provider and has nothing to do with Samsung trunk/line numbering, this is purely coincidental.

You need to have the service provider look at the line or have the telcom guy review what he did.

[Marc Haycook]

Hearing an error message "702" is from the service provider and has nothing to do with Samsung trunk/line numbering, this is purely coincidental.

Larry... wouln't 702 be the second trunk in the system, so he's seeing on the display 702 CO Hung Up. It's been a while since I've been in a Samsung.

[bmreen]

It sounds to me that one of the lines is double punched on a block somewhere or something maybe wrong with the 702 trunk trip ringing or something. I've seen bad CO surge protection do things like this also.

[CMDL_GUY]

Hearing an error message "702" is from the service provider and has nothing to do with Samsung trunk/line numbering, this is purely coincidental.

Larry... wouln't 702 be the second trunk in the system, so he's seeing on the display 702 CO Hung Up. It's been a while since I've been in a Samsung.

That may be........I read it to be an audible message, heard when you call in, a code at the end would tell you what C.O. was sending the message.

[kenzii]

Thanks for the replies.

Sorry should of stated that the CO Hung Up message is a visual message that appears on the phone that answers the call. When the phone is then put down it will ring the phones again and when you answer it a second time the line is dead with the same message again.

The telecoms engineer is coming in to review the work today but from what you guys are saying it doesn't sound like a PABX issue which is a relief for me. (We don't even have technician passwords to the phones) so troubleshooting would have been a nightmare.

Thanks for your help. Hopefully they will be able to resolve!

[CMDL_GUY]

Glad to see you posted back and cleared up where I was confused.  It does sound like a simple wiring error at this point.  Please post back when this is resolved or if you need further help.

[kenzii]

Telecom's company came in this morning and have said that there is no issues on that line (they tested via a standard phone and could recieve and make calls).
So that would point at the issue being the OfficeServ Unit.

Would there be anything in particular that you would check? The Admin console we get via the 'server machine' doesn't really offer to much information or things to configure.
Thanks

[CMDL_GUY]

You can move the line to a spare line port and see if you have a bad port.

OfficeServ  is a name for many Samsung key systems, we need to know which one you have in order to tell where the other lines will connect.

Is it one of the following;

OS100
OS7100
OS7200
Once you determine that, we need to know where the TRK board is located within the system.

It does sound like you may have a double punch with the wiring as bmreen suggested in his post above.  You will need to look carefully at the cross connect wiring. 

Can you post a photo?

[pvj]

He has a 7030 as he also started a thread on the other forum.I already suggested to him that he try and swap lines 1 & 2 to see if the problem follows the line or stays on the trunk port.Never heard back

[CMDL_GUY]

Thanks for the update Paul.