Re: [Sip-implementors] Media Port change during Hold/resume
On 6/8/18 11:29 AM, Parveen Aggarwal wrote: Dear Experts, I am facing one scenario: 1. Make video call: Audio and video port non-zero 2. downgrade video call: audio port non-zero and video port 0 3. Network hold the call: audio:sendonly , video port 0 4. network sending re-invite without SDP, User agent sending offer in 200 OK but with video port 0 5. Network sending ACK with audio: sendonly, video port: 0 === after this Network is resuming the call with re-invite but at the same time it is sending video port as non-zero. Is it a correct behavior to update audio media direction from recvonly to sendrecv and updating the Video port in same re-INVITE? (Any spec reference) I don't see anything particularly wrong in anything above, to the extent that I understand what you mean. It isn't clear to me who initiated the downgrade to audio only. If that was the network, rather than the caller, and if the caller still desires video, then in (4) I would expect it to offer a non-zero video port again. But there is a lot of local discretion in that. It isn't clear to me what it is that you are questioning. Thanks, Paul ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] Media Port change during Hold/resume
Hi Praveen, AFAIK Unhold + Video Upgrade in a same INVITE is valid usecase. Searching for Spec reference. will update once I get it. Could think of one use case. 1. MO make VT call to MT. 2. Call held, Network support only audio announcement. 3. Network downgrades call to audio only and audio direction recvonly at MT. 4. After MO unhold call. Its Upgrade + unhold to MT. Regards, Venkat Ramana On Fri, Jun 8, 2018 at 8:59 PM, Parveen Aggarwal wrote: > Dear Experts, > > I am facing one scenario: > > 1. Make video call: Audio and video port non-zero > 2. downgrade video call: audio port non-zero and video port 0 > 3. Network hold the call: audio:sendonly , video port 0 > 4. network sending re-invite without SDP, User agent sending offer in 200 > OK but with video port 0 > 5. Network sending ACK with audio: sendonly, video port: 0 > === > after this Network is resuming the call with re-invite but at the same time > it is sending video port as non-zero. > > Is it a correct behavior to update audio media direction from recvonly to > sendrecv and updating the Video port in same re-INVITE? (Any spec > reference) > > Thanks for your advice. > > Regards, > Parveen > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[Sip-implementors] Media Port change during Hold/resume
Dear Experts, I am facing one scenario: 1. Make video call: Audio and video port non-zero 2. downgrade video call: audio port non-zero and video port 0 3. Network hold the call: audio:sendonly , video port 0 4. network sending re-invite without SDP, User agent sending offer in 200 OK but with video port 0 5. Network sending ACK with audio: sendonly, video port: 0 === after this Network is resuming the call with re-invite but at the same time it is sending video port as non-zero. Is it a correct behavior to update audio media direction from recvonly to sendrecv and updating the Video port in same re-INVITE? (Any spec reference) Thanks for your advice. Regards, Parveen ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
