Hi Gonzalo Camarillo,
If UE-A wants to communicate with UE-B by video, but UE-B only want to communicate by audio.
and if they uses the new SDP, when pre-conditions met, UE-B will send his/her videos regardless
of UE-B's willing.
And if UE-B never send his video although the pre-conditions are met, then UE-A will be puzzled why
he/she is charged for vedio while receiving NO vedio from UE-B.
I think this is a operational problem that we have to solve too.
regards,
Eric
| Gonzalo Camarillo <Gonzalo.Camarillo@xxxxxxxxxxxx>
2009-02-27 17:10 |
|
Hi,
> Also If pre-conditions are met,and re-INVITE fails, UEs could use the
> new SDP.
> This solution will give someone a way to escape charging.
> For example, if UEs use audio at the first time,
> then one of them raise a re-INVITE with a SDP carrying both audio and
> video,
> after the preconditions are met, then the other rejects the re-INVITE,
> but they can communicate with both audio and video after all.
No, if they negotiate video and the preconditions are met, they will be
charged for video, regardless of what happens with the re-INVITE.
Cheers,
Gonzalo
-------------------------------------------------------- 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
