Of course, it will surely cause the mismatch in stream, because UAC will start streaming in Codec3. Any way UAC is wrong, there is no point in expecting UAS also to be wrong, because call continuation in such a scenario is wrong from UAS point of view.
On 3/17/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > What will happen if the UAS decide to continue the call? > Actually, the UAC may have some errors, such as select a wrong codec > outside the codec list of the SDP Offer. Will the continuing call cause > a mismatch of the stream? > > Please also give reference about this beahvior? Thanks, > > > Alex Zhang > ESN: 6-554-8782 > > > -----Original Message----- > From: Madhav Bhamidipati [mailto:[EMAIL PROTECTED] > Sent: Monday, March 17, 2008 4:20 PM > To: Alex Zhang (GDNTRND) > Cc: [email protected] > Subject: Re: [Sip-implementors] SDP Error Handling -- Unsupported codec > in SDP Answer > > I wonder if it sends ACK in the first place with an unrelated codec. > If UAC sends a kind of > 4XX then call continuation is still possible, i.e UAS has still an > option to continue the call with old parameters. > > If it sends ACK then UAS sends BYE with no other option. > > Madhav > > On 3/17/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Can anybody give guideline about the UAS Behavior as below: > > > > UAC UAS > > <========== Session Establised=========> > > | | > > |-----Re-invite(w/o SDP offer)--->| > > | | > > |<----200 OK(Codec1, Codec2)------| > > | | > > |-------ACK (Codec 3)------------>| > > | | > > | | > > > > Will UAS release the call or continue the call with the previous SDP? > > Thanks, > > > > Alex > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
