Hi Iñaki,
Iñaki Baz Castillo wrote:
Well, I would just like to add that UPDATE for SS can be used just if
that's interesting. I didn't know that - in fact I thought UPDATE
without SDP would not be possible.
the following occurs:
- For the caller: The initial INVITE request must contain "Allow: UPDATE".
- For the called: A provisional or 2XX response must contain "Allow:
UPDATE". But a non reliable response (1XX without 100rel) could omit
such "Allow" value and still be present in the final 2XX.
so, that should be pretty easy to implement.
If you want to dig in the code in SEMS (sst_b2b branch atm, still to
be merged), from implementation standpoint in SEMS I would suggest to
have a session level (in AmB2BSession) flag whether to use UPDATE for
refresh. The B2B app can then set this flag (possibly with a helper
function in AmB2BSession). This flag is checked in two locations:
- AmB2BSession::sendReinvite, where it should call
dlg.sendRequest("UPDATE") instead of dlg.reinvite()
- in onSipReply, similar to is_inv_trans, it should check for UPDATE
and handle replies properly (e.g. tear down if 408/480 - like
onFailedReinvite).
Regards
Stefan
--
Stefan Sayer
VoIP Services Consulting and Development
Warschauer Str. 24
10243 Berlin
tel:+491621366449
sip:[email protected]
email/xmpp:[email protected]
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
