Hi John, that's a really good question and I didn't find any answers in the RFCs.
My option is that you must stop the RTP Session if you have a conncetion. The user wants to hold the conncection and he wouldn't understand why the hold was not successful. Greeting Markus "Wainwright, John" <[EMAIL PROTECTED]> schrieb am 05.05.05 20:47:21: > > If I use "a=sendonly" in the INVITE message when putting a call on hold what > response should I expect back if the endpoint does not support this > attribute ? > > Do I still get the 200OK and determine the attribute is not supported by the > absence of the "a=recvonly" attribute implying I need to fall back to using > "C=0.0.0.0" > > Thanks > John > > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
