On Tue, 2008-09-02 at 10:56 -0400, Raymond Dans wrote: > > In looking at Call Detail Recording, I ran into an issue where > records were not being closed off in abandoned call scenarios. Upon > closer investigation, I noticed that a call failure state event wasn't > being generated in the Proxy because of an apparent change in the 408 > Request Timeout SIP message. The criteria for generating a call > failure state event in this scenario was to look at the "To tag" of > the 408 Request Timemout message. If it was nil then the event was > generated and otherwise it was not. > > In SipXecs 3.10.x, the abandoned scenario would have a nil "To > tag" so the CDR record was correctly closed off. In 3.11.5, the "To > tag" in this scenario is not nil and as a result the record is never > closed off and appears in the active calls list for some time (around > 8 hours). > > Deos anyone know if the change in the 408 message was intentional > or is this a bug that should be reported. Looking at the RFC doesn't > really give a clear answer (to me anyways) as to whether or not the > ToTag should be present.
Since a 408 doesn't set up a dialog, I don't think it should have a To tag... what component added it? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
