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" wrote:
> On 10/22/14 11:37 AM, Saúl Ibarra Corretgé wrote:
>
>> Hi all,
>>
>> I recently ran into an intro issue with
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 conn
If its not mentioned then logic will be left for user to implement
Regards
Pranav
On 22 Oct 2014 21:30, "Balint Menyhart" wrote:
> Hi,
>
> RFC 4566, just where c= lines are defined:
>
> 5.7. Connection Data ("c=")
>
> c=
>
>The "c=" field contains connection data.
>
>A session de
Hi,
RFC 4566, just where c= lines are defined:
5.7. Connection Data ("c=")
c=
The "c=" field contains connection data.
A session description MUST contain either at least one "c=" field in
each media description or a single "c=" field at the session level.
It MAY contain a
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
