[Sip-implementors] RFC 4028 & Reason header

2009-01-29 Thread krishna kalluri
Hi, Keep alive mechanisms are described in RFC 4028. If a session refresh is not received before the interval passes then the UA not acting as a refresher sends BYE request to termination the session. Is it allowed and possible to use the Reason header (RFC 3326) in BYE to tell the reason for the

[Sip-implementors] RRC4245 -- sidebars

2008-12-02 Thread krishna kalluri
RRC4245 -- sidebars Hi, There are requirements related to sidebars in RFC 4245. Some requirements are related to manage sidebars by sip means. For instance Req 3 REQ-3: A conference participant creates a side-bar conference with one or more participants in a conference by SIP means. I like

Re: [Sip-implementors] SIP and firewalls

2008-09-30 Thread krishna kalluri
Hi Paul, If you are not aware this draft please take a look. I found it very useful to understand the nat and firewall scenarios. http://tools.ietf.org/html/draft-ietf-sipping-nat-scenarios-09 Regards Krishna > -- > > Messag

Re: [Sip-implementors] UA behaviour on recieving INVITE withoutmax-forwards header

2008-09-24 Thread krishna kalluri
Hi, Attilas response is correct if a proxy receives an INVITE with out Max-Forwards header field. I think Navneet is saying "Endpoint" Section 16.6 point 3 of RFC 3261 says "If the copy does not contain a Max-Forwards header field, the proxy MUST add one with a field value, which SHOULD be 70" I

Re: [Sip-implementors] sip-implementors@lists.cs.columbia.edu

2008-09-23 Thread krishna kalluri
Hi Karthik, As you stated below the B2BUA role is mainly for any kind of services. It could be PBX, Annoucement, conferencing or for security. In general SIP proxy provides the routing of sip messages. B2BUA is a kind of functionality and if you like you can implement together in the same physica

Re: [Sip-implementors] INVITE processing in UAS -- RFC 3261

2008-09-17 Thread krishna kalluri
Tue, Sep 16, 2008 at 10:04 PM, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > First, look at > http://www.ietf.org/internet-drafts/draft-ietf-sipping-sip-offeranswer-08.txt > > More comments inline. > >Thanks, > Paul > > krishna kalluri wrote: > >>

[Sip-implementors] INVITE processing in UAS -- RFC 3261

2008-09-16 Thread krishna kalluri
Hi, The following para in "13.3.1.4 The INVITE is Accepted" in RFC 3261 is confusing with the description in 13.2.1 (At the end after the bullets) I just split the para in 13.1.4 in to two different statements. >From 13.3.1.4: If the INVITE request contained an offer, and the UAS had not yet sen

Re: [Sip-implementors] question regarding REGISTER - RFC 3665

2008-09-15 Thread krishna kalluri
lementors@lists.cs.columbia.edu > Message-ID: ><[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8 > > 2008/9/15, krishna kalluri <[EMAIL PROTECTED]>: > > Hi, > > > > I have a question related to the usage of Call-Id and CSeq header

[Sip-implementors] question regarding REGISTER - RFC 3665

2008-09-15 Thread krishna kalluri
Hi, I have a question related to the usage of Call-Id and CSeq header fields. I take the examples in section 2 of RFC 3665 ( http://tools.ietf.org/html/rfc3665) and I consider the examples as a sequence of messages exchanged by a UE. So different messages in section 2.1 through 2.4 are exchanged