Hi Paul/Dale/Ankur, Thanks for your reply. below is the scenario please help resolve it.
Below is the updated scenario. sorry for confusion by making step2 as recvonly. now it is fine. The problem here is that after step 9 call becomes audio only. Video disappears. UAC1--------------------------------------------------------------------UAC2 1)---------------------INVITE (a=sendrecv)-------------------------> 2)<---------------------200-OK(a=sendrecv)------------------------- 3)-------------------------------ACK--------------------------------------> 4)<---------------------INVITE (a=sendonly)-------------------------(UAC wants to put call on hold here) 5)---------------------200-OK(a=inactive)-------------------------> 6)<---------------------------ACK ----------------------------------------- 7)<---------------------INVITE (a=sendonly)-------------------------(UAC2 wants to resume the call here) 8)---------------------200-OK(a=recvonly)-------------------------> 9)<---------------------------ACK ----------------------------------------- The call is established in step 3. It's an audio and video call. In step 4 UAC2 puts call on hold by sending (a=sendonly) for both audio and video media lines respectively. In step 5 UAC1 responds with a=inactive for both audio and video lines and along with that it makes video port as 0. While resuming call in step 7 Does UAC2 send video line with valid port or 0 port??? for audio mline it is sending validn port with a=sendrecv. What is happening is UAC2 is sending mline for video as last used(while holding) with valid port and a=sendonly?? Does RFC says anything or is it implementation dependent behavior?? Thanks, _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
