Unsolved
This post is more than 5 years old
2 Posts
0
5711
April 30th, 2006 11:00
Why ignoring call waiting signal?
I don't want to miss incoming calls when I'm connected to Internet by dial-up
so I use Central Office "call waiting" service. I don't need v.92 services from my ISP too.
I just want Internet connection to be dropped and phone begins ringing.
Why notebook integrated "Conexant MDC D110 V.92 Modem" is ignoring "call waiting" signal
instead of dropping connection?
Call waiting signal produces "Carrier Loss" effect.
According to Dell documentation for this modem
register S10 is responsible for setting "Automatic disconnect delay" in case of Carrier Loss.
I have tried set S10 on appropriate Device Manager tab to different values: 0,1,5,10,14,16,20,100,140 but all in vain.
I have feeling that this modem just doesn't care S10 setting at all.
I never had any problems with this modem except this case.
Everything is working fine when connecting Acorp-56EMS (my friend gave it to me for my problem troubleshooting)
to the same line with S10=16 in initialization string. Acorp is dropping connection instantly
and phone begins ringing. So I can deduce that I shouldn't disturb support personal
of my ISP and Central Office because notebook's modem is the source of problem.
What should I do to solve the problem?
Configuration:
My notebook is Inspiron 2200 with preinstalled WinXP.
Modem driver is the latest 7.23.01, previous was 7.12.09
but I see that driver ver in my case doesn't matter.
so I use Central Office "call waiting" service. I don't need v.92 services from my ISP too.
I just want Internet connection to be dropped and phone begins ringing.
Why notebook integrated "Conexant MDC D110 V.92 Modem" is ignoring "call waiting" signal
instead of dropping connection?
Call waiting signal produces "Carrier Loss" effect.
According to Dell documentation for this modem
register S10 is responsible for setting "Automatic disconnect delay" in case of Carrier Loss.
I have tried set S10 on appropriate Device Manager tab to different values: 0,1,5,10,14,16,20,100,140 but all in vain.
I have feeling that this modem just doesn't care S10 setting at all.
I never had any problems with this modem except this case.
Everything is working fine when connecting Acorp-56EMS (my friend gave it to me for my problem troubleshooting)
to the same line with S10=16 in initialization string. Acorp is dropping connection instantly
and phone begins ringing. So I can deduce that I shouldn't disturb support personal
of my ISP and Central Office because notebook's modem is the source of problem.
What should I do to solve the problem?
Configuration:
My notebook is Inspiron 2200 with preinstalled WinXP.
Modem driver is the latest 7.23.01, previous was 7.12.09
but I see that driver ver in my case doesn't matter.
0 events found
No Events found!
NickHH77
2 Posts
0
May 13th, 2006 04:00
I had to read Conexant modem manual which is much better than miserable Dell documentation.
The modem really doesn't care S10 setting at all because of default setting +PCW=0 (issue v.92 request modem-on-hold if call waiting signal detected). It must me changed to +PCW=1 (just hang up if call waiting signal detected) in initilization string and after this everything's OK even with S10 default value.
Conclusion: modem is good, support is bad.