Thanks Thanks:  0
Showing results 1 to 3 of 3

Thread: Arieso & GPEH OSS

  1. #1
    Member Reputation: 514
    Join Date
    2013-02-20
    Posts
    221


    Default Arieso & GPEH OSS

    Hi,

    I recently troubleshoot a case. I used 2 tool Arieso and E** decoder.pl.
    I used Arieso by searching in "Individual call legs with RF condition", and I found the rootcause is related to 1 IMSI.
    Later on I was thinking to use E** decoder.pl and get the GPEH bin file on a specific MP that handle the cell that having issue.
    When I decode GPEH it was showing correct cell, but what make me confused is that it's not showing that IMSI like arieso shows.
    Please do anyone knows if Arieso is only using GPEH trace or they used something else?
    And why is the result trace of Arieso and GPEH being decoded is different? I collect the GPEH in same hour.

    gambar.jpg

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Moderator Reputation: 473
    Join Date
    2009-05-02
    Location
    Nearby
    Posts
    1,237


    Default Re: Arieso & GPEH OSS

    Quote Originally Posted by uchok View Post
    Hi,

    I recently troubleshoot a case. I used 2 tool Arieso and E** decoder.pl.
    I used Arieso by searching in "Individual call legs with RF condition", and I found the rootcause is related to 1 IMSI.
    Later on I was thinking to use E** decoder.pl and get the GPEH bin file on a specific MP that handle the cell that having issue.
    When I decode GPEH it was showing correct cell, but what make me confused is that it's not showing that IMSI like arieso shows.
    Please do anyone knows if Arieso is only using GPEH trace or they used something else?
    And why is the result trace of Arieso and GPEH being decoded is different? I collect the GPEH in same hour.

    gambar.jpg
    Hi,

    Arieso uses several messages then correlating UeRef with IMSI which user registered in the network that's why at the end of analysis you have the IMSI number decoder simply decode the messages and does not correlate the information with other messages thus it can not show the IMSI straight forward. In a single word Arieso doing analysis on GPEH as well as decoding not same as decoder only decode the information. Hope it helps you .


    Cheers

  4. #3
    Member Reputation: 514
    Join Date
    2013-02-20
    Posts
    221


    Default Re: Arieso & GPEH OSS

    Hi Electron,

    Thanks for replying.
    What if I don't correlate this with IMSI. But I'm trying to correlate it with the failure code, as in my example, it has failure code "PROCEDURE_TIMEOUT".
    I tried to find this fault code in GPEH log that was decoded by decoder.pl, but I don't find any.
    Right now it seems I only find the usefull of the decoded GPEH is for finding missing neighbor. I want to know why the decoded GPEH don't show such failure code "PROCEDURE_TIMEOUT".
    I want to know whether Arieso is using other traces that make it able to show "PROCEDURE_TIMEOUT".


    Quote Originally Posted by electron View Post
    Hi,

    Arieso uses several messages then correlating UeRef with IMSI which user registered in the network that's why at the end of analysis you have the IMSI number decoder simply decode the messages and does not correlate the information with other messages thus it can not show the IMSI straight forward. In a single word Arieso doing analysis on GPEH as well as decoding not same as decoder only decode the information. Hope it helps you .


    Cheers

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •