30 May
2014
30 May
'14
4:43 p.m.
if response has reason header, i would like to gets its body to
acc_sip_reason_column field rather than the reason on the response
status line which does not bring any added value.
any comments on how to achieve that?
-- juha
Session Initiation Protocol
Status-Line: SIP/2.0 404 Not Found
...
Reason: Q.850;cause=88;text="INCOMPATIBLE_DESTINATION"
30 May
30 May
5:58 p.m.
Hello,
if you want it as separate column, should work, one option being with
onreply_route[x] and storing the header value in an avp.
If you want it over the existing column, then you have to patch the
module, eventually adding a modparam to control this behaviour. The
reply should be accessible via the transaction structure that is passed
to acc module via a callback function.
Cheers,
Daniel
On 30/05/14 15:43, Juha Heinanen wrote:
if response has reason header, i would like to gets
its body to
acc_sip_reason_column field rather than the reason on the response
status line which does not bring any added value.
any comments on how to achieve that?
-- juha
Session Initiation Protocol
Status-Line: SIP/2.0 404 Not Found
...
Reason: Q.850;cause=88;text="INCOMPATIBLE_DESTINATION"
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
6:07 p.m.
Daniel-Constantin Mierla writes:
if you want it as separate column, should work, one
option being with
onreply_route[x] and storing the header value in an avp.
yes, i thought about that, but since acc_sip_reason_column is mandatory
column, it would be better to re-use it also for reason header.
If you want it over the existing column, then you have
to patch the
module, eventually adding a modparam to control this behaviour. The
reply should be accessible via the transaction structure that is passed
to acc module via a callback function.
i'll see if i'm able to do that.
-- juha
6:14 p.m.
On 30/05/14 17:07, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Pointing it out for safety -- the log backend is writing to syslog in
format: name1=value1;name2=value2;...
The reason header contains such body, therefore check it see if it
doesn't break it - I expect to be enclosed in double quotes and escaped.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
if you want it as separate column, should work,
one option being with
onreply_route[x] and storing the header value in an avp.
yes, i thought about
that, but since acc_sip_reason_column is mandatory
column, it would be better to re-use it also for reason header.
If you want it over the existing column, then you
have to patch the
module, eventually adding a modparam to control this behaviour. The
reply should be accessible via the transaction structure that is passed
to acc module via a callback function.
i'll see if i'm able to do that.
6:34 p.m.
Daniel-Constantin Mierla writes:
Pointing it out for safety -- the log backend is
writing to syslog in
format: name1=value1;name2=value2;...
The reason header contains such body, therefore check it see if it
doesn't break it - I expect to be enclosed in double quotes and escaped.
isn't it the job of syslog backend to check that if value contains
semi-colon, then it will be escaped?
-- juha
3829
days inactive
3829
days old
4 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Juha Heinanen