Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WALJFHR3NSTUORPCT45MEUBMTWUDIEY7/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "WALJFHR3NSTUORPCT45MEUBMTWUDIEY7",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/M66TQD3W3X7GQII6UFHIJEQFLYN3N772/?format=api",
    "sender": {
        "address": "vu3tyg (a) yahoo.co.in",
        "mailman_id": "ffb9caab06b3489aa9d16edd32c0d3b9",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ffb9caab06b3489aa9d16edd32c0d3b9/emails/?format=api"
    },
    "sender_name": "Nitin Muttin",
    "subject": "Re: [amsat-bb] Non standard APRS implementation in AI SAT",
    "date": "2019-04-08T18:52:36Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/M66TQD3W3X7GQII6UFHIJEQFLYN3N772/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "We have not reached out to aprs.fi to show the APRS activity from  AISAT-1 heard by satgates. We have reached out to findu.com for the same. If we are missing something please advice.\n73\nNitin [VU3TYG] \n\n    On Monday, 8 April, 2019, 8:47:17 pm IST, John Langner WB2OSZ via AMSAT-BB <[email protected]> wrote:  \n \n \n\nThere was a discussion, in another group, about why nothing from AISAT was getting showing up on aprs.fi.\n\nK4KDR provided some samples of the signals so they could be analyzed.\n\nThe direwolf \"-dp\" option was used to produce a hexadecimal dump, of the frame, so we could see what is going on.\n\n\n---------------------------------\n\nNotice the extra comma after the last address.\n\n \n K4KDR-6>CQ,AISAT*,::CQ-0    :=3747.66N/07736.67W`de K4KDR [email protected] Virginia  FM17es{847\n------\nU frame UI: p/f=0, No layer 3 protocol implemented., length = 111\n dest    CQ      0 c/r=0 res=3 last=0\n source  K4KDR  6 c/r=0 res=3 last=0\n digi 1  AISAT*  0  h=0 res=3 last=0    <--  The “h” bit indicates that the\n                                          digipeater address has been used\n                                          It should be 1 in this case.  There should NOT be\n                                          the * character in the address field.\n                                                                                                                                                                                \n digi 2          0  h=0 res=3 last=1\n \n \nI reformatted this so the bytes would be in groups of 7 so it is easier to read.\n \n  000:  86 a2 40 40 40 40 60          “CQ”      \n            96 68 96 88 a4 40 6c      “K4KDR”  SSID 6\n            82 92 a6 82 a8 54 60      “AISAT*”      <--  WRONG!!!!!\n        \n                                            The * character is used only for the\n                                            human readable monitoring format.\n                                            It should not be a character in the\n                                            station address.\n \n        40 40 40 40 40 40 61          “      “      WRONG!!!  Field should not\n                                                be here if not needed.\n        03 f0                                    expected control, protocol\n        3a 43                                                                                      :C\n  020:  51 2d 30 20 20 20 20 20 3a 3d 33 37 34 37 2e 36  Q-0    :=3747.6\n  030:  36 4e 2f 30 37 37 33 36 2e 36 37 57 60 64 65 20  6N/07736.67W`de\n  040:  4b 34 4b 44 52 20 73 63 6f 74 74 32 33 31 39 32  K4KDR scott23192\n  050:  40 67 6d 61 69 6c 2e 63 6f 6d 20 56 69 72 67 69  @gmail.com Virgi\n  060:  6e 69 61 20 20 46 4d 31 37 65 73 7b 38 34 37    nia  FM17es{847\n \n \n-----------------------------------\n\nThis is my analysis:\n\n(1) Digipeating does not work normally.  A digipeater should only change the via path.  The information part should not be changed.  Why is it converted into “message” format?\n\n(2) Only the needed digipeater fields should be present.  If they are not needed leave them out.  Don’t fill them with blanks.\n\n(3) A station address should never contain the * character.  That is only in the human readable standard monitoring format.  The * after a station indicates that the H bit is set.\n\n(4) When a digipeater uses up an address in the via path, it must set the “H” bit to 1.  If it responded to an alias, it should substitute its own callsign.\n\nHere is an example of expected behavior:\n\nK4KDR-6>CQ,ARISS:=3747.66N/07736.67W`de K4KDR [email protected] Virginia  FM17es\nK4KDR-6>CQ,RS0ISS*:=3747.66N/07736.67W`de K4KDR [email protected] Virginia  FM17es\n\n- ARISS is recognized as an alias by RS0ISS.\n- RS0ISS substitutes its own call and marks that digipeater field as being used.\n- The * is not a character in the address.  It is the human readable way to indicate that the “H” bit is set.\n- Only the via path is changed.\n- The Information part is not changed at all.\n\n\n\n------------------\n  \n73,\nJohn WB2OSZ\n\n_______________________________________________\nSent via [email protected]. AMSAT-NA makes this open forum available\nto all interested persons worldwide without requiring membership. Opinions expressed\nare solely those of the author, and do not reflect the official views of AMSAT-NA.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n  \n",
    "attachments": []
}