Dear Paul, Many thanks for clarification. I'll definitely go thru RFC 2543.
On Sun, Jan 18, 2015 at 9:10 PM, Paul Kyzivat <pkyzi...@alum.mit.edu> wrote: > On 1/18/15 1:07 AM, Imran Saleem wrote: > >> Dear All, >> >> Can someone please suggest the possible reason for this behavior. >> >> In SBC "The receiving side hooks on before calling party, the line is >> hold, >> the re-Invite changes the stream mode to receive-only and that's why the >> IP >> and port are 0." >> >> What does SIP state.. >> >> > IP of 0.0.0.0 was the "old" (RFC2543) way of doing hold. The recommended > way of doing hold was changed to a=sendonly/inactive in RFC3261. But the > old way is still allowed. Also IP 0.0.0.0 is a way to set up a call (on > hold) before there are *any* RTP resources assigned to the call. > > You should not be upset by this. It is a valid thing to do. > > Thanks, > Paul > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- Br, Imran Saleem +966-533-414475 _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
