On 01.11.2022 17:12, Conrad de Wet wrote:
This works, except I want to extend this even further. I want these 4
branches to keep trying on a loop until the transaction timeout occurs
or one of the calls is answered. Except I find that the
“failure_route” has two main problems, firstly if I tr
Bogdan,
Ah haa! Found it and fixed it!
Much appreciated for your help... This was a good learning experience!
Next up is PSTN routing and local call routing.
Cheers,
Nitesh
On Tue, Nov 1, 2022 at 10:55 AM Bogdan-Andrei Iancu
wrote:
> Hi Nitesh,
>
> Be sure all the remove_hf() are on the r
Hi All,
I’m trying to work out how to Fork/Branch calls to various contacts.
Firstly, my setup is that I have, let’s say, OpenSIPS-Gateway(os-gw) and
OpenSIPS-Websocket clients (os-ws). Both of these are a load balanced array of
servers. So when a client registers on os-ws he could register on
Hi Nitesh,
Be sure all the remove_hf() are on the right execution path and BEFORE
the t_relay() for the sequential requests.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022, online
https://www.opensips.org/tra
Bogdan,
Thanks for your feedback.
After reading the docs and following this tutorial (
https://opensips.org/Documentation/Tutorials-Topology-Hiding) I finally got
it working. Thank you!
INVITE is clean, topology is hidden and ACK is sent back and forth. Calls
are holding good.
While confirming
We all understood what you are doing and why
It's just that... the answer is inside you! And it's wrong :) (famous quote
from an Italian comedian)
answered from mobile, please pardon terseness and typos,
-giovanni
On Mon, Oct 31, 2022, 20:41 Kevin Kennedy wrote:
> Thank you all for your respon
Thank you all for your responses. Maybe I am going about this all wrong.
Maybe I can explain it better with a drawing of what I am trying to do. I
am trying to front end customers with Opensips to Load balance
Registrations to 4 different SBC's. These SBC's will have their own
Registration cache
Sorry, sent by mistake
continuation of email. DIspatcher module. Is this what you are referring
to? Or are you referring to something else.
-
*alg* - the algorithm(s) used to select the destination address
(variables are accepted).
-
“0” - hash over callid
-
“1” -
I am pretty new to Opensips, so maybe I am not understanding what you mean
by hashing. The only place I see hashing is on the dispatcher module
On Mon, Oct 31, 2022 at 12:44 PM Giovanni Maruzzelli
wrote:
> We all understood what you are doing and why
>
> It's just that... the answer is inside
Hi,
The REGISTERs of used X and the calls to user X will both have the X SIP
URI into the TO URI, so hashing it will give the same value, so the same
destination.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022
10 matches
Mail list logo