On Oct 11, 2007, at 4:34 PM, Eric Burger wrote:
Right: "DTMF may not be the only information users want to send to
each
other during a session." This is why one MUST establish multiple
subscription dialogs. How else would one keep track of the different
elements / local routing decisions? If you are proposing application
routing a'la P-Asserted-Service...
One of the arguments for INFO is that it happens in a dialog, not a
session. That is, even if you have multiple event streams, they
happen on the same dialog.
The trick is demuxing the event streams, or in other words, figuring
out the context for each event. INFO currently gives us nothing but
the content- modifiers to figure this out. That's not enough, as has
widely been argued.
Francois proposed using an event wrapper within the dialog This does
give us a bigger handle for demuxing. For example, we could
reasonably demux jpegs which are snapshots from the built-in camera
from jpegs that are intended as keypad overlays or HTML imagemaps.
Might could have done that with content-disposition too, so it's an
imperfect example.
Is the event class enough of a differentiator? For example, we
probably wouldn't be able to differentiate two different DTMF sources
being routed to different applications within a single dialog. I
suspect that's an acceptable limitation, at lest for the sorts of
applications that seem to attract INFO use.
--
Dean
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
