Begin forwarded message:
From: Paweł Pierścionek <[email protected]>
Date: 29 maja 2009 11:05:17 GMT+02:00
To: sipx-dev <[email protected]>
Subject: CSE hacks
Hi,
I am trying to optimize CSE logging as well as add new event type
before I introduce plug-in mechanism to CSEs logging.
For a proper formed dialog between two internal extensions I get 6
CSEs.
3x call_request,
2x call_setup,
1x call_end
I can easily shave off one call_request by testing for a presence
SIP_SIPX_SPIRAL_HEADER but should I try to optimize further ?
Can I test if SipMessage is destined to spiral down so I can
eliminate two more duplicate CSEs ?
Or maybe I can detect that the message is leaving the proxy and only
process such messages.
Second thing:
I would like to add "update" event that would be equivalent of "keep-
alive" message.
That would allow to calculate a minimum length of a dialog in case
of lost BYEs.
What SIP scenarios should trigger such an event ?
Should I trigger this on any 2XX response to UPDATE request ?
It is possible that this event will trigger when the dialog is not
yet formed but this is ok for the EventWriters that I envision.
Is it possible to detect that a 2XX response to an INVITE message is
part of dialog-forming transaction ?
Currently all such responses trigger call_setup event log - even if
they are part of session refresh.
Pawel,
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
