Hi,
I am installing kamailio from source on my ubuntu 16.04 server. *How would
i know the default modules installing automatically with kamailio?*
*Also How can i install all modules(if i want to) with kamailio 5.1?*
Thanks,
Prabhat Kumar
Hello list,
I was trying to yum install Kamailio 5.2.1 on a CentOS 7 from the
http://download.opensuse.org/repositories/home:/kamailio:/v5.2.x-rpms/CentO…
repo, but the kamailio-sipcapture-daemon-config can't be installed because
it depends on the kamailio-sipcapture package, which can't be found...
Is anyone aware of that?
Thank you,
Kind regards,
Patrick Wakano
# yum install kamailio-sipcapture-daemon-config
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.optus.net
* epel: mirror.optus.net
* extras: mirror.intergrid.com.au
* updates: mirror.intergrid.com.au
Resolving Dependencies
--> Running transaction check
---> Package kamailio-sipcapture-daemon-config.x86_64 0:5.2.1-1.el7.centos
will be installed
--> Processing Dependency: kamailio-sipcapture = 5.2.1 for package:
kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64
--> Finished Dependency Resolution
Error: Package: kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64
(home_kamailio_v5.2.x-rpms)
Requires: kamailio-sipcapture = 5.2.1
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
# yum deplist kamailio-sipcapture-daemon-config
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.optus.net
* epel: mirror.optus.net
* extras: mirror.intergrid.com.au
* updates: mirror.intergrid.com.au
package: kamailio-sipcapture-daemon-config.x86_64 5.2.1-1.el7.centos
dependency: /bin/sh
provider: bash.x86_64 4.2.46-31.el7
dependency: kamailio-sipcapture = 5.2.1
Unsatisfied dependency
Hello,
Using this event route (see doc)
event_route[topoh:msg-outgoing] {
if($sndto(ip)=="10.1.1.10") {
drop;
}
}
Cause
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X>
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X>
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error
Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2
Kamailio 5.1.7
Hi all,
I’ve a scenario where after lookup() I get multiple branches, and I want to drop some or all of them based on some filter criteria in a branch route before sending requests out. Problem is that if all branches are dropped, kamailio replies with some implicitly generated 500 server error since there are no more branches, but I want to send a 404 or 480 instead.
Is there a way to determine if I’m processing the last active branch (so all others have been dropped already), so I can send a graceful reply like 404 or 480 instead of dropping this last branch as well if I decide I have to filter that one too?
I’m thinking of a hash table table or something to track and decrease the number of branches for a call, and based on a flag (whether one of the previous branches has been sent out or all have been dropped so far) either drop the last branch or reply with an error. However I’m wondering if kamailio comes with a mechanism to determine the branch state out of the box?
Thanks,
Andreas
Hi Guys,
I have recently setup a Kamailio server which can accept SIP or WebSocket
connections but voice is not coming in the case of SIP client.
I have no idea to change avp in the incoming request, please advise how to
proceed.
Hi!
I'm using subst_hf to add some extra info to contact
subst_hf("Contact", "/^(.*)sip:(.*)@(.*)$/\1sip:encei$var(extra_info)-\2@\3/i", "f");
With combination of topos it's giving me strange results like
2(26) WARNING: sanity [sanity.c:282]: check_ruri_scheme(): failed to parse request uri [sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74><sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74]
Seems, it's doubling R-URI on in-dialog requests. If I'm disabling topos - all is ok.
What is interesting - this can't be reproduced with remove_hf/append_hf mechanisms.
Hi,
I have Kamailio 5.1 and I'm using the topology hiding module (topoh)
that is configured as the following:
modparam("topoh", "mask_key", "...")
modparam("topoh", "uparam_name", "....")
modparam("topoh", "uri_prefix_checks", 0)
Unfortunately Fanvil SIP phone modifies the remote party Contact's
URI before it puts it as R-URI in the re-INVITE request.
For example,
The remote party Contact header:
Contact: <sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd>
The re-INVITE request line:
INVITE sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd;user=phone
SIP/2.0
As you can see, ";user=phone" was added. As result of that Kamailio
tries to send the request to 127.0.0.8.
If I disable sending 'user=phone' in Fanvil configuration then
everything works well.
I assumed that if uri_prefix_checks=0 then the topoh module should
take rid of such URI modifications. Am I wrong? Is there any way to
solve the problem except to modify the endpoint configuration?
Best regards,
Leonid Fainshtein
i have followed the guie in
https://kb.asipto.com/kamailio:presence:k43-blf and asterisk are
working (due we connnect the phones directly to asterisk and works)
but when connect the phones to the kamailio the led in phones does not work!
ther's some info missing or what?
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com