I guess that would make subsequent answer a problem because of session level c line 0.0.0.0 ... stream level is good enough.
Regards Pranav On 22 Oct 2014 22:08, "Paul Kyzivat" <pkyzi...@alum.mit.edu> wrote: > On 10/22/14 11:37 AM, Saúl Ibarra Corretgé wrote: > >> Hi all, >> >> I recently ran into an intro issue with some unknown SIP device. My >> client uses a per-stream SDP connection line, but when a stream is disabled >> (port set to 0) the stream is just reduced to the m= line. >> >> Technically I could put the connection line at the session level in some >> cases, but it could be that I need to have it at the stream level. Should I >> also add it for disabled streams? FWIW, doing so made the aforementioned >> SIP device happy, but I couldn’t find any RFC reference which stated it’s >> always required. >> >> Any clarification (or recommendation) would be appreciated, thanks! >> > > As others have commented, I think you MUST have *some* c-line for each > m-line, whether disabled or not. > > If it makes your logic simpler, you could *always* have a token c-line > (e.g., "c=IN IP4 0.0.0.0") at the session level, and then a separate c-line > for each non-disabled m-line. > > Thanks, > Paul > _______________________________________________ > 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
