[Sip-implementors] If SDP answer in 200 OK is not acceptable.....?

2007-12-19 Thread Arnab Biswas
HI All, If the intial INVITE contains an SDP offer and the next 200 OK for that INVITE carries the answer, but the answer (in the 200 OK) is not acceptable to the originating UA, then what should it do? Should it generate a resonable offer in the ACK (where would be the answer?) and send a fresh

Re: [Sip-implementors] If SDP answer in 200 OK is not acceptable.....?

2007-12-19 Thread Sanjay Sinha (sanjsinh)
UAC will ACK the 200 OK and then send BYE. But why would the answer be not acceptable? It is a subset of the offer from UAC. Sanjay -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arnab Biswas Sent: Wednesday, December 19, 2007 10:46 AM To:

[Sip-implementors] Is it acceptable to have methods= param in the Contact header for a REGISTER message

2007-12-19 Thread Amit P. Ahuja
One of the SIP hardphones that I use sends out a REGISTER message with the Contact header that looks like: Contact: sip:[EMAIL PROTECTED]:5060;methods=INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER I could not find whether the methods= param in the

[Sip-implementors] SDP reject in 200 OK

2007-12-19 Thread Harsha. R
Hi, If a UAC makes an SDP offer in RE-INVITE, can the offer be rejected in a 200 OK? So my basic question is, can SDP rejects be placed in 200 OK to a request containing the offer, or is it mandated that SDP rejects need to be placed in non-2XX responses only Regards Harsha

Re: [Sip-implementors] SDP reject in 200 OK

2007-12-19 Thread Srinivas
Hi All, Adding to your query, if a session between UAC and UAS is in progress and UAC wishes to add a resource type to the existing session. So UAC sends a re-INVITE to the UAS and UAS responds with a 200 OK. Now my query is, whether there will be a case in which, the answer sent in the 200

[Sip-implementors] ACKing 200 OKs

2007-12-19 Thread Harsha. R
Hi Daniel, I will try to answer your questions. Hope it helps. The SIP stack(application and Transport layer) can be primarily viewed as below -- | Transaction User(TU) | - | Transaction Layer | --