Subject: RE: [SIP] How many RTP streams?

From: "Fox, Mike" <[email-masked]>
Date: Mon, 17 Jul 2000 09:42:39 -0700

> From: Jonathan Rosenberg 
> "Fox, Mike" wrote:
> > 
> > Just how many 2833 RTP streams should a UAC support? In 
> terms of "best
> > practices" should each SIP Application Server (SAS) taking 
> part in a session
> > receive it's own 2833 stream from the UAC, or should each 
> application server
> > forward the stream to the next inline SAS? 
> 
> Since each app server will not know about any others, in all 
> likelihood,
> I don't see how any kind of cooperative process, like 
> forwarding, could
> work. In fact, an app server wouldn't even be able to 
> determine if a UAS
> is actually another app server or the final destination.
> 

Please forgive me, as I may be violating some small (or large) print in the
spec...
Could an app server ( lets call it A ) initially establish a ID2833 RTP
stream from the UAC? Could the next hop from A, say it is a UAS, ask for a
ID2833 RTP stream in an INVITE (or ACK), and wouldn't that INVITE cross A?
Could A, knowing that it had access the ID2833 RTP stream for this session
somehow forward the ID2833 RTP it is receiving to the UAS and condition the
INVITE and its response to make things work, instead of allowing the SDP to
go all the way down to the UAC and forking another ID2833 RTP from the UAC?

> 
> Forwarding would allow for some
> > feature interaction reduction by deleting recognized events and not
> > forwarding them to down stream devices, of course this adds delay.
> 
> This seems completely infeasible. How would one app server 
> know what the
> next one wants to do?
> 
> -Jonathan R.
> -- 
> Jonathan D. Rosenberg                       72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> [email-masked]                     FAX:   (973) 952-5050
> http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
> http://www.dynamicsoft.com
> 

_______________________________________________
SIP mailing list
[email-masked]
http://lists.bell-labs.com/mailman/listinfo/sip