Greetings,
I thought about that but i wasn't sure it would be safe. But, in this case,
the Request-URI domain will be the only place where Kamailio will look to
find out the destination right within the dialog right? I'm going the
statelless way, so that might be the correct answer.
Thanks for
Have you tried $rd?
On Wed, Aug 01, 2018 at 04:28:38PM +0100, Duarte Rocha wrote:
> Greetings,
>
> I have a Kamailio server set up without Registers. I'm using Dispatcher
> module for balancing and selecting the destinations. I need to do some
> changes in the message according to the chosen
Greetings,
I have a Kamailio server set up without Registers. I'm using Dispatcher
module for balancing and selecting the destinations. I need to do some
changes in the message according to the chosen destination. If it's the
first INVITE, after Dispatcher operations, i can do it using $dd or $du
Hello,
we have a problem of final reply code in case of 302 and then 486 busy.
This is our scenario:
A, B and C are subscribers.
A --> Kamailio --> B
Kamailio <---302 B
Kamailio ---> C
Kamailio
Hi All,
I'm unable to register an extension to the Upstream Provider by using uac
module.
Getting the following error:
*Jul 31 15:49:39 k1-core1 k1[13146]: ERROR: [core/forward.c:181]:
get_out_socket(): no socket found*
*Jul 31 15:49:39 k1-core1 k1[13146]: ERROR: [core/forward.c:183]:
On 7/31/18 1:36 PM, AL S wrote:
Hi,
Is recent kamalio release interoperable in virtual environment?
Depends on the environment of course. I've never had a problem with
VMware systems.
--fred
___
Kamailio (SER) - Users Mailing List
Hello,
first just a question to clarify regarding the ip addresses: you edited the
logs to show 2.2.2.2 and 8.8.8.8 instead of real addresses, right? Just to
be sure as 8.8.8.8 is google DNS server and I have seen in the past some
local caching dns systems returning the dns server ip if the
Out of interest, can you show me the beginning of your route block - just
the part where you call dmq_handle_message()?
Cheers,
Charles
On Wed, 1 Aug 2018 at 18:05, Rogelio Perez wrote:
> Hello,
>
> We had to rollback the changes as dmq_usrloc notifications are not working
> at all with the
Hello,
We had to rollback the changes as dmq_usrloc notifications are not working
at all with the latest master that includes the DMQ patch.
On the receiving node we see the following errors:
(394) INFO:
Hello,
the rule behind next hop address: if $dd is set, then it is the address of
the next hop. If $dd is not set, then it is $rd.
But there is a dedicated variable so you do not need to do the IFs for
above, just use $nh(d).
Cheers,
Daniel
On Wed, Aug 1, 2018 at 6:09 PM, Duarte Rocha
wrote:
Hello Charles,
sorry for late reply, we've had some issues rebuilding docker images with
kamailo nightly build!
We are running on our local, private on premise kubernetes cluster so
connections from outside is simply impossible (in dev we are using a
"closed" network system)
I've just tried to :
Charles, here you go:
### Routing Logic
# Main SIP request routing logic
# - processing of any incoming SIP request starts with this route
# - note: this is the same as route { ... }
request_route {
# per request initial checks
route(REQINIT);
#!ifdef ENABLE_KDMQ
# Handle
12 matches
Mail list logo
