Hi,
correct.
Carsten
2012/3/29 Uri Shacked :
> Thanks.
> so, when i do append_branch and t_relay... i will send two invites at once,
> right?
> BR,
> Uri
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:cars...@ng
Thanks.
so, when i do append_branch and t_relay... i will send two invites at once,
right?
BR,
Uri
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listin
Hi,
you need the "append_branch" only, if you modify the request URI in
your config (e.g. by doing a lookup()) and you want to have another
branch (e.g. parallel forking to voicebox).
Carsten
2012/3/28 Uri Shacked :
> OK...
> It worked great... and, no append_branch() was needed... only t_on_bra
OK...
It worked great... and, no append_branch() was needed... only t_on_branch
with the main branch route.
When will i need to use the append_branch?
BR,
Uri
On Wed, Mar 28, 2012 at 4:00 PM, Uri Shacked wrote:
> Hi,
>
> Thanks, this was very helpful for understanding.
>
> Still let’s see if i
Hi,
Thanks, this was very helpful for understanding.
Still let’s see if i got it right:
I get the INVITE.
Do whatever I do on the main route.
Then do:
“append_branch();”
“changes….changes…..;”
Now before the t_relay do t_on_branch(name of branch).
Get the reply (301 in my case)
And from
Hi,
On 03/27/2012 04:46 PM, Uri Shacked wrote:
> In my case i need to change the header and then send it.
>
> Here the case works if i make the changes after i sent the invite and
> got the reply. As i know the t_on_branch will work after the invite is
> sent... am i wrong?
>
> There are many q
Are you searching for examples of serial / parallel forking config found in
the TM module documentation ?
Reda
On Tue, Mar 27, 2012 at 16:55, Carsten Bock wrote:
> Hi Uri,
>
> you're wrong.
> "t_on_branch" works before the request is sent out
> The branches work in the manner, you program
Hi Uri,
you're wrong.
"t_on_branch" works before the request is sent out
The branches work in the manner, you program them in your logic (e.g.
set the timeout for a request, then use failure route for serial
branches). There is no general switch (and i'm not aware of any good
docs regarding th
In my case i need to change the header and then send it.
Here the case works if i make the changes after i sent the invite and got
the reply. As i know the t_on_branch will work after the invite is sent...
am i wrong?
There are many questions to ask about the branches... when do they work in
a se
Hi,
try the following:
route {
# Whatever you do in your main-route
t_on_branch("modify_contact");
# Whatever you do in your main-route, the branch route is
automatically triggered for each branch.
t_relay();
}
branch_route[modify_contact] {
remove_hf("Contact");
append_hf("Conta
On Tue, Mar 27, 2012 at 3:13 PM, Uri Shacked wrote:
> Hi,
>
>
>
> Following the advice I got on the subject “remove_hf" and "append_hf" one
> after the other , twice, issue”, I tried to work with the “append_branch()”
> function.
>
> What I need to do is, after I received the invite from the ori
11 matches
Mail list logo
