Modem does not reset after sending alert via TAP

[mpriess]

Hi Alex,

We have a few tests setup to alert to pager via TAP. If an alert is triggered the first one goes through fine; however, any test after that does not. The popup box says "cannot open com port"..."will redial in 15sec". It appears the modem is not getting reset after dialing out once. If I manually reset (turn offon) the external modem...then it works fine. Do you have any recommendations to correct this?

[mpriess]

I just tried adding the following line to the hostmon.ini as described in another post...this modem is on COM1

FixedPagingPort=COM1

...but now I get

Initializing Modem
Initializing Modem
The modem is not responding.
Releasing COM port .. Ok
Error: The modem is not responding.
Next attempt to send message will be made in 15 sec

[mpriess]

running v3.69d

[mpriess]

some more info...

The modem CD (carrier detect) LED stays on after hostmonitor sends an alert via the modem and will not go off unit the modem is turned offon.

[KS-Soft]

Thanks for detailed description of the problem. I understand it but don't know what can be reason for this problem yet. Still checking code...

Regards
Alex

[jromariz]

Hi,

You can try to configure the modem so the CD pedends on the remote one and to reset after the CD signal cycles on/off. Maybe it´s note the best solution but I believe it can work. I would try to check the modem config.

Jromariz.

[KS-Soft]

I found one error and corrected it but... I am not sure this error related to your problem. Under some conditions HostMonitor can use different modem than specified. There is patch at http://www.ks-soft.net/download/hm369k.zip
Please, try it. If it will not help, I will continue investigation.

Regards
Alex

[mpriess]

Hi Alex,
I just applied the patch you provided. It does the same thing...worked the first time fails everytime after that. However, I noticed the first line references TAPI0 and when it fails it references TAPI1? Would this have anything to do with it? The log is shown below:

Log (Port: TAPI0, Baud rate: 2400, Init string: AUTO, Dial string: ATDT)

Error: Error Opening COM port (TAPI1)
Next attempt to send message will be made in 15 sec

Error: Error Opening COM port (TAPI1)
Next attempt to send message will be made in 15 sec

[KS-Soft]

>However, I noticed the first line references TAPI0 and when it fails it references TAPI1?

Fixed. Update at the same place: http://www.ks-soft.net/download/hm369k.zip
But what I am interested in is log of the first (successful) call. Does HostMonitor display message "Releasing COM port .. Ok"?

Regards
Alex

[mpriess]

Still fails with the following...

Log (Port: TAPI, Baud rate: 2400, Init string: AUTO, Dial string: ATDT)

Error: Error Opening COM port (TAPI7)
Next attempt to send message will be made in 15 sec

When the modem is reset manually and a test alert is triggered here is the successful log:

Log (Port: TAPI, Baud rate: 2400, Init string: AUTO, Dial string: ATDT)

Initializing Modem
Dialing 9XXXXXXXXXX
Connected
Sending Password
Password Accepted
Sending Msg 1 Block 1
Disconnecting
Successful - Completed: 1 of 1
Releasing COM port .. Ok
Message has been sent to pager XXXXXXX

Just replaced the actual numbers with X's.
Thanks for your help...

[ This Message was edited by: mpriess on 2003-06-10 16:22 ]

[mpriess]

OK. Good news. I put an old Supra 28.8 in place of the US Robotics 33.6 and all is well now. Maybe the supra likes the init string better? I don't know. But, I tested it over and over and even when hostmonitor reports "cannot release com port"...an alert triggered immediately after is still sent. The modem is now initializing every time. This is an adequate solution for me. Thanks for your help Alex and sorry for taking some of your time away from 4.0 development

[KS-Soft]

Good news. I start thinking about external program that will be able to send message to pager...
Ok, go back to HostMonitor 4

Regards
Alex