View previous topic :: View next topic |
Author |
Message |
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Thu Feb 01, 2007 9:03 am Post subject: controlling timeout on connector/diallers |
|
|
occasionally my diallers do not respond, the last entry in the log being
31/01/2007 23:59:57 Waiting for protocol initialization
is there a way I can force a timeout? my only resolution so far is to reboot the server as the modems on an onboard multitech ISI port
Thanks
Wayne
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1123 Location: US
|
Posted: Thu Feb 01, 2007 9:47 am Post subject: |
|
|
Wayne,
When you review the logs for the dialer that seems to be hanging - is there a common variable? In other words, does it seem to happen during a job to a particular carrier or recipient?_________________ Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate |
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Thu Feb 01, 2007 9:57 am Post subject: |
|
|
i have four diallers and the errors have occured on all diallers at one time or another.. i have used the same carrier each time. the diallers can run for days with no problem. below is a log of the last valid send followed by the fail, followed by the reboot and successful send
hope this helps
Thanks
Wayne
31/01/2007 23:59:34 Start connection to carrier: cellnet
31/01/2007 23:59:34 Connect using TAP protocol
31/01/2007 23:59:34 Resetting communication parameters
31/01/2007 23:59:35 Attempting to reset modem
31/01/2007 23:59:37 Sent:AT<CR>
31/01/2007 23:59:38 Received:<CR><LF>OK<CR><LF>
31/01/2007 23:59:39 Modem reset
31/01/2007 23:59:39 Attempting to send dialer init string
31/01/2007 23:59:39 Sent:AT&FQ0V1X4&D2S37=5<CR>
31/01/2007 23:59:39 Received:<CR><LF>OK<CR><LF>
31/01/2007 23:59:40 Dialer init string sent
31/01/2007 23:59:40 Dialing carrier
31/01/2007 23:59:40 Sent:ATDT907860980480<CR>
31/01/2007 23:59:48 Waiting for connection
31/01/2007 23:59:57 Received:<CR><LF>CONNECT 14400 LAPM COMPRESSED<CR><LF>
31/01/2007 23:59:57 Received 'CONNECT'
31/01/2007 23:59:57 Connected to carrier
31/01/2007 23:59:57 Waiting for protocol initialization
01/02/2007 08:52:50 Module Started
01/02/2007 08:53:07 Running cleanup routine
01/02/2007 08:53:10 Module Stopped
01/02/2007 08:54:27 Module Started
01/02/2007 08:54:30 Time synchronized with scheduler
01/02/2007 08:54:34 ========================================
01/02/2007 08:54:34 Start connection to carrier: cellnet
01/02/2007 08:54:34 Connect using TAP protocol
01/02/2007 08:54:34 Resetting communication parameters
01/02/2007 08:54:34 Attempting to reset modem
01/02/2007 08:54:37 Sent:AT<CR>
01/02/2007 08:54:37 Received:<CR><LF>OK<CR><LF>
01/02/2007 08:54:38 Modem reset
01/02/2007 08:54:38 Attempting to send dialer init string
01/02/2007 08:54:38 Sent:AT&FQ0V1X4&D2S37=5<CR>
01/02/2007 08:54:39 Received:<CR><LF>OK<CR><LF>
01/02/2007 08:54:39 Dialer init string sent
01/02/2007 08:54:39 Dialing carrier
01/02/2007 08:54:39 Sent:ATDT907860980480<CR>
01/02/2007 08:54:47 Waiting for connection
01/02/2007 08:54:56 Received:<CR><LF>CONNECT 14400 LAPM COMPRESSED<CR><LF>
01/02/2007 08:54:56 Received 'CONNECT'
01/02/2007 08:54:57 Connected to carrier
01/02/2007 08:54:57 Waiting for protocol initialization
01/02/2007 08:55:02 Received:<CR><LF>
01/02/2007 08:55:02 Sent:<CR>
01/02/2007 08:55:03 Received:ID=
01/02/2007 08:55:04 TAP protocol detected
01/02/2007 08:55:07 Sent:<ESC>PG1<CR>
01/02/2007 08:55:08 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
01/02/2007 08:55:10 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
01/02/2007 08:55:10 Automatic TAP mode accepted
01/02/2007 08:55:16 ----------------------------------------
01/02/2007 08:55:16 Working on message to: cellnet from: tauweb@uk.fujitsu.com
01/02/2007 08:55:16 Formatting message
01/02/2007 08:55:16 Message contained in single packet
01/02/2007 08:55:16 Message contained in single block
01/02/2007 08:55:16 Sending block
01/02/2007 08:55:16 Sent:<STX>07867822889<CR><F:TaUWeb>UKIS Sev1: 94408/924; SDU: - UNLISTED SDU -; Detail: Back office are not working - Front desks are ok, logged by salinder from WICU, ref 21612 Alfe (c<CR><ETX>35=<CR>
01/02/2007 08:55:18 Received:211 Message 6AF44F21 send successful - message submitted for processing<CR><CR><ACK><CR>
01/02/2007 08:55:18 Block sent successfully
01/02/2007 08:55:18 Packet sent successfully
01/02/2007 08:55:18 SUCCESSFUL Stn:1 To:07867822889 Frm:tauweb@uk.fujitsu.com File:070201084437_01.578 Msg:<F:TaUWeb>UKIS Sev1: 94408/924; SDU: - UNLISTED SDU -; Detail: Back office are not working - Front desks are ok,ˇlogged by salinder from WICU, ref 21612ˇAlfe (c
01/02/2007 08:55:21 ----------------------------------------
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1123 Location: US
|
Posted: Thu Feb 01, 2007 10:03 am Post subject: |
|
|
From what you posted - my suspicion is that you are initiating a job right before PageGate does its daily backup/inspect process. Does the issue always occur right around midnight?_________________ Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate |
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Thu Feb 01, 2007 10:39 am Post subject: |
|
|
its possible.. since i updated the software last weekend, this is the first occurence of a hang i have had.. i will keep an eye on it.. in the meantime if, as you suspect, it happens just prior to pagegate doing its backup/inspect process, what would be the workaround/fix?
Thanks
Wayne
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1123 Location: US
|
Posted: Thu Feb 01, 2007 10:49 am Post subject: |
|
|
If I am correct in assuming that the message is being generated from an automated system - you could re-schedule it from 2359hrs to 0002 hrs_________________ Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate |
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Thu Feb 01, 2007 10:56 am Post subject: |
|
|
the service runs 24/7.. but i could note the time and if after say 23:58 and before 00:02, sleep for a few minutes :-) i will wait for the next occurence and if the hang happens at this time, make the code change..
watch this space :-)
Thanks
Wayne
|
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Tue Feb 20, 2007 8:56 am Post subject: |
|
|
i have not had any re-occurences of the midnight hangup but have recently experienced bad data coming back from the modem and the subsequent resets failing.. any suggestions on how i can overcome this electronically?
Thanks
20/02/2007 12:01:26 Start connection to carrier: cellnet
20/02/2007 12:01:26 Connect using TAP protocol
20/02/2007 12:01:26 Resetting communication parameters
20/02/2007 12:01:28 Attempting to reset modem
20/02/2007 12:01:31 Sent:AT<CR>
20/02/2007 12:01:31 Received:<CR><LF>OK<CR><LF>
20/02/2007 12:01:32 Modem reset
20/02/2007 12:01:32 Attempting to send dialer init string
20/02/2007 12:01:32 Sent:AT&FQ0V1X4&D2S37=5<CR>
20/02/2007 12:01:32 Received:<CR><LF>OK<CR><LF>
20/02/2007 12:01:33 Dialer init string sent
20/02/2007 12:01:33 Dialing carrier
20/02/2007 12:01:33 Sent:ATDT907860980480<CR>
20/02/2007 12:01:41 Waiting for connection
20/02/2007 12:01:59 Received:<CR><LF>CONNECT 14400<CR><LF><0>
20/02/2007 12:01:59 Received 'CONNECT'
20/02/2007 12:01:59 Connected to carrier
20/02/2007 12:01:59 Waiting for protocol initialization
20/02/2007 12:02:04 Sent:<CR>
20/02/2007 12:02:07 Received:{f-3K<RS>qtw!.]o **U9kwgZSz=Efk>/gR2f~6v[x<15>nKI[WF+7?}s<RS>?3]m<22>/6<19>S'<22>^KuR-<11>2-`IW<24>wXB<US>{<22>Ng]m-o6KHfl<US>=Uv~5<ETX>m"o>U[<EOT>G~ReQn[.1zz:u_3<28>z~+<19>s>WV<ESC><SUB>}o[y<ACK>Yy&%_k`VyrcZ7'1onOu~g[pM:g<ACK>+/Z'<ETB>[/e6W}<25><14>{[om<US>{u{?K<19><18>WmsII3
20/02/2007 12:02:07 Sent:<CR>
20/02/2007 12:02:12 Sent:<CR>
20/02/2007 12:02:17 Received:<CR><LF>NO CARRIER<CR><LF>
20/02/2007 12:02:17 Sent:<CR>
20/02/2007 12:02:23 Attempting to hang up modem
20/02/2007 12:02:26 Sent:AT<CR>
20/02/2007 12:02:31 Attempting to hang up modem
20/02/2007 12:02:34 Sent:AT<CR>
20/02/2007 12:02:39 Attempting to hang up modem
20/02/2007 12:02:42 Sent:AT<CR>
20/02/2007 12:02:52 ========================================
20/02/2007 12:02:52 Start connection to carrier: cellnet
20/02/2007 12:02:52 Connect using TAP protocol
20/02/2007 12:02:52 Resetting communication parameters
20/02/2007 12:02:55 Attempting to reset modem
20/02/2007 12:02:58 Sent:AT<CR>
20/02/2007 12:03:02 Attempting to reset modem
20/02/2007 12:03:05 Sent:AT<CR>
20/02/2007 12:03:09 Attempting to reset modem
20/02/2007 12:03:12 Sent:AT<CR>
20/02/2007 12:03:16 Attempting to hang up modem
20/02/2007 12:03:19 Sent:AT<CR>
20/02/2007 12:03:24 Attempting to hang up modem
20/02/2007 12:03:27 Sent:AT<CR>
20/02/2007 12:03:32 Attempting to hang up modem
20/02/2007 12:03:35 Sent:AT<CR>
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4405
|
Posted: Tue Feb 20, 2007 10:02 am Post subject: |
|
|
It appears the trouble you're running into is the baud rate. The terminal you're dialing into doesn't want to talk at 14400 and is returning garbage characters. Try changing the baud rate to something a little slower (each time you change the baud rate, remember to reset the init string to auto).
|
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Tue Feb 20, 2007 10:17 am Post subject: |
|
|
i have been running the same baud rate for years on all 4 modems with just the occasional glitch.. do you think that by running at 9600, i am less likely to hit this problem?
the log below shows the modem succesfully working at 14400 just prior to the problem showing up
20/02/2007 12:00:37 ========================================
20/02/2007 12:00:37 Start connection to carrier: cellnet
20/02/2007 12:00:37 Connect using TAP protocol
20/02/2007 12:00:37 Resetting communication parameters
20/02/2007 12:00:40 Attempting to reset modem
20/02/2007 12:00:42 Sent:AT<CR>
20/02/2007 12:00:42 Received:<CR><LF>OK<CR><LF>
20/02/2007 12:00:43 Modem reset
20/02/2007 12:00:43 Attempting to send dialer init string
20/02/2007 12:00:43 Sent:AT&FQ0V1X4&D2S37=5<CR>
20/02/2007 12:00:44 Received:<CR><LF>OK<CR><LF>
20/02/2007 12:00:45 Dialer init string sent
20/02/2007 12:00:45 Dialing carrier
20/02/2007 12:00:45 Sent:ATDT907860980480<CR>
20/02/2007 12:00:53 Waiting for connection
20/02/2007 12:01:02 Received:<CR><LF>CONNECT 14400 LAPM COMPRESSED<CR><LF>
20/02/2007 12:01:02 Received 'CONNECT'
20/02/2007 12:01:02 Connected to carrier
20/02/2007 12:01:02 Waiting for protocol initialization
20/02/2007 12:01:07 Received:<CR><LF>
20/02/2007 12:01:07 Sent:<CR>
20/02/2007 12:01:08 Received:ID=
20/02/2007 12:01:08 TAP protocol detected
20/02/2007 12:01:08 Sent:<ESC>PG1<CR>
20/02/2007 12:01:10 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
20/02/2007 12:01:10 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
20/02/2007 12:01:10 Automatic TAP mode accepted
20/02/2007 12:01:11 ----------------------------------------
20/02/2007 12:01:11 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 12:01:11 Formatting message
20/02/2007 12:01:11 Message contained in single packet
20/02/2007 12:01:11 Message contained in single block
20/02/2007 12:01:11 Sending block
20/02/2007 12:01:11 Sent:<STX>07867828751<CR>Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00<CR><ETX>39;<CR>
20/02/2007 12:01:12 Received:211 Message 79B3420A send successful - message submitted for processing<CR><CR><ACK><CR>
20/02/2007 12:01:12 Block sent successfully
20/02/2007 12:01:12 Packet sent successfully
20/02/2007 12:01:12 SUCCESSFUL Stn:1 To:07867828751 Frm:notifypro.nhs@uk.fujitsu.com File:070220115935_04.673 Msg:Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00
20/02/2007 12:01:13 ----------------------------------------
20/02/2007 12:01:13 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 12:01:13 Formatting message
20/02/2007 12:01:13 Message contained in single packet
20/02/2007 12:01:13 Message contained in single block
20/02/2007 12:01:13 Sending block
20/02/2007 12:01:13 Sent:<STX>07867832053<CR>Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00<CR><ETX>391<CR>
20/02/2007 12:01:14 Received:211 Message 79B343AB send successful - message submitted for processing<CR><CR><ACK><CR>
20/02/2007 12:01:14 Block sent successfully
20/02/2007 12:01:14 Packet sent successfully
20/02/2007 12:01:14 SUCCESSFUL Stn:1 To:07867832053 Frm:notifypro.nhs@uk.fujitsu.com File:070220115935_10.685 Msg:Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00
20/02/2007 12:01:14 ----------------------------------------
20/02/2007 12:01:14 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 12:01:14 Formatting message
20/02/2007 12:01:14 Message contained in single packet
20/02/2007 12:01:14 Message contained in single block
20/02/2007 12:01:14 Sending block
20/02/2007 12:01:14 Sent:<STX>07867828694<CR>Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00<CR><ETX>3:1<CR>
20/02/2007 12:01:15 Received:211 Message 79B344A6 send successful - message submitted for processing<CR><CR><ACK><CR>
20/02/2007 12:01:15 Block sent successfully
20/02/2007 12:01:15 Packet sent successfully
20/02/2007 12:01:15 SUCCESSFUL Stn:1 To:07867828694 Frm:notifypro.nhs@uk.fujitsu.com File:070220115935_11.687 Msg:Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00
20/02/2007 12:01:15 ----------------------------------------
20/02/2007 12:01:15 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 12:01:15 Formatting message
20/02/2007 12:01:15 Message contained in single packet
20/02/2007 12:01:15 Message contained in single block
20/02/2007 12:01:15 Sending block
20/02/2007 12:01:16 Sent:<STX>07867834413<CR>Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00<CR><ETX>393<CR>
20/02/2007 12:01:17 Received:211 Message 79B3459F send successful - message submitted for processing (transaction limit reached)<CR><CR><ACK><CR>
20/02/2007 12:01:17 Block sent successfully
20/02/2007 12:01:17 Packet sent successfully
20/02/2007 12:01:17 SUCCESSFUL Stn:1 To:07867834413 Frm:notifypro.nhs@uk.fujitsu.com File:070220115935_12.689 Msg:Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00
20/02/2007 12:01:17 ----------------------------------------
20/02/2007 12:01:17 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 12:01:17 Formatting message
20/02/2007 12:01:17 Message contained in single packet
20/02/2007 12:01:17 Message contained in single block
20/02/2007 12:01:17 Sending block
20/02/2007 12:01:17 Sent:<STX>07867824880<CR>Sev2 - RIS - 139847 - Torbay - Network seeing 20% packet loss. Investigations ongoing. Next update 14.00<CR><ETX>39:<CR>
20/02/2007 12:01:18 Received:516 SESSION TERMINATED - MESSAGE LIMIT EXCEEDED (4)<CR><CR><ESC><EOT><CR><CR><LF>*** Annex Port
20/02/2007 12:01:18 Disconnect requested by carrier. Disconnecting
20/02/2007 12:01:18 Sent:<EOT><CR>
20/02/2007 12:01:19 Attempting to hang up modem
20/02/2007 12:01:21 Sent:AT<CR>
20/02/2007 12:01:21 Received:<CR><LF>OK<CR><LF>
20/02/2007 12:01:21 Modem hung up
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4405
|
Posted: Tue Feb 20, 2007 3:14 pm Post subject: |
|
|
Ah! I'm glad you posted the full log. The problem is this:
20/02/2007 12:01:18 Received:516 SESSION TERMINATED - MESSAGE LIMIT EXCEEDED (4)<
The terminal you're dialing into speaks at 14400 just fine. The trouble you're running into is that the terminal will only accept so many messages within a certain timeframe (you'll need to contact the carrier to know how many message they can accept within whatever time limit they've set). You'll notice that it was only after the session was terminated because the limit was exceeded did you start to receive those garbage characters. It's not until you're within the allowed limits once more that the terminal begins to respond properly.
|
|
Back to top |
|
tutartis
Joined: 24 Jan 2007 Posts: 13
|
Posted: Wed Feb 21, 2007 2:58 am Post subject: |
|
|
The carrier I am using will only accept 4 messages before forcing a disconnection.. this has been the case since I started using them many years ago. PageGate always copes with this ok.. see below..
Thanks
Wayne
20/02/2007 17:49:17 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
20/02/2007 17:49:17 Formatting message
20/02/2007 17:49:17 Message contained in single packet
20/02/2007 17:49:17 Message contained in single block
20/02/2007 17:49:17 Sending block
20/02/2007 17:49:17 Sent:<STX>07867832053<CR>PACS 139365 Sev 2 Cheltenham & Gloucester - Changed back to Sev 3 with user approval Kodak visiting site tomorrow. No more updates<CR><ETX>>=3<CR>
20/02/2007 17:49:17 Received:516 SESSION TERMINATED - MESSAGE LIMIT EXCEEDED (4)<CR><CR><ESC><EOT><CR><CR><LF>*** Annex Port
20/02/2007 17:49:17 Disconnect requested by carrier. Disconnecting
20/02/2007 17:49:18 Sent:<EOT><CR>
20/02/2007 17:49:18 Attempting to hang up modem
20/02/2007 17:49:20 Sent:AT<CR>
20/02/2007 17:49:21 Received:<CR><LF>OK<CR><LF>
20/02/2007 17:49:21 Modem hung up
20/02/2007 17:49:26 ========================================
20/02/2007 17:49:26 Start connection to carrier: cellnet
20/02/2007 17:49:26 Connect using TAP protocol
20/02/2007 17:49:26 Resetting communication parameters
20/02/2007 17:49:28 Attempting to reset modem
20/02/2007 17:49:30 Sent:AT<CR>
20/02/2007 17:49:30 Received:<CR><LF>OK<CR><LF>
20/02/2007 17:49:31 Modem reset
20/02/2007 17:49:31 Attempting to send dialer init string
20/02/2007 17:49:31 Sent:AT&FQ0V1X4&D2S37=5<CR>
20/02/2007 17:49:32 Received:<CR><LF>OK<CR><LF>
20/02/2007 17:49:32 Dialer init string sent
20/02/2007 17:49:32 Dialing carrier
20/02/2007 17:49:32 Sent:ATDT907860980480<CR>
20/02/2007 17:49:40 Waiting for connection
20/02/2007 17:49:50 Received:<CR><LF>CONNECT 14400 LAPM COMPRESSED<CR><LF>
20/02/2007 17:49:50 Received 'CONNECT'
20/02/2007 17:49:50 Connected to carrier
20/02/2007 17:49:50 Waiting for protocol initialization
20/02/2007 17:49:54 Received:<CR><LF>
20/02/2007 17:49:54 Sent:<CR>
20/02/2007 17:49:55 Received:ID=
20/02/2007 17:49:55 TAP protocol detected
20/02/2007 17:49:56 Sent:<ESC>PG1<CR>
20/02/2007 17:49:57 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
20/02/2007 17:49:58 Received:110 1.8<CR>Rel: - App:1.9 <CR><CR><ACK><CR><ESC>[p<CR>
20/02/2007 17:49:58 Automatic TAP mode accepted
20/02/2007 17:49:58 ----------------------------------------
20/02/2007 17:49:58 Working on message to: cellnet from: notifypro.nhs@uk.fujitsu.com
|
|
Back to top |
|
|