The template tr_provideEimPackageResult_ePRAndNotif got extended and
has now default parameters that break TC_proc_euicc_pkg_dwnld_exec_rollback,
so we must set euiccPackageResult to "?" to restore the original conditions
of the testcase.
Related: SYS#6563
Change-Id: I1e8c83a317619673cd091da585e44af1a6d8c866
The template tr_provideEimPackageResult_ePRAndNotif has a fixed eUICC package,
let's turn the contained eUICC package into a template parameter so that
we can define the eUICC package templates separately. To be complete, let's
also add a ts_provideEimPackageResult_ePRAndNotif
Related: SYS#6824
Change-Id: If04be6407eb41274b378571147ab469d449eac4a
The template ts_getEimPackageResponse_euiccPkgReq has a fixed eUICC package,
let's turn the contained eUICC package into a template parameter so that
we can define the eUICC package templates separately. To be complete, let's
also add a tr_getEimPackageResponse_euiccPkgReq
Related: SYS#6824
Change-Id: Ibcea9063f25cc8ba90b53c34218c766fa5cab895
We do not have a template for the EsipaMessageFromIpaToEim message
that contains the HandleNotification field with the
profileInstallationResult, so lets add one.
Related: SYS#6824
Change-Id: Ic5d1b2ea1d3d7de20fbcb029b36e9f9daa27cce0
We do not have a template for the GetBoundProfilePackageRequestEsipa,
so lets add one.
Change-Id: I90b699de01c0476262f0e25c196a147e0ccd44aa
Related: SYS#6824
The field profileInstallationResultData in tr/ts_profileInstallationResult
is also present in SGP.32 messages, so lets split this field into a separate
template so that we can use it in the SGP32Definitions_Templates as
well.
Related: SYS#6824
Change-Id: Ie38443f86ed2d8d758f894ff4276ac4109cd2e6d
The field downloadResponseOk in tr/ts_prepareDownloadResponse is also
present in SGP.32 messages, so lets split this field into a separate
template so that we can use it in the SGP32Definitions_Templates as
well.
Change-Id: Id29e2aafee4ff37c25037c75f97f280784b57619
Related: SYS#6824
The templates ts_getBoundProfilePackageRequest and
ts_getBoundProfilePackageResponse have no default values for their
parameters.
Change-Id: I6b26f70962ad1258c7a43b22a6778883288d0876
Related: SYS#6824
When testing the profile download we call it "direct" profile
download, but we actually mean "indirect" profile download.
Related: SYS#6563
Change-Id: I971ed877f76abaa3e05bc05d3e20a0fd1f19982d
This patch is a step towards testing IMS.
So far only the code infrstrastructure to handle the 1st REGISTER
(outside IPSEC) is provided. It can already be seen how Asterisk
sends the second REGISTER over IPSEC, but there's no means to test it
yet in TTCN-3. This will be done in a follow-up patch, which may take
some work.
Change-Id: Idb3b19ccd82cad25948106b2c72aa424d7f79cd8
According to RFC3261 7.4.2, 7.5, 20.14 Content-Length SHOULD be set over
any transport, and MUST be set over TCP.
Hence, make sure we set it in all cases.
This allows Asterisk being able to decode SIP messages sent to it over a
TCP connection, since it uses the Content-Length field to look up for
message boundaries over the TCP stream.
Change-Id: I26e444fe466b4742d74ef5a6e371ce8488a5afcf
Similar to ts_SIP_Response_Ringing. We also have the counterpart tr_*
for both Trying and Ringing. This is needed in a follow-up patch.
Change-Id: I05d8be9ce8860c610c509670392e14f1096fdddb
We're getting a new TLLI assigned during the attach procedure (see
Allocated P-TMSI in the GMM Attach Accept message), which needs to
be registered in order to receive BSSGP PDUs from BSSGP_Emulation.
Change-Id: Idafcbd7e44a523a26dc34dc72e38ff879782148e
Ensure the expected default UEA configuration, which is always
reset properly even if one of the testcases aborts due to a DTE.
Change-Id: Ic2c5a11e86e4349796fa7508076ac27ef22815cd
Since recently, osmo-sgsn is requesting encryption (UEA1 + UEA2)
in RANAP Security Mode Command by default [1]. The testcase
TC_iu_attach is assuming no encryption (UEA0) and thus failing.
Fix this by explicitly setting UEA0 via the VTY, similarly to
what testcase TC_iu_attach_encr does.
Change-Id: Ibaf83db1ab0f82f7e934e89ae3f6c19d014be197
Related: [1] osmo-sgsn.git I4eb9451b4267fc1436ed90a55ff200cf36f16bf6
It's a good practice to tag Actions with an ActionID to do proper
matching of the response once it comes back. It also helps reading a
dump of the conversation if there were events in between.
Change-Id: Iec320762ff0cca86319f7374b53c642f08a6e6df
The AMI documentation webpage mentions "ActionId", but Asterisk is
always returning "ActionID" in all response messages.
Any of the 2 is parsed fine by Asterisk since the keys are case
insensitive, but anyway let's use same case as what Asterisk is actually
transmitting to make reading of output easier.
Change-Id: I8097e461fd0cadfa780d52ab1666e41b9d2b8a0e
Change Telnet_PT to a regular TCP socket for the AMI interface.
I started using Telnet_PT port since initial use of the interface
was done through telnet, but it's not really a telnet interface and
stuff starts becoming difficult to maintain properly when events
(generated by Asterisk at any time) arrive.
The current TEXT decoder/encoder from Titan seems to be struggling in 2
scenarios, so for now we are adding some workarounds in
dec_AMI_Msg_ext() before calling it in order to be able to go forward
and avoid errors:
1- Fields of format "MyFieldName: \r\n" (empty value). I tried changing
the "value" field in record AMI_Field to "optional", but then apparently
the TEXT decoder fails to decode values consisting of several words.
Ideally, I'd expect the TEXT decoder to put an empty "" string in the
"value" field in that case if "optional" is not flagged in the record.
2- Fields of format "MyFieldName: foobar: hey there \r\n" containing a
": " token in the value. I'd expect TEXT decoder to put all subsequent
strings in the last field "value" if no more fields are described in the
record.
Change-Id: Icaf2860c1dd4befa4498f0d176cfadf26cfa8d1d
This allows to keep string handling totally internal to the AMI_Adapter
component, which also means now the CLIENT port acts asynchronously on
full AMI messages.
This allows for instance using activated altsteps to ignore events or
answer to them.
Change-Id: Ibf230d2302fecf443f34e1c4d4acfd4802f4cc79
These are currently used by code in AMI_Functions doing some workaround
for TEXT decoder limitations.
They can be merged independently now since anyway they are totally
generic and may be useful for future users.
Change-Id: I3d6da125a10807b7a2f3ecad8145a046a322c7d6
Fix that 6 tests started failing on ttcn3-hnbgw-test-latest with e.g.:
Timeout waiting for metrics
HNBGW_Tests.ttcn:2885 HNBGW_Tests control part
HNBGW_Tests.ttcn:1536 TC_rab_assign_fail testcase
Fixes: 904b5f1a ("hnbgw: Implement validation of [some] counters")
Change-Id: I0cd47728308757fe6eaaaed1581fbbec03a09cf7
The function f_http_tx_request has two parameters to spcifiy the body
part of the HTTP request (body and binary_body). The function only
sends a request when either body or binary_body is populated, but not
when none of the two is populated. This means requests without body
part (e.g. a GET request) can not be sent.
There is also no proper interlocking between body and binary_body. We
should make sure that this situation does not occur.
Related: SYS#6824
Change-Id: I258ee6209c35d0601f5a4d82423d2f5c6fbb03cc
Add the initial infrastructure to manage 2 SIPmsg_PT ports, one for the
local SIP UAs and one for the IMS core.
Still missing:
* Trigger Asterisk (through AMI) to do the initial connect + register to it
* Configure ipsec after Unauthorized response from IMS core
Change-Id: Ibbbadd54b7facf4ef7384499704e742f482a1252
Remove the dash character, since it makes it impossible to reference the
component name under TESTPORT_PARAMETERS in .default/.cfg files.
While at it, actually, allow the test to provide a full id instead of
always appending the suffix to it. This provides more freedom on the
testsuite to provide a fitting component name.
Change-Id: Iecefe7d98a5842872f1efc55e013f672186ef1a8
This reverts commit e9c6c7b97e which
breaks all of the test cases reliably. I'm surprised how it got
submitted in the first place, as it can never have worked. It uses
127.0.0.1:2905 on both the STP and the HNBGW side.
Change-Id: Ia7d9a743e0359ce7220c42597ded670967d562a9
The template ts_authenticateClientResponseEs9 has no default values,
let's add some default values to make it easier to use
Related: SYS#6824
Change-Id: I07d942a58a3c1c29c37fcaa50d3a274ce8b026bc
Fields of type CtxParams1 are used in other messages too, so it might be
helpful to add a separate template for them.
Related: SYS#6824
Change-Id: Iba6c3780f9f3aec5742d53b3bd7b0c0392b25761
The field serverSigned1 is used in many messages, so it might be helpful
to add a separate template for it.
Change-Id: Ic50676ac2863173b72765afc44794a56d03413a5
Related: SYS#6824
At the moment the HTTP_Adaptor automatically creates a new connection,
performs the HTTP request and closes the connection again. This means
the connection lives only for a single request. Let's add some
flexibility so that we can perform multiple consecutive requests
through the same connection.
Change-Id: Ic6994c504143820dde498c1a2bad2ad6a523dd70
Related: SYS#6824
The HTTP_Adapter currently only supports text only HTTP messages. However,
the HTTPmsg testport API also has a way to deal with binary HTTP messages.
Related: SYS#6824
Change-Id: I18340f19ed462bf80af683dc9f2831b602f4bdf7
Philipp Maier
Pau Espin
Vadim Yanitskiy
Oliver Smith
Harald Welte