Search found 42 matches

i don't think this is a carrier or modem issue ... the process is still within the pager. If i send the message manually, using the modem, there will be no issue. The only workaround I can see for now is to increase the maximum characters for the recipient, which would entail cost in the long run.

Btw, what version of PG are you using? I am using 5.0.8.

For some, especially if it's an international sms, i put that in but this is definitely not the cause of the fault though. With or without it the situation is the same... thanks

There is really something wrong when using the setup I mentioned above.

Can you try sending this message but before that please set your recipient settings to this settings...

RECIPIENT SETTINGS:
Type: Normal
Carrier: <whatever yours is..>
Failover: None
ID/PIN: <whatever yours is..>
Max Chars: 160
Notify Code: 999
Alpha: checked
Drop non-printable characters: checked

MESSAGE:
GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@ab.cd.com/11-1-1111-1111//01/28/10 00:20:07/Max Chars settings. Here are the results:
Max Chars set to 320 --- SUCCESSFUL
Max Chars set to 160 --- FAILED

Based on my testing today: The test message above will only fail if the max char is set to 160. This doesn't mean that if I set every recipient to 320, it will never happen because there is a message length where it will also fail.
But I want to know if you'll be able to replicate the same error on your setup. thanks

Can you try sending this message but before that please set your recipient settings to this settings...

RECIPIENT SETTINGS:
Type: Normal
Carrier: <whatever yours is..>
Failover: None
ID/PIN: <whatever yours is..>
Max Chars: 160
Notify Code: 999
Alpha: checked
Drop non-printable characters: checked

MESSAGE:
GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@ab.cd.com/11-1-1111-1111//01/28/10 00:20:07/Max Chars settings. Here are the results:
Max Chars set to 320 --- SUCCESSFUL
Max Chars set to 160 --- FAILED

Based on my testing today: The test message above will only fail if the max char is set to 160. This doesn't mean that if I set every recipient to 320, it will never happen because there is a message length where it will also fail.

But I want to know if you'll be able to replicate the same error on your setup. thanks

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

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

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.

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.

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

After many months of using the it ... I'm pretty sure that it is failing when a message contains this characters "[" and "]" ... Can you please test on your side and let me know of the results.

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

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

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

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

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

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.

Author	Message
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Tue Feb 02, 2010 12:30 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	i don't think this is a carrier or modem issue ... the process is still within the pager. If i send the message manually, using the modem, there will be no issue. The only workaround I can see for now is to increase the maximum characters for the recipient, which would entail cost in the long run. Btw, what version of PG are you using? I am using 5.0.8.
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Sun Jan 31, 2010 10:20 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	For some, especially if it's an international sms, i put that in but this is definitely not the cause of the fault though. With or without it the situation is the same... thanks There is really something wrong when using the setup I mentioned above.
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Fri Jan 29, 2010 8:12 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	....
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Fri Jan 29, 2010 2:26 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Can you try sending this message but before that please set your recipient settings to this settings... RECIPIENT SETTINGS: Type: Normal Carrier: <whatever yours is..> Failover: None ID/PIN: <whatever yours is..> Max Chars: 160 Notify Code: 999 Alpha: checked Drop non-printable characters: checked MESSAGE: GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@ab.cd.com/11-1-1111-1111//01/28/10 00:20:07/Max Chars settings. Here are the results: Max Chars set to 320 --- SUCCESSFUL Max Chars set to 160 --- FAILED Based on my testing today: The test message above will only fail if the max char is set to 160. This doesn't mean that if I set every recipient to 320, it will never happen because there is a message length where it will also fail. But I want to know if you'll be able to replicate the same error on your setup. thanks
Topic: PageGate fails to send a page due to the no. of chars
sirjames Replies: 13 Views: 25810	Forum: PageGate Support Posted: Fri Jan 29, 2010 2:26 am Subject: PageGate fails to send a page due to the no. of chars
sirjames Replies: 13 Views: 25810	Can you try sending this message but before that please set your recipient settings to this settings... RECIPIENT SETTINGS: Type: Normal Carrier: <whatever yours is..> Failover: None ID/PIN: <whatever yours is..> Max Chars: 160 Notify Code: 999 Alpha: checked Drop non-printable characters: checked MESSAGE: GRP/IM605470/Open/P2/Mitsuyoshi/mchikaoka@ab.cd.com/11-1-1111-1111//01/28/10 00:20:07/Max Chars settings. Here are the results: Max Chars set to 320 --- SUCCESSFUL Max Chars set to 160 --- FAILED Based on my testing today: The test message above will only fail if the max char is set to 160. This doesn't mean that if I set every recipient to 320, it will never happen because there is a message length where it will also fail. But I want to know if you'll be able to replicate the same error on your setup. thanks
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Fri Jan 29, 2010 1:52 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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: ...
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Thu Jan 28, 2010 11:00 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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 tota ...
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Thu Jan 28, 2010 10:37 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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.
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Thu Jan 28, 2010 9:03 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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.
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Wed Jan 27, 2010 12:12 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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
Topic: PageGate fails to send a page due to the no. of chars
sirjames Replies: 13 Views: 25810	Forum: PageGate Support Posted: Wed Jan 27, 2010 12:09 am Subject: PageGate fails to send a page due to the no. of chars
sirjames Replies: 13 Views: 25810	After many months of using the it ... I'm pretty sure that it is failing when a message contains this characters "[" and "]" ... Can you please test on your side and let me know of the results.
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Tue Sep 08, 2009 9:29 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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 .... ... 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
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Mon Sep 07, 2009 12:46 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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 .... ... 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
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Wed Sep 02, 2009 9:30 am Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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
Topic: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	Forum: PageGate Support Posted: Mon Aug 31, 2009 10:38 pm Subject: Connector Retries a message more than the no. of retries set
sirjames Replies: 20 Views: 50162	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.