24 Sep
2008
24 Sep
'08
10:17 p.m.
Hello Alex,
On 09/24/08 20:11, Alex Balashov wrote:
Hi Daniel,
Kamailio is most definitely not re-enabling the gateway. I will look
into it as you suggest and pass along what I find.
ok
As far as the "algorithm" used by
ds_next_dst()/domain(), why is there
not an algorithm implemented which simply uses the first gateway in the
route set? Why do I have to resort to using an unnumbered algorithm
("X") for that:
Sep 24 13:07:55 [29155] WARNING:dispatcher:ds_select_dst: algo 256 not
implemented - using first entry...
Attempting to relay INVITE from 205.221.123.11 to 212.42.196.8
I don't want any hashing of any headers. And I don't want to use any
hash algorithm which always hashes to one value, because I have no
control over what that single value is.
I would think that using one gateway primarily, with a secondary as a
standby, is a very, very common use case. What is the best way to do
this with dispatcher?
Add a new algorithm as you described, that is very simple, i will have
it it mind.
Cheers,
Daniel
Thanks,
-- Alex
Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
kamailio should automatically enable the gateway.
The mechanism used is
based n internal tm callbacks. If the gateway is not brought back, then
there is something wrong with matching it when reply comes back.
Can you run on debug mode and send the messages along with sip trace?