Search found 5 matches

Hello Everyone.

We finally solved this issue by checking the “Drop non-printable characters” checkbox in the TAP protocol section in the PageGate Admin.

Thanks all for your time reading our issue.

I will try to post another message today and copy all the messages communication in the terminal and I'll post it here.

And I got this tip from one of our colleague:

===
Reference to the log file of a successful TAP transaction between the Page Gate Server and the Model 2700 terminal, it is noted when an alphanumeric page is initiated from the Page Gate ‘Admin’ application, it is not sending any ‘control character’ (indicated by <SUB> / or HEX 1A).

As per TAP 1.8 protocol ‘SUB’ has written something about the ‘control character’ as per the below:

‘If a control character which would cause a protocol conflict must be transmitted within the packet, the originator must perform ‘transparency insertion’ to make the control character transparent to the protocol. This is done by converting the control byte to two bytes consisting of a SUB (Hex 1A) character followed by the printable ASCII character formed by adding Hex 40 to the ASCII value of the control character to be sent’.
- TAP PROTOCOL Version 1.8 pp. 6

From the above it seems that there is an issue of protocol conflict caused by control character insertion within the packet on pages initiated from the Web Page application.
===

Hello Everyoe,

The message both appears in the Terminal console, but it seems all the messages from all the module of PageGate, including the getAscii and webgate are not being forwarded to pager, only messages from the PageGate Admin are forwarded, and we are using a TAP connection.

Right now we temporarily swithched to the old model terminal, using a modem connection and it all work as fine.

But we really need to use the new model 2700 because our old terminal are not supporting pager numbers from 4000 and above.

And that's the reason we upgrade... Do you think PageGate 4.0 are not compatible with the model 2700?

Dear TechSupport,

We are having the following issue, please advice:

1.) An alphanumeric page initiated from the Page Gate ‘Admin’ application is successfully processed by the Model 2700 paging terminal.

2.) An alphanumeric page initiated from the Page Gate ‘Web Page’ application is NOT processed by the Model 2700 paging terminal, although the Model 2700 acknowledges with ‘page accepted’ response to the Page Gate application through the TAP protocol.

Below are 2 log files, 1 for a successful TAP transaction between the Page Gate ‘Admin’ application and the Model 2700 terminal and another log file of the TAP transaction between the Page Gate ‘Web Page’ and the Model 2700 terminal.

PageGate Admin Log:
==============

