Bug #6254
open
Reconnects of the ttcn3 aren't handled
Added by lynxis 6 months ago.
Updated 6 months ago.
Description
When the mme drops the connection and tries to reconnect it doesn't work.
Same for ttcn3 tests
- Status changed from New to In Progress
- Assignee set to lynxis
- Subject changed from Reconnects of the open5gs-mmed aren't handled to Reconnects of the ttcn3 aren't handled
The reconnect from the open5gs-mmed is working. But ttcn3 has still problems.
I've tried to set origin_state_id to (1,2,3,...) , but it still doesn't work.
Hi Lynxis,
On Fri, Nov 10, 2023 at 06:58:46PM +0000, lynxis wrote:
The reconnect from the open5gs-mmed is working. But ttcn3 has still problems.
I'm not familiar with the detailed code, but in case you have any specific questions on TTCN3, feel free to ask.
- % Done changed from 0 to 60
The problem lies in the connect/watchdog timer as specified by the diameter.
Either we add an explicit disconnect in the ttcn3 code or we just reduce the timers to <=1s and sleep in the test code.
Or we use a different connection/identity (?) in every test.
Also available in: Atom
PDF
