By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,084 Members | 1,207 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,084 IT Pros & Developers. It's quick & easy.

VoIP Dialer

P: n/a
Appreciate a lead of locating some code to dial phone numbers using
VoIP rather than my modem. Have switched my service from Verizon to
Comcast VoIP and now the utility I wrote to dial my personal phone
book using MSCommLib and AxMSCommLib procedures (Term code) of course
no longer works. Found nothing with my Google search but not exactly
sure of necessary key words. I am getting to old to enter 10 digits
without error<g>

Ed
Aug 20 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
would would it no longer work? Comcast VoIP just uses standard phone lines
to get back to the residential gateway device... it should work exactly like
a normal phone does
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uy****************@TK2MSFTNGP04.phx.gbl...
Appreciate a lead of locating some code to dial phone numbers using VoIP
rather than my modem. Have switched my service from Verizon to Comcast
VoIP and now the utility I wrote to dial my personal phone book using
MSCommLib and AxMSCommLib procedures (Term code) of course no longer
works. Found nothing with my Google search but not exactly sure of
necessary key words. I am getting to old to enter 10 digits without
error<g>

Ed

Aug 20 '06 #2

P: n/a
Neither the small dialer program I wrote or a shareware Fax program
(MightyFax) can access the modem. My program fails on the line
AxMsComm3..portopen = true and reports Err=8012 for which I have not
found an explaination.

Ed

"Smokey Grindel" <no****@nospam.comwrote in message
news:u3**************@TK2MSFTNGP02.phx.gbl...
would would it no longer work? Comcast VoIP just uses standard phone
lines to get back to the residential gateway device... it should
work exactly like a normal phone does
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uy****************@TK2MSFTNGP04.phx.gbl...
>Appreciate a lead of locating some code to dial phone numbers using
VoIP rather than my modem. Have switched my service from Verizon
to Comcast VoIP and now the utility I wrote to dial my personal
phone book using MSCommLib and AxMSCommLib procedures (Term code)
of course no longer works. Found nothing with my Google search but
not exactly sure of necessary key words. I am getting to old to
enter 10 digits without error<g>

Ed


Aug 21 '06 #3

P: n/a
Is the modem connected through a standard phone line to your VoIP gateway?
If so there should be no difference at all... unless you had a computer
based VoIP (software solution going through the computer only) which would
be the only reason this would not work, but if its just a standard phone
connection to a VoIP gateway, then sould work just like it did on a standard
copper land line
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uu**************@TK2MSFTNGP06.phx.gbl...
Neither the small dialer program I wrote or a shareware Fax program
(MightyFax) can access the modem. My program fails on the line
AxMsComm3..portopen = true and reports Err=8012 for which I have not found
an explaination.

Ed

"Smokey Grindel" <no****@nospam.comwrote in message
news:u3**************@TK2MSFTNGP02.phx.gbl...
>would would it no longer work? Comcast VoIP just uses standard phone
lines to get back to the residential gateway device... it should work
exactly like a normal phone does
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uy****************@TK2MSFTNGP04.phx.gbl...
>>Appreciate a lead of locating some code to dial phone numbers using VoIP
rather than my modem. Have switched my service from Verizon to Comcast
VoIP and now the utility I wrote to dial my personal phone book using
MSCommLib and AxMSCommLib procedures (Term code) of course no longer
works. Found nothing with my Google search but not exactly sure of
necessary key words. I am getting to old to enter 10 digits without
error<g>

Ed



Aug 21 '06 #4

P: n/a
Smokey,

