Alex Hermann writes:
> That would work. Just remember to store the value you use somewhere (RR-param
> or $sht) to be able to tear down the session when a BYE comes in.
i don't think that that is necessary. based on my observations, at bye
rtpengine_delete() does the job.
-- juha
On Thursday 28 May 2015, Juha Heinanen wrote:
> The question has been, what value could I assign to extra_id_pv to
> uniquely identify the branch. Since $T_branch_idx exists, perhaps a
> good choice could be $sel(via[1].branch) + $T_branch_idx.
That would work. Just remember to store the value yo
Alex Balashov writes:
> Oh, I see. I would agree with your interpretation of the documentation,
> but that would render such a feature rather useless, since, as you point
> out, this does not expose branch-level control. So, I'm wondering if the
> documentation is perhaps unclear about what it
On 05/28/2015 06:20 AM, Juha Heinanen wrote:
Alex Balashov writes:
There is already something related to the branch in the rtpproxy
function flags, see:
-http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#idp125632
Indeed. As I understand the documentation, this uses the incoming
Alex Balashov writes:
> > There is already something related to the branch in the rtpproxy
> > function flags, see:
> >
> > -http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#idp125632
>
> Indeed. As I understand the documentation, this uses the incoming branch
> ID/Via added by the
On 05/28/2015 06:16 AM, Juha Heinanen wrote:
My understanding from the rtpengine README is that if would use branch
id of the incoming branch in the offers, I could not delete single
failed branches, because rtpengine_delete on the incoming branch id
would delete the whole call.
Oh, I see. I w
Alex Balashov writes:
> Is there a reason you specifically need to identify the next branch,
> rather than operating on the ID of an incoming branch?
Branch id of incoming branch is unique for the whole call. If the call
parallel forks and I call rtpengine_offer for each branch, I need to be
ab
On 05/28/2015 06:00 AM, Juha Heinanen wrote:
the question is if 3 or extra is used, what value can be assigned to
extra_id_pv to uniquely identify the next branch to be created by
t_relay().
Is there a reason you specifically need to identify the next branch,
rather than operating on the ID o
Daniel-Constantin Mierla writes:
> There is already something related to the branch in the rtpproxy
> function flags, see:
>
> - http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#idp125632
rtpproxy flags 1, 2, 3, and b correspond to rtpengine via-branch values
1, 2, auto, and extra.
On 05/28/2015 05:44 AM, Daniel-Constantin Mierla wrote:
There is already something related to the branch in the rtpproxy
function flags, see:
-http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#idp125632
Indeed. As I understand the documentation, this uses the incoming branch
ID/V
There is already something related to the branch in the rtpproxy
function flags, see:
- http://kamailio.org/docs/modules/stable/modules/rtpproxy.html#idp125632
Cheers,
Daniel
On 28/05/15 11:41, Juha Heinanen wrote:
> Alex Balashov writes:
>
>> As far as I know, there is not a way to do this. It
://www.evaristesys.com/, http://www.csrpswitch.com/
Sent from my BlackBerry.
Original Message
From: Juha Heinanen
Sent: Thursday, May 28, 2015 11:41
To: Kamailio (SER) - Users Mailing List
Reply To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] next via branch value
Alex Balashov
Alex Balashov writes:
> As far as I know, there is not a way to do this. It's a limitation
> we've run into before as well, and it probably arises from the fact
> that the branch GUID generator isn't run until t_relay() is called.
Thanks for your reply.
How about the index of the next new via b
As far as I know, there is not a way to do this. It's a limitation we've run
into before as well, and it probably arises from the fact that the branch GUID
generator isn't run until t_relay() is called.
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
At
14 matches
Mail list logo
