Hello,
indeed, the format was wrong, I just pushed a patch for it in master and
branch 5.0:
-
https://github.com/kamailio/kamailio/commit/0956257ae6fdc0a801ce109017089ac18018e63b
Cheers,
Daniel
On 03.11.17 17:01, Marrold wrote:
> Hi All,
>
> I am currently trying to retrieve the contents of a
If you're trying to modify the contact on your branch I believe you need to
do that in a branch route. For example in branch_route[EVAPIRESPONSE] you
could modify the contact header and. Just make sure to set the branch route
in route[EVAPIRESPONSE].
Then instead of using a var you could use an av
Hi All,
I am currently trying to retrieve the contents of a htable using the
JSONRPC-S module over HTTP, however I have observed if a slot contains
multiple values, the JSON returned has duplicate keys which could be
considered invalid.
Here are the relevant lines from kamailio.cfg -
event_route
Hi john, thanks for your answer. I'm using this in route[EVAPIRESPONSE]
because of async request with evapi.
I tried what you said too with no success.
#$var(first) = 0;
#while ($var(i) < $var(contacts_len)){
# jansson_get("contacts[$var(i)]
Because it determines the proper route based on the method described in the
'mhomed' section of the docs.
Your choices are either to let Kamailio do that, or set mhomed=0 and choose the
egress interface manually based on your own criteria. You can do this by
setting $fs prior to t_relay(), e.g.
Why would it choose a different IP from the one it received on? How do I make
it use the correct ip?
> On 3 Nov 2017, at 15:06, Alex Balashov wrote:
>
> That's probably because the mhomed test, as described in the docs, determines
> that this should be the outbound interface.
>
> On Novemb
Also, to correct a previous statement: it does seem that Kamailio attempts to
resolve the reverse DNS entries of its listeners on boot. That can be disabled
via DNS core configuration parameters. It can also be ignored as it's of no
concern to this scenario.
On November 3, 2017 11:06:57 AM EDT
That's probably because the mhomed test, as described in the docs, determines
that this should be the outbound interface.
On November 3, 2017 10:51:06 AM EDT, Oz Mortimer wrote:
>Ok,
>
>So sort of progress..
>
>With mhomed=0 the calls arrive at the media server from the IP the call
>was sent to
Ok,
So sort of progress..
With mhomed=0 the calls arrive at the media server from the IP the call was
sent to,
With mhomed=1 the calls arrive at the media server from the first registered IP
address regardless of which IP the call was sent to.
So mhomed is doing the reverse of what I would exp
I would not be concerned about superficial errors.
I am more concerned that the system is attempting to "resolve" an IP address.
This would only happen if its format is not deemed to be that if an IP address.
On November 3, 2017 10:38:41 AM EDT, Oz Mortimer wrote:
>nb. I only get
>>> fix_hos
nb. I only get
>> fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
When mhomed=1
> On 3 Nov 2017, at 14:21, Alex Balashov wrote:
>
> Are you sure the IP is correct?
>
> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer wrote:
>> Ok - did that and got the same error, though this t
Yeah 100%
So, I figured it might be something with DNS so I set auto_aliases=no but then
get the following.
Nov 3 14:32:19 IS-56434 kamailio: INFO: [tcp_main.c:4745]: init_tcp():
using epoll_lt as the io watch method (auto detected)
Nov 3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: WARNING:
Hi Daniel,
That warning was written, it was my mistake, i didn't have noticed the
warning msg because of lot activity on logging regarding to number of calls
being processed.
Sorry for the noise :)
Thank you.
Best regards
2017-11-03 14:24 GMT+00:00 Daniel-Constantin Mierla :
> Hello,
>
> in su
Hello,
in such case there should be a warning log messages printed at startup
if the ifdefs number is different than endif ... if it was not written,
then I have to check why ...
Cheers,
Daniel
On 03.11.17 14:54, José Seabra wrote:
> Hi there,
> I found the root cause of the problem reported on
Are you sure the IP is correct?
On November 3, 2017 10:20:17 AM EDT, Oz Mortimer wrote:
>Ok - did that and got the same error, though this time I looked at what
>it was;
>Im /var/log/messages I see -
>Nov 3 14:13:28 IS-56434 kamailio: WARNING:
>[socket_info.c:1392]: fix_hostname(): could not
Ok - did that and got the same error, though this time I looked at what it was;
Im /var/log/messages I see -
Nov 3 14:13:28 IS-56434 kamailio: WARNING: [socket_info.c:1392]:
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov 3 14:13:28 IS-56434 kamailio: WARNING: [socket_info.c:1392]:
On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
> I have listen commented out - which means it listens on all IPs
> (doesn’t it?) - do I need to set them explicitly?
Try setting them explicitly, so that you can route them explicitly.
> I did add mhomed=1 on this setup - but the call
I have listen commented out - which means it listens on all IPs (doesn’t it?) -
do I need to set them explicitly?
I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t
manage to capture quite what was happening).
Thoughts?
> On 3 Nov 2017, at 13:59, Alex Balashov wrote:
Hi,
1. Do you have a listener (listen=) for all necessary IPs and transports?
2. Outbound interface selection is done either via the 'mhomed' option,
https://www.kamailio.org/wiki/cookbooks/5.0.x/core#mhomed
or, if it's not doing what you want, by manually steering it via $fs:
https://www.kam
Hi all,
I have Kamailio set as an SBC with freeswitch behind - that all works fine.
Freeswitch can send calls out VIA Kamailio to external IP address’, but if I
try sending a call to another IP hosted by Kamailio the seems to go nowhere…
Supplier -> Kamailio -> Customer1 -> Kamailio -> Customer
Hi there,
I found the root cause of the problem reported on my last email.
The reason for this problem, was that i had a wrong on #!endif tag, i
wrote #!enif instead of #!endif and the kamailio during the restart
didn't give an error, because i have anothers #!ifdef/#!endif tag.
Regards
2017-1
Hello,
I am planning to create the got branch 5.1 (to be used for v5.1.x
series) by end of next week (likely on Friday, Nov 10, 2017). After
that, the master will be open for new features and fixes will need to be
backported to 5.1.
Should anyone want a different schedule, reply to the mailing li
Ok, thx!
BTW, do you know if it is possible to build the http_async_client rpm on the
openSUSE download server?
The http_client is present, but not the http_async one
Regards
Giovanni
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
_
OK Giovanni,
this is likely to be an issue with the way CURLOPT_CAPATH is set. I'll
submit a fix as soon as possible.
Giacomo
On 3 November 2017 at 09:49, gmele wrote:
> Hello Giacomo,
>
> currently, I don't see these CURL warnings. Here are the logs I get using
> the verbose mode of Curl.
>
>
Hi there,
I'm facing an issue regarding with replies coming to kamailio that aren't
processes inside of onreply_route block.
Anyone here can help me understand why these replies (1XX) aren't entering
on onreply_route bock? is there any situation already identified on
Kamailio that can originate th
Hello Giacomo,
currently, I don't see these CURL warnings. Here are the logs I get using
the verbose mode of Curl.
When it works:
Nov 3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
to pusher-service p
Hello!
Maybe it will be useful for somebody, I applied next configuration and iOS
starts working.
modparam("rtpengine", "write_sdp_pv", "$avp(sdp)")
rtpengine_manage("trust-address replace-origin replace-session-connection
rtcp-mux-offer rtcp-mux-accept media-handover ICE=force RTP/SAVP
Hello,
can you try with latest master? I just pushed a patch that should handle
this case. Let me know if works or not.
Cheers,
Daniel
On 01.11.17 11:57, Aleksandar Sosic wrote:
> Thank you Daniel!
> --
> Aleksandar Sosic
> mail: alex.so...@timenet.it
> skype: alex.sosic
> cell: +385 91 2505 14
Hello Daisy,
One option is to use usrloc with db_mode 3, which will allow you to share the
location table between two registrars using a shared database table. It would
then be possible to do registrar lookup() on one server and determine, by way
of the 'socket' attribute, that the registration
Hi guys.
I'm trying to realize active/active schema with kamailio.
Topology is as following:
active/active kamailio -> routing server (asterisk)
Kamailio servers work as registrar/location servers and sbc.
Asterisk server performs routing functions for calls.
We use sip / sips / ws / wss for sig
Hi Guys
Please forgive me if I seem to asking stupid questions but I am a complete
dummy at the moment regarding this software.
I would love to be able to set up two kamailio servers with the idea of
expansion in the future to handle SIP registrations, however having a two
server model how wou
31 matches
Mail list logo
