in Search
Untitled Page

ARCHIVED FORUM -- April 2007 to March 2012
READ ONLY FORUM

This is the first Archived Forum which was active between 17th April 2007 and 1st March February 2012

 

Latest post 07-16-2008 9:41 AM by Claremont1. 11 replies.
Page 1 of 1 (12 items)
Sort Posts: Previous Next
  • 06-09-2007 5:39 PM

    Beocom 6000 'line busy' message

    I wiped my Beocom 6000 over with a cloth and now find that it continually says 'line busy'. I cannot get rid of the message. I have rung the B&O showroom, restarted the phone, reset the PSTN base and re-registered the phone.

    Can anyone help?

    I'm sure I have inadvertantly hit a combination of keys that has caused this as the phone has worked perfectly until now.

    Patrick

  • 06-09-2007 5:54 PM In reply to

    • Jandyt
    • Top 10 Contributor
      Male
    • Joined on 04-01-2007
    • Clitheroe, Lancashire, UK
    • Posts 13,004
    • Founder

    Re: Beocom 6000 'line busy' message

    Hi Patrick, How many handsets do you have, and which base. Pyramid, Old, big black box or new small black box?

    Andy T.

    Poor me, never win owt!

  • 06-09-2007 6:20 PM In reply to

    • cozza
    • Top 500 Contributor
    • Joined on 04-17-2007
    • New Zealand
    • Posts 119
    • Bronze Member

    Re: Beocom 6000 'line busy' message

    Check the base connections to make sure the phone line is connected correctly. If there is no phone line voltage detected by the base you will get this message. Try another non cordless phone to check the phone socket. If good, suspect the beocom phone wire or T adapter is defective.
  • 06-11-2007 9:47 PM In reply to

    Re: Beocom 6000 'line busy' message

    Thank you someone must have dislodged the plug from the telephone socket. All is well now again. You have been the only one who has picked this as the problem.Thank you

    Patrick

  • 06-12-2007 5:50 PM In reply to

    • Dan27
    • Not Ranked
    • Joined on 06-12-2007
    • Posts 2
    • Bronze Member

    Re: Beocom 6000 'line busy' message

    I just bought a Mark II, having had a Mark I working fine for several years. I managed to register the Mark II with my pyramid base, but when I try to use it to dial out or pickup an incoming call, the display shows "Line is Busy" and I hear a series of beeps in the earpiece.

     I've checked the wiring to the base - it works fine with the old Mark I - I can send and receive calls OK using the Mark I on the same base.

     I spoke to the dealer and they say the message means my phone line is at fault, but that doesn't explain why the Mark I works fine.

     
    Can anyone help shed light on this?

     

    Thanks
     

    Filed under:
  • 06-12-2007 6:15 PM In reply to

    • Jandyt
    • Top 10 Contributor
      Male
    • Joined on 04-01-2007
    • Clitheroe, Lancashire, UK
    • Posts 13,004
    • Founder

    Re: Beocom 6000 'line busy' message

    Hi Dan and welcome to the forum.
    As far as I'm aware, your new handset is compatible with the old pyramid base but only if the software in the base is upgraded to SW 2.5
    The new handset will not charge by sitting in the old pyramid as the contact points are different.

    Andy T.

    Poor me, never win owt!

  • 06-12-2007 6:29 PM In reply to

    • cozza
    • Top 500 Contributor
    • Joined on 04-17-2007
    • New Zealand
    • Posts 119
    • Bronze Member

    Re: Beocom 6000 'line busy' message

    It does sound like a software problem with the two generations of handset and base. It can't be a phone line problem if your other handset works correctly - your dealer may not understand this. Take the base in for a software upgrade to version 2.5 and make sure that they back up the phonebook first.
  • 06-13-2007 7:14 AM In reply to

    Re: Beocom 6000 'line busy' message

    Well, I would not rule out the phone line just because the Mark I works and the Mark II does not. The reason for saying this, is that the Mark II has CLI features not found in the Mark I and therefore problems can occur if you have a marginal line voltage.

    The way to quickly check this is to take the BeoCom 6000 base and handset to a friends house and try it. If it works then you have a marginal line issue, if it fails in the same manner, then you have an interesting problem which will require more thought.

    Regards Keith....

  • 06-13-2007 5:55 PM In reply to

    • cozza
    • Top 500 Contributor
    • Joined on 04-17-2007
    • New Zealand
    • Posts 119
    • Bronze Member

    Re: Beocom 6000 'line busy' message

    From what I gather from Dan's post, he has a MKI pyramid base with a MKII handset registered to it. The CLI feature changes apply to the MKII small rectangular PSTN. The PSTN base software version is a known issue with this combination of old and new telephone product, and the dealer should have been aware of this.
  • 06-14-2007 2:50 AM In reply to

    Re: Beocom 6000 'line busy' message

    Cozza,

    Whilst you are 100% correct that his unit needs software verion 2.5

    If the handset has a lower software version (1.50), the display will show:
    Line 1: Software update
    Line 2: needed

    So, that is why I was not focused on the software version, yes it does need to be at 2.5, but in my view there is something else causing the problem. Clearly we should ask Dan to get his dealer to confirm he has the correct software version.

    Regards Keith....

  • 06-16-2007 9:17 AM In reply to

    • Dan27
    • Not Ranked
    • Joined on 06-12-2007
    • Posts 2
    • Bronze Member

    Re: Beocom 6000 'line busy' message

    That sounds about right. I've had the old base for years so I guess it's an old software version. Will speak to the B&O shop. Thanks for your help everyone! Will let you know how I get on!
  • 07-16-2008 9:41 AM In reply to

    Re: Beocom 6000 'line busy' message

    Cozza, just wanted to thank you for your reply which saved me a great deal of time.  I have just had three Beocom 6000 handsets fully upgraded frommark I to Mark II, including keypad sets, and had this error message.  5 minutes checking lines was successful in fixing the problem as the other posts had left me wondering if there would be a complicated software issue.

    Thanks again
Page 1 of 1 (12 items)