My telephones, along with my modem, connect directly to the Comcast
VoIP box (actaully they go out to the NIB and simply return to the
VoIP box where that line was severed from the Verizon phone line. So
my modem is talking to the VoIP box which in turn sends its
information out through the cable and somewhere down the road at a
Comcast site it "miraculously" feeds into the telephone system so I
can talk to the rest of the world. How is that for a non-technical
description.

If I work my way to the Properties tab for the Modem it tests out
fine - I think, here is the log:
08-21-2006 07:57:50.625 - TSP(0000): Making Call
08-21-2006 07:57:50.640 - Passthrough On
08-21-2006 07:57:50.656 - TSP Completing Async Operation(0x00010011)
Status 0x00000000
08-21-2006 07:57:50.656 - TSP(0000): LINEEVENT:
LINECALLSTATE_CONNECTED
08-21-2006 07:57:55.687 - TSP(0000): Dropping Call
08-21-2006 07:57:55.687 - Passthrough Off
08-21-2006 07:57:55.687 - 115200,8,N,1, ctsfl=1, rtsctl=2
08-21-2006 07:57:55.687 - Initializing modem.
08-21-2006 07:57:55.703 - Send: AT<cr>
08-21-2006 07:57:55.859 - Recv: <cr><lf>OK<cr><lf>
08-21-2006 07:57:55.859 - Interpreted response: OK
08-21-2006 07:57:55.875 - Send: AT&F E0 Q0 X4 S0=0 &D2 &C1 &S0 V1
W4<cr>
08-21-2006 07:57:56.093 - Recv: <cr><lf>OK<cr><lf>
08-21-2006 07:57:56.093 - Interpreted response: OK
08-21-2006 07:57:56.109 - Send:
ATS7=60S30=0L3M1+ES=3,0,2;%C1+DS=3,0;+DS44=3,0;&K3 X4<cr>
08-21-2006 07:57:56.343 - Recv: <cr><lf>OK<cr><lf>
08-21-2006 07:57:56.343 - Interpreted response: OK
08-21-2006 07:57:56.343 - Waiting for a call.
08-21-2006 07:57:56.359 - Send: at+vcid=1<cr>
08-21-2006 07:57:56.531 - Recv: <cr><lf>OK<cr><lf>
08-21-2006 07:57:56.531 - Interpreted response: OK
08-21-2006 07:57:56.546 - Send: ATS0=0<cr>
08-21-2006 07:57:56.718 - Recv: <cr><lf>OK<cr><lf>
08-21-2006 07:57:56.718 - Interpreted response: OK
08-21-2006 07:57:56.718 - TSP(0000): LINEEVENT:
LINECALLSTATE_DISCONNECTED(0x1)
08-21-2006 07:57:56.718 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
08-21-2006 07:57:56.718 - TSP Completing Async Operation(0x000103bc)
Status 0x00000000
08-21-2006 07:57:56.796 - TSP(0000): Closing Call

Ed

"Smokey Grindel" <no****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
Is the modem connected through a standard phone line to your VoIP
gateway? If so there should be no difference at all... unless you
had a computer based VoIP (software solution going through the
computer only) which would be the only reason this would not work,
but if its just a standard phone connection to a VoIP gateway, then
sould work just like it did on a standard copper land line
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uu**************@TK2MSFTNGP06.phx.gbl...
>Neither the small dialer program I wrote or a shareware Fax program
(MightyFax) can access the modem. My program fails on the line
AxMsComm3..portopen = true and reports Err=8012 for which I have
not found an explaination.

Ed

"Smokey Grindel" <no****@nospam.comwrote in message
news:u3**************@TK2MSFTNGP02.phx.gbl...
>>would would it no longer work? Comcast VoIP just uses standard
phone lines to get back to the residential gateway device... it
should work exactly like a normal phone does
"Ed Bitzer" <ed******@yahoo.comwrote in message
news:uy****************@TK2MSFTNGP04.phx.gbl.. .
Appreciate a lead of locating some code to dial phone numbers
using VoIP rather than my modem. Have switched my service from
Verizon to Comcast VoIP and now the utility I wrote to dial my
personal phone book using MSCommLib and AxMSCommLib procedures
(Term code) of course no longer works. Found nothing with my
Google search but not exactly sure of necessary key words. I am
getting to old to enter 10 digits without error<g>

Ed

Aug 21 '06 #5

P: n/a
Hi,

Error 8012 is "Application-defined or object-defined error." This error
(generally) comes from the driver for the device, and is relayed up by
MSComm32.ocx. What is the physical device? Is is a USB adapter? Can you
open it successfully using HyperTerminal?

BTW, if you are using VS 2003, you might prefer to download
DesktopSerialIO.dll from my homepage. This is simpler to use than MSComm,
though its use won't solve this particular problem, perhaps. For VS 2005,
you can use the built-in System.IO.Ports namespace.

Dick

--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See www.hardandsoftware.net for details and contact information.
Aug 21 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.