Re: [Sip-implementors] Capability negotiation in SIP

2012-02-07 Thread Sreenath Kulkarni
Hello Vineet, If the meaning of "I believe I have assumes that SIP sends only one codec once rather than a set of them" words is sending single codec in Offer then you are wrong. You can send any number of codecs what the device supports in your offer. If not please clarify me the meaning of you

Re: [Sip-implementors] Expected UAC behavior when a reliable/non-reliable 18x without SDP is recieved for an INVITE sent without an offer and require 100 rel

2012-01-20 Thread Sreenath Kulkarni
Hello Hemanth, According to RFC3262 section 5 the below statement "If a reliable provisional response is the first reliable message sent back to the UAC, and the INVITE did not contain an offer, one MUST appear in that reliableprovisional response." UAS MUST send Offer in 183 response In your

Re: [Sip-implementors] Reduce the time to send UPDATE message in SIP call

2011-12-28 Thread Sreenath Kulkarni
Hello Verma, I'm assuming that sending of UPDATE is for session expiry feature. In this case if the A-node is not the refresher, then he may not send the UPDATE request so your suggestion may work some times only. Even decreasing of the timer to 1 - 2 minutes leads the increases of network traf

Re: [Sip-implementors] Query in Request URI

2009-06-23 Thread Sreenath Kulkarni
Hi Paul, I got a doubt by seeing the RFC 3261 section 19.1.1. Thanks for the explanation. Regards, Sreenath From: Paul Kyzivat To: Sreenath Kulkarni Cc: sip-implementors@lists.cs.columbia.edu Sent: Tuesday, 23 June, 2009 9:54:37 AM Subject: Re: [Sip

Re: [Sip-implementors] Query in Request URI

2009-06-22 Thread Sreenath Kulkarni
2009, Sreenath Kulkarni escribió: > Hi Sudhir, > > According to RFC 3261 Section 19.1.1, the sip uri should be.. > > sip:user:passw...@host:port;uri-parameters?headers >  > And in Section 25 of RFC 3261 it mentioned the ABNF for SIP uri. >  > But in the request uri it

Re: [Sip-implementors] Query in Request URI

2009-06-22 Thread Sreenath Kulkarni
Hi Sudhir, According to RFC 3261 Section 19.1.1, the sip uri should be.. sip:user:passw...@host:port;uri-parameters?headers   And in Section 25 of RFC 3261 it mentioned the ABNF for SIP uri.   But in the request uri its not clear that wht is the meaning of VoiceMail. I think the request uri shou

Re: [Sip-implementors] What a UAC should/must do with a NOTIFY request outside a dialog ?

2009-06-16 Thread Sreenath Kulkarni
: Re: [Sip-implementors] What a UAC should/must do with a NOTIFY request outside a dialog ? El Martes, 16 de Junio de 2009, Sreenath Kulkarni escribió: > Then I think in this case INFO would be better, as some times OPTIONS > mandates to provide the capabilities of the entity. Please provide c

Re: [Sip-implementors] What a UAC should/must do with a NOTIFY request outside a dialog ?

2009-06-16 Thread Sreenath Kulkarni
Then I think in this case INFO would be better, as some times OPTIONS mandates to provide the capabilities of the entity. Please provide coments on this. Thanks & Regards, Sreenath. From: Vikram Chhibber To: Sreenath Kulkarni Cc: sip-implemen

Re: [Sip-implementors] What a UAC should/must do with a NOTIFY request outside a dialog ?

2009-06-16 Thread Sreenath Kulkarni
Its like if the client understands the NOTIFY request then needs to send 481 response, if not 405 response is the better options. But u have to provide some error response in this case which stops the retransmissions of NOTIFY request. Iñaki can u please give us an example how the OPTIONS requ

Re: [Sip-implementors] Proxy behaviour in a subscribe dialog

2009-06-14 Thread Sreenath Kulkarni
Hi Dushyant, Will your proxy acts like an hop between your client and application server? If yes then I think there is no need to maintain the dialog information. Sreenath. From: Dushyant Dhalia To: sip-implementors@lists.cs.columbia.edu Sent: Saturday, 13 J

Re: [Sip-implementors] [OT] SIP ALG Detector released

2009-06-14 Thread Sreenath Kulkarni
Hi, I'm sorry to put this question. Can u please tell me where I can use this detecters and how it is usefull to test my client or server. Thanks, Sreenath. From: Iñaki Baz Castillo To: sip-implementors@lists.cs.columbia.edu Sent: Saturday, 13 June, 2009 8:4

Re: [Sip-implementors] Subscription is done for 'presence'. But NOTIFYrecd with event header 'reg' (or/and) 'presence'. What err resp?

2009-06-02 Thread Sreenath Kulkarni
Hi Hanifa,   According to RFC3265 section 3.2.4   If, for some reason, the event package designated in the "Event" header of the NOTIFY request is not supported, the subscriber will respond with a "489 Bad Event" response.   So I think we should send 489 for the response. But one question here is