Re: [Sip-implementors] UPDATE on early dialog

2007-11-26 Thread Pandurangan R S
Hi,

You have to compile sipp like this

*With PCAP play
<http://sipp.sourceforge.net/doc/reference.html#pcapplay>and without
authentication<http://sipp.sourceforge.net/doc/reference.html#authentication>support
*:

# gunzip sipp-xxx.tar.gz
# tar -xvf sipp-xxx.tar
# cd sipp
# make pcapplay

 *With PCAP play <http://sipp.sourceforge.net/doc/reference.html#pcapplay>and
authentication<http://sipp.sourceforge.net/doc/reference.html#authentication>support
*:

# gunzip sipp-xxx.tar.gz
# tar -xvf sipp-xxx.tar
# cd sipp
# make pcapplay_ossl



Regards
Pandu

On 11/27/07, Ramya Jyothi <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> Refer RFC 3311
> UPDATE allows a client to update
> parameters of a session (such as the set of media streams and their
>codecs) but has no impact on the state of a dialog.  In that sense,
>it is like a re-INVITE, but unlike re-INVITE, it can be sent before
>the initial INVITE has been completed.  This makes it very useful for
>updating session parameters within early dialogs.
>
> -Regards Ramya
>
>
> - Original Message -
> From: "Murali Radhakrishnan" <[EMAIL PROTECTED]>
> To: 
> Sent: Saturday, November 24, 2007 11:07 AM
> Subject: [Sip-implementors] UPDATE on early dialog
>
>
> > Hi,
> >
> > I have an Application Runing on a Weblogic Sip Server (BEA). In Case
> 1
> > - Non Reliable scenario, when i send a UPDATE request, it reaches the
> > destination (Request-URI) is set to the target.
> >
> > Case 1 :- Non- Reliable
> >
> > A  (UAC)   (App) Wlss (B2B)B (UAS)
> >
> >  INVITEINVITE
> > |-->|
> > -->|
> >200OK   200OK
> > |<--|
> > <--|
> > ACK   ACK
> >
> |-->|-->|
> >UPDATE  UPDATE
> >
> |-->|-->|
> >
> > In this below case 2, where there is a early dialog and reliable
> > provisional
> > response situation. The UPDATE received at the application does not
> reach
> > the destination. The request-uri is not set to the target.
> >
> > My question is
> >
> > Can we send UPDATE when there is a early dialog  and will it reach the
> > target ?
> > Do we need to complete the 3-way handshake ( create dialog as in case 1)
> > to
> > send the UPDATE request ?
> >
> >
> > Case 2 :- Reliable Provisional response
> >
> > A  (UAC)   (App) Wlss (B2B)B (UAS)
> >
> > INVITE
> > |-->|
> > -->|
> > 183 SP rel  183 SP rel
> >   /Early dialog established/
> > |<--|
> > <--|
> > PRACK   PRACK
> >
> |-->|-->|
> > 200 (PRACK) 200 (PRACK)
> > |<--
> > |<--|
> > UPDATE
> > |-->| fails
> >
> > Thanks and Regards,
> > Murali.R
> > ___
> > Sip-implementors mailing list
> > Sip-implementors@lists.cs.columbia.edu
> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


Re: [Sip-implementors] UPDATE on early dialog

2007-11-26 Thread Ramya Jyothi
Hi

Refer RFC 3311
UPDATE allows a client to update
 parameters of a session (such as the set of media streams and their
   codecs) but has no impact on the state of a dialog.  In that sense,
   it is like a re-INVITE, but unlike re-INVITE, it can be sent before
   the initial INVITE has been completed.  This makes it very useful for
   updating session parameters within early dialogs.

-Regards Ramya


- Original Message - 
From: "Murali Radhakrishnan" <[EMAIL PROTECTED]>
To: 
Sent: Saturday, November 24, 2007 11:07 AM
Subject: [Sip-implementors] UPDATE on early dialog


