|
> But, as indicated in Gonzalo's draft, that can be avoided by the UAS > sending an UPDATE instead of 4xx. I showed a example that UAC can not accept the UPDATE. But he did not give further explanation. session before Re-INVITE has two m-line, as m1 and m2 UAC send Re-INVITE to add m3 and remove m2, m3 with precondition. Then UAS can not alert the user. After m3's precondition OK, m2 has removed(because Offer/Answer pairs has exchanged). Then user rejected the modification. Then the undo UPDATE re-open m2 and remove m3. Re-open m2 can need precondition. Then the UAC can not accept it at once. 微软地图实时路况，为您节省的不仅仅是时间！ 立即查看！ |
_______________________________________________ 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
