i noticed that if i try to add in openser.cfg file a
direction=active
sdp line using fix_nated_sdp("1") just before i call t_write_unix to send the request to sems, sems does not get that added line.
is it so that currently there is no way to add sdp lines in the same openser.cfg that calls t_write_sems and that adding sdp lines needs to be done in earlier openser instance?
-- juha
Hi Juha,
using
fix_nated_sdp("1")
will set the FL_FORCE_ACTIVE flag (idx 1) into the message private flags.
t_write_xxx() will print these flags as: P-MsgFlags: XXXX in reverted hexa format.
SEMS was looking for the flag there.
could you check if the flag is set in the print?
regards, bogdn
Juha Heinanen wrote:
i noticed that if i try to add in openser.cfg file a
direction=active
sdp line using fix_nated_sdp("1") just before i call t_write_unix to send the request to sems, sems does not get that added line.
is it so that currently there is no way to add sdp lines in the same openser.cfg that calls t_write_sems and that adding sdp lines needs to be done in earlier openser instance?
-- juha
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Bogdan-Andrei Iancu writes:
using
fix_nated_sdp("1")
will set the FL_FORCE_ACTIVE flag (idx 1) into the message private flags.
t_write_xxx() will print these flags as: P-MsgFlags: XXXX in reverted hexa format.
SEMS was looking for the flag there.
could you check if the flag is set in the print?
yes, after fix_nated_sdp("1") call
P-MsgFlags: 2
header is added to the request.
i checked from sems source and it does check this flag as well as direction=active sdp line.
so everything is ok,
-- juha