Re: SIP Tracing Facility
Hadriel Kaplan <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <E6C2E8958BA59A4FB960963D475F7AC314C4C40EBA@mail> |
Yes that's what I was thinking too - for basic connectivity check type things, do SIP ping/traceroute. To troubleshoot actual proxy and UA behavior issues, retargeting issues, perform any type of root-cause, etc., you need logs and there's just no getting away from that. And only the authoritative administrator of each SIP device can (and *should*) be able to get such info. The real question is whether we can (or could) provide standardized ways of helping admin's get the info they need. And I think that is actually a really good topic for a BOF, or at least a discussion on RAI-DISPATCH. -hadriel > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Eric > Burger > Sent: Friday, March 06, 2009 1:00 PM > > Wouldn't SIP-CLF be a better way to go? _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip