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/XCWGKGTB27W7TCEALG6Y3LFK6NKSFGM4/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "XCWGKGTB27W7TCEALG6Y3LFK6NKSFGM4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SG5MUL47T5HKC7YQ5HMCZEHGWNEQ56BB/",
    "sender": {
        "address": "w8eh.ernie (a) gmail.com",
        "mailman_id": "7a040161827a4a5db92c1f01c6b2e908",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/7a040161827a4a5db92c1f01c6b2e908/emails/"
    },
    "sender_name": "Ernie Howard",
    "subject": "[amsat-bb] Re: Terrestrial QRM to FM satellites",
    "date": "2007-09-21T02:17:41Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/MBOH6ZZVRR6IATZOOTHQZEKJUB7RB3GD/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "It seems that we have been down this road before......\n\nThe short data burst is not paging. The 'squawk' that seems to be at the end \nof the 'offenders' individual transmissions in the first part of the clip is \nrecognizable to me. It is 1200 baud, and from the sound/duration it is \nMotorola MDC1200 coding. The MDC1200 is used for ID and status on public \nsafety and other systems. Several hams in my area have taken to using the \nMotorola radios with the MDC1200 system to ID and contact each other \n(selective calling, status, emergency, etc.). It is not likely that it would \ngive us much info to go on, if we could decode it. The MDC 1200 system uses \nhex number data, it is not ASCII. The data, when decoded on another radio \nwill be a 4 digit number. There is a short write up (and sound samples) on:\nhttp://en.wikipedia.org/wiki/MDC-1200\n\nAnother possibility is that someone has established a simplex Echolink \nsystem on the uplink. That may be why some have reported a CW id, and the \ncarrier hanging on for longer than a normal simplex transmission.\n\nPerhaps someone with AMSAT could contact the ARRL Official Observer \ncoordinator. They have been known to send out requests for the OO corps to \nlisten for specific interference problems. This might be important enough to \nget all ears listening. I don't hear it here.\n\n73 Ernie W8EH\n\n\nBruce Robertson wrote:\n\n> Once I started hearing this QRM while listening to AO-27, I recorded the\n> tail-end of the 20:00Z pass. Interested persons may download a mp3 file at\n> http://heml.mta.ca/Amsat/ (There is no promise that this link will be in\n> place for a long time.)\n> \n> Besides the beeps and long periods of carrier-induced silence, there are\n> some conversational snippets which seem to me from native English speakers.\n> One of the amateurs on the bird suggested the QRM comes from a pager, and I\n> labeled the file as such, but I don't mean to suggest that this\n> identification is secure. \n\n\n-- \n\n------------------------------------------------------\nErnie Howard, Jr    W8EH    Middletown, Ohio\nE-mail: [email protected]\n------------------------------------------------------\n",
    "attachments": []
}