sage-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Parveen
Aggarwal
Sent: Friday, June 8, 2018 9:00 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Media Port change during Hold/resume
** This mail
Parveen Aggarwal writes:
> 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)
There are few limitations regarding the changes that a new offer can
propose. Mostly, the number of m- lines may
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,
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
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
