Hi,
ftag is something specific to OpenSER/SER, there is no standard doc/spec
about it. The idea behind is to add the from tag to the Record-Route
header when the initial request passes. by comparing this value (the tag
of original from hdr) with the from tag of the sequential requests you
can figure out the direction of this request.
regards,
bogdan
tele wrote:
Hi,
Can you point me to some documentation about the ftag parameter in the
RR/Route header?
I've search in the RFCs but not found any informations about.
thank you
On Mon, 2006-07-10 at 14:44 +0300, Bogdan-Andrei Iancu wrote:
>Hi,
>
>in this case it means that the UA you were using was not correctly using
>via the RR/Route headers and the RR header inserted by OpenSER was not
>correctly mirrored into a Route hdr - this header is used to determine
>the direction of the sequential requests.
>
>regards,
>bogdan
>
>tele wrote:
>
>
>
>>Hi bogdan,
>>
>>now it works i can see the debug messages and OpenSER correctly swap
>>From/To for the accounting.
>>
>>But i didn't change the config, the only thing is that now signalling
>>message come from another proxy and not directly from UA.
>>
>>thank you for the support.
>>
>>On Mon, 2006-07-03 at 09:44 +0200, tele wrote:
>>
>>
>>
>>
>>>Hi Bogdan,
>>>
>>>I've updated to last CVS-head version. but in the log i can't see
debug
>>>messages.
>>>maybe there is an error in my accounting configuration. pls have a look:
>>>
>>>modparam("acc", "log_level", 2)
>>>modparam("acc", "log_fmt", "cdfimorstup")
>>>modparam("acc", "report_ack", 0)
>>>modparam("acc", "detect_direction", 1)
>>>modparam("acc", "radius_flag", 3)
>>>modparam("acc", "radius_missed_flag", 5)
>>>modparam("acc", "radius_config",
>>>"/usr/local/etc/radiusclient-ng/radiusclient_auth.conf")
>>>modparam("acc", "radius_extra",
"h323-setup-time=$avp(setup_time);
>>>h323-connect-time=$avp(connect_time);
>>>h323-disconnect-time=$avp(disconnect_time);
>>>h323-remote-address=$avp(remote_address)")
>>>
>>>and before loose_route() i have:
>>>
>>>if (is_method("BYE"))
>>>{
>>> setflag(3);
>>> setflag(5);
>>>};
>>>
>>>is it correct?
>>>
>>>Bogdan-Andrei Iancu wrote:
>>>
>>>
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>as I saw in the log, the FROM restoring in BYE works properly, so
>>>>RR/Route processing is fine. Are you sure you enabled the accounting
>>>>for BYE?
>>>>
>>>>just in case, I added some more debug messages about this on cvs -
>>>>please update and see the output. You should get:
>>>> DBUG:acc:acc_onreq: UPSTREAM req detected -> flaging it
>>>>and
>>>> DBUG:acc:fmt2strar: UPSTREAM flag set -> swap F/T
>>>>
>>>>