Juha Heinanen writes:
> While testing xflags, i noticed that a regular flag that I set AFTER
> calling t_newtrans() stays set in onreply_route even when I do not
> call t_flush_flags().
I made the same test with xflags and they do require t_flush_xflags()
call if an xflag is set after t_newtrans(
### Description
Yealink phones is subscribes using `application/dialog-info+xml`. In this case
for many phones false reported `early` state.
### Troubleshooting
Reproduction
Not knows. Some phones is displayes properly, some is not.
Debugging Data
none
Log Messages
not yet
Daniel-Constantin Mierla writes:
> I pushed a patch for it -- onreply_route was using the xflags from reply
> structure, not from transaction.
Thanks, it works now,
-- Juha
___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https:
I pushed a patch for it -- onreply_route was using the xflags from reply
structure, not from transaction.
Cheers,
Daniel
On 25.03.18 10:02, Juha Heinanen wrote:
> I tested xflags by making these calls in a route block:
>
> INFO(** setting flag 19);
> setflag(19);
> INFO(*
Module: kamailio
Branch: master
Commit: 2af701f0a1df5d3c705f614167c9e815ddcc1708
URL:
https://github.com/kamailio/kamailio/commit/2af701f0a1df5d3c705f614167c9e815ddcc1708
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2018-03-26T09:37:19+02:00
tm: set xflags in priv
