You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a sipp scenario which contains a setdest action (see https://sipp.readthedocs.io/en/latest/scenarios/actions.html#setdest) with transport mode "UDP with one socket per call" using ./sipp -t un ... it crashes with the error "Cannot create socket" when starting the first call. When removing the setdest action, this error does not occur and calls can be performed without any errors.
This error even happens when the contents of setdest are the same as the original destination passed to the cli:
When setting the transport mode to "UDP with one socket" or "TCP with one socket per call" whilst keeping setdest in the scenario, the "Cannot create socket" error does not occur either.
So it appears to only be an issue with setdest and the un transport mode.
The text was updated successfully, but these errors were encountered:
When running a sipp scenario which contains a
setdest
action (see https://sipp.readthedocs.io/en/latest/scenarios/actions.html#setdest) with transport mode "UDP with one socket per call" using./sipp -t un ...
it crashes with the error "Cannot create socket" when starting the first call. When removing thesetdest
action, this error does not occur and calls can be performed without any errors.This error even happens when the contents of
setdest
are the same as the original destination passed to the cli:When setting the transport mode to "UDP with one socket" or "TCP with one socket per call" whilst keeping
setdest
in the scenario, the "Cannot create socket" error does not occur either.So it appears to only be an issue with
setdest
and theun
transport mode.The text was updated successfully, but these errors were encountered: