How about you just paste it here or start a thread on it? Could more eyes hurt on it? Ive had some experience on these things and it could take lots of eyes and/or lateral thought to solve hard ones (Im no expert though). First make sure you've already tried the basics:
1) Make sure that the encrypted data contains enough bits to store a meaningful message, if it's not long enough then it's likely to be super hard to decrypt and/or not be useful (ie. if you only have a few digits, it's likely hopeless unless you have some idea what the data contains - the obelisk positions at beta site H group would be an example of too small of a data set).
2) Perform heuristic analysis on the content if you believe it's a cipher and you know the language it's written in. Different letters have different frequencies and you can construct a probability table of which bits of data likely correspond to which letters. #1 needs to be satisfied for a proper analysis to be constructed. Note this technique is useless if the cipher is not stateless. A lot of this legwork can be automated with tools likely available on the web.
PS. These ruins remind me of the san jose semaphore puzzle, read this if you're interested in learning some techniques with a cool case study
http://www.adobe.com/aboutadobe/philanthropy/sjsemaphore/pdf/decoding.pdf
No doubt you are aware that the active obelisks (glowing + flashy glyphs on them) seem to transmit a high-pitched (9Khz to 17Khz range) code of sorts. Based on over 3 hours of recording I have been able to see some rules to how the signals/codes are generated.
1) Each signal / code consists of 7 discernible smaller signals, or "tokens", as I call them, effectively forming a "string" of tokens.
2) Each string ends in a seemingly identical end sequence that looks different from the rest of the tokens. However, it appears that even these last blocks seem to differ *extremely* slightly (namely the very last token or part of the end signal seems to be made out of a varied amount of pulses).
3) Each string always has one of every token, which sets the smallest string length to 7 tokens + end block. (4 strings with 7 tokens all have shown to have 1 of every token - this is statistically significant. No string has been observed to be smaller than 7 tokens.) - I believe this is our clue to a common number, such as, for example, 0. Problem here being, the tokens seem to be in a randomized sequence.
4) No token can appear twice in a row.
5) Analysis shows, that the tokens seem to have a uniform spread in the long run.
6) There is no common divisor for the length of the strings, except number 1 (which tells us nothing).
At first glance, it looks like the strings are completely random sequences of tokens that simply follow those rules, however, it must be noted here, that another clue may be, that repeating sequences are more common than simple randomization would have it happen (EG. strings that look like this: "AEFEABABAGCD" (notice the ABABA) are not uncommon).
Furthermore, earlier today/yesterday a fellow commander said that in the christmas 24 hour livestream, it was hinted that there is an encrypted signal within the ruins that noone was able to break (I am guessing they were talking about the QA testers). I believe the obelisk audio signal is a custom-encrypted signal of sorts (my best guess is, that it contains numbers or glyph configurations, the former being more probable) with the key somewhere within the ruins or in the signal itself (end block?).
If you'd like to discuss this further then I suggest we get in touch over Discord or some other service for chatting - it didn't appear that many people were interested in breaking the code a few weeks ago/a week ago... and I would imagine the standing for the majority hasn't changed.