Hi
I have a scenario where I need to implement serial forking but each
destination has also a next hop proxy. I can do the forking using
append_branch, but how can I set the destination URI for each branch? In
some cases the R-URI does not change, only the next hop proxy.
Example:
R-URI
Hi Ilie,
You’re asking more of a proxy than it can do. :-) After a call is established,
the initial INVITE transaction is over and the destinations are fixed. That
initial INVITE transaction is the only point at which the proxy can do any kind
of forking.
— Alex
> On Nov 4, 2022, at 8:42
Hello,
I have a challenge here to do serial forking, not when the call is failed
on the first destination, but when the call is ended. So, the first will go
to one destination, will be answered, and when it's ended the BYE message
should be dropped and forward the initial INVITE to another
Hi, thanks for answering. Based on your answer I was able to move the
call sequence to Twilio instead of handling in kamailio, now I send
the INVITE from kamailio to Twilio and in Twilio make a request to my
own API endpoint to create the call sequence and call logs.
thanks
Filippo
I think
I think what you’re asking is: if a call is answered and hung up, can Kamailio
make another call to somewhere else?
If so, the answer is no; proxies just can’t do that. Forking deals with the
management early-stage requests during their pendency. Once a final dispositive
reply for a request
Hi all,
I have a question for my kamailio configuration which works like this:
- INVITE arrives to kamailio
- HTTP async request to API endpoint
- Resume, use of rtjson module for parallel forking and loop to kamailio
itself
- One of the invite is "transformed" in serial forking with rtjson
Hello,
it should be possible to provide only the uri attribute in each of the
serial routes. To URI should not be overwriten in such case. Can you get
the debug messages for such case with debug=3 in kamailio.cfg as well as
the pcap file with the sip traffic?
Cheers,
Daniel
On 10.07.20 17:48,
Hi,
I would like to know if it is possible to use the rtjson module to do serial
forking and at each failure only replacing the R-URI from the initial request?
Have some of you already tried this module in this way?
If so, how should the json body look like? Could I have a body with only
how can I change
this behaviour to do serial forking instead.
-Message d'origine-
De : sr-users De la part de Daniel Tryba
Envoyé : lundi 28 mai 2018 17:13
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Serial forking
On Mon, May 28, 2018 at 04:55:30PM +0200
On Mon, May 28, 2018 at 04:55:30PM +0200, igor.potjevle...@gmail.com wrote:
> I know that the default behaviour of two aliases in kamailio.aliases result
> in parallel forking.
>
> I'm wondering if its possible to do serial forking instead? For example, in
> case that the first INVITE has no
Hello,
I know that the default behaviour of two aliases in kamailio.aliases result
in parallel forking.
I'm wondering if its possible to do serial forking instead? For example, in
case that the first INVITE has no 180/183, or neither 100 Trying, then send
the INVITE to the second entry?
11 matches
Mail list logo
