The only thought I have is to possibly use Call-ID reuse as an indication that this next call is actually not a new call but related to the previous (and hence should not be logged as a separate call). For example, when a 407 or 401 challenge is made, the retried INVITE reuses the same Call-ID - a logging algorithm would not want to record this as a double call (first a failed one, then a successful one). Recursing using redirects and Error-Info URIs may also reuse the Call-ID (this is what the Call Flows document shows) so this might work for this as well.
If MOH=Music On Hold, then I presume you are talking about call transfer/pickup scenarios? I'm not sure how this would work without knowing your MOH call flow.
Thanks, Alan Johnston MCI
At 05:40 PM 8/14/2003 +0200, Christian Stredicke wrote:
Dear All,
I am wondering how a user agent can indicate that a call should not occur in the call lists. This is helpful to keep the list of last calls clean from error-info and MOH calls etc.
I see the following ways:
- use caller preferences (draft-ietf-sip-callerprefs-09.txt), something like "Request-Disposition: proxy, no-logging" where no-logging would be something new - Invent a new header for this purpose - Include a parameter in the To header - ?!
Any ideas? Thanks,
Christian -- Christian Stredicke sip:[EMAIL PROTECTED]
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
