Comment # 2
on bug 9622
from Robert Gahan
(In reply to Luke Mewburn from comment #1)
> Would it be possible to provide a sample capture containing the complete
> TCAP transaction that reproduces the problem?
>
> If the TCAP transaction (session) is correctly matched then the Application
> Context in the TCAP BEGIN should result in Wireshark decoding the message
> correctly in the remaining packets in the transaction.
>
> For this to operate the TCAP "Service Response Time Analyse" preference
> needs to be set, and possibly the SCCP "Set Source and Destination GT
> Addresses" preference.
>
>
> (There are edge cases where the transaction matching doesn't correctly work,
> including when the called party in the TCAP BEGIN is changed as part of TCAP
> address confirmation in the first CONTINUE (or END), and I have some fixes
> I'm testing for that, but it's easier to prove with existing sample captures
> from existing bugs)
Will try to in the new future.
However, I would expect that by doing the following that the decode would work
File - > Preferences -> GSM_MAP -> Application Cintext Version "Treat as AC1"
So looks like problem is with schema ??
You are receiving this mail because:
- You are watching all bug changes.