Re: Re: Multiple sip applications with Jain-sip

Listening point maps to ip-address, port

Provider maps to ip-address,port,transport. It is the "event source".

Stack is a "management artifact", (i.e. in jsip 1.2 it is not
connected to ipaddress and port). Hence you can "start" or "stop" a
stack etc.

There is one SipListener per stack.

If you wanted two "applications", then I assume the intent is to
manage each independently of the other. Therefore one would assume to
stacks are needed.

Ranga.

note: I cc-ing users@jain-sip because the discussion originated there.

On 5/4/07, niepin <[email protected]> wrote:
> Hi,
> I wonder if this is multi-apps or multiple sessions. If one streaming
> application could be treated as one streaming session, then one SipStack and
> SipListener is enough. Each streaming instance is bound with a UDPHandler
> behind, which deals with the media socket.
>
> Multiple sip stack is applied only when the underlying signaling channel
> changes, e.g. transport (TCP+UDP), or port number. Is it so?
>
> BR
>
> niepin
>
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>


-- 
M. Ranganathan
"There are two ways to write error-free programs; only the third one
works." --  Alan Perlis