Hi,
if a RR hdr is present in INVITE/200 OK, it must be present in all
sequential request of that dialog, including the BYE. If your SS doesn't
do so, it means it is nor RFC SIP compliant and you should report the
bug to the vendor.
I don't thing is any way around as it generates the BYE.
regards,
bogdan
tele wrote:
Hi bogdan,
Unfortunaly the BYE come from my SoftSwitch is without route header.
I'm try to do something like that:
SS ------> OpenSER(acct) ----> OpenSER
BYE BYE BYE
OpenSER(acct) <----
maybe if the BYE come from another proxy it can recognize the ftag
paramater and do the correct accounting.
Or do have you others idea?
On Tue, 2006-07-11 at 09:30 +0300, Bogdan-Andrei Iancu wrote:
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
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
