Hello,
only several algorithms are suitable for full stateless usage, I am
mainly referring to those doing hashes over attributes of the sip
message (like hash over call id).
For the other you would need to use tm module and t_relay(). That will
make it easy for you.
Otherwise, you can use
Hi Daniel,
Yes I am using forward() because I thought it would be the fastest solution.
I guess I was lead on by the dispatcher documentation saying it can be used
statelessly, so I tried to do the whole route script stateless.
However, I've recently been looking at t_relay and in particular
t_ch
Hello,
by stateless dispatcher do you mean using forward() to send out the INVITE?
Cheers,
Daniel
On 11/28/12 1:40 PM, SIP Mailing-list wrote:
Further edit:
Actually I tried using ds_select_dst to forward the ACK on the
unconfirmed (unanswered; 603 Decline) call but it routed to another
des
Further edit:
Actually I tried using ds_select_dst to forward the ACK on the unconfirmed
(unanswered; 603 Decline) call but it routed to another destination.
My work-around involves using ds_next_dst to send the ACK to *all*
destinations.
Does anyone know if there is a way to fix this behaviour?
Hi guys,
I wonder if someone could sanity check something for me.
I currently have a simple load balancer set up using algorithm 10 (call
load distribution) from the dispatcher module. I'm using Record-Routing so
that I can clear down the call load record at the end of the call.
Everything looked
