Thread: [sendpage-devel] Sendpage Dialing Problems
Brought to you by:
keescook
Menu
▾
▴
sendpage-devel
|
From: Walt W. <wd...@gm...> - 2009-09-15 14:01:37
|
Hello there all.
1) I have RHEL5 64 bit running on a Dell server. The server has an internal
PCIE 56k faxmodem. I also tried an external USR Sportster modem.
2) I am able to cleanly install the sendpage package with the required Perl
modules. The daemon starts up correctly and accepts pages correctly from the
command line and my Zenoss monitoring server.
3) Everything works fine until sendpage proceeds to dial. I get the
following error message:
sendpage[30748]: Failed to dial modem
sendpage[30748]: proto startup failed (Could not dial out)
4) I am able to dial my office phone through either modem with minicom. I
know both modems work. I've tried uninstalling and reinstalling. I've even
read the Perl code hoping I might find something to indicate a had a system
issue. The modemtest perl script appears to be successful when running. I've
included an abbreviated config below.
[modem:sportster]
dev=/dev/modem
baud=2400
areacode=555
dialwait=20
[pc:propage]
phonenum=1234567
#stricttap=true
[recip:pager_wdw]
dest = @propage
I would greatly appreciate any help. Thanks in advance!
WDW
|
|
From: Peter S. <Pet...@UT...> - 2009-09-15 14:38:45
|
Have you tried adding an "init=" entry to your "[modem:]" section? Perhaps just put in a reset, like "init=ATZ". Mine use the following, but really I don't think it is *much* more than a reset. "init=ATZwwww&Q6S11=40S7=20M0" Peter >>> Walt Wyndroski <wd...@gm...> 2009-09-15 8:30 AM/08:30:18 >>> Hello there all. 1) I have RHEL5 64 bit running on a Dell server. The server has an internal PCIE 56k faxmodem. I also tried an external USR Sportster modem. <snip> WDW |
|
From: Walt W. <wd...@gm...> - 2009-09-15 15:59:42
|
I actually had already tried that. Knowing that it defaulted to init=ATZ, I mannually inserted that anyway with the same results. I also copied the init string from minicom with the same results. Walt On Tue, Sep 15, 2009 at 10:38 AM, Peter Smith < Pet...@ut...> wrote: > Have you tried adding an "init=" entry to your "[modem:]" section? Perhaps > just put in a reset, like "init=ATZ". Mine use the following, but really I > don't think it is *much* more than a reset. "init=ATZwwww&Q6S11=40S7=20M0" > > Peter > > >>> WDW >>> > Hello there all. > > 1) I have RHEL5 64 bit running on a Dell server. The server has an internal > PCIE 56k faxmodem. I also tried an external USR Sportster modem. > <snip> > > WDW > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > sendpage-devel mailing list > sen...@li... > https://lists.sourceforge.net/lists/listinfo/sendpage-devel > |
|
From: Walt W. <wd...@gm...> - 2009-09-16 03:46:28
|
I tried the init string below and got the same results. However I get an
'OK' if I issue it from minicom. I now have all the debug logging enabled.
Here is a snippet of the start up:
Tue Sep 15 23:24:05 2009 [32767 info]: baud requested: '9600' baud set:
'9600'
Tue Sep 15 23:24:05 2009 [32767 info]: parity requested: 'even' parity set:
'even'
Tue Sep 15 23:24:05 2009 [32767 info]: databits requested: '7' databits set:
'7'
Tue Sep 15 23:24:05 2009 [32767 info]: stopbits requested: '1' stopbits set:
'1'
Tue Sep 15 23:24:05 2009 [32767 info]: flow requested: 'rts' flow set: 'rts'
Tue Sep 15 23:24:05 2009 [32767 info]: reseting DTR ...
Tue Sep 15 23:24:05 2009 [32767 info]: forcing RTS ...
Tue Sep 15 23:24:05 2009 [32767 info]: to send: ATZ{0x0D}
Tue Sep 15 23:24:05 2009 [32767 info]: want: OK
Tue Sep 15 23:24:05 2009 [32767 info]: kicker: ATZ{0x0D}
Tue Sep 15 23:24:05 2009 [32767 info]: timeout: 4 retries: 2
Tue Sep 15 23:24:05 2009 [32767 info]: have:
Tue Sep 15 23:24:05 2009 [32767 info]: wrote: 4 ATZ{0x0D}
Tue Sep 15 23:24:05 2009 [32767 info]: 1 seen: A
Tue Sep 15 23:24:05 2009 [32767 info]: have: A
Tue Sep 15 23:24:05 2009 [32767 info]: (timeout: 0/4, retries: 0/2)
Tue Sep 15 23:24:06 2009 [32767 info]: 9 seen:
TZ{0x0D}{0x0D}{0x0A}OK{0x0D}{0x0A}
Tue Sep 15 23:24:06 2009 [32767 info]: have:
ATZ{0x0D}{0x0D}{0x0A}OK{0x0D}{0x0A}
Tue Sep 15 23:24:06 2009 [32767 info]: chat success: OK
Tue Sep 15 23:24:06 2009 [32767 info]: Modem Object 'sportster' being
destroyed
Tue Sep 15 23:24:06 2009 [32767 info]: unlocking Modem 'sportster'
Tue Sep 15 23:24:06 2009 [32767 info]: Modem Object 'sportster' destroyed
Tue Sep 15 23:24:06 2009 [32767 info]: found functioning modem: sportster
Here is a snippet after I issue snpp from the command line: (I replaced the
10 digit number with @'s)
Sep 15 23:41:08 nms sendpage[1586]: QueueRun requested for 'propage' ...
Sep 15 23:41:08 nms sendpage[1586]: Locking with '/var/lock/LCK..modem' ...
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Baud': '9600'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Parity':
'even'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting
'StrictParity': '0'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Data': '7'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Stop': '1'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Flow': 'rts'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Init':
'ATZwwww&Q6S11=40S7=20M0'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'InitOK': 'OK'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'InitWait':
'4'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'InitRetry':
'2'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Error':
'ERROR'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'Dial': 'ATDT'
' p 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'DialOK':
'CONNECT.*
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'DialWait':
'60'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'DialRetry':
'3'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'NoCarrier':
'ERROR|NO CARRIER|BUSY|NO DIAL|VOICE'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting
'CarrierDetect': 'on'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting
'DTRToggleTime': '0.5'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'AreaCode':
'-'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'LongDist':
'1'
Sep 15 23:41:08 nms sendpage[1586]: Modem 'sportster' setting 'DialOut': ''
Sep 15 23:41:08 nms sendpage[1586]: baud requested: '9600' baud set: '9600'
Sep 15 23:41:08 nms sendpage[1586]: parity requested: 'even' parity set:
'even'
Sep 15 23:41:08 nms sendpage[1586]: databits requested: '7' databits set:
'7'
Sep 15 23:41:08 nms sendpage[1586]: stopbits requested: '1' stopbits set:
'1'
Sep 15 23:41:08 nms sendpage[1586]: flow requested: 'rts' flow set: 'rts'
Sep 15 23:41:08 nms sendpage[1586]: reseting DTR ...
Sep 15 23:41:09 nms sendpage[1586]: forcing RTS ...
Sep 15 23:41:09 nms sendpage[1586]: to send:
ATZwwww&Q6S11=40S7=20M0{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: want: OK
Sep 15 23:41:09 nms sendpage[1586]: kicker:
ATZwwww&Q6S11=40S7=20M0{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: timeout: 4 retries: 2
Sep 15 23:41:09 nms sendpage[1586]: have:
Sep 15 23:41:09 nms sendpage[1586]: wrote: 24 ATZwwww&Q6S11=40S7=20M0{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: 17 seen: ATZwwww&Q6S11=40S
Sep 15 23:41:09 nms sendpage[1586]: have: ATZwwww&Q6S11=40S
Sep 15 23:41:09 nms sendpage[1586]: (timeout: 0/4, retries: 0/2)
Sep 15 23:41:09 nms sendpage[1585]: SNPP connection (pid 1588) finished
Sep 15 23:41:09 nms sendpage[1586]: 13 seen:
7=20M0{0x0D}{0x0D}{0x0A}OK{0x0D}{0x0A}
Sep 15 23:41:09 nms sendpage[1586]: have:
ATZwwww&Q6S11=40S7=20M0{0x0D}{0x0D}{0x0A}OK{0x0D}{0x0A}
Sep 15 23:41:09 nms sendpage[1586]: chat success: OK
Sep 15 23:41:09 nms sendpage[1586]: Calling with Num: '@@@@@@@@@@'
Sep 15 23:41:09 nms sendpage[1586]: to send: ATDT@@@@@@@@@@{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: want: CONNECT.*{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: kicker:
Sep 15 23:41:09 nms sendpage[1586]: timeout: 60 retries: 1
Sep 15 23:41:09 nms sendpage[1586]: have: {0x0D}{0x0A}
Sep 15 23:41:09 nms sendpage[1586]: wrote: 15 ATDT@@@@@@@@@@{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: 15 seen: ATDT@@@@@@@@@@{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: have: {0x0D}{0x0A}ATDT@@@@@@@@@@{0x0D}
Sep 15 23:41:09 nms sendpage[1586]: (timeout: 0/60, retries: 0/1)
Sep 15 23:41:10 nms sendpage[1586]: (timeout: 1/60, retries: 0/1)
Sep 15 23:41:11 nms sendpage[1586]: (timeout: 2/60, retries: 0/1)
Sep 15 23:41:12 nms sendpage[1586]: (timeout: 3/60, retries: 0/1)
Sep 15 23:41:13 nms sendpage[1586]: (timeout: 4/60, retries: 0/1)
Sep 15 23:41:14 nms sendpage[1586]: (timeout: 5/60, retries: 0/1)
Sep 15 23:41:15 nms sendpage[1586]: (timeout: 6/60, retries: 0/1)
Sep 15 23:41:16 nms sendpage[1586]: (timeout: 7/60, retries: 0/1)
Sep 15 23:41:17 nms sendpage[1586]: (timeout: 8/60, retries: 0/1)
Sep 15 23:41:18 nms sendpage[1586]: (timeout: 9/60, retries: 0/1)
Sep 15 23:41:19 nms sendpage[1586]: (timeout: 10/60, retries: 0/1)
Sep 15 23:41:20 nms sendpage[1586]: (timeout: 11/60, retries: 0/1)
Sep 15 23:41:21 nms sendpage[1586]: (timeout: 12/60, retries: 0/1)
Sep 15 23:41:22 nms sendpage[1586]: (timeout: 13/60, retries: 0/1)
Sep 15 23:41:23 nms sendpage[1586]: (timeout: 14/60, retries: 0/1)
Sep 15 23:41:24 nms sendpage[1586]: (timeout: 15/60, retries: 0/1)
Thanks again for your help.
Walt
On Tue, Sep 15, 2009 at 11:59 AM, Walt Wyndroski <WDW> wrote:
> I actually had already tried that. Knowing that it defaulted to init=ATZ, I
> mannually inserted that anyway with the same results. I also copied the init
> string from minicom with the same results.
>
> Walt
>
> On Tue, Sep 15, 2009 at 10:38 AM, Peter Smith <
> Pet...@ut...> wrote:
>
>> Have you tried adding an "init=" entry to your "[modem:]" section?
>> Perhaps just put in a reset, like "init=ATZ". Mine use the following, but
>> really I don't think it is *much* more than a reset.
>> "init=ATZwwww&Q6S11=40S7=20M0"
>>
>> Peter
>>
>> >>> WDW >>>
>> Hello there all.
>>
>> 1) I have RHEL5 64 bit running on a Dell server. The server has an
>> internal
>> PCIE 56k faxmodem. I also tried an external USR Sportster modem.
>> <snip>
>>
>> WDW
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> sendpage-devel mailing list
>> sen...@li...
>> https://lists.sourceforge.net/lists/listinfo/sendpage-devel
>>
>
>
|
|
From: Walt W. <wd...@gm...> - 2009-09-16 10:38:48
|
Hey Peter, it takes a man to admit when the problem was on his side and that's what I'm doing. Though I had a correct paging number, the required paging center number for my service was incorrect. :( /cry. Next I'll have to check my companies pager records more closely. However, it did give me a chance a read through some of the Perl code and learn a lot about serial I/O with Perl. :) There's an upside to everything if you look. Anyway, I want to give a big thanks to the developers for such robust and great opensource code! Walt On Tue, Sep 15, 2009 at 9:30 AM, Walt Wyndroski <WDW> wrote: > Hello there all. > > 1) I have RHEL5 64 bit running on a Dell server. The server has an internal > PCIE 56k faxmodem. I also tried an external USR Sportster modem. > > 2) I am able to cleanly install the sendpage package with the required Perl > modules. The daemon starts up correctly and accepts pages correctly from the > command line and my Zenoss monitoring server. > > 3) Everything works fine until sendpage proceeds to dial. I get the > following error message: > sendpage[30748]: Failed to dial modem > sendpage[30748]: proto startup failed (Could not dial out) > > 4) I am able to dial my office phone through either modem with minicom. I > know both modems work. I've tried uninstalling and reinstalling. I've even > read the Perl code hoping I might find something to indicate a had a system > issue. The modemtest perl script appears to be successful when running. I've > included an abbreviated config below. > > [modem:sportster] > dev=/dev/modem > baud=2400 > areacode=555 > dialwait=20 > [pc:propage] > phonenum=1234567 > #stricttap=true > [recip:pager_wdw] > dest = @propage > I would greatly appreciate any help. Thanks in advance! > > WDW > |
|
From: Walt W. <wd...@gm...> - 2009-09-16 18:31:18
|
Is there any method that could be added in the debug logs that would indicate if the phone line were not answered by another computer? i.e Someone puts in a direct pager number and an auto-attendant answers. That way it would be much easier to notice if the paging center number is not used. Thanks, Walt On Wed, Sep 16, 2009 at 6:38 AM, Walt Wyndroski <WDW> wrote: > Hey Peter, it takes a man to admit when the problem was on his side and > that's what I'm doing. Though I had a correct paging number, the required > paging center number for my service was incorrect. :( /cry. Next I'll have > to check my companies pager records more closely. > > However, it did give me a chance a read through some of the Perl code and > learn a lot about serial I/O with Perl. :) There's an upside to everything > if you look. > > Anyway, I want to give a big thanks to the developers for such robust and > great opensource code! > > Walt > > > On Tue, Sep 15, 2009 at 9:30 AM, Walt Wyndroski <WDW> wrote: > >> Hello there all. >> >> 1) I have RHEL5 64 bit running on a Dell server. The server has an >> internal PCIE 56k faxmodem. I also tried an external USR Sportster modem. >> >> 2) I am able to cleanly install the sendpage package with the required >> Perl modules. The daemon starts up correctly and accepts pages correctly >> from the command line and my Zenoss monitoring server. >> >> 3) Everything works fine until sendpage proceeds to dial. I get the >> following error message: >> sendpage[30748]: Failed to dial modem >> sendpage[30748]: proto startup failed (Could not dial out) >> >> 4) I am able to dial my office phone through either modem with minicom. I >> know both modems work. I've tried uninstalling and reinstalling. I've even >> read the Perl code hoping I might find something to indicate a had a system >> issue. The modemtest perl script appears to be successful when running. I've >> included an abbreviated config below. >> >> [modem:sportster] >> dev=/dev/modem >> baud=2400 >> areacode=555 >> dialwait=20 >> [pc:propage] >> phonenum=1234567 >> #stricttap=true >> [recip:pager_wdw] >> dest = @propage >> I would greatly appreciate any help. Thanks in advance! >> >> WDW >> > > |
|
From: Peter S. <Pet...@UT...> - 2009-09-16 19:04:53
|
Sorry I wasn't watching the thread too closely. That's good news that you figured out a solution. If your modem can discern voice, then I believe you can just make sure that its response code set includes the VOICE responses, and it will likely get logged. X6 perhaps? Peter |
Thanks for helping keep SourceForge clean.
X