Re: [Sip-implementors] Proper negative final status code formalformedSDP

2008-12-07 Thread Rockson Li (zhengyli)
I think 415 is too specific, there's no limitation in RFC3261 that 400 is only applicable to msg headers. Regards, -Rockson -Original Message- From: Avasarala Ranjit-A20990 [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 3:03 PM To: Rockson Li (zhengyli); Tarun2 Gupta; Maxim So

Re: [Sip-implementors] Proper negative final status code formalformedSDP

2008-12-07 Thread Avasarala Ranjit-A20990
Hi When you are sure SDP is malformed, then won't 415 Unsupported media is better? 400 would be better if any of the headers of INVITE are wrong. Regards Ranjit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rockson Li (zhengyli) Sent: Monday, Decemb

Re: [Sip-implementors] Proper negative final status code for malformedSDP

2008-12-07 Thread Rockson Li (zhengyli)
I agree with Tarun here Rockson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tarun2 Gupta Sent: Monday, December 08, 2008 11:39 AM To: Maxim Sobolev; sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Proper negative final status c

[Sip-implementors] How to build a SIP packet over UDP ?

2008-12-07 Thread cool goose
Hi All, I am writing small application which sends a REGISTER message to a registrar and in turn receives a 200 OK. My application reads all the details for the REGISTER message from an XML file and uses UDP sockets to send the data to registrar. As of now, I have developed the reading from XML fi

Re: [Sip-implementors] Proper negative final status code for malformedSDP

2008-12-07 Thread Tarun2 Gupta
Hi IMO, 400 is the most apt response code. Regards, Tarun Gupta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maxim Sobolev Sent: Saturday, December 06, 2008 11:12 AM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors]

Re: [Sip-implementors] Query on RFC 3680.

2008-12-07 Thread Dale Worley
> <> > The contacts A1 & A2 from the UA's perspective are just different ways > to get a call delivered to it. UA does not intend to prioritize one over > the other. What would be the need for the server in this case to return > different expires. While I understand that theoretically it is possibl

Re: [Sip-implementors] Query on RFC 3680.

2008-12-07 Thread P Sudarshanakrishnan-A14377
Inline a couple of clarifications -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Sunday, December 07, 2008 10:10 PM To: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Query on RFC 3680. From: "P Sudarsh

[Sip-implementors] Per DID Billing in an IP-PBX

2008-12-07 Thread SungWoo Lee
Dear all, I have a question regarding per-did billing in a IP-PBX, and the scenario is this. An IP-PBX has 3 DIDs assigned from a Service Providers and two companies are sharing the IP-PBX for cost saving; assigning 2 DIDs for 'A' compa

Re: [Sip-implementors] Proper negative final status code for malformed SDP

2008-12-07 Thread Dale . Worley
From: Maxim Sobolev <[EMAIL PROTECTED]> Yes, this is my best pick at the moment, however, I am little bit unsure as SDP syntax is not part of SIP RFC. Since there doesn't appear to be any more specific response, 400 appears to be the only choice. Dale _

Re: [Sip-implementors] Query on RFC 3680.

2008-12-07 Thread Dale . Worley
From: "P Sudarshanakrishnan-A14377" <[EMAIL PROTECTED]> Assuming A registers contacts A1, A2. When a network entity initiates a notification I am not sure if there is a possibility that it indicates different attributes (say rejected for A1 and probation for A2) for the individual c