Loading ...
Sorry, an error occurred while loading the content.

Re: [BPQ32] Protocol Error receiving message from Airmail.

Expand Messages
  • Dave Webb
    I also was unable to duplicate the error. I ll write Jim and ask him how he sends out a message from Airmail to make it show up to me as a bulletin. 73 Dave
    Message 1 of 31 , Oct 22, 2011
    • 0 Attachment
      I also was unable to duplicate the error. I'll write Jim and ask him how he sends out a message from Airmail to make it show up to me as a bulletin.
      73
      Dave


      On 10/22/2011 10:26 AM, John Wiseman wrote:  

      Dave,
       
      I can't get it to fail here, though I'm using Airmail 3.3.081.
       
      Is this using packet or pactor?
       
      And does it fail on all messages?
       
      Thanks,
      John
       
       
       


      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Dave Webb
      Sent: 22 October 2011 01:44
      To: BPQ32@yahoogroups.com
      Subject: [BPQ32] Protocol Error receiving message from Airmail.

       

      John,
      I now get a protocol error when receiving messages from an Airmail station.
      I back of a version and the message comes in OK.
      73
      Dave
      AFA2HV / WB2HVF

      Log portion below.......

      111022 00:03:56 |AFB2MC Incoming Connect from AFB2MC
      111022 00:03:56 >AFB2MC [BPQ-1.0.4.45-B2FWIHJM$]
      111022 00:03:56 >AFB2MC HELLO Jim.
      111022 00:03:56 >AFB2MC de AFC2MC>
      111022 00:04:32 <AFB2MC [AirMail-3.3.080-B2FHIM$]
      111022 00:04:39 <AFB2MC ; AFC2MC de AFB2MC QTC: 1 2846 1470
      111022 00:04:40 <AFB2MC FC EM ARLP_11042 2846 1470 0
      111022 00:04:42 <AFB2MC F> E2
      111022 00:04:42 >AFB2MC FS Y
      111022 00:05:49 >AFB2MC *** Protocol Error - Invalid Binary Message
      Format (Invalid Message Type)
      111022 00:05:51 |AFB2MC Disconnect received from AFB2MC during Binary
      Transfer - 500 Bytes Saved for restart
      111022 00:05:51 |AFB2MC AFB2MC Disconnected

      Now same message on the previous version.
      (Note: AFE3MC is set up for immediate forwarding via AXIP)

      111022 00:28:24 |AFB2MC Incoming Connect from AFB2MC
      111022 00:28:24 >AFB2MC [BPQ-1.0.4.40-B2FWIHJM$]
      111022 00:28:24 >AFB2MC HELLO Jim.
      111022 00:28:24 >AFB2MC de AFC2MC>
      111022 00:28:47 <AFB2MC [AirMail-3.3.080-B2FHIM$]
      111022 00:28:48 <AFB2MC ; AFC2MC de AFB2MC QTC: 1 2846 1470
      111022 00:28:51 <AFB2MC FC EM ARLP_11042 2846 1470 0
      111022 00:28:51 <AFB2MC F> E2
      111022 00:28:51 >AFB2MC FS Y
      111022 00:31:44 |AFB2MC Uncompressing Message Comp Len 1470 Msg Len
      2846 CRC ae4
      111022 00:31:44 ?AFB2MC B2 Msg To: PROP@SOLAR
      111022 00:31:44 ?AFB2MC Msg 22712 Routing Trace To PROP Via SOLAR
      111022 00:31:44 ?AFB2MC Routing Trace Type B (Flood) TO PROP VIA
      SOLAR Route On SOLAR (null) (null) (null) (null)
      111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFB2MC
      111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFC2MC
      111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFC4MC
      111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFE3MC
      111022 00:31:44 >AFB2MC FF
      111022 00:31:50 |AFE3MC Connecting to BBS AFE3MC
      111022 00:31:50 <AFE3MC *** CONNECTED
      111022 00:31:50 >AFE3MC C 4 AFE3MC-1
      111022 00:31:51 <AFE3MC NJBEV:AFC2MC-2} Connected to WMSBR1:AFE3MC-1
      111022 00:31:51 >AFE3MC C AFE3MC
      111022 00:31:52 <AFE3MC WMSBR1:AFE3MC-1} Connected to BBS
      111022 00:31:53 <AFE3MC [BPQ-1.0.4.40-BFWIHJM$]
      111022 00:31:53 <AFE3MC de AFE3MC>
      111022 00:31:53 >AFE3MC [BPQ-1.0.4.40-BFIHJM$]
      111022 00:31:53 >AFE3MC FA B AFB2MC SOLAR PROP ARLP_11042 2900
      111022 00:31:53 >AFE3MC F> CC
      111022 00:31:54 <AFB2MC FQ
      111022 00:31:54 |AFB2MC AFB2MC Disconnected
      111022 00:31:54 <AFE3MC FS +
      111022 00:31:54 | Compressed Message Comp Len 1462 Msg Len 2749
      CRC 2f98
      111022 00:31:56 <AFE3MC FF
      111022 00:31:56 >AFE3MC FQ
      111022 00:31:58 |AFE3MC AFE3MC Disconnected

    • Dave Webb
      I also was unable to duplicate the error. I ll write Jim and ask him how he sends out a message from Airmail to make it show up to me as a bulletin. 73 Dave
      Message 31 of 31 , Oct 22, 2011
      • 0 Attachment
        I also was unable to duplicate the error. I'll write Jim and ask him how he sends out a message from Airmail to make it show up to me as a bulletin.
        73
        Dave


        On 10/22/2011 10:26 AM, John Wiseman wrote:  

        Dave,
         
        I can't get it to fail here, though I'm using Airmail 3.3.081.
         
        Is this using packet or pactor?
         
        And does it fail on all messages?
         
        Thanks,
        John
         
         
         


        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Dave Webb
        Sent: 22 October 2011 01:44
        To: BPQ32@yahoogroups.com
        Subject: [BPQ32] Protocol Error receiving message from Airmail.

         

        John,
        I now get a protocol error when receiving messages from an Airmail station.
        I back of a version and the message comes in OK.
        73
        Dave
        AFA2HV / WB2HVF

        Log portion below.......

        111022 00:03:56 |AFB2MC Incoming Connect from AFB2MC
        111022 00:03:56 >AFB2MC [BPQ-1.0.4.45-B2FWIHJM$]
        111022 00:03:56 >AFB2MC HELLO Jim.
        111022 00:03:56 >AFB2MC de AFC2MC>
        111022 00:04:32 <AFB2MC [AirMail-3.3.080-B2FHIM$]
        111022 00:04:39 <AFB2MC ; AFC2MC de AFB2MC QTC: 1 2846 1470
        111022 00:04:40 <AFB2MC FC EM ARLP_11042 2846 1470 0
        111022 00:04:42 <AFB2MC F> E2
        111022 00:04:42 >AFB2MC FS Y
        111022 00:05:49 >AFB2MC *** Protocol Error - Invalid Binary Message
        Format (Invalid Message Type)
        111022 00:05:51 |AFB2MC Disconnect received from AFB2MC during Binary
        Transfer - 500 Bytes Saved for restart
        111022 00:05:51 |AFB2MC AFB2MC Disconnected

        Now same message on the previous version.
        (Note: AFE3MC is set up for immediate forwarding via AXIP)

        111022 00:28:24 |AFB2MC Incoming Connect from AFB2MC
        111022 00:28:24 >AFB2MC [BPQ-1.0.4.40-B2FWIHJM$]
        111022 00:28:24 >AFB2MC HELLO Jim.
        111022 00:28:24 >AFB2MC de AFC2MC>
        111022 00:28:47 <AFB2MC [AirMail-3.3.080-B2FHIM$]
        111022 00:28:48 <AFB2MC ; AFC2MC de AFB2MC QTC: 1 2846 1470
        111022 00:28:51 <AFB2MC FC EM ARLP_11042 2846 1470 0
        111022 00:28:51 <AFB2MC F> E2
        111022 00:28:51 >AFB2MC FS Y
        111022 00:31:44 |AFB2MC Uncompressing Message Comp Len 1470 Msg Len
        2846 CRC ae4
        111022 00:31:44 ?AFB2MC B2 Msg To: PROP@SOLAR
        111022 00:31:44 ?AFB2MC Msg 22712 Routing Trace To PROP Via SOLAR
        111022 00:31:44 ?AFB2MC Routing Trace Type B (Flood) TO PROP VIA
        SOLAR Route On SOLAR (null) (null) (null) (null)
        111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFB2MC
        111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFC2MC
        111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFC4MC
        111022 00:31:44 ?AFB2MC Routing Trace AT PROP Matches BBS AFE3MC
        111022 00:31:44 >AFB2MC FF
        111022 00:31:50 |AFE3MC Connecting to BBS AFE3MC
        111022 00:31:50 <AFE3MC *** CONNECTED
        111022 00:31:50 >AFE3MC C 4 AFE3MC-1
        111022 00:31:51 <AFE3MC NJBEV:AFC2MC-2} Connected to WMSBR1:AFE3MC-1
        111022 00:31:51 >AFE3MC C AFE3MC
        111022 00:31:52 <AFE3MC WMSBR1:AFE3MC-1} Connected to BBS
        111022 00:31:53 <AFE3MC [BPQ-1.0.4.40-BFWIHJM$]
        111022 00:31:53 <AFE3MC de AFE3MC>
        111022 00:31:53 >AFE3MC [BPQ-1.0.4.40-BFIHJM$]
        111022 00:31:53 >AFE3MC FA B AFB2MC SOLAR PROP ARLP_11042 2900
        111022 00:31:53 >AFE3MC F> CC
        111022 00:31:54 <AFB2MC FQ
        111022 00:31:54 |AFB2MC AFB2MC Disconnected
        111022 00:31:54 <AFE3MC FS +
        111022 00:31:54 | Compressed Message Comp Len 1462 Msg Len 2749
        CRC 2f98
        111022 00:31:56 <AFE3MC FF
        111022 00:31:56 >AFE3MC FQ
        111022 00:31:58 |AFE3MC AFE3MC Disconnected

      Your message has been successfully submitted and would be delivered to recipients shortly.