3/3/2008 4:20:48 PM ========================================
3/3/2008 4:20:48 PM ========================================
3/3/2008 4:20:48 PM Start connection to carrier: kfmc
3/3/2008 4:20:48 PM Connect using TAP protocol
3/3/2008 4:20:48 PM Setting communication parameters
3/3/2008 4:20:48 PM Connected to carrier
3/3/2008 4:20:48 PM Waiting for protocol initialization
3/3/2008 4:20:48 PM Sent:<CR>
3/3/2008 4:20:51 PM Sent:<CR>
3/3/2008 4:20:52 PM Received:ID=
3/3/2008 4:20:52 PM TAP protocol detected
3/3/2008 4:20:52 PM Sent:<ESC>PG1<CR>
3/3/2008 4:20:53 PM Received:<CR><CR><ACK><CR>110 1.8114 Please proceed....<CR><ESC>[p<CR>
3/3/2008 4:20:54 PM Received:<CR><CR><ACK><CR>110 1.8114 Please proceed....<CR><ESC>[p<CR>
3/3/2008 4:20:54 PM Automatic TAP mode accepted
3/3/2008 4:20:54 PM ----------------------------------------
3/3/2008 4:20:54 PM Working on message to: 9999 from: TestSender
3/3/2008 4:20:54 PM Formatting message
3/3/2008 4:20:54 PM Message contained in single packet
3/3/2008 4:20:54 PM Message contained in single block
3/3/2008 4:20:54 PM Sending block
3/3/2008 4:20:54 PM Sen ...

Author	Message
Topic: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Forum: PageGate Support Posted: Thu Mar 06, 2008 5:43 am Subject: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Hello Everyone. We finally solved this issue by checking the “Drop non-printable characters” checkbox in the TAP protocol section in the PageGate Admin. Thanks all for your time reading our issue.
Topic: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Forum: PageGate Support Posted: Wed Mar 05, 2008 11:16 pm Subject: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	I will try to post another message today and copy all the messages communication in the terminal and I'll post it here.
Topic: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Forum: PageGate Support Posted: Wed Mar 05, 2008 11:09 pm Subject: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	And I got this tip from one of our colleague: === Reference to the log file of a successful TAP transaction between the Page Gate Server and the Model 2700 terminal, it is noted when an alphanumeric page is initiated from the Page Gate ‘Admin’ application, it is not sending any ‘control character’ (indicated by <SUB> / or HEX 1A). As per TAP 1.8 protocol ‘SUB’ has written something about the ‘control character’ as per the below: ‘If a control character which would cause a protocol conflict must be transmitted within the packet, the originator must perform ‘transparency insertion’ to make the control character transparent to the protocol. This is done by converting the control byte to two bytes consisting of a SUB (Hex 1A) character followed by the printable ASCII character formed by adding Hex 40 to the ASCII value of the control character to be sent’. - TAP PROTOCOL Version 1.8 pp. 6 From the above it seems that there is an issue of protocol conflict caused by control character insertion within the packet on pages initiated from the Web Page application. ===
Topic: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Forum: PageGate Support Posted: Wed Mar 05, 2008 11:03 pm Subject: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Hello Everyoe, The message both appears in the Terminal console, but it seems all the messages from all the module of PageGate, including the getAscii and webgate are not being forwarded to pager, only messages from the PageGate Admin are forwarded, and we are using a TAP connection. Right now we temporarily swithched to the old model terminal, using a modem connection and it all work as fine. But we really need to use the new model 2700 because our old terminal are not supporting pager numbers from 4000 and above. And that's the reason we upgrade... Do you think PageGate 4.0 are not compatible with the model 2700?
Topic: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Forum: PageGate Support Posted: Wed Mar 05, 2008 6:18 am Subject: Page Gate Server / Model 2700 TAP Connectivity Issue
gnome2008 Replies: 8 Views: 24616	Dear TechSupport, We are having the following issue, please advice: 1.) An alphanumeric page initiated from the Page Gate ‘Admin’ application is successfully processed by the Model 2700 paging terminal. 2.) An alphanumeric page initiated from the Page Gate ‘Web Page’ application is NOT processed by the Model 2700 paging terminal, although the Model 2700 acknowledges with ‘page accepted’ response to the Page Gate application through the TAP protocol. Below are 2 log files, 1 for a successful TAP transaction between the Page Gate ‘Admin’ application and the Model 2700 terminal and another log file of the TAP transaction between the Page Gate ‘Web Page’ and the Model 2700 terminal. PageGate Admin Log: ============== 3/3/2008 4:20:48 PM ======================================== 3/3/2008 4:20:48 PM ======================================== 3/3/2008 4:20:48 PM Start connection to carrier: kfmc 3/3/2008 4:20:48 PM Connect using TAP protocol 3/3/2008 4:20:48 PM Setting communication parameters 3/3/2008 4:20:48 PM Connected to carrier 3/3/2008 4:20:48 PM Waiting for protocol initialization 3/3/2008 4:20:48 PM Sent:<CR> 3/3/2008 4:20:51 PM Sent:<CR> 3/3/2008 4:20:52 PM Received:ID= 3/3/2008 4:20:52 PM TAP protocol detected 3/3/2008 4:20:52 PM Sent:<ESC>PG1<CR> 3/3/2008 4:20:53 PM Received:<CR><CR><ACK><CR>110 1.8114 Please proceed....<CR><ESC>[p<CR> 3/3/2008 4:20:54 PM Received:<CR><CR><ACK><CR>110 1.8114 Please proceed....<CR><ESC>[p<CR> 3/3/2008 4:20:54 PM Automatic TAP mode accepted 3/3/2008 4:20:54 PM ---------------------------------------- 3/3/2008 4:20:54 PM Working on message to: 9999 from: TestSender 3/3/2008 4:20:54 PM Formatting message 3/3/2008 4:20:54 PM Message contained in single packet 3/3/2008 4:20:54 PM Message contained in single block 3/3/2008 4:20:54 PM Sending block 3/3/2008 4:20:54 PM Sen ...