RE: [reSIProcate] DUM: Overlapping SIP transations in a dialog
My thoughts are below...
-----Original Message-----
From: Derek MacDonald [mailto:derek@xxxxxxxx]
Sent: Tuesday, August 03, 2004 9:25 PM
To: 'Robert Sparks'; rohan@xxxxxxxxx
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] DUM: Overlapping SIP transations in a dialog
I'm working on non-invite transactions in a Dialog, and how they interact
with each other; here are some questions.
1.) If I'm in an INVITE dialog, and I send an INFO message(for example),
which I haven't received a response from yet, can I send a BYE or another
non-INVITE transaction?
[Scott] Section 15.1.2 of RFC3261 (Terminating a Session with a BYE
Request) states: "The UAS must still respond to any pending requests
received for that dialog. It is RECOMMENDED that a 487 (Request Terminated)
response be generated to those pending requests". This seems to indicated
that you can send a BYE request before receiving responses from other
requests such as INFO. I can't find anything in the spec that says you
can't send another non-INIVTE transaction before receiving a previous
response. Although some methods like UPDATE specify that you can't do this
- other methods like INFO don't cover this in the RFC.
2.) Can INFO/MESSAGE/etc be sent in an early dialog?
[Scott] - Good question - INFO spec talks only of "mid-session" use. My
guess is that they should be allowed in an early dialog - since they are not
supposed to effect dialog state.
API questions:
1.) Which in dialog requests such as message should be part of the
InviteSession API and which should be part of a dialog level API?
[Scott] - I would think that the dialog level API is the appropriate place -
to reduce duplication.
2.) If overlapping non-INVITE transactions are allowed, should we allow them
in DUM?
[Scott] I don't really have a strong opinion here - if it's considered
"allowable" - it would be better if DUM supported it. But I don't
personally any current needs for it.
Derek
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel