On 11/22/2015 05:50 AM, Juha Heinanen wrote:
Richard Fuchs writes:
Yes, one of the two usual call timers. Off the top of my head I believe
the longer ("silenced") timer is the relevant one here.
Just for curiosity, I tried to find out from the sources, how long that
SILENT timer is, but didn'
Richard Fuchs writes:
> Yes, one of the two usual call timers. Off the top of my head I believe
> the longer ("silenced") timer is the relevant one here.
Just for curiosity, I tried to find out from the sources, how long that
SILENT timer is, but didn't succeed.
-- Juha
___
On 11/19/2015 05:58 PM, Juha Heinanen wrote:
Richard Fuchs writes:
if via-branch=extra is used in offers of branched, should it also be
used in answers and deletes?
Yes it should, as rtpengine uses the via-branch to match the answers to
the offers which didn't have a to-tag. Looking at the so
Richard Fuchs writes:
> > if via-branch=extra is used in offers of branched, should it also be
> > used in answers and deletes?
>
> Yes it should, as rtpengine uses the via-branch to match the answers to
> the offers which didn't have a to-tag. Looking at the sources, the same
> logic appears t
On 11/18/2015 08:47 AM, Juha Heinanen wrote:
rtpengine readme tells:
via-branch=... - Include the “branch” value of one of the “Via” headers
in the request to the RTP proxy. Possible values are: “1” - use the
first “Via” header; “2” - use the second “Via” header; “auto” - use the
fir
Juha Heinanen writes:
> via-branch=... - Include the “branch” value of one of the “Via” headers
> in the request to the RTP proxy. Possible values are: “1” - use the
> first “Via” header; “2” - use the second “Via” header; “auto” - use the
> first “Via” header if this is a request, or the
rtpengine readme tells:
via-branch=... - Include the “branch” value of one of the “Via” headers
in the request to the RTP proxy. Possible values are: “1” - use the
first “Via” header; “2” - use the second “Via” header; “auto” - use the
first “Via” header if this is a request, or the second