> Hi,
>
> I have an Application Runing on a Weblogic Sip Server (BEA). In Case 1
> - Non Reliable scenario, when i send a UPDATE request, it reaches the
> destination (Request-URI) is set to the target.
>
> Case 1 :- Non- Reliable
>
> A  (UAC)   (App) Wlss (B2B)B (UAS)
>
>  INVITEINVITE
> |-->|
> -->|
>200OK   200OK
> |<--|
> <--|
> ACK   ACK
> |-->|-->|
>UPDATE  UPDATE
> |-->|-->|
>
> In this below case 2, where there is a early dialog and reliable 
> provisional
> response situation. The UPDATE received at the application does not reach
> the destination. The request-uri is not set to the target.
>
> My question is
>
> Can we send UPDATE when there is a early dialog  and will it reach the
> target ?
> Do we need to complete the 3-way handshake ( create dialog as in case 1) 
> to
> send the UPDATE request ?
>
>
> Case 2 :- Reliable Provisional response
>
> A  (UAC)   (App) Wlss (B2B)B (UAS)
>
> INVITE
> |-->|
> -->|
> 183 SP rel  183 SP rel
>   /Early dialog established/
> |<--|
> <--|
> PRACK   PRACK
> |-->|-->|
> 200 (PRACK) 200 (PRACK)
> |<--
> |<--|
> UPDATE
> |-->| fails
>
> Thanks and Regards,
> Murali.R
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors 

___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


Re: [Sip-implementors] UPDATE on early dialog

2007-11-24 Thread Paul Kyzivat


Murali Radhakrishnan wrote:
> Hi,
> 
>  I have an Application Runing on a Weblogic Sip Server (BEA). In Case 1
> - Non Reliable scenario, when i send a UPDATE request, it reaches the
> destination (Request-URI) is set to the target.
> 
>  Case 1 :- Non- Reliable
> 
>  A  (UAC)   (App) Wlss (B2B)B (UAS)
> 
>   INVITEINVITE
>  |-->|
> -->|
> 200OK   200OK
>  |<--|
> <--|
>  ACK   ACK
>  
> |-->|-->|
> UPDATE  UPDATE
>  
> |-->|-->|
> 
> In this below case 2, where there is a early dialog and reliable provisional
> response situation. The UPDATE received at the application does not reach
> the destination. The request-uri is not set to the target.
> 
> My question is
> 
> Can we send UPDATE when there is a early dialog  and will it reach the
> target ?
>  Do we need to complete the 3-way handshake ( create dialog as in case 1) to
> send the UPDATE request ?

Superficially what you are doing in case 2 looks fine, and you should 
expect that it will work.

But there could be some issue with the details of the messages, so it 
would be good if you could provide actual message details.

Thanks,
Paul

> Case 2 :- Reliable Provisional response
> 
> A  (UAC)   (App) Wlss (B2B)B (UAS)
> 
> INVITE
>  |-->|
> -->|
>  183 SP rel  183 SP rel
>/Early dialog established/
>  |<--|
> <--|
>  PRACK   PRACK
>  
> |-->|-->|
>  200 (PRACK) 200 (PRACK)
> |<--
> |<--|
>  UPDATE
>  |-->| fails
> 
> Thanks and Regards,
> Murali.R
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


[Sip-implementors] UPDATE on early dialog

2007-11-23 Thread Murali Radhakrishnan
Hi,

 I have an Application Runing on a Weblogic Sip Server (BEA). In Case 1
- Non Reliable scenario, when i send a UPDATE request, it reaches the
destination (Request-URI) is set to the target.

 Case 1 :- Non- Reliable

 A  (UAC)   (App) Wlss (B2B)B (UAS)

  INVITEINVITE
 |-->|
-->|
200OK   200OK
 |<--|
<--|
 ACK   ACK
 
|-->|-->|
UPDATE  UPDATE
 
|-->|-->|

In this below case 2, where there is a early dialog and reliable provisional
response situation. The UPDATE received at the application does not reach
the destination. The request-uri is not set to the target.

My question is

Can we send UPDATE when there is a early dialog  and will it reach the
target ?
 Do we need to complete the 3-way handshake ( create dialog as in case 1) to
send the UPDATE request ?


Case 2 :- Reliable Provisional response

A  (UAC)   (App) Wlss (B2B)B (UAS)

INVITE
 |-->|
-->|
 183 SP rel  183 SP rel
   /Early dialog established/
 |<--|
<--|
 PRACK   PRACK
 
|-->|-->|
 200 (PRACK) 200 (PRACK)
|<--
|<--|
 UPDATE
 |-->| fails

Thanks and Regards,
Murali.R
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors