[SIPForum-techwg] (Interop) Basic Call Survey

[Peter Musgrave]

All, 

 

So there have been a few comments on what level of functionality should
be required in a basic SIPConnect call and the opinion that my initial
deliberately Draconian "straw-person" was too extreme.

 

I'm interested in where to "relax" the requirements and want to gather
input on some decision points. The questions I have for a basic call are
below. 

 

The goal is to develop a use case for a basic call which: 

*        is guaranteed to work between any SP and any Enterprise

*        provides enough functionality to be "useful" (i.e. SP -
Enterprise call can do normal things like fail to voicemail, be
transferred etc.)

 

I'd appreciate it if people could just add yes/no/don't care to each
item and send a response to me. 

 

(1)   Require Digest Authentication for REGISTER from Enterprise to SP?
(i.e. TLS is not enough)

(2)   Require Digest Authentication for INVITE from Enterprise to SP?

(3)   Allow reINVITE to do onhold?

(4)   Allow a reINVITE which changes the sdp destination?

(5)   Respond to a 302 message with a new INVITE (RFC3261 says SHOULD)?

(6)   Ignore headers which are not understood in SIP messages or sdp?

(7)   Allow early media (with the final media in 200 OK at a different
destination)?

(8)   Allow Identity headers?

(9)   Advertise but do not require session timers?

 

Once I get responses, I'll provide a summary. 

 

Feel free to add requirements you think I have missed.

 

Thanks, 

 

Peter

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20070430/4fbe7ec7/attachment.html