Re: [Sip-implementors] Query related to SDP in 200 OK after UPDATE

2009-01-19 Thread Rockson Li (zhengyli)
Sdp should not be present in the 200(INVITE), RFC3261 sec 13.2.1 Creating the Initial INVITE o Once the UAS has sent or received an answer to the initial offer, it MUST NOT generate subsequent offers in any responses to the initial INVITE. This means that a UAS based on

[Sip-implementors] Query related to SDP in 200 OK after UPDATE

2009-01-19 Thread Subbu Rajendran
Hi All, Following is example call flow from RFC 3311 (SIP UPDATE Method). Is SDP a must in the 200 OK for INVITE in this case? If it is required, then 200 OK should contain 'answer 3'. Is this a legal behavior as answer in 200 OK for INVITE ('answer 3') is not based on the offer in the INVITE ('off

Re: [Sip-implementors] ad hoc conferences with SIP

2009-01-19 Thread Simon Shaw
Hi Ranjit, In this scenario Alice, Bob and Charlie are registered to a B2BUA proxy (I accidentally omitted the fact that I will be developing the B2BUA proxy is from my original description) that can initiate the call between Charlie and the conference server using 3PCC. I am specifically looking

Re: [Sip-implementors] ad hoc conferences with SIP

2009-01-19 Thread Avasarala Ranjit-A20990
Hi Simon In adhoc conferences scenarios you described, it is possible that when Alice invites Charlie to the conference between Alice and Bob, then Alice does the media mixing and sends to Charlie. So here Alice could act as a focus. So here conference server may or may not be involved. Yes true B

Re: [Sip-implementors] FW: Regarding Refer-To header

2009-01-19 Thread Paul Kyzivat
It could have been stated better in 3261 so that it would apply in all cases, rather than only in the named cases. The basic rule should be that when there is an ambiguity in the grammar around the parsing of an addr-spec (as to whether the ',' ';' or '?' is part of the addr-spec or part of som

Re: [Sip-implementors] FW: Regarding Refer-To header

2009-01-19 Thread Brett Tate
It is a known issue. http://bugs.sipit.net/show_bug.cgi?id=765 > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Rockson Li > (zhengyli) > Sent: Monday, January 19, 2009 9:38 AM > To: harbh.

Re: [Sip-implementors] FW: Regarding Refer-To header

2009-01-19 Thread Rockson Li (zhengyli)
Harbhanu, I agree with you, addr-spec must be used as well for Refer-To. However, looks like RFC3515 does not state this explicitly. Regards, -Rockson -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf

Re: [Sip-implementors] ad hoc conferences with SIP

2009-01-19 Thread Iñaki Baz Castillo
2009/1/19 Simon Shaw : > All, > > I am looking for the SIP standard/draft that defines how an ad-hoc > conference should be initiated where the focus is not one of the > original users as follows: > > 1) Alice is talking to Bob in a standard P2P call (RTP flowing in > both directions between A

[Sip-implementors] ad hoc conferences with SIP

2009-01-19 Thread Simon Shaw
All, I am looking for the SIP standard/draft that defines how an ad-hoc conference should be initiated where the focus is not one of the original users as follows: 1) Alice is talking to Bob in a standard P2P call (RTP flowing in both directions between Alice and Bob) 2) Alice invites

[Sip-implementors] Query regarding Early-session(RFC-3959) with precondition

2009-01-19 Thread A A ANEES-RJD876
Hi , Please provide directions and sample message flows for implementing early-session(RFC-3959) with precondition(RFC-3311) enabled. If 183 contains Require: precondition is this applicable for Early-session also? If applicable please provide some message flows for the same. Regards Anees

Re: [Sip-implementors] FW: Regarding Refer-To header

2009-01-19 Thread Iñaki Baz Castillo
2009/1/19 harbhanu : > Hi, > > For all the headers defined in 3261, which are obtained from ( name-addr / > addr-spec ), we have a rules saying that the values > > must be wrapped with '<' and '>', incase addr-spec contains any of comma, > semi-colon or question mark. > > > So, does the value for