Unsolved
This post is more than 5 years old
4 Posts
0
11363
October 7th, 2004 06:00
BCM V.92 56K Modem - Getting Error 676 : Phone is busy
Hello !!
I have a brand new Inspiron notebook. Currently, I'm away in India & have tried couple of times connecting to internet using dial ups. It worked couple of time from some locations. However from other locations, it didn't. I'm continuously getting this error while connecting to internet using my phone line.
Error 676 : - The phone line is busy.
My ISP says this is an settings issue with the notebook.
Appreciate, if you can guide me in getting this solved pls.
Thanks,
No Events found!
jrj23
4 Posts
0
October 7th, 2004 07:00
My notebook details -
Dell - Inspiron 1150
Modem - BCM V.92 56K
OS - Win XP Home Edition
Any thing to do with COM port settings / IRQ settings ???
johnallg
2 Intern
•
7.3K Posts
0
October 7th, 2004 19:00
jrj23
4 Posts
0
October 8th, 2004 08:00
I did everythig that I could but to my dismay, no luck.
Seems that some handshake issues could be there between the modem & ISP.
I did following -
1. Rechecked & disabled Call Waiting on my telephone line
2. Tried with both Tone & Pulse methods.
3. Also added ATS50.4=0S51=31 in [Extra initialization commands] field & checked. (This I searched for BCM Modem from their site.)
4. Tried with HyperTerm -While I got all the expected commands, the final command was BUSY.
5. Disabled the "Use Dialing Rules" checkbox in my dialup connection properties.
6. Finally, I tried reinstalling Modem driver but no lock with any of the above methods.
I think, I have tried with most options. Seems to me that the modem is trying to connect. I can listen to the dialing tones before getting the error. May be that it's not able to open any specific COM port. As the heading above the Error says - "Opening Port..." Any settings need to be changed for COM ports pls ?
Appreciate if you can give me detailed explaination rather than pointing me to -Google Error 676
EFa
1 Message
0
October 23rd, 2004 21:00
the solution at my location was the following modem command (extra settings)
ATx0
This disables busy detection.
The cause for the error might be a special calling-feature the modem can't deal with.
Message Edited by EFa on 10-23-2004 05:47 PM
jrj23
4 Posts
0
October 30th, 2004 09:00
Thanks EFa, this seems to be working.
I have got this command ATS22=118 that helped in working. This too disables the busy detection/call waiting.
Thanks for the answer.