Re: [reSIProcate] [reSIProcate-commit] resiprocate 7042 nash: DialogUsageManager:
Hi Derek,
This was originally added in the TelTel-client branch, as is the DUM API offered couldn't tell the onAnswer triggered is a 200 OK or ACK, and I also made the distinction of first INVITE and re-INVITE, I haven't get into the details of understanding PRACK, all I know it's a PRE-ACK thing, can you explain why it will complicate PRACK development?
Nash
On 4/20/07, Derek MacDonald <derek@xxxxxxxxxxxxxxx
> wrote:
Hi Nash,
What is the motivation for InviteSessionHandler::AnswerReason? This adds complexity and doesn't really fit the DUM api, and will complicate PRACK development, or separating out the offer/answer state machine. I think we should remove this unless there is a compelling use case.
-Derek
Project |
resiprocate |
New Revision |
7042 |
Committer |
nash (Nash Tsai) |
Date |
2007-04-09 02:02:41 -0500 (Mon, 09 Apr 2007) |
Log
DialogUsageManager:
add ExternalMessageHandler interface
add hasEvent method
changes to process methods to allow mutex lock while in-processing
ClientRegistration/ClientSubscription/ClientPagerMessage/ClientPublication/InviteSession/ServerInviteSession/ServerPagerMessage:
Provide asynchronous method access by using command
Added:
Modified:
_______________________________________________
resiprocate-commit mailing list
resiprocate-commit@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-commit
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel