core cookbook reads:
append_branch
Similarly to t_fork_to, it extends destination set by a new entry. The difference is that current URI is taken as new entry.
what is t_fork_to? i could not find it in tm README.
-- juha
On 11/30/2012 02:07 AM, Juha Heinanen wrote:
core cookbook reads:
append_branch
Similarly to t_fork_to, it extends destination set by a new entry. The difference is that current URI is taken as new entry.
what is t_fork_to? i could not find it in tm README.
What's more, it doesn't exist. :-)
sasha@diminuendo-2:~/sip-router/modules/tm$ fgrep -HR t_fork_to . sasha@diminuendo-2:~/sip-router/modules/tm$
The only mention of it in the entire source tree is in obsoleted configs:
sasha@diminuendo-2:~/sip-router$ fgrep -HR t_fork_to . ./etc/obsoleted/to_fox.cfg:# t_fork_to_uri("sip:200@bat.iptel.org:5064"); ./etc/obsoleted/blb.cfg: t_fork_to_uri("sip:200@bat.iptel.org:5064"); ./etc/obsoleted/secondary.cfg:# t_fork_to("001795061546@195.37.77.110"); ./etc/obsoleted/secondary.cfg:# t_fork_to("195.37.77.110", "5060");
In fact, I can't even find it in a tarball of SER 0.9.6:
sasha@higuera:~/Desktop/ser-0.9.6$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/ser-0.9.6$
Nor in a tarball of OpenSER 1.1.1:
sasha@higuera:~/Desktop/openser-1.1.1-notls$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/openser-1.1.1-notls$
Nor in OpenSER 1.2.3:
sasha@higuera:~/Desktop/openser-1.2.3-notls$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/openser-1.2.3-notls$
Whence cometh this t_fork_to()? Is it a ghost? Did it ever exist, anywhere, at all? :-)
The docs have to be updated, the function is no longer in the code (if it actually ever was).
Go ahead and update the wiki. In tm I did some clean up recently, because append_branch was documented there.
Cheers, Daniel
On 11/30/12 8:31 AM, Alex Balashov wrote:
On 11/30/2012 02:07 AM, Juha Heinanen wrote:
core cookbook reads:
append_branch
Similarly to t_fork_to, it extends destination set by a new entry. The difference is that current URI is taken as new entry.
what is t_fork_to? i could not find it in tm README.
What's more, it doesn't exist. :-)
sasha@diminuendo-2:~/sip-router/modules/tm$ fgrep -HR t_fork_to . sasha@diminuendo-2:~/sip-router/modules/tm$
The only mention of it in the entire source tree is in obsoleted configs:
sasha@diminuendo-2:~/sip-router$ fgrep -HR t_fork_to . ./etc/obsoleted/to_fox.cfg:# t_fork_to_uri("sip:200@bat.iptel.org:5064"); ./etc/obsoleted/blb.cfg: t_fork_to_uri("sip:200@bat.iptel.org:5064"); ./etc/obsoleted/secondary.cfg:# t_fork_to("001795061546@195.37.77.110"); ./etc/obsoleted/secondary.cfg:# t_fork_to("195.37.77.110", "5060");
In fact, I can't even find it in a tarball of SER 0.9.6:
sasha@higuera:~/Desktop/ser-0.9.6$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/ser-0.9.6$
Nor in a tarball of OpenSER 1.1.1:
sasha@higuera:~/Desktop/openser-1.1.1-notls$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/openser-1.1.1-notls$
Nor in OpenSER 1.2.3:
sasha@higuera:~/Desktop/openser-1.2.3-notls$ fgrep -HRi to_fork_to . sasha@higuera:~/Desktop/openser-1.2.3-notls$
Whence cometh this t_fork_to()? Is it a ghost? Did it ever exist, anywhere, at all? :-)
-
Alex Balashov -
Daniel-Constantin Mierla -
Juha Heinanen