Ok so I found the 'set/get ApplicationData' method which belongs to the
transaction type of the JAIN SIP library - however I cannot find, for my
life, where the ProtocolProviderServiceSipImpl object is set inside the
transaction with this method - I just cannot find it.
One main question lingers - why is it necessary to match the incomming sip
request / response to a ProtocolProvicerServiceSipImpl? I am not getting
the multiplicity factor here - in other words, how many can there be? If
this is a sip account then there would only be one protocol provider right?
Why the need to 'look' for one?
Again I apologize if this isnt the right forum for these questions but I
could not find an appropriate place to find this information - I figured the
developers would be the best place to go - and by the way this seems to me a
very very well written and documented code base.
On Wed, May 19, 2010 at 11:07 AM, Matthew Ishii <firstname.lastname@example.org>wrote:
Hello - I apologize if this is the wrong forum but I am trying to get up to
speed on how SC works
The only thing I am not quite sure I understand is how the SipStackSharing
dispatches transactions via processResponse/Request to the main
I know once it gets to the PPSSI it uses its processResponse/Request and
sends it to a 'MethodProcessor' for the various methods - REGISTER or dialog
sets invite - etc.
However from the main SipStackSharing it gets confusing - how do we get the
PPSSI object out of the transaction 'data'? It looks through the
SipApplicationData object seeking the PPSSI object - but how does that
relate to the transaction? is it because it exists within the
transaction/container because the client request originated from the
Anyone who could point me in the right direction would be appreciated. I
tried looking through the SC dev docs but it was too high level.