Menu
▾
▴
gull-users
|
From: Joaquin A. <Joa...@le...> - 2017-01-04 13:05:56
|
Hi Guys
I am almost finished with an OCS Diameter configuration where I have to send.
CCR-I
CCR-U
CCR-T
All this CCRs have to maintain the same Session ID.
Currently:
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
So When sending the CCR-U the counter increases the value one so from CCR-I to CCR-U it will have different Session-Id.
Putting a harcoded value (the same all the time I will try to avoid it).
Is there a way to maintain the Session ID which such as a combination of YYYYMMDDhhmmss?
Bellow the ccr-cca.client.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario>
<counter>
<counterdef name="HbH-counter" init="1000"> </counterdef>
<counterdef name="EtE-counter" init="2000"> </counterdef>
<counterdef name="session-counter" init="0"> </counterdef>
</counter>
<init>
<send channel="channel-1">
<command name="CER">
<avp name="Origin-Host" value="XX"> </avp>
<avp name="Origin-Realm" value="XX"> </avp>
<avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
<avp name="Vendor-Id" value="2"> </avp>
<avp name="Product-Name" value="HP Cx Interface"> </avp>
<avp name="Origin-State-Id" value="1094807040"> </avp>
<avp name="Vendor-Specific-Application-Id">
<avp name="Vendor-Id" value="11"></avp>
<avp name="Auth-Application-Id" value="167772151"></avp>
<avp name="Acct-Application-Id" value="0"></avp>
</avp>
<avp name="Firmware-Revision" value="1"> </avp>
</command>
</send>
<receive channel="channel-1">
<command name="CEA">
</command>
</receive>
</init>
<!-- Traffic -->
<traffic>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXX"> </avp>
<avp name="Destination-Realm" value="XXX"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="1"> </avp>
<avp name="CC-Request-Number" value="0"> </avp>
<avp name="Service-Context-Id" value="32...@3g..."></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="XXX"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XXXXXXXXXX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XXXXXX"></avp>
<avp name="GGSN-Address" value="XXXXXXX"></avp>
<avp name="CG-Address" value="XXXXXXXXX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="up_lebara.dra.hplmn"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXXXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
<avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="2"> </avp>
<avp name="CC-Request-Number" value="1"> </avp>
<avp name="Service-Context-Id" value="32...@3g..."></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="OCG"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Multiple-Services-Credit-Control">
<avp name="Requested-Service-Unit" value=""></avp>
<avp name="Used-Service-Unit">
<avp name="CC-Time" value="0"></avp>
<avp name="CC-Total-Octets" value="0"></avp>
<avp name="CC-Input-Octets" value="0"></avp>
<avp name="CC-Output-Octets" value="0"></avp>
</avp>
<avp name="Rating-Group" value="3000"></avp>
<avp name="3GPP-Reporting-Reason" value="4"></avp>
</avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="XXX"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XX"></avp>
<avp name="GGSN-Address" value="XX"></avp>
<avp name="CG-Address" value="XX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="XXXXXXXXXXX"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
</traffic>
</scenario>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
|
|
From: Konstantin T. <kt...@am...> - 2017-01-04 17:20:59
|
Hello Joaquin,
I believe you need "<inc-counter name="session-counter"> </inc-counter>" only when you send CCR-I. Try to remove it from CCR-U and CCR-T.
I'm not sure if it's possible to set current time as a counter variable and assign it to Session-ID.
Regards,
Konstantin Tyurin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 7:06
To: gul...@li...
Subject: [Seagull-users] Session-ID
Hi Guys
I am almost finished with an OCS Diameter configuration where I have to send.
CCR-I
CCR-U
CCR-T
All this CCRs have to maintain the same Session ID.
Currently:
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
So When sending the CCR-U the counter increases the value one so from CCR-I to CCR-U it will have different Session-Id.
Putting a harcoded value (the same all the time I will try to avoid it).
Is there a way to maintain the Session ID which such as a combination of YYYYMMDDhhmmss?
Bellow the ccr-cca.client.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario>
<counter>
<counterdef name="HbH-counter" init="1000"> </counterdef>
<counterdef name="EtE-counter" init="2000"> </counterdef>
<counterdef name="session-counter" init="0"> </counterdef>
</counter>
<init>
<send channel="channel-1">
<command name="CER">
<avp name="Origin-Host" value="XX"> </avp>
<avp name="Origin-Realm" value="XX"> </avp>
<avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
<avp name="Vendor-Id" value="2"> </avp>
<avp name="Product-Name" value="HP Cx Interface"> </avp>
<avp name="Origin-State-Id" value="1094807040"> </avp>
<avp name="Vendor-Specific-Application-Id">
<avp name="Vendor-Id" value="11"></avp>
<avp name="Auth-Application-Id" value="167772151"></avp>
<avp name="Acct-Application-Id" value="0"></avp>
</avp>
<avp name="Firmware-Revision" value="1"> </avp>
</command>
</send>
<receive channel="channel-1">
<command name="CEA">
</command>
</receive>
</init>
<!-- Traffic -->
<traffic>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXX"> </avp>
<avp name="Destination-Realm" value="XXX"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="1"> </avp>
<avp name="CC-Request-Number" value="0"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="XXX"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XXXXXXXXXX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XXXXXX"></avp>
<avp name="GGSN-Address" value="XXXXXXX"></avp>
<avp name="CG-Address" value="XXXXXXXXX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="up_lebara.dra.hplmn"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXXXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
<avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="2"> </avp>
<avp name="CC-Request-Number" value="1"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="OCG"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Multiple-Services-Credit-Control">
<avp name="Requested-Service-Unit" value=""></avp>
<avp name="Used-Service-Unit">
<avp name="CC-Time" value="0"></avp>
<avp name="CC-Total-Octets" value="0"></avp>
<avp name="CC-Input-Octets" value="0"></avp>
<avp name="CC-Output-Octets" value="0"></avp>
</avp>
<avp name="Rating-Group" value="3000"></avp>
<avp name="3GPP-Reporting-Reason" value="4"></avp>
</avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="XXX"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XX"></avp>
<avp name="GGSN-Address" value="XX"></avp>
<avp name="CG-Address" value="XX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="XXXXXXXXXXX"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
</traffic>
</scenario>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
|
|
From: Joaquin A. <Joa...@le...> - 2017-01-04 18:17:09
|
Thanks Kostantin, that make the Session ID to be the same throughout the message.
Was hoping to add the date (or some other form of rand()) so I could have a random Session-ID each time I launch the ./start_client….
What you suggested work fine.
From: Konstantin Tyurin [mailto:kt...@am...]
Sent: 04 January 2017 17:21
To: Joaquin Alzola <Joa...@le...>
Cc: gul...@li...
Subject: RE: Session-ID
Hello Joaquin,
I believe you need “<inc-counter name="session-counter"> </inc-counter>” only when you send CCR-I. Try to remove it from CCR-U and CCR-T.
I’m not sure if it’s possible to set current time as a counter variable and assign it to Session-ID.
Regards,
Konstantin Tyurin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 7:06
To: gul...@li...<mailto:gul...@li...>
Subject: [Seagull-users] Session-ID
Hi Guys
I am almost finished with an OCS Diameter configuration where I have to send.
CCR-I
CCR-U
CCR-T
All this CCRs have to maintain the same Session ID.
Currently:
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
So When sending the CCR-U the counter increases the value one so from CCR-I to CCR-U it will have different Session-Id.
Putting a harcoded value (the same all the time I will try to avoid it).
Is there a way to maintain the Session ID which such as a combination of YYYYMMDDhhmmss?
Bellow the ccr-cca.client.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario>
<counter>
<counterdef name="HbH-counter" init="1000"> </counterdef>
<counterdef name="EtE-counter" init="2000"> </counterdef>
<counterdef name="session-counter" init="0"> </counterdef>
</counter>
<init>
<send channel="channel-1">
<command name="CER">
<avp name="Origin-Host" value="XX"> </avp>
<avp name="Origin-Realm" value="XX"> </avp>
<avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
<avp name="Vendor-Id" value="2"> </avp>
<avp name="Product-Name" value="HP Cx Interface"> </avp>
<avp name="Origin-State-Id" value="1094807040"> </avp>
<avp name="Vendor-Specific-Application-Id">
<avp name="Vendor-Id" value="11"></avp>
<avp name="Auth-Application-Id" value="167772151"></avp>
<avp name="Acct-Application-Id" value="0"></avp>
</avp>
<avp name="Firmware-Revision" value="1"> </avp>
</command>
</send>
<receive channel="channel-1">
<command name="CEA">
</command>
</receive>
</init>
<!-- Traffic -->
<traffic>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXX"> </avp>
<avp name="Destination-Realm" value="XXX"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="1"> </avp>
<avp name="CC-Request-Number" value="0"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="XXX"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XXXXXXXXXX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XXXXXX"></avp>
<avp name="GGSN-Address" value="XXXXXXX"></avp>
<avp name="CG-Address" value="XXXXXXXXX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="up_lebara.dra.hplmn"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXXXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
<avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="2"> </avp>
<avp name="CC-Request-Number" value="1"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="OCG"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Multiple-Services-Credit-Control">
<avp name="Requested-Service-Unit" value=""></avp>
<avp name="Used-Service-Unit">
<avp name="CC-Time" value="0"></avp>
<avp name="CC-Total-Octets" value="0"></avp>
<avp name="CC-Input-Octets" value="0"></avp>
<avp name="CC-Output-Octets" value="0"></avp>
</avp>
<avp name="Rating-Group" value="3000"></avp>
<avp name="3GPP-Reporting-Reason" value="4"></avp>
</avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="XXX"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XX"></avp>
<avp name="GGSN-Address" value="XX"></avp>
<avp name="CG-Address" value="XX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="XXXXXXXXXXX"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
</traffic>
</scenario>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
|
|
From: Konstantin T. <kt...@am...> - 2017-01-04 18:28:34
|
As far as I know seagull can't do it.
You can write some bash/perl script for this. Long time ago we did it to emulate different Result-Code values from server. There was a scenario template file with placeholder inside. You run the starting script, it replaces the placeholder to the value you want (random or current date in your case) and then starts the seagull with this scenario. Unfortunately I don't have such script but it was just a few lines, will be easy for you if you decide to write one.
Regards,
Konstantin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 12:17
To: Konstantin Tyurin <kt...@am...>
Cc: gul...@li...
Subject: RE: Session-ID
Thanks Kostantin, that make the Session ID to be the same throughout the message.
Was hoping to add the date (or some other form of rand()) so I could have a random Session-ID each time I launch the ./start_client....
What you suggested work fine.
From: Konstantin Tyurin [mailto:kt...@am...]
Sent: 04 January 2017 17:21
To: Joaquin Alzola <Joa...@le...<mailto:Joa...@le...>>
Cc: gul...@li...<mailto:gul...@li...>
Subject: RE: Session-ID
Hello Joaquin,
I believe you need "<inc-counter name="session-counter"> </inc-counter>" only when you send CCR-I. Try to remove it from CCR-U and CCR-T.
I'm not sure if it's possible to set current time as a counter variable and assign it to Session-ID.
Regards,
Konstantin Tyurin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 7:06
To: gul...@li...<mailto:gul...@li...>
Subject: [Seagull-users] Session-ID
Hi Guys
I am almost finished with an OCS Diameter configuration where I have to send.
CCR-I
CCR-U
CCR-T
All this CCRs have to maintain the same Session ID.
Currently:
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
So When sending the CCR-U the counter increases the value one so from CCR-I to CCR-U it will have different Session-Id.
Putting a harcoded value (the same all the time I will try to avoid it).
Is there a way to maintain the Session ID which such as a combination of YYYYMMDDhhmmss?
Bellow the ccr-cca.client.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario>
<counter>
<counterdef name="HbH-counter" init="1000"> </counterdef>
<counterdef name="EtE-counter" init="2000"> </counterdef>
<counterdef name="session-counter" init="0"> </counterdef>
</counter>
<init>
<send channel="channel-1">
<command name="CER">
<avp name="Origin-Host" value="XX"> </avp>
<avp name="Origin-Realm" value="XX"> </avp>
<avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
<avp name="Vendor-Id" value="2"> </avp>
<avp name="Product-Name" value="HP Cx Interface"> </avp>
<avp name="Origin-State-Id" value="1094807040"> </avp>
<avp name="Vendor-Specific-Application-Id">
<avp name="Vendor-Id" value="11"></avp>
<avp name="Auth-Application-Id" value="167772151"></avp>
<avp name="Acct-Application-Id" value="0"></avp>
</avp>
<avp name="Firmware-Revision" value="1"> </avp>
</command>
</send>
<receive channel="channel-1">
<command name="CEA">
</command>
</receive>
</init>
<!-- Traffic -->
<traffic>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXX"> </avp>
<avp name="Destination-Realm" value="XXX"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="1"> </avp>
<avp name="CC-Request-Number" value="0"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="XXX"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XXXXXXXXXX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XXXXXX"></avp>
<avp name="GGSN-Address" value="XXXXXXX"></avp>
<avp name="CG-Address" value="XXXXXXXXX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="up_lebara.dra.hplmn"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXXXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
<avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="2"> </avp>
<avp name="CC-Request-Number" value="1"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="OCG"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Multiple-Services-Credit-Control">
<avp name="Requested-Service-Unit" value=""></avp>
<avp name="Used-Service-Unit">
<avp name="CC-Time" value="0"></avp>
<avp name="CC-Total-Octets" value="0"></avp>
<avp name="CC-Input-Octets" value="0"></avp>
<avp name="CC-Output-Octets" value="0"></avp>
</avp>
<avp name="Rating-Group" value="3000"></avp>
<avp name="3GPP-Reporting-Reason" value="4"></avp>
</avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="XXX"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XX"></avp>
<avp name="GGSN-Address" value="XX"></avp>
<avp name="CG-Address" value="XX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="XXXXXXXXXXX"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
</traffic>
</scenario>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
|
|
From: Joaquin A. <Joa...@le...> - 2017-01-04 19:06:10
|
Thx for the tip
date=`date +"%Y%m%d%H%M%S"`
sed -e "s/XXCXX/$date/g" ../scenario/ccr-cca.client.xml.macro > ../scenario/ccr-cca.client.xml
seagull -conf ../config/conf.client.1call.xml -dico ../config/base_cc.xml -scen ../scenario/ccr-cca.client.xml -log ../logs/client.log -llevel ET
got it working now with uniq Session-Ids.
One thing less to worry :)
From: Konstantin Tyurin [mailto:kt...@am...]
Sent: 04 January 2017 18:28
To: Joaquin Alzola <Joa...@le...>
Cc: gul...@li...
Subject: RE: Session-ID
As far as I know seagull can’t do it.
You can write some bash/perl script for this. Long time ago we did it to emulate different Result-Code values from server. There was a scenario template file with placeholder inside. You run the starting script, it replaces the placeholder to the value you want (random or current date in your case) and then starts the seagull with this scenario. Unfortunately I don’t have such script but it was just a few lines, will be easy for you if you decide to write one.
Regards,
Konstantin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 12:17
To: Konstantin Tyurin <kt...@am...<mailto:kt...@am...>>
Cc: gul...@li...<mailto:gul...@li...>
Subject: RE: Session-ID
Thanks Kostantin, that make the Session ID to be the same throughout the message.
Was hoping to add the date (or some other form of rand()) so I could have a random Session-ID each time I launch the ./start_client….
What you suggested work fine.
From: Konstantin Tyurin [mailto:kt...@am...]
Sent: 04 January 2017 17:21
To: Joaquin Alzola <Joa...@le...<mailto:Joa...@le...>>
Cc: gul...@li...<mailto:gul...@li...>
Subject: RE: Session-ID
Hello Joaquin,
I believe you need “<inc-counter name="session-counter"> </inc-counter>” only when you send CCR-I. Try to remove it from CCR-U and CCR-T.
I’m not sure if it’s possible to set current time as a counter variable and assign it to Session-ID.
Regards,
Konstantin Tyurin.
From: Joaquin Alzola [mailto:Joa...@le...]
Sent: 4 января 2017 г. 7:06
To: gul...@li...<mailto:gul...@li...>
Subject: [Seagull-users] Session-ID
Hi Guys
I am almost finished with an OCS Diameter configuration where I have to send.
CCR-I
CCR-U
CCR-T
All this CCRs have to maintain the same Session ID.
Currently:
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
So When sending the CCR-U the counter increases the value one so from CCR-I to CCR-U it will have different Session-Id.
Putting a harcoded value (the same all the time I will try to avoid it).
Is there a way to maintain the Session ID which such as a combination of YYYYMMDDhhmmss?
Bellow the ccr-cca.client.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<scenario>
<counter>
<counterdef name="HbH-counter" init="1000"> </counterdef>
<counterdef name="EtE-counter" init="2000"> </counterdef>
<counterdef name="session-counter" init="0"> </counterdef>
</counter>
<init>
<send channel="channel-1">
<command name="CER">
<avp name="Origin-Host" value="XX"> </avp>
<avp name="Origin-Realm" value="XX"> </avp>
<avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
<avp name="Vendor-Id" value="2"> </avp>
<avp name="Product-Name" value="HP Cx Interface"> </avp>
<avp name="Origin-State-Id" value="1094807040"> </avp>
<avp name="Vendor-Specific-Application-Id">
<avp name="Vendor-Id" value="11"></avp>
<avp name="Auth-Application-Id" value="167772151"></avp>
<avp name="Acct-Application-Id" value="0"></avp>
</avp>
<avp name="Firmware-Revision" value="1"> </avp>
</command>
</send>
<receive channel="channel-1">
<command name="CEA">
</command>
</receive>
</init>
<!-- Traffic -->
<traffic>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXX"> </avp>
<avp name="Destination-Realm" value="XXX"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="1"> </avp>
<avp name="CC-Request-Number" value="0"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="XXX"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XXXXXXXXXX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XXXXXX"></avp>
<avp name="GGSN-Address" value="XXXXXXX"></avp>
<avp name="CG-Address" value="XXXXXXXXX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="up_lebara.dra.hplmn"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
<send channel="channel-1">
<action>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id"
format="$(HbH-counter)"></set-value>
<set-value name="EtE-id"
format="$(EtE-counter)"></set-value>
<set-value name="Session-Id"
format=".;1096298391;$(session-counter)"></set-value>
</action>
<command name="CCR">
<avp name="Session-Id" value="value_is_replaced"> </avp>
<avp name="Origin-Host" value="XXXXXXXXX"> </avp>
<avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
<avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
<avp name="Auth-Application-Id" value="4"></avp>
<avp name="CC-Request-Type" value="2"> </avp>
<avp name="CC-Request-Number" value="1"> </avp>
<avp name="Service-Context-Id" value="32...@3g...<mailto:32...@3g...>"></avp>
<avp name="Origin-State-Id" value="612"></avp>
<avp name="Destination-Host" value="OCG"> </avp>
<avp name="Subscription-Id">
<avp name="Subscription-Id-Type" value="0"></avp>
<avp name="Subscription-Id-Data" value="31645958277"></avp>
</avp>
<avp name="Multiple-Services-Indicator" value="1"> </avp>
<avp name="Multiple-Services-Credit-Control">
<avp name="Requested-Service-Unit" value=""></avp>
<avp name="Used-Service-Unit">
<avp name="CC-Time" value="0"></avp>
<avp name="CC-Total-Octets" value="0"></avp>
<avp name="CC-Input-Octets" value="0"></avp>
<avp name="CC-Output-Octets" value="0"></avp>
</avp>
<avp name="Rating-Group" value="3000"></avp>
<avp name="3GPP-Reporting-Reason" value="4"></avp>
</avp>
<avp name="Service-Information">
<avp name="PS-Information">
<avp name="3GPP-Charging-Id" value="XXX"></avp>
<avp name="3GPP-PDP-Type" value="0"></avp>
<avp name="PDP-Address" value="XX"></avp>
<avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-23921f9196fefe742bfefe006200"></avp>
<avp name="SGSN-Address" value="XX"></avp>
<avp name="GGSN-Address" value="XX"></avp>
<avp name="CG-Address" value="XX"></avp>
<avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
<avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
<avp name="3GPP-NSAPI" value="5"></avp>
<avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
<avp name="3GPP-Selection-Mode" value="0"></avp>
<avp name="3GPP-Charging-Characteristics" value="0800"></avp>
<avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
<!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
<avp name="3GPP-User-Location-Info" value="0x0102f496232e9246"></avp>
<avp name="3GPP-RAT-Type" value="01"></avp>
<avp name="PDP-Context-Type" value="0"></avp>
<avp name="Charging-Rule-Base-Name" value="XXXXXXXXXXX"></avp>
</avp>
</avp>
<!-- Added -->
</command>
<action>
<start-timer></start-timer>
</action>
</send>
<receive channel="channel-1">
<action>
<stop-timer></stop-timer>
</action>
<command name="CCA">
</command>
</receive>
</traffic>
</scenario>
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
This email is confidential and may be subject to privilege. If you are not the intended recipient, please do not copy or disclose its content but contact the sender immediately upon receipt.
|
|
From: Andrzej K. <kol...@gm...> - 2017-01-05 09:32:35
|
hi,
I usually have action section before the initial request
<action>
<!-- select MSISDN from msisdn.csv file -->
<restore-from-external field="0" entity="Subscription-Id-Data">
</restore-from-external>
<restore-from-external field="2" name="SID"> </restore-from-external>
<!-- For each new call, increment the session-ID counter -->
<inc-counter name="HbH-counter"> </inc-counter>
<inc-counter name="EtE-counter"> </inc-counter>
<inc-counter name="session-counter"> </inc-counter>
<set-value name="HbH-id" format="$(HbH-counter)"></set-value>
<set-value name="EtE-id" format="$(EtE-counter)"></set-value>
<!--<set-value name="Session-Id"
format="VOICE_TEST$(SID)_$(session-counter)"></set-value>-->
<set-value name="Session-Id"
format="$(SID)_VOICE_DEBIT_$(session-counter)"></set-value>
</action>
this selects a MSISD and session ID form a file that might look similar to
this one where the last field is the randomized session ID. Making the
session ID pool large enough decreases the chance of collision.
"string";"string";"string";
"6475733471";"666";"414120592";
"6475733471";"666";"39512391 ";
"6475733471";"666";"990417978";
"6475733471";"666";"909629085";
"6475733471";"666";"802470384";
"6475733471";"666";"600034366";
"6475733471";"666";"414104570";
"6475733471";"666";"889011086";
"6475733471";"666";"950753403";
then throughout the scenario file you must maintain the session id
so after each request you must store the values in an action section
<action>
<store name="SESSION_ID" entity="Session-Id"></store>
<store name="MSISDN" entity="Subscription-Id-Data"> </store>
<start-timer></start-timer>
</action>
and the restore them before the next request.
I don't really bother formatting part of the session ID from date as this
still can result in an Id that is not unique if the rate is high enough...
don't forget to configure your file in the config...
cheers,
Andrzej
On 4 January 2017 at 19:50, Joaquin Alzola <Joa...@le...>
wrote:
> Thx for the tip
>
>
>
> date=`date +"%Y%m%d%H%M%S"`
>
> sed -e "s/XXCXX/$date/g" ../scenario/ccr-cca.client.xml.macro >
> ../scenario/ccr-cca.client.xml
>
> seagull -conf ../config/conf.client.1call.xml -dico ../config/base_cc.xml
> -scen ../scenario/ccr-cca.client.xml -log ../logs/client.log -llevel ET
>
>
>
> got it working now with uniq Session-Ids.
>
>
>
> One thing less to worry J
>
>
>
> *From:* Konstantin Tyurin [mailto:kt...@am...]
> *Sent:* 04 January 2017 18:28
>
> *To:* Joaquin Alzola <Joa...@le...>
> *Cc:* gul...@li...
> *Subject:* RE: Session-ID
>
>
>
> As far as I know seagull can’t do it.
>
>
>
> You can write some bash/perl script for this. Long time ago we did it to
> emulate different Result-Code values from server. There was a scenario
> template file with placeholder inside. You run the starting script, it
> replaces the placeholder to the value you want (random or current date in
> your case) and then starts the seagull with this scenario. Unfortunately I
> don’t have such script but it was just a few lines, will be easy for you if
> you decide to write one.
>
>
>
> Regards,
>
> Konstantin.
>
>
>
> *From:* Joaquin Alzola [mailto:Joa...@le...
> <Joa...@le...>]
> *Sent:* 4 января 2017 г. 12:17
> *To:* Konstantin Tyurin <kt...@am...>
> *Cc:* gul...@li...
> *Subject:* RE: Session-ID
>
>
>
> Thanks Kostantin, that make the Session ID to be the same throughout the
> message.
>
> Was hoping to add the date (or some other form of rand()) so I could have
> a random Session-ID each time I launch the ./start_client….
>
>
>
> What you suggested work fine.
>
>
>
> *From:* Konstantin Tyurin [mailto:kt...@am... <kt...@am...>]
>
> *Sent:* 04 January 2017 17:21
> *To:* Joaquin Alzola <Joa...@le...>
> *Cc:* gul...@li...
> *Subject:* RE: Session-ID
>
>
>
> Hello Joaquin,
>
>
>
> I believe you need “<inc-counter name="session-counter"> </inc-counter>”
> only when you send CCR-I. Try to remove it from CCR-U and CCR-T.
>
>
>
> I’m not sure if it’s possible to set current time as a counter variable
> and assign it to Session-ID.
>
>
>
> Regards,
>
> Konstantin Tyurin.
>
>
>
> *From:* Joaquin Alzola [mailto:Joa...@le...
> <Joa...@le...>]
> *Sent:* 4 января 2017 г. 7:06
> *To:* gul...@li...
> *Subject:* [Seagull-users] Session-ID
>
>
>
> Hi Guys
>
>
>
> I am almost finished with an OCS Diameter configuration where I have to
> send.
>
>
>
> CCR-I
>
> CCR-U
>
> CCR-T
>
>
>
> All this CCRs have to maintain the same Session ID.
>
>
>
> Currently:
>
> <set-value name="Session-Id"
>
> format=".;1096298391;$(session-counter)"></set-value>
>
>
>
> So When sending the CCR-U the counter increases the value one so from
> CCR-I to CCR-U it will have different Session-Id.
>
>
>
> Putting a harcoded value (the same all the time I will try to avoid it).
>
>
>
> Is there a way to maintain the Session ID which such as a combination of
> YYYYMMDDhhmmss?
>
>
>
>
>
> Bellow the ccr-cca.client.xml
>
>
>
> <?xml version="1.0" encoding="ISO-8859-1" ?>
>
> <scenario>
>
>
>
> <counter>
>
> <counterdef name="HbH-counter" init="1000"> </counterdef>
>
> <counterdef name="EtE-counter" init="2000"> </counterdef>
>
> <counterdef name="session-counter" init="0"> </counterdef>
>
> </counter>
>
>
>
> <init>
>
> <send channel="channel-1">
>
> <command name="CER">
>
> <avp name="Origin-Host" value="XX"> </avp>
>
> <avp name="Origin-Realm" value="XX"> </avp>
>
> <avp name="Host-IP-Address" value="xxxxxxxx"> </avp>
>
> <avp name="Vendor-Id" value="2"> </avp>
>
> <avp name="Product-Name" value="HP Cx Interface"> </avp>
>
> <avp name="Origin-State-Id" value="1094807040"> </avp>
>
> <avp name="Vendor-Specific-Application-Id">
>
> <avp name="Vendor-Id" value="11"></avp>
>
> <avp name="Auth-Application-Id" value="167772151
> <16%20777%2021%2051>"></avp>
>
> <avp name="Acct-Application-Id" value="0"></avp>
>
> </avp>
>
> <avp name="Firmware-Revision" value="1"> </avp>
>
> </command>
>
> </send>
>
>
>
> <receive channel="channel-1">
>
> <command name="CEA">
>
> </command>
>
> </receive>
>
> </init>
>
>
>
> <!-- Traffic -->
>
> <traffic>
>
> <send channel="channel-1">
>
> <action>
>
> <!-- For each new call, increment the session-ID counter -->
>
> <inc-counter name="HbH-counter"> </inc-counter>
>
> <inc-counter name="EtE-counter"> </inc-counter>
>
> <inc-counter name="session-counter"> </inc-counter>
>
> <set-value name="HbH-id"
>
> format="$(HbH-counter)"></set-value>
>
> <set-value name="EtE-id"
>
> format="$(EtE-counter)"></set-value>
>
> <set-value name="Session-Id"
>
> format=".;1096298391;$(session-counter)"></set-value>
>
> </action>
>
> <command name="CCR">
>
> <avp name="Session-Id" value="value_is_replaced"> </avp>
>
> <avp name="Origin-Host" value="XXXXX"> </avp>
>
> <avp name="Origin-Realm" value="XXXXX"> </avp>
>
> <avp name="Destination-Realm" value="XXX"> </avp>
>
> <avp name="Auth-Application-Id" value="4"></avp>
>
> <avp name="CC-Request-Type" value="1"> </avp>
>
> <avp name="CC-Request-Number" value="0"> </avp>
>
> <avp name="Service-Context-Id" value="32...@3g..."></avp>
>
> <avp name="Origin-State-Id" value="612"></avp>
>
> <avp name="Destination-Host" value="XXX"> </avp>
>
> <avp name="Subscription-Id">
>
> <avp name="Subscription-Id-Type" value="0"></avp>
>
> <avp name="Subscription-Id-Data" value="31645958277"></avp>
>
> </avp>
>
> <avp name="Multiple-Services-Indicator" value="1"> </avp>
>
> <avp name="Service-Information">
>
> <avp name="PS-Information">
>
> <avp name="3GPP-Charging-Id" value="0x8200033b"></avp>
>
> <avp name="3GPP-PDP-Type" value="0"></avp>
>
> <avp name="PDP-Address" value="XXXXXXXXXX"></avp>
>
> <avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-
> 23921f9196fefe742bfefe006200"></avp>
>
> <avp name="SGSN-Address" value="XXXXXX"></avp>
>
> <avp name="GGSN-Address" value="XXXXXXX"></avp>
>
> <avp name="CG-Address" value="XXXXXXXXX"></avp>
>
> <avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
>
> <avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
>
> <avp name="3GPP-NSAPI" value="5"></avp>
>
> <avp name="Called-Station-Id" value="XXXXXXXXXX"></avp>
>
> <avp name="3GPP-Selection-Mode" value="0"></avp>
>
> <avp name="3GPP-Charging-Characteristics"
> value="0800"></avp>
>
> <avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
>
> <!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
>
> <avp name="3GPP-User-Location-Info"
> value="0x0102f496232e9246"></avp>
>
> <avp name="3GPP-RAT-Type" value="01"></avp>
>
> <avp name="PDP-Context-Type" value="0"></avp>
>
> <avp name="Charging-Rule-Base-Name"
> value="up_lebara.dra.hplmn"></avp>
>
> </avp>
>
> </avp>
>
> <!-- Added -->
>
> </command>
>
> <action>
>
> <start-timer></start-timer>
>
> </action>
>
> </send>
>
>
>
> <receive channel="channel-1">
>
> <action>
>
> <stop-timer></stop-timer>
>
> </action>
>
> <command name="CCA">
>
> </command>
>
> </receive>
>
>
>
> <send channel="channel-1">
>
> <action>
>
> <!-- For each new call, increment the session-ID counter -->
>
> <inc-counter name="HbH-counter"> </inc-counter>
>
> <inc-counter name="EtE-counter"> </inc-counter>
>
> <inc-counter name="session-counter"> </inc-counter>
>
> <set-value name="HbH-id"
>
> format="$(HbH-counter)"></set-value>
>
> <set-value name="EtE-id"
>
> format="$(EtE-counter)"></set-value>
>
> <set-value name="Session-Id"
>
> format=".;1096298391;$(session-counter)"></set-value>
>
> </action>
>
> <command name="CCR">
>
> <avp name="Session-Id" value="value_is_replaced"> </avp>
>
> <avp name="Origin-Host" value="XXXXXXXXX"> </avp>
>
> <avp name="Origin-Realm" value="XXXXXXXXXXX"> </avp>
>
> <avp name="Destination-Realm" value="ocg.huawei.com"> </avp>
>
> <avp name="Auth-Application-Id" value="4"></avp>
>
> <avp name="CC-Request-Type" value="2"> </avp>
>
> <avp name="CC-Request-Number" value="1"> </avp>
>
> <avp name="Service-Context-Id" value="32...@3g..."></avp>
>
> <avp name="Origin-State-Id" value="612"></avp>
>
> <avp name="Destination-Host" value="OCG"> </avp>
>
> <avp name="Subscription-Id">
>
> <avp name="Subscription-Id-Type" value="0"></avp>
>
> <avp name="Subscription-Id-Data" value="31645958277"></avp>
>
> </avp>
>
> <avp name="Multiple-Services-Indicator" value="1"> </avp>
>
> <avp name="Multiple-Services-Credit-Control">
>
> <avp name="Requested-Service-Unit" value=""></avp>
>
> <avp name="Used-Service-Unit">
>
> <avp name="CC-Time" value="0"></avp>
>
> <avp name="CC-Total-Octets" value="0"></avp>
>
> <avp name="CC-Input-Octets" value="0"></avp>
>
> <avp name="CC-Output-Octets" value="0"></avp>
>
> </avp>
>
> <avp name="Rating-Group" value="3000"></avp>
>
> <avp name="3GPP-Reporting-Reason" value="4"></avp>
>
> </avp>
>
> <avp name="Service-Information">
>
> <avp name="PS-Information">
>
> <avp name="3GPP-Charging-Id" value="XXX"></avp>
>
> <avp name="3GPP-PDP-Type" value="0"></avp>
>
> <avp name="PDP-Address" value="XX"></avp>
>
> <avp name="3GPP-GPRS-Negotiated-QoS-Profile" value="05-
> 23921f9196fefe742bfefe006200"></avp>
>
> <avp name="SGSN-Address" value="XX"></avp>
>
> <avp name="GGSN-Address" value="XX"></avp>
>
> <avp name="CG-Address" value="XX"></avp>
>
> <avp name="3GPP-IMSI-MCC-MNC" value="20469"></avp>
>
> <avp name="3GPP-GGSN-MCC-MNC" value="20469"></avp>
>
> <avp name="3GPP-NSAPI" value="5"></avp>
>
> <avp name="Called-Station-Id" value="XXXXXXXXXXX"></avp>
>
> <avp name="3GPP-Selection-Mode" value="0"></avp>
>
> <avp name="3GPP-Charging-Characteristics"
> value="0800"></avp>
>
> <avp name="3GPP-SGSN-MCC-MNC" value="20469"></avp>
>
> <!-- <avp name="3GPP-MS-TimeZone" value="0"></avp> -->
>
> <avp name="3GPP-User-Location-Info"
> value="0x0102f496232e9246"></avp>
>
> <avp name="3GPP-RAT-Type" value="01"></avp>
>
> <avp name="PDP-Context-Type" value="0"></avp>
>
> <avp name="Charging-Rule-Base-Name"
> value="XXXXXXXXXXX"></avp>
>
> </avp>
>
> </avp>
>
> <!-- Added -->
>
> </command>
>
> <action>
>
> <start-timer></start-timer>
>
> </action>
>
> </send>
>
>
>
> <receive channel="channel-1">
>
> <action>
>
> <stop-timer></stop-timer>
>
> </action>
>
> <command name="CCA">
>
> </command>
>
> </receive>
>
>
>
> </traffic>
>
>
>
> </scenario>
>
>
>
>
>
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at http://www.amdocs.com/email_disclaimer.asp
> This email is confidential and may be subject to privilege. If you are not
> the intended recipient, please do not copy or disclose its content but
> contact the sender immediately upon receipt.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Gull-users mailing list
> Gul...@li...
> https://lists.sourceforge.net/lists/listinfo/gull-users
>
>
--
---
Andrzej Kolodkiewicz
|
Thanks for helping keep SourceForge clean.
X