[Serdev] logging of error responses

[Chris Thompson]

Hi,

Many thanks, I will look at this more closely, it is not quite what I was
hoping to be able to do, but better than the current set up.

I appreciate your help.

chris

> Try "log_facility=LOG_LOCAL6" in your ser.cfg and "local6.*
> /var/log/ser.log" in your syslog.conf file and restart syslogd.
>
> All output will be in the indicated file instead of mixing with other
> syslog
> messages. However, you still have to filter other ser debug messages but
> that would be much less than before.
>
>> -----Original Message-----
>> From: Chris Thompson
>> Sent: Friday, 10 June 2005 6:18 PM
>> To: Zeus Ng
>> Subject: RE: [Serdev] logging of error responses
>>
>>
>> Hi Ng,
>>
>> Thanks for your response but unfortunately xlog does not
>> quite do what I need.
>>
>> I am currently using the exec_msg("printenv SRCIP... method
>> to output the requests as they come through and output to
>> file. The idea is to have another application take this
>> output file and create message flows, potentially for billing
>> putposes.
>>
>> I was hoping to be able to do the same thing for all messages
>> created by the SER router so I can see an INVITE, coming in
>> and a failure message going back for reporting.
>>
>> This information is in the syslog but that means writing the
>> third party application to parse the syslog, looking for the
>> relevant data rather than a single file created by SRCIP type
>> output so all data is relevant.
>>
>> I am hoping that this allows me to show that load balanced
>> machines can run the SIP layer control and a third server can
>> periodically copy over the output files and mediate them in
>> some way. The beauty of the SRCIP method is that I should be
>> able to follow the full conversation including the agreed upon codex.
>>
>> This is all very proof of concept and I am up against large
>> cost alternatives so am desperate to make open source work.
>>
>> Many thanks
>>
>> Chris
>>
>>
>>
>> > The xlog module can pretty much print the whole message,
>> both request
>> > and response to your syslog facility. Use it as a template to write
>> > your own module.
>> >
>> >> -----Original Message-----
>> >> From: Chris Thompson
>> >> Sent: Friday, 10 June 2005 8:17 AM
>> >> To: serdev at lists.iptel.org
>> >> Subject: [Serdev] logging of error responses
>> >>
>> >>
>> >> Hi all,
>> >>
>> >> I hope someone can help me, I am playing around with SER
>> and have set
>> >> it up to  output the messages to an external file for easy parsing
>> >> and data extraction.
>> >>
>> >> Unfortunately I have not mamanged to get it to work for the error
>> >> responses, such as "478 Unresolveable destination" that
>> get sent back
>> >> to the client.
>> >>
>> >> Ideally I would either pass the error to a perl program or
>> direct to
>> >> the output file so all messages through or created by SER
>> are in one
>> >> place.
>> >>
>> >> Just to log does not work for me as it is too cluttered and the
>> >> message is cut off so I do not get the full message.
>> >>
>> >> Has anyone else looked at doing this and have any pointers for me.
>> >>
>> >> Any help would be really appreciated, I am pulling my hair
>> out here.
>> >> I have a demo in the morning and am up against it a bit.
>> >>
>> >> Thanks in advance
>> >>
>> >> Chris
>> >>
>> >>
>> >> _______________________________________________
>> >> Serdev mailing list
>> >> serdev at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
>> >>
>> >>
>> >
>> >
>>
>
>