From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/*
|
|
|
|
* camel-persistentdata.c
|
|
|
|
* Source for lists and hash tables used in wireshark's camel dissector
|
|
|
|
* for calculation of delays in camel calls
|
|
|
|
* Copyright 2006 Florent Drouin
|
|
|
|
*
|
|
|
|
* Wireshark - Network traffic analyzer
|
|
|
|
* By Gerald Combs <gerald@wireshark.org>
|
|
|
|
* 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.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
# include "config.h"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include <glib.h>
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <string.h>
|
|
|
|
|
|
|
|
#include <epan/emem.h>
|
|
|
|
#include "epan/packet.h"
|
|
|
|
#include "epan/conversation.h"
|
2006-10-10 08:12:40 +00:00
|
|
|
#include "epan/tap.h"
|
2007-05-13 20:58:29 +00:00
|
|
|
#include <epan/asn1.h>
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#include "epan/camel-persistentdata.h"
|
|
|
|
#include "epan/dissectors/packet-tcap.h"
|
|
|
|
#include "epan/dissectors/packet-mtp3.h"
|
|
|
|
|
2006-10-04 07:18:58 +00:00
|
|
|
const value_string camelSRTtype_naming[]= {
|
|
|
|
{ CAMELSRT_SESSION, "TCAP_Session" },
|
|
|
|
{ CAMELSRT_VOICE_INITIALDP, "InialDP/Continue" },
|
2007-02-19 15:14:00 +00:00
|
|
|
{ CAMELSRT_VOICE_ACR1, "Slice1_ACR/ACH" },
|
2006-10-04 07:18:58 +00:00
|
|
|
{ CAMELSRT_VOICE_ACR2, "Slice2_ACR/ACH" },
|
|
|
|
{ CAMELSRT_VOICE_ACR3, "Slice3_ACR/ACH" },
|
|
|
|
{ CAMELSRT_VOICE_DISC, "EvtRepBSCM/Release" },
|
|
|
|
{ CAMELSRT_SMS_INITIALDP, "InitialDP/ContinueSMS" },
|
|
|
|
{ CAMELSRT_GPRS_INITIALDP, "InitialDP/ContinueGPRS" },
|
|
|
|
{ CAMELSRT_GPRS_REPORT, "EvtRepGPRS/ContinueGPRS" },
|
|
|
|
{ 0,NULL}
|
|
|
|
};
|
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
static gint camelsrt_call_equal(gconstpointer k1, gconstpointer k2);
|
|
|
|
static guint camelsrt_call_hash(gconstpointer k);
|
2007-02-19 15:14:00 +00:00
|
|
|
static struct camelsrt_call_t *find_camelsrt_call(struct camelsrt_call_info_key_t *p_camelsrt_call_key);
|
|
|
|
static struct camelsrt_call_t *new_camelsrt_call(struct camelsrt_call_info_key_t *p_camelsrt_call_key);
|
|
|
|
|
|
|
|
static void update_camelsrt_call(struct camelsrt_call_t *p_camelsrt_call,
|
|
|
|
packet_info *pinfo, guint msg_category);
|
|
|
|
|
|
|
|
static void camelsrt_begin_call_matching(packet_info *pinfo,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info);
|
|
|
|
|
|
|
|
static void camelsrt_request_call_matching(tvbuff_t *tvb, packet_info *pinfo,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
proto_tree *tree,
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_info_t *p_camelsrt_info,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
guint srt_type);
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
static void camelsrt_report_call_matching(tvbuff_t *tvb, packet_info *pinfo,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
proto_tree *tree,
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_info_t *p_camelsrt_info,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
guint srt_type);
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
static void camelsrt_close_call_matching(packet_info *pinfo,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
static void camelsrt_display_DeltaTime(proto_tree *tree, tvbuff_t *tvb,
|
|
|
|
nstime_t *value_ptr, guint category);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
static void raz_camelsrt_call (struct camelsrt_call_t *p_camelsrt_call);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
void camelsrt_tcap_matching(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
|
|
|
|
struct tcaphash_context_t *tcap_context);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
/* When several Camel components are received in a single TCAP message,
|
|
|
|
we have to use several buffers for the stored parameters
|
|
|
|
because else this data are erased during TAP dissector call */
|
|
|
|
#define MAX_CAMEL_INSTANCE 10
|
|
|
|
int camelsrt_global_current=0;
|
|
|
|
struct camelsrt_info_t camelsrt_global_info[MAX_CAMEL_INSTANCE];
|
|
|
|
|
|
|
|
/* Configuration parameters to enable or disable the Service Response Time */
|
|
|
|
extern gboolean gcamel_HandleSRT;
|
|
|
|
gboolean gcamel_PersistentSRT=FALSE;
|
|
|
|
gboolean gcamel_DisplaySRT=FALSE;
|
|
|
|
gboolean gcamel_StatSRT=FALSE;
|
|
|
|
|
|
|
|
extern int camel_tap;
|
|
|
|
|
|
|
|
extern int hf_camelsrt_SessionId;
|
|
|
|
extern int hf_camelsrt_RequestNumber;
|
|
|
|
extern int hf_camelsrt_Duplicate;
|
|
|
|
extern int hf_camelsrt_RequestFrame;
|
|
|
|
extern int hf_camelsrt_ResponseFrame;
|
|
|
|
extern int hf_camelsrt_DeltaTime;
|
|
|
|
extern int hf_camelsrt_SessionTime;
|
|
|
|
extern int hf_camelsrt_DeltaTime31;
|
|
|
|
extern int hf_camelsrt_DeltaTime75;
|
|
|
|
extern int hf_camelsrt_DeltaTime65;
|
|
|
|
extern int hf_camelsrt_DeltaTime22;
|
|
|
|
extern int hf_camelsrt_DeltaTime35;
|
|
|
|
extern int hf_camelsrt_DeltaTime80;
|
|
|
|
|
|
|
|
/* Global hash tables*/
|
|
|
|
static GHashTable *srt_calls = NULL;
|
|
|
|
guint32 camelsrt_global_SessionId=1;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DEBUG fonctions
|
|
|
|
*/
|
|
|
|
|
|
|
|
#undef DEBUG_CAMELSRT
|
|
|
|
/* #define DEBUG_CAMELSRT */
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdarg.h>
|
|
|
|
static unsigned debug_level = 99;
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
static void dbg(unsigned level, char *fmt, ...) {
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
va_list ap;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if (level > debug_level) return;
|
|
|
|
va_start(ap,fmt);
|
|
|
|
vfprintf(stderr, fmt, ap);
|
|
|
|
va_end(ap);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Functions needed for Hash-Table
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* compare 2 keys */
|
2007-02-19 15:14:00 +00:00
|
|
|
static gint
|
|
|
|
camelsrt_call_equal(gconstpointer k1, gconstpointer k2)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
const struct camelsrt_call_info_key_t *key1 = (const struct camelsrt_call_info_key_t *) k1;
|
|
|
|
const struct camelsrt_call_info_key_t *key2 = (const struct camelsrt_call_info_key_t *) k2;
|
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
return (key1->SessionIdKey == key2->SessionIdKey) ;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* calculate a hash key */
|
2007-02-19 15:14:00 +00:00
|
|
|
static guint
|
|
|
|
camelsrt_call_hash(gconstpointer k)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
const struct camelsrt_call_info_key_t *key = (const struct camelsrt_call_info_key_t *) k;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
return key->SessionIdKey;
|
|
|
|
}
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
/*
|
|
|
|
* Find the dialog by Key and Time
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static struct camelsrt_call_t *
|
|
|
|
find_camelsrt_call(struct camelsrt_call_info_key_t *p_camelsrt_call_key)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_t *p_camelsrt_call = NULL;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_call = (struct camelsrt_call_t *)g_hash_table_lookup(srt_calls, p_camelsrt_call_key);
|
|
|
|
|
|
|
|
if(p_camelsrt_call) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(10,"D%d ", p_camelsrt_call->session_id);
|
|
|
|
#endif
|
|
|
|
} else {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(23,"Not in hash ");
|
2007-02-19 15:14:00 +00:00
|
|
|
#endif
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return p_camelsrt_call;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-02-19 15:14:00 +00:00
|
|
|
* New record to create, to identify a new transaction
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static struct camelsrt_call_t *
|
|
|
|
new_camelsrt_call(struct camelsrt_call_info_key_t *p_camelsrt_call_key)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_info_key_t *p_new_camelsrt_call_key;
|
|
|
|
struct camelsrt_call_t *p_new_camelsrt_call = NULL;
|
|
|
|
|
|
|
|
/* Register the transaction in the hash table
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
with the tcap transaction Id as main Key
|
|
|
|
Once created, this entry will be updated later */
|
|
|
|
|
|
|
|
p_new_camelsrt_call_key = se_alloc(sizeof(struct camelsrt_call_info_key_t));
|
|
|
|
p_new_camelsrt_call_key->SessionIdKey = p_camelsrt_call_key->SessionIdKey;
|
|
|
|
p_new_camelsrt_call = se_alloc(sizeof(struct camelsrt_call_t));
|
|
|
|
raz_camelsrt_call(p_new_camelsrt_call);
|
|
|
|
p_new_camelsrt_call->session_id = camelsrt_global_SessionId++;
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(10,"D%d ", p_new_camelsrt_call->session_id);
|
|
|
|
#endif
|
|
|
|
/* store it */
|
|
|
|
g_hash_table_insert(srt_calls, p_new_camelsrt_call_key, p_new_camelsrt_call);
|
|
|
|
return p_new_camelsrt_call;
|
|
|
|
}
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
/*
|
|
|
|
* Update a record with the data of the Request
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
update_camelsrt_call(struct camelsrt_call_t *p_camelsrt_call, packet_info *pinfo,
|
|
|
|
guint msg_category)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
|
|
|
p_camelsrt_call->category[msg_category].req_num = pinfo->fd->num;
|
|
|
|
p_camelsrt_call->category[msg_category].rsp_num = 0;
|
|
|
|
p_camelsrt_call->category[msg_category].responded = FALSE;
|
|
|
|
p_camelsrt_call->category[msg_category].req_time = pinfo->fd->abs_ts;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Routine called when the TAP is initialized.
|
|
|
|
* so hash table are (re)created
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
void
|
|
|
|
camelsrt_init_routine(void)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
|
|
|
|
|
|
|
/* free hash-tables and mem_chunks for SRT */
|
|
|
|
if (srt_calls != NULL) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(16,"Destroy hash ");
|
|
|
|
#endif
|
|
|
|
g_hash_table_destroy(srt_calls);
|
|
|
|
}
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* create new hash-tables and mem_chunks for SRT */
|
|
|
|
srt_calls = g_hash_table_new(camelsrt_call_hash, camelsrt_call_equal);
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(16,"Create hash ");
|
|
|
|
#endif
|
|
|
|
/* Reset the session counter */
|
|
|
|
camelsrt_global_SessionId=1;
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
/* The Display of SRT is enable
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* 1) For wireshark only if Persistent Stat is enable
|
|
|
|
* 2) For Tshark, if the SRT handling is enable
|
|
|
|
*/
|
|
|
|
gcamel_DisplaySRT=gcamel_PersistentSRT || gcamel_HandleSRT&gcamel_StatSRT;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Service Response Time analyze, called just after the camel dissector
|
2007-02-19 15:14:00 +00:00
|
|
|
* According to the camel operation, we
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* - open/close a context for the camel session
|
2007-02-19 15:14:00 +00:00
|
|
|
* - look for a request, or look for the corresponding response
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
void
|
|
|
|
camelsrt_call_matching(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info)
|
|
|
|
{
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(10,"tcap_session #%d ", p_camelsrt_info->tcap_session_id);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
switch (p_camelsrt_info->opcode) {
|
|
|
|
|
|
|
|
case 0: /*InitialDP*/
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_begin_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_VOICE_INITIALDP);
|
|
|
|
break;
|
|
|
|
case 60: /*InitialDPSMS*/
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_begin_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
2007-02-19 15:14:00 +00:00
|
|
|
CAMELSRT_SMS_INITIALDP);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
break;
|
|
|
|
case 78: /*InitialDPGPRS*/
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_begin_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
2007-02-19 15:14:00 +00:00
|
|
|
CAMELSRT_GPRS_INITIALDP);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
break;
|
|
|
|
|
|
|
|
case 23: /*RequestReportBCSMEvent*/
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 63: /*RequestReportSMSEvent*/
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 81: /*RequestReportGPRSEvent*/
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 24: /*EventReportBCSMEvent*/
|
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_VOICE_DISC );
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 64: /*EventReportSMS*/
|
|
|
|
/* Session has been explicity closed without TC_END */
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_close_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
tcapsrt_close(p_camelsrt_info->tcap_context, pinfo);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 80: /*EventReportGPRS*/
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_begin_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_GPRS_REPORT);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 35: /*ApplyCharging*/
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
2007-02-19 15:14:00 +00:00
|
|
|
CAMELSRT_VOICE_ACR1 );
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 71: /*ApplyChargingGPRS*/
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 36: /*ApplyChargingReport*/
|
|
|
|
camelsrt_request_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_VOICE_ACR1 );
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 72: /*ApplyChargingReportGPRS*/
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case 31: /*Continue*/
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_VOICE_INITIALDP);
|
|
|
|
break;
|
|
|
|
case 65: /*ContinueSMS*/
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_SMS_INITIALDP);
|
|
|
|
break;
|
|
|
|
case 75: /*ContinueGPRS*/
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_GPRS_INITIALDP);
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_GPRS_REPORT);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 22: /*ReleaseCall*/
|
|
|
|
camelsrt_report_call_matching(tvb, pinfo, tree, p_camelsrt_info,
|
|
|
|
CAMELSRT_VOICE_DISC);
|
|
|
|
/* Session has been closed by Network */
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_close_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
break;
|
|
|
|
|
|
|
|
case 66: /*ReleaseSMS*/
|
|
|
|
/* Session has been closed by Network */
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_close_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
tcapsrt_close(p_camelsrt_info->tcap_context,pinfo);
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 79: /*ReleaseGPRS*/
|
|
|
|
/* Session has been closed by Network */
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_close_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
break;
|
|
|
|
} /* switch opcode */
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Callback function for the TCAP dissector
|
2007-02-19 15:14:00 +00:00
|
|
|
* This callback function is used to inform the camel layer, that the session
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* has been Closed or Aborted by a TCAP message without Camel component
|
|
|
|
* So, we can close the context for camel session, and update the stats.
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
void
|
|
|
|
camelsrt_tcap_matching(tvbuff_t *tvb _U_, packet_info *pinfo,
|
|
|
|
proto_tree *tree _U_,
|
|
|
|
struct tcaphash_context_t *p_tcap_context)
|
|
|
|
{
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info;
|
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Camel_CallBack ");
|
|
|
|
#endif
|
|
|
|
p_camelsrt_info=camelsrt_razinfo();
|
2007-02-19 15:14:00 +00:00
|
|
|
|
|
|
|
p_camelsrt_info->tcap_context=p_tcap_context;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if (p_tcap_context) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Close TCAP ");
|
|
|
|
#endif
|
|
|
|
p_camelsrt_info->tcap_session_id = p_tcap_context->session_id;
|
2007-02-19 15:14:00 +00:00
|
|
|
camelsrt_close_call_matching(pinfo, p_camelsrt_info);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
tap_queue_packet(camel_tap, pinfo, p_camelsrt_info);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
/*
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* Create the record identifiying the Camel session
|
|
|
|
* As the Tcap session id given by the TCAP dissector is uniq, it will be
|
|
|
|
* used as main key.
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
camelsrt_begin_call_matching(packet_info *pinfo,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_t *p_camelsrt_call;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
struct camelsrt_call_info_key_t camelsrt_call_key;
|
|
|
|
|
|
|
|
p_camelsrt_info->bool_msginfo[CAMELSRT_SESSION]=TRUE;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
|
|
|
/* prepare the key data */
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_call_key.SessionIdKey = p_camelsrt_info->tcap_session_id;
|
|
|
|
|
|
|
|
/* look up the request */
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(10,"\n Session begin #%u\n", pinfo->fd->num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
dbg(11,"Search key %lu ",camelsrt_call_key.SessionIdKey);
|
|
|
|
#endif
|
|
|
|
p_camelsrt_call = (struct camelsrt_call_t *)g_hash_table_lookup(srt_calls, &camelsrt_call_key);
|
|
|
|
if (p_camelsrt_call) {
|
|
|
|
/* We have seen this request before -> do nothing */
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(22,"Already seen ");
|
|
|
|
#endif
|
|
|
|
} else { /* p_camelsrt_call has not been found */
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(10,"New key %lu ",camelsrt_call_key.SessionIdKey);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_call = new_camelsrt_call(&camelsrt_call_key);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_call->tcap_context=p_camelsrt_info->tcap_context;
|
|
|
|
update_camelsrt_call(p_camelsrt_call, pinfo,CAMELSRT_SESSION);
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Update Callback ");
|
|
|
|
#endif
|
|
|
|
p_camelsrt_call->tcap_context->callback=camelsrt_tcap_matching;
|
|
|
|
}
|
|
|
|
}
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/*
|
|
|
|
* Register the request, and try to find the response
|
|
|
|
*
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
camelsrt_request_call_matching(tvbuff_t *tvb, packet_info *pinfo,
|
|
|
|
proto_tree *tree,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info,
|
|
|
|
guint srt_type )
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_t *p_camelsrt_call;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
struct camelsrt_call_info_key_t camelsrt_call_key;
|
|
|
|
proto_item *ti;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(10,"\n %s #%u\n", val_to_str(srt_type, camelSRTtype_naming, "Unk"),pinfo->fd->num);
|
2007-02-19 15:14:00 +00:00
|
|
|
#endif
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
/* look only for matching request, if matching conversation is available. */
|
|
|
|
camelsrt_call_key.SessionIdKey = p_camelsrt_info->tcap_session_id;
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Search key %lu ", camelsrt_call_key.SessionIdKey);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_call = find_camelsrt_call(&camelsrt_call_key);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if(p_camelsrt_call) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(12,"Found ");
|
2007-02-19 15:14:00 +00:00
|
|
|
#endif
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if (gcamel_DisplaySRT)
|
|
|
|
proto_tree_add_uint(tree, hf_camelsrt_SessionId, tvb, 0,0, p_camelsrt_call->session_id);
|
|
|
|
|
|
|
|
|
|
|
|
/* Hmm.. As there are several slices ApplyChargingReport/ApplyCharging
|
|
|
|
* we will prepare the measurement for 3 slices with 3 categories */
|
2007-02-19 15:14:00 +00:00
|
|
|
if (srt_type==CAMELSRT_VOICE_ACR1) {
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].req_num == 0) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR1;
|
2007-02-19 15:14:00 +00:00
|
|
|
} else if ( (p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].req_num == 0)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
&& (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num != 0)
|
|
|
|
&& (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num < pinfo->fd->num) ) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR2;
|
|
|
|
} else if ( (p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].req_num == 0)
|
|
|
|
&& (p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].rsp_num != 0)
|
|
|
|
&& (p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].rsp_num < pinfo->fd->num) ) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR3;
|
|
|
|
} else if (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num > pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR1;
|
|
|
|
} else if ( p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].rsp_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].rsp_num > pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR2;
|
|
|
|
} else if (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].rsp_num > pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR3;
|
|
|
|
}
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-02-19 15:14:00 +00:00
|
|
|
dbg(70,"Request ACR %u ",srt_type);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
dbg(70,"ACR1 %u %u",p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].req_num, p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].rsp_num);
|
|
|
|
dbg(70,"ACR2 %u %u",p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].req_num, p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].rsp_num);
|
|
|
|
dbg(70,"ACR3 %u %u",p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].req_num, p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].rsp_num);
|
|
|
|
#endif
|
|
|
|
} /* not ACR */
|
|
|
|
p_camelsrt_info->bool_msginfo[srt_type]=TRUE;
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
|
|
|
|
if (p_camelsrt_call->category[srt_type].req_num == 0) {
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* We have not yet seen a request to that call, so this must be the first request
|
2007-02-19 15:14:00 +00:00
|
|
|
remember its frame number. */
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(5,"Set reqlink #%u ", pinfo->fd->num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#endif
|
|
|
|
update_camelsrt_call(p_camelsrt_call, pinfo, srt_type);
|
|
|
|
} else {
|
|
|
|
/* We have seen a request to this call - but was it *this* request? */
|
|
|
|
if (p_camelsrt_call->category[srt_type].req_num != pinfo->fd->num) {
|
2007-02-19 15:14:00 +00:00
|
|
|
|
|
|
|
if (srt_type!=CAMELSRT_VOICE_DISC) {
|
|
|
|
/* No, so it's a duplicate resquest. Mark it as such. */
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(21,"Display_duplicate with req %d ", p_camelsrt_call->category[srt_type].req_num);
|
|
|
|
#endif
|
|
|
|
p_camelsrt_info->msginfo[srt_type].is_duplicate = TRUE;
|
2007-02-19 15:14:00 +00:00
|
|
|
if (gcamel_DisplaySRT)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
proto_tree_add_uint_hidden(tree, hf_camelsrt_Duplicate, tvb, 0,0, 77);
|
|
|
|
|
|
|
|
} else {
|
|
|
|
/* Ignore duplicate frame */
|
|
|
|
if (pinfo->fd->num > p_camelsrt_call->category[srt_type].req_num) {
|
|
|
|
p_camelsrt_call->category[srt_type].req_num = pinfo->fd->num;
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(5,"DISC Set reqlink #%u ", pinfo->fd->num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#endif
|
|
|
|
update_camelsrt_call(p_camelsrt_call, pinfo, srt_type);
|
|
|
|
} /* greater frame */
|
|
|
|
} /* DISC */
|
|
|
|
} /* req_num already seen */
|
|
|
|
} /* req_num != 0 */
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* add link to response frame, if available */
|
|
|
|
if ( gcamel_DisplaySRT &&
|
|
|
|
(p_camelsrt_call->category[srt_type].rsp_num != 0) &&
|
|
|
|
(p_camelsrt_call->category[srt_type].req_num != 0) &&
|
|
|
|
(p_camelsrt_call->category[srt_type].req_num == pinfo->fd->num) ) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(20,"Display_framersplink %d ",p_camelsrt_call->category[srt_type].rsp_num);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
ti = proto_tree_add_uint_format(tree, hf_camelsrt_RequestFrame, tvb, 0, 0,
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_call->category[srt_type].rsp_num,
|
2007-02-19 15:14:00 +00:00
|
|
|
"Linked response %s in frame %u",
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
val_to_str(srt_type, camelSRTtype_naming, "Unk"),
|
|
|
|
p_camelsrt_call->category[srt_type].rsp_num);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
} /* frame valid */
|
2007-02-19 15:14:00 +00:00
|
|
|
} /* call reference */
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Check if the received message is a response to a previous request
|
|
|
|
* registered is the camel session context.
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
camelsrt_report_call_matching(tvbuff_t *tvb, packet_info *pinfo,
|
|
|
|
proto_tree *tree,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info,
|
|
|
|
guint srt_type)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_t *p_camelsrt_call;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
struct camelsrt_call_info_key_t camelsrt_call_key;
|
|
|
|
nstime_t delta;
|
|
|
|
proto_item *ti;
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(10,"\n %s #%u\n", val_to_str(srt_type, camelSRTtype_naming, "Unk"),pinfo->fd->num);
|
2007-02-19 15:14:00 +00:00
|
|
|
#endif
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_call_key.SessionIdKey = p_camelsrt_info->tcap_session_id;
|
|
|
|
/* look only for matching request, if matching conversation is available. */
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Search key %lu ",camelsrt_call_key.SessionIdKey);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_call = find_camelsrt_call(&camelsrt_call_key);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if(p_camelsrt_call) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(12,"Found, req=%d ",p_camelsrt_call->category[srt_type].req_num);
|
|
|
|
#endif
|
|
|
|
if ( gcamel_DisplaySRT )
|
|
|
|
proto_tree_add_uint(tree, hf_camelsrt_SessionId, tvb, 0,0, p_camelsrt_call->session_id);
|
|
|
|
|
2007-02-19 15:14:00 +00:00
|
|
|
if (srt_type==CAMELSRT_VOICE_ACR1) {
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if (p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].req_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR3].req_num < pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR1;
|
|
|
|
} else if ( p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].req_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR2].req_num < pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR2;
|
|
|
|
} else if (p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].req_num != 0
|
|
|
|
&& p_camelsrt_call->category[CAMELSRT_VOICE_ACR1].req_num < pinfo->fd->num) {
|
|
|
|
srt_type=CAMELSRT_VOICE_ACR1;
|
|
|
|
}
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(70,"Report ACR %u ",srt_type);
|
|
|
|
#endif
|
|
|
|
} /* not ACR */
|
|
|
|
p_camelsrt_info->bool_msginfo[srt_type]=TRUE;
|
|
|
|
|
|
|
|
if (p_camelsrt_call->category[srt_type].rsp_num == 0) {
|
|
|
|
if ( (p_camelsrt_call->category[srt_type].req_num != 0)
|
|
|
|
&& (pinfo->fd->num > p_camelsrt_call->category[srt_type].req_num) ){
|
|
|
|
/* We have not yet seen a response to that call, so this must be the first response;
|
2007-02-19 15:14:00 +00:00
|
|
|
remember its frame number only if response comes after request */
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(14,"Set reslink #%d req %u ",pinfo->fd->num, p_camelsrt_call->category[srt_type].req_num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#endif
|
|
|
|
p_camelsrt_call->category[srt_type].rsp_num = pinfo->fd->num;
|
|
|
|
|
|
|
|
} else {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(2,"badreslink #%u req %u ",pinfo->fd->num, p_camelsrt_call->category[srt_type].req_num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#endif
|
|
|
|
} /* req_num != 0 */
|
|
|
|
} else { /* rsp_num != 0 */
|
|
|
|
/* We have seen a response to this call - but was it *this* response? */
|
|
|
|
if (p_camelsrt_call->category[srt_type].rsp_num != pinfo->fd->num) {
|
|
|
|
/* No, so it's a duplicate response. Mark it as such. */
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(21,"Display_duplicate rsp=%d ", p_camelsrt_call->category[srt_type].rsp_num);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_info->msginfo[srt_type].is_duplicate = TRUE;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if ( gcamel_DisplaySRT )
|
|
|
|
proto_tree_add_uint_hidden(tree, hf_camelsrt_Duplicate, tvb, 0,0, 77);
|
|
|
|
}
|
|
|
|
} /* rsp_num != 0 */
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if ( (p_camelsrt_call->category[srt_type].req_num != 0) &&
|
|
|
|
(p_camelsrt_call->category[srt_type].rsp_num != 0) &&
|
|
|
|
(p_camelsrt_call->category[srt_type].rsp_num == pinfo->fd->num) ) {
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_call->category[srt_type].responded = TRUE;
|
|
|
|
p_camelsrt_info->msginfo[srt_type].request_available = TRUE;
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(20,"Display_frameReqlink %d ",p_camelsrt_call->category[srt_type].req_num);
|
|
|
|
#endif
|
|
|
|
/* Indicate the frame to which this is a reply. */
|
|
|
|
if ( gcamel_DisplaySRT ) {
|
|
|
|
ti = proto_tree_add_uint_format(tree, hf_camelsrt_ResponseFrame, tvb, 0, 0,
|
|
|
|
p_camelsrt_call->category[srt_type].req_num,
|
|
|
|
"Linked request %s in frame %u",
|
|
|
|
val_to_str(srt_type, camelSRTtype_naming, "Unk"),
|
|
|
|
p_camelsrt_call->category[srt_type].req_num);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
}
|
|
|
|
/* Calculate Service Response Time */
|
|
|
|
nstime_delta(&delta, &pinfo->fd->abs_ts, &p_camelsrt_call->category[srt_type].req_time);
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_info->msginfo[srt_type].is_delta_time = TRUE;
|
|
|
|
p_camelsrt_info->msginfo[srt_type].delta_time = delta; /* give it to tap */
|
|
|
|
p_camelsrt_info->msginfo[srt_type].req_time = p_camelsrt_call->category[srt_type].req_time;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* display Service Response Time and make it filterable */
|
|
|
|
camelsrt_display_DeltaTime(tree, tvb, &delta, srt_type);
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
} /*req_num != 0 && not duplicate */
|
|
|
|
} /* call reference found */
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Update the Camel session info, and close the session.
|
|
|
|
* Then remove the associated context, if we do not have persistentSRT enable
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
camelsrt_close_call_matching(packet_info *pinfo,
|
|
|
|
struct camelsrt_info_t *p_camelsrt_info)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_call_t *p_camelsrt_call;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
struct camelsrt_call_info_key_t camelsrt_call_key;
|
|
|
|
nstime_t delta;
|
|
|
|
|
|
|
|
p_camelsrt_info->bool_msginfo[CAMELSRT_SESSION]=TRUE;
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
2007-04-16 04:52:51 +00:00
|
|
|
dbg(10,"\n Session end #%u\n", pinfo->fd->num);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
#endif
|
|
|
|
/* look only for matching request, if matching conversation is available. */
|
|
|
|
camelsrt_call_key.SessionIdKey = p_camelsrt_info->tcap_session_id;
|
|
|
|
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(11,"Search key %lu ",camelsrt_call_key.SessionIdKey);
|
|
|
|
#endif
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_call = find_camelsrt_call(&camelsrt_call_key);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if(p_camelsrt_call) {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(12,"Found ");
|
2007-02-19 15:14:00 +00:00
|
|
|
#endif
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* Calculate Service Response Time */
|
|
|
|
nstime_delta(&delta, &pinfo->fd->abs_ts, &p_camelsrt_call->category[CAMELSRT_SESSION].req_time);
|
|
|
|
p_camelsrt_call->category[CAMELSRT_SESSION].responded = TRUE;
|
2007-02-19 15:14:00 +00:00
|
|
|
p_camelsrt_info->msginfo[CAMELSRT_SESSION].request_available = TRUE;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_info->msginfo[CAMELSRT_SESSION].is_delta_time = TRUE;
|
|
|
|
p_camelsrt_info->msginfo[CAMELSRT_SESSION].delta_time = delta; /* give it to tap */
|
|
|
|
p_camelsrt_info->msginfo[CAMELSRT_SESSION].req_time = p_camelsrt_call->category[CAMELSRT_SESSION].req_time;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if ( !gcamel_PersistentSRT ) {
|
|
|
|
g_hash_table_remove(srt_calls, &camelsrt_call_key);
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(20,"remove hash ");
|
|
|
|
#endif
|
|
|
|
} else {
|
|
|
|
#ifdef DEBUG_CAMELSRT
|
|
|
|
dbg(20,"keep hash ");
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
} /* call reference found */
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-02-19 15:14:00 +00:00
|
|
|
* Display the delta time between two messages in a field corresponding
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
* to the category (hf_camelsrt_DeltaTimexx).
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
camelsrt_display_DeltaTime(proto_tree *tree, tvbuff_t *tvb, nstime_t *value_ptr,
|
|
|
|
guint category)
|
|
|
|
{
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
proto_item *ti;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
if ( gcamel_DisplaySRT ) {
|
|
|
|
switch(category) {
|
|
|
|
case CAMELSRT_VOICE_INITIALDP:
|
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime31, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case CAMELSRT_VOICE_ACR1:
|
|
|
|
case CAMELSRT_VOICE_ACR2:
|
2007-02-19 15:14:00 +00:00
|
|
|
case CAMELSRT_VOICE_ACR3:
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime22, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case CAMELSRT_VOICE_DISC:
|
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime35, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case CAMELSRT_GPRS_INITIALDP:
|
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime75, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
case CAMELSRT_GPRS_REPORT:
|
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime80, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
2007-02-19 15:14:00 +00:00
|
|
|
|
|
|
|
case CAMELSRT_SMS_INITIALDP:
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
ti = proto_tree_add_time(tree, hf_camelsrt_DeltaTime65, tvb, 0, 0, value_ptr);
|
|
|
|
PROTO_ITEM_SET_GENERATED(ti);
|
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Initialize the Message Info used by the main dissector
|
2007-02-19 15:14:00 +00:00
|
|
|
* Data are linked to a TCAP transaction
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_info_t *
|
|
|
|
camelsrt_razinfo(void)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
2007-02-19 15:14:00 +00:00
|
|
|
struct camelsrt_info_t *p_camelsrt_info ;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
/* Global buffer for packet extraction */
|
|
|
|
camelsrt_global_current++;
|
|
|
|
if(camelsrt_global_current==MAX_CAMEL_INSTANCE){
|
|
|
|
camelsrt_global_current=0;
|
|
|
|
}
|
2007-02-19 15:14:00 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
p_camelsrt_info=&camelsrt_global_info[camelsrt_global_current];
|
2007-02-19 15:14:00 +00:00
|
|
|
memset(p_camelsrt_info,0,sizeof(struct camelsrt_info_t));
|
|
|
|
|
|
|
|
p_camelsrt_info->opcode=255;
|
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
return p_camelsrt_info;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Initialize the data per call for the Service Response Time Statistics
|
|
|
|
* Data are linked to a Camel operation in a TCAP transaction
|
|
|
|
*/
|
2007-02-19 15:14:00 +00:00
|
|
|
static void
|
|
|
|
raz_camelsrt_call (struct camelsrt_call_t *p_camelsrt_call)
|
|
|
|
{
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
memset(p_camelsrt_call,0,sizeof(struct camelsrt_call_t));
|
|
|
|
}
|