[Sip-implementors] SIP Media Loopback call-flows.

2014-06-25 Thread Madhav Bhamidipati
Hello All, I am looking for Call-flows for SIP-RTP-Meida Loopback, can somebody point me ink on this? Thanks in advance, Madhav ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu

Re: [Sip-implementors] Does Don'tDisturm mode always return 480 Not Available

2008-04-04 Thread Madhav Bhamidipati
Busy here would give a wrong impression, caller would try repeatedly, better include some retry-after header. Madhav On Fri, Apr 4, 2008 at 3:21 PM, Iñaki Baz Castillo [EMAIL PROTECTED] wrote: Hi, just to clarify: do all the SIP phone reply a 480 Not Available when they are in DontDisturb

Re: [Sip-implementors] Server behavior on receiving same INVITE request differing only in the CSeq value,

2008-03-28 Thread Madhav Bhamidipati
It is perfectly valid, there are lots of such scenarios, simplest example is call-hold. Session refresh is one more scenario. Please go through RFC3261. Madhav On Fri, Mar 28, 2008 at 3:56 PM, Nitin Arora [EMAIL PROTECTED] wrote: is that really a possible scenario. When some UAC generates a

Re: [Sip-implementors] What to do if a UAS receives a request with Via - received param?

2008-03-26 Thread Madhav Bhamidipati
Hi Attila, I wonder if the following topology is invalid, in which case the forwarding stateless proxy can as well put the received information in Via header. If UAS erases the received information then it would be impossible for the proxy would send response to UAC. UAC NAT1

Re: [Sip-implementors] doubt on MIME body [RFC-3204]

2008-03-24 Thread Madhav Bhamidipati
Note that the Content-Length header is not mandatory in SIP on UDP. If body is there then content-type header will be there in all positive cases. You need to interpret body based on the content-type header. Madhav On Mon, Mar 24, 2008 at 3:57 PM, Avasarala Ranjit-A20990 [EMAIL PROTECTED]

Re: [Sip-implementors] Re :Re: SDP Error Handling -- Unsupported codec inSDP Answer

2008-03-19 Thread Madhav Bhamidipati
. Will the continuing call cause a mismatch of the stream? Please also give reference about this beahvior? Thanks, Alex Zhang ESN: 6-554-8782 -Original Message- From: Madhav Bhamidipati [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2008 4:20 PM To: Alex Zhang (GDNTRND

Re: [Sip-implementors] SDP Error Handling -- Unsupported codec in SDP Answer

2008-03-17 Thread Madhav Bhamidipati
, Alex Zhang ESN: 6-554-8782 -Original Message- From: Madhav Bhamidipati [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2008 4:20 PM To: Alex Zhang (GDNTRND) Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] SDP Error Handling -- Unsupported codec

Re: [Sip-implementors] Is valid a To_tag in 100 Trying?

2008-03-07 Thread Madhav Bhamidipati
As such for compatibility reasons nothing can be inferred from to-tag in 100 Trying. That is, there won't be any use even if it identified that the dialog has been established. If you are thinking on how to terminate the call at this point then CANCEL still holds good. Madhav On 3/7/08, Iñaki

Re: [Sip-implementors] Query on UAC Behaviour for 183 with SDP followed by 180 Ringing

2008-02-27 Thread Madhav Bhamidipati
Ignore 180 with 'NO SDP', better give preference to 18X with SDP. in some cases you may receive 180(SDP) then 183 (SDP) (very rare cases) but I have seen such case, in such cases generally 180 (SDP) will be inband ringback and 183 (SDP) may be inband ringback or an announcement so better switch