Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Olle E. Johansson
13 jan 2011 kl. 23.36 skrev Paul Kyzivat: > > > On 1/13/2011 10:38 AM, Iñaki Baz Castillo wrote: >> 2011/1/13 Olle E. Johansson: >>> - Does your UA add an SDP to a 488 error message? >> >> Most probably no UA in the world adds SDP to a 488 response. > > I don't know, but I suspect you are rig

Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Paul Kyzivat
On 1/13/2011 10:38 AM, Iñaki Baz Castillo wrote: > 2011/1/13 Olle E. Johansson: >> - Does your UA add an SDP to a 488 error message? > > Most probably no UA in the world adds SDP to a 488 response. I don't know, but I suspect you are right, or nearly so. > And for sure, no UA in the galaxy woul

Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Iñaki Baz Castillo
2011/1/13 Olle E. Johansson : > - Does your UA add an SDP to a 488 error message? Most probably no UA in the world adds SDP to a 488 response. And for sure, no UA in the galaxy would inspect/interpret a SDP in a 488 response, at least not within next 20 years. -- Iñaki Baz Castillo __

Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Kevin P. Fleming
On 01/13/2011 08:57 AM, Olle E. Johansson wrote: > > 13 jan 2011 kl. 15.36 skrev Paul Kyzivat: > >> Also, the following from the description of 488: >> >>A message body containing a description of media capabilities MAY be >>present in the response, which is formatted according to the Accep

Re: [Sip-implementors] Query on Subscription dialog for reg event upon DeRegistration

2011-01-13 Thread Paul Kyzivat
Sunil, Its not clear to me if you have a question for sip-implementors, or a question for IMS-implementors. The reg event package provides a way to monitor the status of *all* the registrations for a particular AoR. The fact that a UA has unregistered itself (or been unregistered) does not mea

Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Olle E. Johansson
13 jan 2011 kl. 15.36 skrev Paul Kyzivat: > Also, the following from the description of 488: > > A message body containing a description of media capabilities MAY be > present in the response, which is formatted according to the Accept > header field in the INVITE (or application/sdp if no

Re: [Sip-implementors] draft sipping-v6-transition and SDP offer/answer

2011-01-13 Thread Paul Kyzivat
Also, the following from the description of 488: A message body containing a description of media capabilities MAY be present in the response, which is formatted according to the Accept header field in the INVITE (or application/sdp if not present), the same as a message body in a

[Sip-implementors] Query on Subscription dialog for reg event upon DeRegistration

2011-01-13 Thread Sunil
Hi All, According to the 3GPP 24.229 spec, Upon successful de-registration UA should not delete the dialog for Subscription to reg event package if it had subscribed. Exerts from 24.229: -

Re: [Sip-implementors] REGISTER contact screening

2011-01-13 Thread Iñaki Baz Castillo
2011/1/13 Olle E. Johansson : > I don't like the idea of sending 200 OK to failed requests though, it kind of > breaks my vulcan logic circuit. Yes, it's a bit exotic but the UAC is supposed to inspect the Contact URI's of the 200 for a REGISTER to realize of the registered locations: The 2xx

Re: [Sip-implementors] REGISTER contact screening

2011-01-13 Thread Olle E. Johansson
13 jan 2011 kl. 10.02 skrev Iñaki Baz Castillo: > 2011/1/13 Olle E. Johansson : >> YOu're talking about "reject the request" - how do we reject the request >> based on policy after a successful authentication? > > REGISTER -> > <- 401 > REGISTER -> (correct credentials) > <

Re: [Sip-implementors] REGISTER contact screening

2011-01-13 Thread Iñaki Baz Castillo
2011/1/13 Olle E. Johansson : > YOu're talking about "reject the request" - how do we reject the request > based on policy after a successful authentication? REGISTER -> <- 401 REGISTER -> (correct credentials) <- 403 What is wrong sending such 403 after successful authent