Menu
▾
▴
Re: [Seagull-users] Diameter server scenario with multiple messages in one session
|
From: Volker B. <VBe...@or...> - 2014-06-26 15:08:04
|
I assume the problem is the timeout
> 2014-06-26.17:44:03.480|T|Call timeout detected
> 2014-06-26.17:44:03.480|V|Error Timeout: Scenario failed call-id [ 33
34 34 38 64 35 34 32 2d 32
> 35 30 39 2d 34 30 30 30 2d 62 63 61 31 2d 30 36 33 33 63 38 36 38 64 37
61 36 ]
If seagull detects a timeout for a call (scenario) then it will stop this
call.
So for seagull it is the start of a new call if it receive the next
request of this scenario.
May a
<wait-ms>
will help
Gal Goffer <gg...@in...> wrote on 26.06.2014 16:51:25:
> From: Gal Goffer <gg...@in...>
> To: 'Volker Bensberg' <VBe...@or...>,
> Cc: "'gul...@li...'"
<gul...@li...>
> Date: 26.06.2014 16:51
> Subject: RE: [Seagull-users] Diameter server scenario with multiple
messages in one session
>
> I am tracing this with Wireshark and I can tell that the session-ID is a
unique value (UUID). In-
> fact our system is built to fail any ACR/ACA transmission where the
session ID does not match the
> previous request in the session (impossible to send START on one session
and STOP on another).
> Here is the log output (I?ve removed irrelevant buffer logging
information):
> 2014-06-26.17:43:53.443|M|Received [[ACR
> |M|[protocol-version] = [ 1]
> |M|[msg-length] = [ 1516]
> |M|[flags] = [ 128]
> |M|[cmd-code] = [ 271]
> |M|[application-id] = [ 3]
> |M|[HbH-id] = [ 59117359]
> |M|[EtE-id] = [ 1499307684]
> |M| [Session-Id
> |M| (avp-code = 263)(flags = 64)] = [
> |M| 33 34 34 38 64 35 34 32 2d 32 35 30 39 2d 34
30
> |M| 30 30 2d 62 63 61 31 2d 30 36 33 33 63 38 36
38
> |M| 64 37 61 36
> |M| ]
> |M| [Destination-Realm
> |M| (avp-code = 283)(flags = 64)] = [
> |M| 6f 6e 65 2e 61 74 74 2e 63 6f 6d
> |M| ]
> |M| [Origin-Host
> |M| (avp-code = 264)(flags = 64)] = [
> |M| 31 37 32 2e 32 30 2e 33 32 2e 32 34 32
> |M| ]
> |M| [Origin-Realm
> |M| (avp-code = 296)(flags = 64)] = [
> |M| 6f 6e 65 2e 61 74 74 2e 6e 65 74
> |M| ]
> |M| [Accounting-Record-Type
> |M| (avp-code = 480)(flags = 64)] = [
> |M| 00 00 00 02
> |M| ]
> |M| [Accounting-Record-Number
> |M| (avp-code = 485)(flags = 64)] = [0]
> |M| [Acct-Application-Id
> |M| (avp-code = 259)(flags = 64)] = [3]
> |M| [Event-Timestamp
> |M| (avp-code = 55)(flags = 64)] = [
> |M| d7 56 b0 29
> |M| ]
> |M| [Service-Information
> |M| (avp-code = 873)(flags = 64)] = [
> |M| ]
> |M|]
> ]
> 2014-06-26.17:43:53.443|M|Send [[ACA
> |M|[protocol-version] = [ 1]
> |M|[msg-length] = [ 0]
> |M|[flags] = [ 0]
> |M|[cmd-code] = [ 271]
> |M|[application-id] = [ 3]
> |M|[HbH-id] = [ 59117359]
> |M|[EtE-id] = [ 1499307684]
> |M| [Session-Id
> |M| (avp-code = 263)(flags = 64)] = [
> |M| 33 34 34 38 64 35 34 32 2d 32 35 30 39 2d 34
30
> |M| 30 30 2d 62 63 61 31 2d 30 36 33 33 63 38 36
38
> |M| 64 37 61 36
> |M| ]
> |M| [Vendor-Specific-Application-Id
> |M| (avp-code = 260)(flags = 64)] = [
> |M| | [Vendor-Id
> |M| | (avp-code = 266)(flags = 64)] = [10415]
> |M| | [Acct-Application-Id
> |M| | (avp-code = 259)(flags = 64)] = [3]
> |M| ]
> |M| [Origin-Host
> |M| (avp-code = 264)(flags = 64)] = [
> |M| 31 37 32 2e 32 30 2e 33 32 2e 32 34 32
> |M| ]
> |M| [Origin-Realm
> |M| (avp-code = 296)(flags = 64)] = [
> |M| 6f 6e 65 2e 61 74 74 2e 63 6f 6d
> |M| ]
> |M| [Accounting-Record-Type
> |M| (avp-code = 480)(flags = 64)] = [
> |M| 00 00 00 02
> |M| ]
> |M| [Accounting-Record-Number
> |M| (avp-code = 485)(flags = 64)] = [0]
> |M| [Result-Code
> |M| (avp-code = 268)(flags = 64)] = [2001]
> |M| [Acct-Interim-Interval
> |M| (avp-code = 85)(flags = 64)] = [900]
> |M|]]
>
> 2014-06-26.17:43:59.421|V|Scenario Ignore stat behavior call-id
[3357103568]
> 2014-06-26.17:44:03.480|T|Call timeout detected
> 2014-06-26.17:44:03.480|V|Error Timeout: Scenario failed call-id [ 33
34 34 38 64 35 34 32 2d 32
> 35 30 39 2d 34 30 30 30 2d 62 63 61 31 2d 30 36 33 33 63 38 36 38 64 37
61 36 ]
> 2014-06-26.17:44:07.470|W|No definition found for [461]
> 2014-06-26.17:44:07.470|W|No definition found for [443]
> 2014-06-26.17:44:07.470|W|No definition found for [876]
> 2014-06-26.17:44:07.470|W|No definition found for [2030]
> 2014-06-26.17:44:07.470|W|No definition found for [1000]
> 2014-06-26.17:44:07.470|M|Received [[ACR
> |M|[protocol-version] = [ 1]
> |M|[msg-length] = [ 1136]
> |M|[flags] = [ 128]
> |M|[cmd-code] = [ 271]
> |M|[application-id] = [ 3]
> |M|[HbH-id] = [ 59117360]
> |M|[EtE-id] = [ 1499307685]
> |M| [Session-Id
> |M| (avp-code = 263)(flags = 64)] = [
> |M| 33 34 34 38 64 35 34 32 2d 32 35 30 39 2d 34
30
> |M| 30 30 2d 62 63 61 31 2d 30 36 33 33 63 38 36
38
> |M| 64 37 61 36
> |M| ]
> |M| [Destination-Realm
> |M| (avp-code = 283)(flags = 64)] = [
> |M| 6f 6e 65 2e 61 74 74 2e 63 6f 6d
> |M| ]
> |M| [Origin-Host
> |M| (avp-code = 264)(flags = 64)] = [
> |M| 31 37 32 2e 32 30 2e 33 32 2e 32 34 32
> |M| ]
> |M| [Origin-Realm
> |M| (avp-code = 296)(flags = 64)] = [
> |M| 6f 6e 65 2e 61 74 74 2e 6e 65 74
> |M| ]
> |M| [Accounting-Record-Type
> |M| (avp-code = 480)(flags = 64)] = [
> |M| 00 00 00 04
> |M| ]
> |M| [Accounting-Record-Number
> |M| (avp-code = 485)(flags = 64)] = [1]
> |M| [Acct-Application-Id
> |M| (avp-code = 259)(flags = 64)] = [3]
> |M| [Event-Timestamp
> |M| (avp-code = 55)(flags = 64)] = [
> |M| d7 56 b0 37
> |M| ]
> |M| [Service-Information
> |M| (avp-code = 873)(flags = 64)] = [
> |M| ]
> |M|]
> ]
> 2014-06-26.17:44:07.470|E|check failed in [ACR] command, value of avp
[Accounting-Record-Type].
> Expected [ 00 00 00 02 ] but got [ 00 00 00 04 ]
> 2014-06-26.17:44:07.470|T|Parameter value check error on call with
session-id [0]
> 2014-06-26.17:44:07.470|T|Execution error on call with session-id [0]
> 2014-06-26.17:44:07.470|V|Error check behavior: Scenario failed call-id
[0]
>
>
> From: Volker Bensberg [mailto:VBe...@or...]
> Sent: Thursday, June 26, 2014 5:37 PM
> To: Gal Goffer
> Cc: 'gul...@li...'
> Subject: RE: [Seagull-users] Diameter server scenario with multiple
messages in one session
>
> This means that every request with the same Session-Id AVP belongs to
the same scenario.
>
> You have to make sure that your client sends the request for the same
scenario also with the same
> Session-Id AVP.
> The error message complains about session-id 0.
> Maybe you switch on full debug level in order to see what your client
really sends in its requests.
>
> Gal Goffer <gg...@in...> wrote on 26.06.2014 16:24:22:
>
> > From: Gal Goffer <gg...@in...>
> > To: 'Volker Bensberg' <VBe...@or...>,
> > Cc: "'gul...@li...'"
<gul...@li...>
> > Date: 26.06.2014 16:24
> > Subject: RE: [Seagull-users] Diameter server scenario with multiple
messages in one session
> >
> > Thanks for the reply Volker.
> >
> > I?m using the first definition ? Session-Id.
> > How do I set this value to follow through on the entire session then?
I didn?t understand how to
> > solve this.
> >
> > Thanks.
> > Gal
> >
> > From: Volker Bensberg [mailto:VBe...@or...]
> > Sent: Thursday, June 26, 2014 4:50 PM
> > To: Gal Goffer
> > Cc: 'gul...@li...'
> > Subject: Re: [Seagull-users] Diameter server scenario with multiple
messages in one session
> >
> > How do you identify your session ?
> >
> > You might either define in seagull dictionary
> > <command session-id="Session-Id" out-of-session-id="HbH-id">
> > or
> > <command session-id="HbH-id" out-of-session-id="HbH-id">
> >
> > If you use the second definition, but the client increments Hbh-id at
every new request,
> > then for seagull it is a new session and it will start at the
beginning of the scenario
> > instead of continuing the existing one.
> >
> > Gal Goffer <gg...@in...> wrote on 26.06.2014 14:50:34:
> >
> > > From: Gal Goffer <gg...@in...>
> > > To: "'gul...@li...'"
<gul...@li...>,
> > > Date: 26.06.2014 15:18
> > > Subject: [Seagull-users] Diameter server scenario with multiple
messages in one session
> > >
> > > Hi,
> > >
> > > I am trying to simulate a server scenario where the client sends
several ACR messages.
> > > However it seems that following the first part of the scenario which
ran successfully (ACR
> > > received and ACA sent), the next messages are not properly
correlated to the same session.
> > > Rf Client Rf Server
> > > (Seagull)
> > > | |
> > > |---- CER ------------->|
> > > | |
> > > |<--- CEA --------------|
> > > | |
> > > |---> ACR (START) ----->|
> > > | |
> > > |<--- ACA --------------|
> > > | |
> > > |---- ACR (STOP) ------>|
> > > | |
> > > |<--- ACA --------------|
> > > | |
> > >
> > > I can tell that there is no match since the next message arriving
has Accounting-Record-Type set
> > > to 4 (STOP) which should be validated as I requested using the
check-value action and according
> > > to the log the server seems to expect 2 (another START).
> > >
> > > Here is the error message from the log:
> > >
> > > 2014-06-26.15:16:39.328|A|START log
> > > 2014-06-26.15:16:39.328|A|Platform use LITTLE_ENDIAN coding
> > > 2014-06-26.15:16:39.328|A|Integer32 Type size is: 4
> > > 2014-06-26.15:16:39.328|A|Integer64 Type size is: 8
> > > 2014-06-26.15:16:39.328|A|Configuration data:
> > > | |option_log_file
[../logs/acr-aca.server.log]
> > > | |option_conf_file
[../config/conf.server.xml]
> > > | |option_dico_file [../config/base_rf.xml]
> > > | |option_scen_file
[../scenario/acr-aca.server.xml]
> > > | |log_stat_file [../logs/server-stat.csv]
> > > | |option_log_level [ET]
> > > | |option_bg_mode [false]
> > > | |call_rate [0]
> > > | |burst_limit [0]
> > > | |max_send [2000]
> > > | |max_receive [2000]
> > > | |select_timeout [50]
> > > | |max_simult_calls [2000]
> > > | |call_timeout_ms [10000]
> > > | |msg_buffer_size [4096]
> > > | |display_period [5]
> > > | |log_stat_period [15]
> > > | |resp_time_repart [50,75,100,150,300,5000]
> > > | |number_calls [0]
> > > | |notimelog [false]
> > > | |msg check [false]
> > > | |msg check mask [P]
> > > | |check behaviour [warning]
> > > | |call rate scale [1]
> > > | |model traffic [best-effort]
> > > | |external data file [none]
> > > | |external data select [sequential]
> > > 2014-06-26.15:16:39.329|A|PID [24091]
> > > 2014-06-26.15:19:59.082|T|Call timeout detected
> > > 2014-06-26.15:20:03.099|E|check failed in [ACR] command, value of
avp [Accounting-Record-Type].
> > > Expected [ 00 00 00 02 ] but got [ 00 00 00 04 ]
> > > 2014-06-26.15:20:03.099|T|Parameter value check error on call with
session-id [0]
> > > 2014-06-26.15:20:03.099|T|Execution error on call with session-id
[0]
> > >
> > > And the scenario:
> > > <scenario>
> > >
> > > <init>
> > > <receive channel="channel-1">
> > > <command name="CER">
> > > </command>
> > > <action>
> > > <store name="ven" entity="Vendor-Id"> </store>
> > > </action>
> > > </receive>
> > >
> > > <send channel="channel-1">
> > > <command name="CEA">
> > > <avp name="Origin-Host" value="ccf-server"> </avp>
> > > <avp name="Origin-Realm" value="one.att.com"> </avp>
> > > <avp name="Result-Code" value="2001"> </avp>
> > > <avp name="Host-IP-Address" value="0x0001ac1420f2"> </avp>
> > > <avp name="Vendor-Id" value="14954"> </avp>
> > > <avp name="Product-Name" value="Server"> </avp>
> > > <avp name="Inband-Security-Id" value="0"> </avp>
> > > <avp name="Firmware-Revision" value="1"> </avp>
> > > <avp name="Vendor-Specific-Application-Id">
> > > <avp name="Vendor-Id" value="10415"></avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </command>
> > > </send>
> > > </init>
> > >
> > > <traffic>
> > >
> > >
> > > <!------------------ ACR START -------------------->
> > > <receive channel="channel-1">
> > > <command name="ACR">
> > > <!-- Only need to specify what needs to be parsed -->
> > > <avp name="Session-Id" value="dont_care"> </avp>
> > > <avp name="Accounting-Record-Type" value="0x00000002">
</avp>
> > > </command>
> > > <!-- Store action is at the end of the command -->
> > > <action>
> > > <store name="HbH" entity="HbH-id"></store>
> > > <store name="E2E" entity="EtE-id"></store>
> > > <store name="sid" entity="Session-Id"></store>
> > > <store name="recordType"
entity="Accounting-Record-Type"></store>
> > > <store name="recordNumber"
entity="Accounting-Record-Number"></store>
> > > <check-value name="Accounting-Record-Type"
behaviour="error"></check-value>
> > > </action>
> > > </receive>
> > > <!------------------ ACA START -------------------->
> > > <send channel="channel-1">
> > > <!-- Restore action is before the command -->
> > > <action>
> > > <restore name="HbH" entity="HbH-id"> </restore>
> > > <restore name="E2E" entity="EtE-id"> </restore>
> > > <restore name="sid" entity="Session-Id"> </restore>
> > > <restore name="recordType" entity="Accounting-Record-Type">
</restore>
> > > <restore name="recordNumber"
entity="Accounting-Record-Number"> </restore>
> > > </action>
> > > <!-- Warning: content of CCA to check -->
> > > <command name="ACA">
> > > <avp name="Session-Id" value="will_be_erased"> </avp>
> > > <avp name="Vendor-Specific-Application-Id">
> > > <avp name="Vendor-Id" value="10415"></avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </avp>
> > > <avp name="Origin-Host" value="172.20.32.242"> </avp>
> > > <avp name="Origin-Realm" value="one.att.com"> </avp>
> > > <avp name="Accounting-Record-Type" value="0"> </avp>
> > > <avp name="Accounting-Record-Number" value="0"> </avp>
> > > <avp name="Result-Code" value="2001"> </avp>
> > > <avp name="Acct-Interim-Interval" value="900"> </avp>
> > > </command>
> > > </send>
> > >
> > >
> > > <!------------------ ACR STOP -------------------->
> > > <receive channel="channel-1">
> > > <command name="ACR">
> > > <!-- Only need to specify what needs to be parsed -->
> > > <avp name="Session-Id" value="dont_care"> </avp>
> > > <avp name="Accounting-Record-Type" value="0x00000004">
</avp>
> > > </command>
> > > <!-- Store action is at the end of the command -->
> > > <action>
> > > <store name="HbH" entity="HbH-id"></store>
> > > <store name="E2E" entity="EtE-id"></store>
> > > <store name="sid" entity="Session-Id"></store>
> > > <store name="recordType"
entity="Accounting-Record-Type"></store>
> > > <store name="recordNumber"
entity="Accounting-Record-Number"></store>
> > > <check-value name="Accounting-Record-Type"
behaviour="error"></check-value>
> > > </action>
> > > </receive>
> > >
> > > <!------------------ ACA STOP -------------------->
> > > <send channel="channel-1">
> > > <!-- Restore action is before the command -->
> > > <action>
> > > <restore name="HbH" entity="HbH-id"> </restore>
> > > <restore name="E2E" entity="EtE-id"> </restore>
> > > <restore name="sid" entity="Session-Id"> </restore>
> > > <restore name="recordType" entity="Accounting-Record-Type">
</restore>
> > > <restore name="recordNumber"
entity="Accounting-Record-Number"> </restore>
> > > </action>
> > > <!-- Warning: content of CCA to check -->
> > > <command name="ACA">
> > > <avp name="Session-Id" value="will_be_erased"> </avp>
> > > <avp name="Vendor-Specific-Application-Id">
> > > <avp name="Vendor-Id" value="10415"></avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </avp>
> > > <avp name="Origin-Host" value="172.20.32.242"> </avp>
> > > <avp name="Origin-Realm" value="one.att.com"> </avp>
> > > <avp name="Accounting-Record-Type" value="0"> </avp>
> > > <avp name="Accounting-Record-Number" value="0"> </avp>
> > > <avp name="Result-Code" value="2001"> </avp>
> > > <avp name="Acct-Interim-Interval" value="900"> </avp>
> > > </command>
> > > </send>
> > > </traffic>
> > >
> > >
> > >
> > > <default behaviour="ignore">
> > > <receive channel="channel-1">
> > > <command name="DWR">
> > > </command>
> > > </receive>
> > > <send channel="channel-1">
> > > <command name="DWA">
> > > <avp name="Origin-Host" value="ccf-server"> </avp>
> > > <avp name="Origin-Realm" value="one.att.com"> </avp>
> > > <avp name="Result-Code" value="2001"> </avp>
> > > </command>
> > > </send>
> > > </default>
> > >
> > > <default behaviour="ignore">
> > > <receive channel="channel-1">
> > > <command name="CER">
> > > </command>
> > > <action>
> > > <store name="ven" entity="Vendor-Id"> </store>
> > > </action>
> > > </receive>
> > >
> > > <send channel="channel-1">
> > > <command name="CEA">
> > > <avp name="Origin-Host" value="ccf-server"> </avp>
> > > <avp name="Origin-Realm" value="one.att.com"> </avp>
> > > <avp name="Result-Code" value="2001"> </avp>
> > > <avp name="Host-IP-Address" value="0x0001ac1420f2"> </avp>
> > > <avp name="Vendor-Id" value="14954"> </avp>
> > > <avp name="Product-Name" value="Server"> </avp>
> > > <avp name="Inband-Security-Id" value="0"> </avp>
> > > <avp name="Firmware-Revision" value="1"> </avp>
> > > <avp name="Vendor-Specific-Application-Id">
> > > <avp name="Vendor-Id" value="10415"></avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </avp>
> > > <avp name="Acct-Application-Id" value="3"></avp>
> > > </command>
> > > </send>
> > > </default>
> > > </scenario>
> > >
> > >
> > >
> > >
> > > Gal Goffer
> > > R&D, Multimedia Telephony Team
> > > AT&T Unified Communications
> >
> > >
> > >
> > >
> > >
> > >
> > >
************************************************************************************
> > > This footnote confirms that this email message has been scanned by
> > > PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
> > >
************************************************************************************
> > >
------------------------------------------------------------------------------
> > > Open source business process management suite built on Java and
Eclipse
> > > Turn processes into business applications with Bonita BPM Community
Edition
> > > Quickly connect people, data, and systems into organized workflows
> > > Winner of BOSSIE, CODIE, OW2 and Gartner awards
> > >
http://p.sf.net/sfu/Bonitasoft_______________________________________________
> > > Gull-users mailing list
> > > Gul...@li...
> > > https://lists.sourceforge.net/lists/listinfo/gull-users
> >
> > The information included in this e-mail and any files transmitted with
it is strictly
> > confidential and may be privileged or otherwise protected from
disclosure. If you are not the
> > intended recipient, please notify the sender immediately by e-mail and
delete this e-mail as well
> > as any attachment from your system. If you are not the intended
recipient you are not authorized
> > to use and/or copy this message and/or attachment and/or disclose the
contents to any other person.
> >
> >
> >
> >
************************************************************************************
> > This footnote confirms that this email message has been scanned by
> > PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
> >
************************************************************************************
> >
> >
> >
> >
> >
************************************************************************************
> > This footnote confirms that this email message has been scanned by
> > PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
> >
************************************************************************************
>
> The information included in this e-mail and any files transmitted with
it is strictly
> confidential and may be privileged or otherwise protected from
disclosure. If you are not the
> intended recipient, please notify the sender immediately by e-mail and
delete this e-mail as well
> as any attachment from your system. If you are not the intended
recipient you are not authorized
> to use and/or copy this message and/or attachment and/or disclose the
contents to any other person.
>
>
>
>
************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
>
************************************************************************************
>
>
>
>
>
************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
>
************************************************************************************
The information included in this e-mail and any files transmitted with it is strictly confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this e-mail as well as any attachment from your system. If you are not the intended recipient you are not authorized to use and/or copy this message and/or attachment and/or disclose the contents to any other person. |
