Thanks, this makes sense and is what most UAs do i believe but I thought if the version number does not change the same identical SDP used previously should be sent ,in this example the SDP has a sendonly attribute.
Hence the confusion, are we saying an identical SDP need not be present as long as the version number is kept the same? Thanks --- On Thu, 28/4/11, Shanbhag, Somesh (NSN - IN/Bangalore) <[email protected]> wrote: > From: Shanbhag, Somesh (NSN - IN/Bangalore) <[email protected]> > Subject: RE: [Sip-implementors] Broadworks Reinvite issue > To: [email protected], [email protected] > Date: Thursday, 28 April, 2011, 8:14 > In case of session-audit from SBC, > > UAC <------------ Broadworks > INVITE ver=2 > inactive > UAC--------------> Broadworks > INVITE ver=2 > ?? > > ?? Should be a=inactive because UAC is already in hold. And > also, earlier for a=sendonly, UAC had got a=inactive. > > -Somesh > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of ext Nauman Sulaiman > Sent: Thursday, April 28, 2011 12:31 PM > To: [email protected] > Subject: [Sip-implementors] Broadworks Reinvite issue > > Hi, > > Scenario is as follows UAC makes call to UAS over > Broadworks B2BUA and then UAC goes on hold. Broadworks > periodically issues Session Audit with SDP version number > unchanged, this is for UAC and UAS which do not support > session timers or UPDATE method. > > UAC -------> Broadworks ------------> UAS > INVITE ver=1 > INVITE ver=1 > sendrecv > sendrecv > UAC <------- > Broadworks <---------- UAS > 200OK ver=1 > 200OK ver=1 > sendrecv > sendrecv > > UAC goes on hold > > UAC------------> Broadworks -----------> UAS > INVITE ver=2 > INVITE ver=2 > sendonly > inactive > > UAC <--------- Broadworks > <--------- UAS > 200OK ver=2 > 200OK ver =2 > inactive > inactive > > > Broadworks session audit (UPDATE not supported by UAC > or UAS) > > > UAC <------------ Broadworks > INVITE ver=2 > inactive > UAC--------------> Broadworks > INVITE ver=2 > ?? > > > With session Audit shown at the end, Broadworks sends the > UAC a REINVITE with the session version unchanged. However > the last SDP that the UAC sent broadworks had a media > attribute of sendonly. > > What should the UAC send back in the media attribute field > here, should SDP be unchanged if the version no. is > unchanged but in this case we would send back the original > sdp with an attribute of sendonly. > > I have seen UAs put inactive in this field, what is > correct? > > > Many thanks > > _______________________________________________ > 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
