Re: [Sip-implementors] Is route set be recomputed while sending ACK for retransmitted 2xx?

Thanks for your inputs Nebojsa and Vikram. I understand that the retransmitted 2xx has to follow the same path as the first 2xx. Now I have a doubt that whether an intermediate proxy can change the record-route to indicate that it will be available at some different URI in future before forwardi

Re: [Sip-implementors] The non-2xx final response is allowed to be sentby UAS before PRACK of the Provisional Response?

UAS must hold off from sending 200 OK if it sent reliable 18x with SDP and PRACK was not yet received. That's it. Any other final response 4xx/5xx/6xx can be sent without waiting for PRACK. On 10/15/2007 9:17 PM, [EMAIL PROTECTED] wrote: > I am a little about the sentence: " unless the final res

Re: [Sip-implementors] Cannot cancel pending Invite client transaction after receiver restarts

INVITE transaction will expire if CANCEL does not produce 487 for INVITE. Every transaction has limited time it is willing to wait for a final response. This is well defined in RFC 3261. On 10/5/2007 5:00 AM, Marco Ambu wrote: > Hi, > I would like to submit to you the following problem: > we have

Re: [Sip-implementors] Is route set be recomputed while sending ACK for retransmitted 2xx?

Since 200 OK responses must follow the Vias listed in INVITE, they cannot be retransmitted over different proxies. On 10/17/2007 2:12 AM, praveen dandin wrote: > Hi, > Consider the following scenario ( proxies between UAC and UAS are not shown) > UAC

Re: [Sip-implementors] RFC 3323: location of critical

From: "Brett Tate" <[EMAIL PROTECTED]> Since some vendors are validating the position of "critical" within the Privacy header based upon the following rfc3323 text, I decided to ask a few questions. RFC 3323 section 4.2: "When a Privacy header is constructed, it MUST consist of

[Sip-implementors] SIP in a FPGA with VHDL

Hi, i'm newbie in this topic (SIP), and I tried to implement over FPGA specify in a Xilinx Spartan 3E, but the fact is that i don't know the architecture of SIP, I study the RFC3261 but I don't understand very well. I request your help to understand the protocol and implement in a FPGA with VHDL.

Re: [Sip-implementors] changes on 3GPP SIP with reference to IETF SIP

From: [EMAIL PROTECTED] Can someone tell me what are the changes done in IETF SIP for making it suitable for 3GPP SIP. This is a SIP mailing list. You might want to ask the 3GPP people this question. Dale ___ Sip-implementors mailing list

[Sip-implementors] Mapping of P-Asserted-Identity to ETSI EN 300 659-3 (Data Link Presentation for CLIP, OIP)

Hi, Suppose you have the next message (in an IMS environment) P-Asserted-Identity: "John Doe" P-Asserted-Identity: tel:<+1-212-555-> The "Display" Protocol defined in ETSI standard EN 300 659 (or the equivalent BellCore MDMF/SDMF one for North America) is used for the IMS Originating

Re: [Sip-implementors] Procedure for ENUM Look Up

No. > -Original Message- > From: [EMAIL PROTECTED] [mailto:sip- > [EMAIL PROTECTED] On Behalf Of Jitendra Singh > Bhadoriya > Sent: Thursday, October 18, 2007 8:40 AM > To: [EMAIL PROTECTED] > Cc: Jitendra Singh Bhadoriya; sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors

[Sip-implementors] Procedure for ENUM Look Up

Hi, ENUM (E.164 Number Mapping, RFC 3761 ) is a system that uses DNS to translate telephone numbers, like '+12025332600', into URIs (Uniform Resource Identifiers, RFC 2396

[Sip-implementors] Procedure for ENUM Look Up

Hi, ENUM (E.164 Number Mapping, RFC 3761 ) is a system that uses DNS to translate telephone numbers, like '+12025332600', into URIs (Uniform Resource Identifiers, RFC 2396