Re: PRACK: Change MUST requirement to include SDP offerin first reliable provisional response

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Hi,
>  
> I guess it depends on whether sending an early-session SDP offer
> "fulfills" the requirement to send an SDP offer in the first
> reliable response.


It's OK if the first reliable 18x with early media fulfill the requirement.

>  
> If it does, is it then allowed to complete the whole INVITE
> transaction with only an early-session SDP offer/answer?



I think there must be normal session offer/answer exchange if the final response
is 2xx, but if the final response is 3xx-6xx as INVITE fails, an early-session
SDP offer/answer on the purpose of failure-notice is enough.


Then, if the INVITE carrys NO SDP ,the first reliable response generator must
fill the response with at least one SDP(early-session, or normal session, or both).
There must be at least one normal session offer/answer exchange if the final response
is 2xx.


Regards,
Eric


>  
> Regards,
>  
> Christer
>
> From: wang.libo@xxxxxxxxxx [mailto:wang.libo@xxxxxxxxxx]
> Sent: Thursday, April 02, 2009 9:25 AM
> To: Christer Holmberg
> Cc: Hisham Khartabil; Sanjay Sinha (sanjsinh); sipping@xxxxxxxx;
> sipping-bounces@xxxxxxxx
> Subject: Re: PRACK: Change MUST requirement to include SDP
> offerin first reliable provisional response

>
> Hi,
>
>   Considering early-session, if the UAS receives an INVITE without SDP,
> before transmit it,the UAS wants to play a tone with early-session in order
> to inform the caller the call is ongoing.The UAS may have no rule to
> generate a normal session SDP.Unless UAS creates a fake one e.g with
> ip 0.0.0.0.
>
> UAC                 UAS
> |--------INVITE----->|
> |<-----183(early)----|-----INVITE-->
> |-----PRACK(early)-->|
> |<--------200--------|
>
>
> Regards
> Eric

> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this
> mail is solely property of the sender's organization. This mail
> communication is confidential. Recipients named above are obligated
> to maintain secrecy and are not permitted to disclose the contents
> of this communication to others.
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please
> notify the originator of the message. Any views expressed in this
> message are those of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux