2005-06-07 05:49:06 +00:00
|
|
|
/* Do not modify this file. */
|
2006-05-24 12:24:54 +00:00
|
|
|
/* It is created automatically by the ASN.1 to Wireshark dissector compiler */
|
2007-08-24 07:12:04 +00:00
|
|
|
/* ./packet-tcap.h */
|
2006-05-24 12:24:54 +00:00
|
|
|
/* ../../tools/asn2wrs.py -b -e -p tcap -c tcap.cnf -s packet-tcap-template tcap.asn */
|
2005-06-07 05:49:06 +00:00
|
|
|
|
|
|
|
/* Input file: packet-tcap-template.h */
|
|
|
|
|
2005-12-08 23:29:21 +00:00
|
|
|
#line 1 "packet-tcap-template.h"
|
2003-10-02 06:13:29 +00:00
|
|
|
/* packet-tcap.h
|
|
|
|
*
|
2004-07-18 00:24:25 +00:00
|
|
|
* $Id$
|
2003-10-02 06:13:29 +00:00
|
|
|
*
|
2005-06-07 05:49:06 +00:00
|
|
|
* Copyright 2004, Tim Endean <endeant@hotmail.com>
|
2003-10-02 06:13:29 +00:00
|
|
|
*
|
2006-05-21 04:49:01 +00:00
|
|
|
* Wireshark - Network traffic analyzer
|
|
|
|
* By Gerald Combs <gerald@wireshark.org>
|
2003-10-02 06:13:29 +00:00
|
|
|
* Copyright 1998 Gerald Combs
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
* as published by the Free Software Foundation; either version 2
|
|
|
|
* of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
*/
|
|
|
|
|
2004-03-19 07:54:58 +00:00
|
|
|
|
2005-06-07 05:49:06 +00:00
|
|
|
#ifndef PACKET_tcap_H
|
|
|
|
#define PACKET_tcap_H
|
2004-03-19 07:54:58 +00:00
|
|
|
/* TCAP component type */
|
|
|
|
#define TCAP_COMP_INVOKE 0xa1
|
|
|
|
#define TCAP_COMP_RRL 0xa2
|
|
|
|
#define TCAP_COMP_RE 0xa3
|
|
|
|
#define TCAP_COMP_REJECT 0xa4
|
|
|
|
#define TCAP_COMP_RRN 0xa7
|
|
|
|
|
2005-06-07 05:49:06 +00:00
|
|
|
|
2004-03-19 07:54:58 +00:00
|
|
|
#define ANSI_TC_INVOKE_L 0xe9
|
|
|
|
#define ANSI_TC_RRL 0xea
|
|
|
|
#define ANSI_TC_RE 0xeb
|
|
|
|
#define ANSI_TC_REJECT 0xec
|
|
|
|
#define ANSI_TC_INVOKE_N 0xed
|
|
|
|
#define ANSI_TC_RRN 0xee
|
|
|
|
|
2007-04-03 19:08:00 +00:00
|
|
|
|
2004-03-19 07:54:58 +00:00
|
|
|
#define TCAP_SEQ_TAG 0x30
|
|
|
|
#define TCAP_SET_TAG 0x31
|
|
|
|
|
|
|
|
#define TCAP_INVOKE_ID_TAG 0x02
|
|
|
|
#define TCAP_LINKED_ID_TAG 0x80
|
|
|
|
|
2007-07-27 19:24:40 +00:00
|
|
|
#define TCAP_EOC_LEN 2
|
2004-03-19 07:54:58 +00:00
|
|
|
|
|
|
|
#define TCAP_CONSTRUCTOR(TCtag) (TCtag & 0x20)
|
|
|
|
|
From Florent Drouin:
Here are some patches and a new module to introduce the notion of Tcap context for a Tcap transaction. For each Tcap transaction, several parameters, like session identifier, start time or OID, will be saved in a hash table, to keep these informations available for the next messages. This context is then given to the upper layer, and can be used, for example, to generate transaction-associated statistics.
Moreover, the Upper protocol, detected in the Begin of the TCAP transaction ( according to the OID ), is saved in the context, and will be reused for the next messages of the transaction. This help the decoding of SS7 messages, without any SSN configuration in the "wireshark preferences".
You will have too, the possibility to apply a filter to see only the messages related to a TCAP transaction. (tcap.srt.session_id=XXX)
To enable the use of the Tcap context, you have 2 new parameters in the preferences,
- SRT, enable search for a Tcap context for any TCAP messages
- persistentSRT, keep the Tcap context, even after the transaction has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
There is 2 new timers in the preferences for the statistics, to tune the retransmission timeout, and messages lost timeout.
svn path=/trunk/; revision=19341
2006-09-27 20:06:06 +00:00
|
|
|
#define TC_BEGIN 1
|
|
|
|
#define TC_CONT 2
|
|
|
|
#define TC_END 3
|
|
|
|
#define TC_ABORT 4
|
2007-07-27 19:24:40 +00:00
|
|
|
#define TC_ANSI_ABORT 5
|
|
|
|
#define TC_ANSI_ALL 6
|
From Florent Drouin:
Here are some patches and a new module to introduce the notion of Tcap context for a Tcap transaction. For each Tcap transaction, several parameters, like session identifier, start time or OID, will be saved in a hash table, to keep these informations available for the next messages. This context is then given to the upper layer, and can be used, for example, to generate transaction-associated statistics.
Moreover, the Upper protocol, detected in the Begin of the TCAP transaction ( according to the OID ), is saved in the context, and will be reused for the next messages of the transaction. This help the decoding of SS7 messages, without any SSN configuration in the "wireshark preferences".
You will have too, the possibility to apply a filter to see only the messages related to a TCAP transaction. (tcap.srt.session_id=XXX)
To enable the use of the Tcap context, you have 2 new parameters in the preferences,
- SRT, enable search for a Tcap context for any TCAP messages
- persistentSRT, keep the Tcap context, even after the transaction has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
There is 2 new timers in the preferences for the statistics, to tune the retransmission timeout, and messages lost timeout.
svn path=/trunk/; revision=19341
2006-09-27 20:06:06 +00:00
|
|
|
|
|
|
|
struct tcap_private_t {
|
|
|
|
gboolean acv; /* Is the Application Context Version present */
|
|
|
|
void * oid;
|
|
|
|
guint32 session_id;
|
|
|
|
void * context;
|
2007-01-01 22:03:01 +00:00
|
|
|
gchar *TransactionID_str;
|
From Florent Drouin:
Here are some patches and a new module to introduce the notion of Tcap context for a Tcap transaction. For each Tcap transaction, several parameters, like session identifier, start time or OID, will be saved in a hash table, to keep these informations available for the next messages. This context is then given to the upper layer, and can be used, for example, to generate transaction-associated statistics.
Moreover, the Upper protocol, detected in the Begin of the TCAP transaction ( according to the OID ), is saved in the context, and will be reused for the next messages of the transaction. This help the decoding of SS7 messages, without any SSN configuration in the "wireshark preferences".
You will have too, the possibility to apply a filter to see only the messages related to a TCAP transaction. (tcap.srt.session_id=XXX)
To enable the use of the Tcap context, you have 2 new parameters in the preferences,
- SRT, enable search for a Tcap context for any TCAP messages
- persistentSRT, keep the Tcap context, even after the transaction has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
There is 2 new timers in the preferences for the statistics, to tune the retransmission timeout, and messages lost timeout.
svn path=/trunk/; revision=19341
2006-09-27 20:06:06 +00:00
|
|
|
};
|
2005-06-07 05:49:06 +00:00
|
|
|
|
|
|
|
extern gint tcap_standard;
|
|
|
|
|
|
|
|
extern const value_string tcap_component_type_str[];
|
2007-07-27 19:24:40 +00:00
|
|
|
void proto_reg_handoff_tcap(void);
|
|
|
|
void proto_register_tcap(void);
|
2005-06-07 05:49:06 +00:00
|
|
|
|
2006-02-05 03:56:29 +00:00
|
|
|
extern dissector_handle_t get_itu_tcap_subdissector(guint32 ssn);
|
2007-07-27 19:24:40 +00:00
|
|
|
dissector_handle_t get_ansi_tcap_subdissector(guint32 ssn);
|
2006-02-05 03:56:29 +00:00
|
|
|
|
2005-12-17 16:55:45 +00:00
|
|
|
extern void add_ansi_tcap_subdissector(guint32 ssn, dissector_handle_t dissector);
|
|
|
|
extern void add_itu_tcap_subdissector(guint32 ssn, dissector_handle_t dissector);
|
|
|
|
|
|
|
|
extern void delete_ansi_tcap_subdissector(guint32 ssn, dissector_handle_t dissector);
|
|
|
|
extern void delete_itu_tcap_subdissector(guint32 ssn, dissector_handle_t dissector);
|
2005-06-07 05:49:06 +00:00
|
|
|
|
2007-04-03 19:08:00 +00:00
|
|
|
extern void call_tcap_dissector(dissector_handle_t, tvbuff_t*, packet_info*, proto_tree*);
|
|
|
|
|
2007-04-21 20:53:35 +00:00
|
|
|
|
|
|
|
/*--- Included file: packet-tcap-exp.h ---*/
|
|
|
|
#line 1 "packet-tcap-exp.h"
|
|
|
|
extern const value_string tcap_DialoguePDU_vals[];
|
|
|
|
extern const value_string tcap_UniDialoguePDU_vals[];
|
2007-05-13 20:58:29 +00:00
|
|
|
int dissect_tcap_DialoguePDU(gboolean implicit_tag _U_, tvbuff_t *tvb _U_, int offset _U_, asn1_ctx_t *actx _U_, proto_tree *tree _U_, int hf_index _U_);
|
|
|
|
int dissect_tcap_UniDialoguePDU(gboolean implicit_tag _U_, tvbuff_t *tvb _U_, int offset _U_, asn1_ctx_t *actx _U_, proto_tree *tree _U_, int hf_index _U_);
|
2007-04-21 20:53:35 +00:00
|
|
|
|
|
|
|
/*--- End of included file: packet-tcap-exp.h ---*/
|
2007-07-27 19:24:40 +00:00
|
|
|
#line 88 "packet-tcap-template.h"
|
2007-04-21 20:53:35 +00:00
|
|
|
|
From Florent Drouin:
Here are some patches and a new module to introduce the notion of Tcap context for a Tcap transaction. For each Tcap transaction, several parameters, like session identifier, start time or OID, will be saved in a hash table, to keep these informations available for the next messages. This context is then given to the upper layer, and can be used, for example, to generate transaction-associated statistics.
Moreover, the Upper protocol, detected in the Begin of the TCAP transaction ( according to the OID ), is saved in the context, and will be reused for the next messages of the transaction. This help the decoding of SS7 messages, without any SSN configuration in the "wireshark preferences".
You will have too, the possibility to apply a filter to see only the messages related to a TCAP transaction. (tcap.srt.session_id=XXX)
To enable the use of the Tcap context, you have 2 new parameters in the preferences,
- SRT, enable search for a Tcap context for any TCAP messages
- persistentSRT, keep the Tcap context, even after the transaction has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
There is 2 new timers in the preferences for the statistics, to tune the retransmission timeout, and messages lost timeout.
svn path=/trunk/; revision=19341
2006-09-27 20:06:06 +00:00
|
|
|
#endif /* PACKET_tcap_H */
|