On Thursday 13 June 2013 04:09 PM, Binod wrote:Sorry please read the above method as getAcknowledgedResponse...
On Thursday 13 June 2013 12:56 AM, Eric Cheung wrote:
Hi BinodHere are some other methods that could go to appropriate interfaces.
To clarify 1(A), is this proposal to define new interface classes to represent requests and responses of all SIP methods, and initially only SipInviteRequest will define several methods?
pushPath -> SipRegisterRequest
createAck, createPrack -> SipInviteResponse
getAcknowledgedRequest -> SipAckRequest, SipPrackRequest
Otherwise, yes, all other interfaces are pretty empty.
(I may be missing some SIP methods)
>> Keith's original proposal has now evolved to two different set of
>> 1. See Keith's e-mail with latest PDF. The approach in this
proposal is to
>> create a new interface called SipInviteRequest to hold pending
>> for invite. From yesterday's discussion, seems like there
>> paths on this proposal.
>> (A) Define interfaces for methods also. For example,
>> SipRegisterRequest, SipAckRequest,
>> SipInviteResponse etc. This would make the API
>> all the methods.
-------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Thrupoint, Inc. nXaR2cC3
Re: B2B/PendingMessage Discussion/ Meeting notes