Works!
I can access location data presents only in the memory. Now, next step
is using $(ulc(contacto=>socket)) to decide which Kamailio have to
process the call.
Thank you
---
I'm SoCIaL, MayBe
El 30/07/2021 a las 11:51 a. m., Henning Westerholt escribió:
Hi,
just quickly looked in the
Works!
I can access location data presents only in the memory. Now, next step
is using $(ulc(contacto=>socket)) to decide which kamailio have to
process the call.
Thank you
---
I'm SoCIaL, MayBe
El 30/07/2021 a las 11:51 a. m., Henning Westerholt escribió:
Hi,
just quickly looked in the
I'll try and report.
Thank you
---
I'm SoCIaL, MayBe
El 30/07/2021 a las 11:51 a. m., Henning Westerholt escribió:
Hi,
just quickly looked in the registrar code, it uses the standard usrloc
functions to get data from memory or database.
Maybe just give it a try, I think it should work
Hi,
just quickly looked in the registrar code, it uses the standard usrloc
functions to get data from memory or database.
Maybe just give it a try, I think it should work also in in-memory/dmq mode.
Cheers,
Henning
From: sr-users On Behalf Of Social Boh
Sent: Friday, July 30, 2021 6:42 PM
Hello,
reg_fetch_contacts use a table (I understood) to looking for data about
a user.
I'm using USRLOC module without database.
Regards
---
I'm SoCIaL, MayBe
El 30/07/2021 a las 11:18 a. m., Henning Westerholt escribió:
Hello,
have you looked to the reg_fetch_contact as already
Hello,
have you looked to the reg_fetch_contact as already pointed out? Then you can
access e.g. the socket with the $ulc PV, see the end of the registrar docs for
an example.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services –
Hello,
maybe is better I explain what I'd like to achieve:
I have two Kamailio using DMQ and DMQ_USRLOC modules so each REGISTER is
replicate on each Kamailio. I'm using DNS weight to distribute the
REGISTERs between the 2 Kamailios.
The only difference I have seen in the location data,
Unfortunately, I faced a different problem after the
"tls_set_connect_server_id()" function was applied.
After Kamailio starts, second trunk is the first one to establish
connection:
*Jul 29 21:25:22 kamailio /usr/sbin/kamailio[2645]: DEBUG:
[core/parser/msg_parser.c:154]: get_hdr_field(): cseq
Hello!
We used sems to interconnect with external operators. But with a heavy call
load and with the processing of the media stream, it often crashed.
Now we use Kamailio / Rtpengine for media stream processing and sems for
signaling processing. We install all this on one server. It probably looks
Hello,
delete the xavps based on the names you set via modparams xavp_dst and
xavp_ctx.
Cheers,
Daniel
On 30.07.21 11:14, Serdar GÜÇLÜER wrote:
> Hello all,
>
> I have a trouble that is related to the way of usage of dispatcher module.
>
> I am working with Kamailio 5.3.2 and using dispatcher
Dear Team,
I would like to know how to link Kamailio with openIMSCore?I would like to use
Kamailio as an Application server.Please guide me or if there is someone who
has worked on this subject, I would like to benefit from his help.
__
Hello all,
I have a trouble that is related to the way of usage of dispatcher module.
I am working with Kamailio 5.3.2 and using dispatcher module as load
balancer to route calls to the media gateways.
My dispatching routes are below as simply,
route[DISPATCH] {
if(ds_select_domain("2",
If you mean, if there is another way appart from doing a lookup() call ... that
depends on what you whant to do ... 'kamctl ul show' it's really a RPC call to
the registar module, but if you store your location information on any DB
backend (redis, mysql, etc.) you could use other modules like
13 matches
Mail list logo