Rockson Li (zhengyli) wrote:
>Hi folks,
>
>Recently, I am confused on the identity of a RTP session.
>
>per RFC3550
>
> RTP session: An association among a set of participants
> communicating with RTP. ... A participant distinguishes
> multiple RTP sessions by reception of differe
Hi folks,
Recently, I am confused on the identity of a RTP session.
per RFC3550
RTP session: An association among a set of participants
communicating with RTP. ... A participant distinguishes
multiple RTP sessions by reception of different sessions using
different pairs
Fernando Mercês wrote:
> Thank you, Paul.
>
> Other fact is that 415 error must send a list of acceptable codecs,
> types and languages (like RFC says) but my 415 do not send this list.
> So, it's really misused by voicemail erver.
>
> I'm trying to change some parameters from my PBX to see the
El Jueves, 27 de Noviembre de 2008, Michael Procter escribió:
> Iñaki Baz Castillo wrote:
> > Hi, I've read Session Timers RFC but it's a bit confusing for me. I've a
> > basic doubt:
> >
> >alice proxy bob
> >
> > - alice calls bob.
> > - proxy doesn't implement SessionTimers (in the
Iñaki Baz Castillo wrote:
> Hi, I've read Session Timers RFC but it's a bit confusing for me. I've a
> basic
> doubt:
>
>alice proxy bob
>
> - alice calls bob.
> - proxy doesn't implement SessionTimers (in the way a proxy could implement
> it).
> - bob implements SessionTimers and
Hi, I've read Session Timers RFC but it's a bit confusing for me. I've a basic
doubt:
alice proxy bob
- alice calls bob.
- proxy doesn't implement SessionTimers (in the way a proxy could implement
it).
- bob implements SessionTimers and want to use them.
In this scenario, can Sess
Thank you, Paul.
Other fact is that 415 error must send a list of acceptable codecs,
types and languages (like RFC says) but my 415 do not send this list.
So, it's really misused by voicemail erver.
I'm trying to change some parameters from my PBX to see the results,
but without sucess yet. I don
Iñaki Baz Castillo wrote:
> I think it's a bad specification in RFC 3261.
No. This is a classical problem of protocol encoding rules. SIP doesn't
separate encoding rule from the data structures it operate (the same is
in XMPP). That's because there is a lot of broken parsers - implementers
ju
El Jueves, 27 de Noviembre de 2008, Pandurangan R S escribió:
> I can see that RFC 3261 defines it correctly
>
> uri-parameter = transport-param / user-param / method-param
> / ttl-param / maddr-param / lr-param / other-param
>
>
> lr-param = "lr"
>
> Even other-
>>I think it's a bad specification in RFC 3261. It defines parameters as:
>>
>> ;pname=pvalue
that's not true, the grammar says:
other-param = pname [ "=" pvalue ]
People should (generally) write their parsers from the grammar.
-Original Message-
From: [EMAIL PROTECTED] [ma
I can see that RFC 3261 defines it correctly
uri-parameter = transport-param / user-param / method-param
/ ttl-param / maddr-param / lr-param / other-param
lr-param = "lr"
Even other-param is defined as follows (with optional value parameter)
other-param
El Jueves, 27 de Noviembre de 2008, Attila Sipos escribió:
> I guess it's because just about all other parameters have a value, so
> people wrote their parsers to expect ";some_parameter=some_value" and then
> when they came across ";lr", they thought, "my parser won't like this, so
> I'll just sti
El Jueves, 27 de Noviembre de 2008, Rockson Li (zhengyli) escribió:
> When I first encounter the issue is interworking with openser server,
> which adds lr=on, but I don't know who is the original author of this
> behavior.
No, default behaviour is not adding value to "lr". It's optional:
1.4.1.
I guess it's because just about all other parameters have a value, so people
wrote their parsers to expect ";some_parameter=some_value" and then when they
came across ";lr", they thought, "my parser won't like this, so I'll just stick
a value in there".
Of course, that's pure speculation.
But
On Thu, Nov 27, 2008 at 4:01 AM, Rockson Li (zhengyli)
<[EMAIL PROTECTED]> wrote:
> When I first encounter the issue is interworking with openser server,
> which adds lr=on, but I don't know who is the original author of this
> behavior.
https://lists.cs.columbia.edu/pipermail/sip-implementors/20
15 matches
Mail list logo
