Receiving the following message on the node receiving usr_loc via DMQ, for each
location received:
DEBUG: dmq [worker.c:87]: worker_loop(): dmq_worker [0 54958] lock acquired
DEBUG: dmq_usrloc [usrloc_sync.c:460]: usrloc_dmq_handle_msg(): dmq message
received from sip:usrloc@x.x.x.x
DEBUG:
Just grab it right before the consume_credentials() block, after all the
challenge stuff.
--
Sent from mobile. Apologies for brevity and errors.
-Original Message-
From: David Villasmil
To: "Kamailio (SER) - Users Mailing List"
Sent: Wed, 05 Sep 2018 6:27 PM
Subject: [SR-Users] null
Hello,
in the block:
if (is_method("REGISTER") || from_uri==myself) {
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
auth_challenge("$fd", "0");
exit;
}
# user authenticated - remove auth header
Am Mittwoch, 5. September 2018, 17:43:34 CEST schrieb Karlheinz Knapp:
> we want to use kamailio as a IPv6 to IPv4 proxy.
> IPv4 to IPv4 bridging with NAT works.
>
> If we come from an IPv6 address, the registration packet is send via IPv4
> to the provider.
> He answers with 401 Unauthorized and
Am Dienstag, 4. September 2018, 11:37:43 CEST schrieb Mojtaba:
> I am used topoh module in kamailio, Why this module does not work (No
> change ) in Register request Method?
> I need to change UA' ip address in Via header in Register request
> before forwarded to my network? Does the topoh module
Hello!
Kamilio version 5.1.0
Please tell me why the module dispatcher does not correctly determine the
availability of destination gateways.
The scheme is as follows:
Kamailio (udp:XX.XX.XX.XX:5060) - Provider_1 -> (sip:aa.bb.cc.dd:5060)
Dest GW
Kamailio (udp:YY.YY.YY.YY:5060)
Hi Daniel,
Have got these core dumps. Let me know if I should be doing a bt full. I'll
pastebin and send. Thanks,
Core was generated by `/usr/local/kamailio/sbin/kamailio -P
/var/run/siptrunk.pid -f /usr/local/carrie'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0
Hi,
we want to use kamailio as a IPv6 to IPv4 proxy.
IPv4 to IPv4 bridging with NAT works.
If we come from an IPv6 address, the registration packet is send via IPv4
to the provider.
He answers with 401 Unauthorized and one Via line in the header.
On the IPv6 side was no Via line in the packet.
There is only one branch_route - MANAGE_BRANCH. Same as in default Kamailio
configuration file.
Thank you.
2018-09-05 17:31 GMT+03:00 Vitalii Aleksandrov :
> How many branches do you have? Failure route is called for the whole
> transaction failure and not for every individual failed branch.
>
How many branches do you have? Failure route is called for the whole
transaction failure and not for every individual failed branch.
On 05.09.18 15:03, Володимир Іванець wrote:
Hello everyone,
I wanted to ask those who know if Kamailio's behavior I'm facing is
expected or I should make some
Hi all,
I was looking for a solution to set a dedicated From URI in OPTIONS
requests to a specific dispatcher target.
ds_ping_from (
https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_ping_from)
applies globally, why I needed the granularity of a single target.
Hi All,
I've just started playing with the SCA module and am encountering an
issue whereby SCA cannot seem to find an in-use appearance for the BYE
message.
From my limited understanding of SCA, the module, in this case, appears
to be trying to track the state of the call using callid as
Hello everyone,
I wanted to ask those who know if Kamailio's behavior I'm facing is
expected or I should make some improvements to the configuration. Kamailio
version is 5.1.0.
I have a route where RTPEngine parameters are being collected and
*rtpengine_offer()* is called. After that
Hello,
the backtrace doesn't show any hint about kamailio, only from closelog() up.
It may be the core generated by shutdown procedure, have you enabled one
core file per pid/process? If not, do it and reproduce the issue again,
you may get two core files, one being the runtime issue and the
There is the dlg.terminate_dlg rpc command that requires callid,
from-tag and to-tag as parameters:
*
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg
So it expects something like:
dlg.terminate_dlg
_CALLID_VALUE__
_FROM_TAG_VALUE__
_TO_TAG_VALUE__
I
Hello,
I'm using kamailio 5.1.5 with evapi. I have a node.js connecting with
kamailio evapi to which I send events and also consume events based on
which I do the routing. I have 8 evapi workers defined in the config.
The problem is that kamailio randomly crashes on high load. I'm assuming
that it
Hi all,
I try to used SEMS in this regards, But i have this issue.
https://lists.kamailio.org/pipermail/sr-users/2018-August/102753.html
Any updates?
Thanks
On Tue, Sep 4, 2018 at 2:07 PM Mojtaba wrote:
>
> Hello,
> I am used topoh module in kamailio, Why this module does not work (No
> change )
Yup that's exactly right.
It would be fairly simple to implement an additional XMLRPC format if
there's a particular one that's more friendly towards Kamailio.
Cheers
On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:
Looking quickly at the readme of rtpengine application and digging a
Looking quickly at the readme of rtpengine application and digging a bit
with google, it is something like rtpengine has to be started with
-b http(s)://myrpcserver.ip/path -x 1
and then the xmlrpc request is going to be sent to that url, having a
format like:
teardown
_CALLID_VALUE__
Is
It does an XMLRPC callback. Currently there's two formats for it, one is
a sems sbc teardown request (using the from-tag), the other is a generic
"teardown" command using the call ID.
Cheers
On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:
Hello,
what do you get from rtpengine on rtp
20 matches
Mail list logo
