Search found 13 matches

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 W ...

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.c ...

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< ...

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

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

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 ...

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

software upgrade was painless and so far no problems detected.. fingers crossed :-)

Thanks
Wayne

ok i will apply the new release over the weekend when the service is not so busy

thanks
Wayne

my thinking exactly :-) i have just downloaded the latest version. should i take any precautions with the existing live service [other than stopping the service] ?

Thanks
Wayne

the binary does not exist :-( so i guess my stuff is out of date.. most of the binaries are dated 2002. my s/n is 6794 if that helps

Thanks
Wayne

perhaps i should have added i am processing some 4000 messages per day. in all cases where a message has not been processed, the same message has been sent to a number of other recipients successfully, and therefore is not failing because of its unreadability.

as it has found its way into the process directory i am happy that pagegate has accepted the message from its parent directory and that pagegate successfully sent identical messages to other recipients.

my workaround .. which did work!! was to move items that had remained in the process directory for more than 1 hour into the parent directory.. i had to remove the workaround though, because occasionally owing to heavy loads, items were genuinely waiting to be processed and my workround was causing the messages to be sent twice :-(

does this help?

thanks for the quick reply

Wayne

i have been running pagegate version 4.0 for many years now using the getascii interface. occasionally i have detected messages being left in the process directory which have not been sent.. is there a fix for this? or work around to force pagegate to process them?

Thanks
Wayne

Author	Message
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Wed Feb 21, 2007 2:58 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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 W ...
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Tue Feb 20, 2007 10:17 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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.c ...
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Tue Feb 20, 2007 8:56 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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< ...
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Thu Feb 01, 2007 10:56 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Thu Feb 01, 2007 10:39 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Thu Feb 01, 2007 9:57 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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 ...
Topic: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	Forum: PageGate Support Posted: Thu Feb 01, 2007 9:03 am Subject: controlling timeout on connector/diallers
tutartis Replies: 11 Views: 24615	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
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Sat Jan 27, 2007 5:05 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	software upgrade was painless and so far no problems detected.. fingers crossed :-) Thanks Wayne
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Thu Jan 25, 2007 3:37 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	ok i will apply the new release over the weekend when the service is not so busy thanks Wayne
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Wed Jan 24, 2007 11:56 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	my thinking exactly :-) i have just downloaded the latest version. should i take any precautions with the existing live service [other than stopping the service] ? Thanks Wayne
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Wed Jan 24, 2007 10:31 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	the binary does not exist :-( so i guess my stuff is out of date.. most of the binaries are dated 2002. my s/n is 6794 if that helps Thanks Wayne
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Wed Jan 24, 2007 7:49 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	perhaps i should have added i am processing some 4000 messages per day. in all cases where a message has not been processed, the same message has been sent to a number of other recipients successfully, and therefore is not failing because of its unreadability. as it has found its way into the process directory i am happy that pagegate has accepted the message from its parent directory and that pagegate successfully sent identical messages to other recipients. my workaround .. which did work!! was to move items that had remained in the process directory for more than 1 hour into the parent directory.. i had to remove the workaround though, because occasionally owing to heavy loads, items were genuinely waiting to be processed and my workround was causing the messages to be sent twice :-( does this help? thanks for the quick reply Wayne
Topic: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	Forum: PageGate Support Posted: Wed Jan 24, 2007 6:20 am Subject: getascii occasionally missing messages
tutartis Replies: 9 Views: 22932	i have been running pagegate version 4.0 for many years now using the getascii interface. occasionally i have detected messages being left in the process directory which have not been sent.. is there a fix for this? or work around to force pagegate to process them? Thanks Wayne