View previous topic :: View next topic |
Author |
Message |
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Sun Aug 30, 2009 6:57 pm Post subject: Connector Retries a message more than the no. of retries set |
|
|
My Connector using a GSM modem to send SMS is set to retry 3 times ... what should happen after 3 unsuccessful retries?
1. Should it stop retrying and mark it as bad as docemented?
2. or should it continue trying until someone manually deletes the message?
My PageGate Setup is doing no. 2. Is this a correct connector behaviour?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Mon Aug 31, 2009 8:52 am Post subject: |
|
|
Hmm... it should be doing #1 but there are a few cases where it won't, where it will attempt to resend the message until someone cancels it. When you try to send the message, are you getting a specific error code back? |
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Mon Aug 31, 2009 10:38 pm Post subject: |
|
|
For sending the msg .. On the connector logs it says ..
Error Sending Packet ...
Then after 3 tries ..
Error Sending Packet
Message Retry Limit exceeded
Module stopped <<=== it restarts the connector module
Module start
Then after a lot of attempts ... It will crash the the connector and the TAP interface (will not accept message). I notice an UPDATE statement error on the logs. To recover, I have to restart and rebuild my DB using the PG tools. Is there any solution to this? This is what makes my PG server crash all the time.
Additionally, if you are wondering why there is a packet sent error ... the message being sent have some chars that might not be accepted by the modem ... has a format of //???[??][???] ... the ? represents a character. I haven't proven this yet but this is besides the point for now.
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1122 Location: US
|
Posted: Tue Sep 01, 2009 7:14 am Post subject: |
|
|
How is your cellular modem connected (usb, serial, or ethernet)
what baud rate are you using for the connector, the carrier, and the com port
what carrier is the device subscribed to
is there a sms plan on the device account
is there a data plan on the account_________________ 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 |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Wed Sep 02, 2009 9:30 am Post subject: |
|
|
Hi Aaron,
How is your cellular modem connected (usb, serial, or ethernet)
-- Serial
what baud rate are you using for the connector, the carrier, and the com port
-- 115200
what carrier is the device subscribed to
--- A cellular company (Asia)
is there a sms plan on the device account
--- yes
is there a data plan on the account
--- yes
Is there a relation to the failure of the connector to limit retries and junk the message? or is this on the characters that are not being sent -- I still need to prove this by sending a message manually using the modem.
Thanks
|
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Mon Sep 07, 2009 12:46 am Post subject: |
|
|
Additional information:
-- I did further investigation if the characters being used on the message are characters reserved for my modem commands ... I used hyperterminal to send the message manualy - It was successful! I therefore conlude that the characters are something the PageGate Connector can not sent ... it has a pattern like .... [INC] [MA] ...
So, now, I have 2 questions...
1.) Why are these messages failing when characters in this pattern is sent via the connector (GSM)?
2.) Why does the connector tries to send it beyond the limit of 3 tries?
Cheers,
James
|
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Tue Sep 08, 2009 9:29 pm Post subject: |
|
|
sirjames wrote: |
Additional information:
-- I did further investigation if the characters being used on the message are characters reserved for my modem commands ... I used hyperterminal to send the message manualy - It was successful! I therefore conlude that the characters are something the PageGate Connector can not sent ... it has a pattern like .... [INC] [MA] ...
So, now, I have 2 questions...
1.) Why are these messages failing when characters in this pattern is sent via the connector (GSM)?
2.) Why does the connector tries to send it beyond the limit of 3 tries?
Anyone from NotePage Tech Support?
Cheers,
James |
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Wed Sep 09, 2009 10:01 am Post subject: |
|
|
sirjames wrote: |
1.) Why are these messages failing when characters in this pattern is sent via the connector (GSM)? |
Can you send me a copy of all of the log files from your PageGate Server? They should be located in your logging directory (by default, c:\pagegatedata\logs\). I've never seen the [INC][MA] commands as part of any GSM-AT transmission before, so email me the logs so I can see it in context.
Quote: |
2.) Why does the connector tries to send it beyond the limit of 3 tries?
|
When you run into a database error (or any hard error) that stops and restarts the connector module, the program doesn't have a chance to update the counter statement for the connection attempts. As such, it tries the connection ad infintum. |
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Wed Jan 27, 2010 12:12 am Post subject: |
|
|
Please try sending a message containing the characters "[" and "]" and see if it fails ... my suspicion is on the script that updates the Access database. Thanks
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1122 Location: US
|
Posted: Wed Jan 27, 2010 8:58 am Post subject: |
|
|
Tested -no issues - I suspect your issue is likely related to your modem. The below snapshot of the logfiles is from a PageGate system with the MultiTech MTCBA series modem attached:
1/27/2010 8:43:04 AM ========================================
1/27/2010 8:43:04 AM Start connection to carrier: SMS_Modem
1/27/2010 8:43:04 AM Connect using GSM protocol
1/27/2010 8:43:04 AM Setting communication parameters (115200,n,8,1)
1/27/2010 8:43:05 AM Attempting to reset modem
1/27/2010 8:43:07 AM Sent:AT<CR>
1/27/2010 8:43:08 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:43:08 AM Modem reset
1/27/2010 8:43:08 AM Sent:AT+CMGF=1<CR>
1/27/2010 8:43:09 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:43:09 AM Text delivery mode entered
1/27/2010 8:43:09 AM ----------------------------------------
1/27/2010 8:43:09 AM Working on message to: osgood_aaron_cell from: ado
1/27/2010 8:43:09 AM Formatting message
1/27/2010 8:43:09 AM Message broken into 2 packets
1/27/2010 8:43:09 AM Sending packet
1/27/2010 8:43:09 AM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/27/2010 8:43:10 AM Received:<CR><LF>>
1/27/2010 8:43:10 AM Sent:1of2:ado:OM:{E3265F14-C4BF-475D-9C61-5984FE02A6D8}/Major/FILESYSTEM.shared-tivoli.FSCapacity/FILESYSTEM shared-tivoli FSCapacity in ALARM 96 percent <SUB>
1/27/2010 8:43:13 AM Received:<CR><LF>+CMGS: 37<CR><LF><CR><LF>OK<CR><LF>
1/27/2010 8:43:13 AM Packet sent successfully
1/27/2010 8:43:13 AM Sending packet
1/27/2010 8:43:14 AM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/27/2010 8:43:14 AM Received:<CR><LF>>
1/27/2010 8:43:14 AM Sent:2of2:full/20080719 19:25:54<SUB>
1/27/2010 8:43:17 AM Received:<CR><LF>+CMGS: 38<CR><LF><CR><LF>OK<CR><LF>
1/27/2010 8:43:17 AM Packet sent successfully
1/27/2010 8:43:17 AM SUCCESSFUL Stn:10 To:osgood_aaron_cell Frm:ado Msg:OM:{E3265F14-C4BF-475D-9C61-5984FE02A6D8}/Major/FILESYSTEM.shared-tivoli.FSCapacity/FILESYSTEM shared-tivoli FSCapacity in ALARM 96 percent full/20080719 19:25:54
1/27/2010 8:43:17 AM Attempting to hang up modem
1/27/2010 8:43:19 AM Sent:AT<CR>
1/27/2010 8:43:20 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:43:20 AM Modem hung up
1/27/2010 8:44:00 AM Log ping...
1/27/2010 8:44:05 AM ========================================
1/27/2010 8:44:05 AM Start connection to carrier: SMS_Modem
1/27/2010 8:44:05 AM Connect using GSM protocol
1/27/2010 8:44:05 AM Setting communication parameters (115200,n,8,1)
1/27/2010 8:44:06 AM Attempting to reset modem
1/27/2010 8:44:08 AM Sent:AT<CR>
1/27/2010 8:44:08 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:44:09 AM Modem reset
1/27/2010 8:44:09 AM Sent:AT+CMGF=1<CR>
1/27/2010 8:44:09 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:44:09 AM Text delivery mode entered
1/27/2010 8:44:09 AM ----------------------------------------
1/27/2010 8:44:09 AM Working on message to: osgood_aaron_cell from: ado
1/27/2010 8:44:09 AM Formatting message
1/27/2010 8:44:09 AM Message contained in a single packet
1/27/2010 8:44:09 AM Sending packet
1/27/2010 8:44:10 AM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/27/2010 8:44:10 AM Received:<CR><LF>>
1/27/2010 8:44:10 AM Sent:ado:this is a [test]<SUB>
1/27/2010 8:44:12 AM Received:<CR><LF>+CMGS: 39<CR><LF><CR><LF>OK<CR><LF>
1/27/2010 8:44:12 AM Packet sent successfully
1/27/2010 8:44:12 AM SUCCESSFUL Stn:10 To:osgood_aaron_cell Frm:ado Msg:this is a [test]
1/27/2010 8:44:12 AM Attempting to hang up modem
1/27/2010 8:44:15 AM Sent:AT<CR>
1/27/2010 8:44:15 AM Received:<CR><LF>OK<CR><LF>
1/27/2010 8:44:15 AM Modem hung up_________________ 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 |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Thu Jan 28, 2010 9:03 pm Post subject: |
|
|
I tried sending the message manually using a modem and it was successful. So, I'm sure it was not a modem issue.
Here is the exact line where the error message appears.
08:07:16 AM Program Halted. Database error: 3144 Syntax error in UPDATE statement in Procedure: SendGSM.
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1122 Location: US
|
Posted: Thu Jan 28, 2010 10:17 pm Post subject: |
|
|
This may sound elementary - but - is it possible that there is another application on the PC that may be trying to use the same COM port as PageGate? I have been able to duplicate that error when 2 devices tried to grab the same port. I have also seen it with some USB Cellular modems - including RS-232 Serial devices when connected via USB adaptor. It appears to be closely related to the USB ->COM port driver_________________ 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 |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Thu Jan 28, 2010 10:37 pm Post subject: |
|
|
The modem is connected via a serial port and some messages are getting sent while the message in question remains... but you are right .. I tried sending from the pagegate server itself (same message you used for testing) and it is going out ... It is just so weird why this is happening.
Do you know the reason for the error message that I posted. It is the only application running on the computer.
|
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Thu Jan 28, 2010 11:00 pm Post subject: |
|
|
This is the log of the connector.
These are are my observation.
1) I highlighted the message that was failing. It seems that pagegate failed to break the message into 2 packets and continuously failed until I deleted the message.
Note: What is weird is that when i tried resending the same message... it was successful. It looks like that there is a certain condition that causes this incident. Unfortunately, that condition is hard to pinpoint.
2) The first few lines is an example of a message that was successfully broken into 2 packets.
1/28/2010 9:36:32 PM ----------------------------------------
1/28/2010 9:36:32 PM Working on message to: os2019 from:
1/28/2010 9:36:32 PM Formatting message
1/28/2010 9:36:32 PM Message broken into 2 packets
1/28/2010 9:36:32 PM Sending packet
1/28/2010 9:36:32 PM Sent:AT+CMGS="xxxxxxxxxxxx"<CR>
1/28/2010 9:36:32 PM Received:<CR><LF>>
1/28/2010 9:36:32 PM Sent:1of2:1/02:GRP/IM587382/Reassigned/P2/Shelly/shrobbins@bogus.com/1-404-676-3407/NAT 910C/01/04/2010 14:37:19/SAP Finance - he total amount of these invoices <SUB>
1/28/2010 9:36:36 PM Received:<CR><LF>+CMGS: 50<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 9:36:36 PM Packet sent successfully
1/28/2010 9:36:36 PM Sending packet
1/28/2010 9:36:36 PM Sent:AT+CMGS="xxxxxxxxxxxx"<CR>
1/28/2010 9:36:37 PM Received:<CR><LF>>
1/28/2010 9:36:37 PM Sent:2of2:are not what is shown as the total amount of the invoice in Accounts Rec/finance/na/break<SUB>
1/28/2010 9:36:41 PM Received:<CR><LF>+CMGS: 51<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 9:36:41 PM Packet sent successfully
1/28/2010 9:36:41 PM SUCCESSFUL Stn:5 To:os2019 Msg:1/02:GRP/IM587382/Reassigned/P2/Shelly/shrobbins@bogus.com/1-404-676-3407/NAT 910C/01/04/2010 14:37:19/SAP Finance - he total amount of these invoices are not what is shown as the total amount of the invoice in Accounts Rec/finance/na/break
1/28/2010 9:36:41 PM ----------------------------------------
1/28/2010 9:36:41 PM Working on message to: os2019 from:
1/28/2010 9:36:41 PM Formatting message
1/28/2010 9:36:41 PM Message contained in a single packet
1/28/2010 9:36:41 PM Sending packet
1/28/2010 9:36:41 PM Sent:AT+CMGS="xxxxxxxxxxxx"<CR>
1/28/2010 9:36:41 PM Received:<CR><LF>>
1/28/2010 9:36:41 PM Sent:2/02:fix/sap finance<SUB>
1/28/2010 9:36:44 PM Received:<CR><LF>+CMGS: 52<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 9:36:44 PM Packet sent successfully
1/28/2010 9:36:44 PM SUCCESSFUL Stn:5 To:os2019 Msg:2/02:fix/sap finance
1/28/2010 9:36:44 PM ----------------------------------------
1/28/2010 9:36:44 PM Working on message to: os2018 from:
1/28/2010 9:36:44 PM Formatting message
1/28/2010 9:36:44 PM Message broken into 2 packets
1/28/2010 9:36:44 PM Sending packet
1/28/2010 9:36:44 PM Sent:AT+CMGS="xxxxxxxxxxxxxx"<CR>
1/28/2010 9:36:45 PM Received:<CR><LF>>
1/28/2010 9:36:45 PM Sent:1of2:1/02:GRP/IM587382/Reassigned/P2/Shelly/shrobbins@bogus.com/1-404-676-3407/NAT 910C/01/04/2010 14:37:19/SAP Finance - he total amount of these invoices <SUB>
1/28/2010 9:36:49 PM Received:<CR><LF>+CMGS: 53<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 9:36:49 PM Packet sent successfully
1/28/2010 9:36:49 PM Sending packet
1/28/2010 9:36:49 PM Sent:AT+CMGS="xxxxxxxxxxxxxx"<CR>
1/28/2010 9:36:49 PM Received:<CR><LF>>
1/28/2010 9:36:50 PM Sent:2of2:are not what is shown as the total amount of the invoice in Accounts Rec/finance/na/break<SUB>
1/28/2010 9:36:53 PM Received:<CR><LF>+CMGS: 54<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 9:36:53 PM Packet sent successfully
1/28/2010 9:36:53 PM SUCCESSFUL Stn:5 To:os2018 Msg:1/02:GRP/IM587382/Reassigned/P2/Shelly/shrobbins@bogus.com/1-404-676-3407/NAT 910C/01/04/2010 14:37:19/SAP Finance - he total amount of these invoices are not what is shown as the total amount of the invoice in Accounts Rec/finance/na/break
1/28/2010 9:36:58 PM ========================================
1/28/2010 9:36:58 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:36:58 PM Connect using GSM protocol
1/28/2010 9:36:58 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:36:58 PM ----------------------------------------
1/28/2010 9:36:58 PM Working on message to: a45793 from:
1/28/2010 9:36:58 PM Formatting message
1/28/2010 9:36:58 PM Message contained in a single packet
1/28/2010 9:36:58 PM Sending packet
1/28/2010 9:36:58 PM Sent:AT+CMGS="+639178544803"<CR>
1/28/2010 9:36:59 PM Received:<CR><LF>>
1/28/2010 9:36:59 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:37:29 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:37:29 PM Error sending packet
1/28/2010 9:37:29 PM Message retry limit reached
1/28/2010 9:37:29 PM FAILED Stn:5 To:a45793 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:37:29 PM Module Stopped
1/28/2010 9:37:37 PM Module Started
1/28/2010 9:37:41 PM Time synchronized with scheduler
1/28/2010 9:37:45 PM ========================================
1/28/2010 9:37:45 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:37:45 PM Connect using GSM protocol
1/28/2010 9:37:46 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:37:46 PM ----------------------------------------
1/28/2010 9:37:46 PM Working on message to: a45884 from:
1/28/2010 9:37:46 PM Formatting message
1/28/2010 9:37:46 PM Message contained in a single packet
1/28/2010 9:37:46 PM Sending packet
1/28/2010 9:37:46 PM Sent:AT+CMGS="xxxxxxxxxxxxxx"<CR>
1/28/2010 9:37:47 PM Received:<CR><LF>>
1/28/2010 9:37:47 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:38:17 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:38:17 PM Error sending packet
1/28/2010 9:38:17 PM Message retry limit reached
1/28/2010 9:38:17 PM FAILED Stn:5 To:a45884 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:38:17 PM Module Stopped
1/28/2010 9:38:27 PM Module Started
1/28/2010 9:38:28 PM Time synchronized with scheduler
1/28/2010 9:38:32 PM ========================================
1/28/2010 9:38:32 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:38:32 PM Connect using GSM protocol
1/28/2010 9:38:32 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:38:32 PM ----------------------------------------
1/28/2010 9:38:32 PM Working on message to: a45829 from:
1/28/2010 9:38:32 PM Formatting message
1/28/2010 9:38:32 PM Message contained in a single packet
1/28/2010 9:38:32 PM Sending packet
1/28/2010 9:38:33 PM Sent:AT+CMGS="+639178249949"<CR>
1/28/2010 9:38:33 PM Received:<CR><LF>>
1/28/2010 9:38:33 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:39:03 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:39:03 PM Error sending packet
1/28/2010 9:39:03 PM Message retry limit reached
1/28/2010 9:39:03 PM FAILED Stn:5 To:a45829 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:39:03 PM Module Stopped
1/28/2010 9:39:13 PM Module Started
1/28/2010 9:39:17 PM Time synchronized with scheduler
1/28/2010 9:39:21 PM ========================================
1/28/2010 9:39:21 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:39:21 PM Connect using GSM protocol
1/28/2010 9:39:21 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:39:21 PM ----------------------------------------
1/28/2010 9:39:21 PM Working on message to: a45885 from:
1/28/2010 9:39:21 PM Formatting message
1/28/2010 9:39:21 PM Message contained in a single packet
1/28/2010 9:39:21 PM Sending packet
1/28/2010 9:39:21 PM Sent:AT+CMGS="+639064790998"<CR>
1/28/2010 9:39:22 PM Received:<CR><LF>>
1/28/2010 9:39:22 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:39:52 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:39:52 PM Error sending packet
1/28/2010 9:39:52 PM Message retry limit reached
1/28/2010 9:39:52 PM FAILED Stn:5 To:a45885 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:39:52 PM Module Stopped
1/28/2010 9:40:02 PM Module Started
1/28/2010 9:40:04 PM Time synchronized with scheduler
1/28/2010 9:40:08 PM ========================================
1/28/2010 9:40:08 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:40:08 PM Connect using GSM protocol
1/28/2010 9:40:08 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:40:08 PM ----------------------------------------
1/28/2010 9:40:08 PM Working on message to: a45832 from:
1/28/2010 9:40:08 PM Formatting message
1/28/2010 9:40:08 PM Message contained in a single packet
1/28/2010 9:40:08 PM Sending packet
1/28/2010 9:40:09 PM Sent:AT+CMGS="+639175949365"<CR>
1/28/2010 9:40:09 PM Received:<CR><LF>>
1/28/2010 9:40:09 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:40:40 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:40:40 PM Error sending packet
1/28/2010 9:40:40 PM Message retry limit reached
1/28/2010 9:40:40 PM FAILED Stn:5 To:a45832 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:40:40 PM Module Stopped
1/28/2010 9:40:48 PM Module Started
1/28/2010 9:40:50 PM Time synchronized with scheduler
1/28/2010 9:40:59 PM ========================================
1/28/2010 9:40:59 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:40:59 PM Connect using GSM protocol
1/28/2010 9:40:59 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:40:59 PM ----------------------------------------
1/28/2010 9:40:59 PM Working on message to: a45793 from:
1/28/2010 9:40:59 PM Formatting message
1/28/2010 9:40:59 PM Message contained in a single packet
1/28/2010 9:40:59 PM Sending packet
1/28/2010 9:41:00 PM Sent:AT+CMGS="+639178544803"<CR>
1/28/2010 9:41:00 PM Received:<CR><LF>>
1/28/2010 9:41:00 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:41:30 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:41:30 PM Error sending packet
1/28/2010 9:41:30 PM Message retry limit reached
1/28/2010 9:41:30 PM FAILED Stn:5 To:a45793 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
1/28/2010 9:41:31 PM Module Stopped
1/28/2010 9:41:37 PM Module Started
1/28/2010 9:41:40 PM Time synchronized with scheduler
1/28/2010 9:41:44 PM ========================================
1/28/2010 9:41:44 PM Start connection to carrier: SMC_GSM_1
1/28/2010 9:41:44 PM Connect using GSM protocol
1/28/2010 9:41:44 PM Setting communication parameters (115200,n,8,1)
1/28/2010 9:41:45 PM ----------------------------------------
1/28/2010 9:41:45 PM Working on message to: a45884 from:
1/28/2010 9:41:45 PM Formatting message
1/28/2010 9:41:45 PM Message contained in a single packet
1/28/2010 9:41:45 PM Sending packet
1/28/2010 9:41:45 PM Sent:AT+CMGS="xxxxxxxxxxxxxx"<CR>
1/28/2010 9:41:45 PM Received:<CR><LF>>
1/28/2010 9:41:45 PM Sent:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/e<SUB>
1/28/2010 9:42:16 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 9:42:16 PM Error sending packet
1/28/2010 9:42:16 PM Message retry limit reached
1/28/2010 9:42:16 PM FAILED Stn:5 To:a45884 Msg:GRP/IM605792/Open/P1/Raimon/raleyva@bogus.com///01/28/2010 08:04:14/Access to server ATLH02/HUB/NA/TCCC can not be established by getting stats. [RTHE-7JSHXE]/email and calendaring/notes server/server not responding/slow/atlh02-notes
|
|
Back to top |
|
sirjames
Joined: 08 May 2008 Posts: 42
|
Posted: Fri Jan 29, 2010 1:52 am Post subject: |
|
|
Here's another log with the same incident ....
1/28/2010 1:12:36 PM ========================================
1/28/2010 1:12:36 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:12:36 PM Connect using GSM protocol
1/28/2010 1:12:36 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:12:37 PM ----------------------------------------
1/28/2010 1:12:37 PM Working on message to: g69266 from:
1/28/2010 1:12:37 PM Formatting message
1/28/2010 1:12:37 PM Message broken into 2 packets
1/28/2010 1:12:37 PM Sending packet
1/28/2010 1:12:37 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:12:37 PM Received:<CR><LF>>
1/28/2010 1:12:38 PM Sent:1of2:GRP/IM601253/Reassigned/P2/Concepcion/cdeandres@bogus.com/xxxxxxxxxx//01/22/2010 05:52:07/Compass - Duplicate Source number code/marketing/eu/bre<SUB>
1/28/2010 1:12:42 PM Received:<CR><LF>+CMGS: 139<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 1:12:42 PM Packet sent successfully
1/28/2010 1:12:42 PM Sending packet
1/28/2010 1:12:42 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:12:42 PM Received:<CR><LF>>
1/28/2010 1:12:42 PM Sent:2of2:ak fix/compass - eu<SUB>
1/28/2010 1:12:45 PM Received:<CR><LF>+CMGS: 140<CR><LF><CR><LF>OK<CR><LF>
1/28/2010 1:12:45 PM Packet sent successfully
1/28/2010 1:12:45 PM SUCCESSFUL Stn:5 To:g69266 Msg:GRP/IM601253/Reassigned/P2/Concepcion/cdeandres@bogus.com/xxxxxxxxxx//01/22/2010 05:52:07/Compass - Duplicate Source number code/marketing/eu/break fix/compass - eu
1/28/2010 1:15:46 PM ========================================
1/28/2010 1:15:46 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:15:46 PM Connect using GSM protocol
1/28/2010 1:15:46 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:15:47 PM ----------------------------------------
1/28/2010 1:15:47 PM Working on message to: os2034 from:
1/28/2010 1:15:47 PM Formatting message
1/28/2010 1:15:47 PM Message contained in a single packet
1/28/2010 1:15:47 PM Sending packet
1/28/2010 1:15:47 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:15:48 PM Received:<CR><LF>>
1/28/2010 1:15:48 PM Sent:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM59<SUB>
1/28/2010 1:16:18 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 1:16:18 PM Error sending packet
1/28/2010 1:17:19 PM ========================================
1/28/2010 1:17:19 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:17:19 PM Connect using GSM protocol
1/28/2010 1:17:19 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:17:19 PM ----------------------------------------
1/28/2010 1:17:19 PM Working on message to: os2034 from:
1/28/2010 1:17:19 PM Formatting message
1/28/2010 1:17:19 PM Message contained in a single packet
1/28/2010 1:17:19 PM Sending packet
1/28/2010 1:17:19 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:17:20 PM Received:<CR><LF>>
1/28/2010 1:17:20 PM Sent:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM59<SUB>
1/28/2010 1:17:50 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 1:17:50 PM Error sending packet
1/28/2010 1:18:56 PM ========================================
1/28/2010 1:18:56 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:18:56 PM Connect using GSM protocol
1/28/2010 1:18:56 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:18:56 PM ----------------------------------------
1/28/2010 1:18:56 PM Working on message to: os2034 from:
1/28/2010 1:18:56 PM Formatting message
1/28/2010 1:18:56 PM Message contained in a single packet
1/28/2010 1:18:56 PM Sending packet
1/28/2010 1:18:56 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:18:57 PM Received:<CR><LF>>
1/28/2010 1:18:57 PM Sent:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM59<SUB>
1/28/2010 1:19:27 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 1:19:27 PM Error sending packet
1/28/2010 1:20:32 PM ========================================
1/28/2010 1:20:32 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:20:32 PM Connect using GSM protocol
1/28/2010 1:20:32 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:20:33 PM ----------------------------------------
1/28/2010 1:20:33 PM Working on message to: os2034 from:
1/28/2010 1:20:33 PM Formatting message
1/28/2010 1:20:33 PM Message contained in a single packet
1/28/2010 1:20:33 PM Sending packet
1/28/2010 1:20:33 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:20:34 PM Received:<CR><LF>>
1/28/2010 1:20:34 PM Sent:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM59<SUB>
1/28/2010 1:21:04 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 1:21:04 PM Error sending packet
1/28/2010 1:21:04 PM Message retry limit reached
1/28/2010 1:21:04 PM FAILED Stn:5 To:os2034 Msg:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM598907/finance/pacific/release related/release strategy - pacific
1/28/2010 1:21:04 PM Module Stopped
1/28/2010 1:21:15 PM Module Started
1/28/2010 1:21:17 PM Time synchronized with scheduler
1/28/2010 1:21:26 PM ========================================
1/28/2010 1:21:26 PM Start connection to carrier: SMC_GSM_1
1/28/2010 1:21:26 PM Connect using GSM protocol
1/28/2010 1:21:26 PM Setting communication parameters (115200,n,8,1)
1/28/2010 1:21:26 PM ----------------------------------------
1/28/2010 1:21:26 PM Working on message to: os2034 from:
1/28/2010 1:21:26 PM Formatting message
1/28/2010 1:21:26 PM Message contained in a single packet
1/28/2010 1:21:26 PM Sending packet
1/28/2010 1:21:26 PM Sent:AT+CMGS="xxxxxxxxxx"<CR>
1/28/2010 1:21:27 PM Received:<CR><LF>>
1/28/2010 1:21:27 PM Sent:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM59<SUB>
1/28/2010 1:21:57 PM Received:<CR><LF>ERROR<CR><LF>
1/28/2010 1:21:57 PM Error sending packet
1/28/2010 1:21:57 PM Message retry limit reached
1/28/2010 1:21:57 PM FAILED Stn:5 To:os2034 Msg:GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@bogus.com/xxxxxxxxxx//01/28/10 00:20:07/[SR]Request for updating of I6-Capex Release Strategy - Adjustment of IM598907/finance/pacific/release related/release strategy - pacific
|
|
Back to top |
|
|