Hello,
Kamailio SIP Server v5.6.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.6, that
includes fixes since the release of v5.6.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.6.x. Deployments running previous v5.6.x
versions are strongly recommended to be upgraded to v5.6.4.
For more details about version 5.6.4 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2023/02/kamailio-v5-6-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
An additional note to say that call for speakers and registration for
Kamailio World Conference 2023 are now open, more details at:
* https://www.kamailioworld.com
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com
Hello,
We have one Kamailio Instance connected with MS Teams (based on this instruction: https://skalatan.de/en/blog/kamailio-sbc-teams), which worked fine for a while until recently we noticed that calls from teams are not working anymore. When I looked through the logs I found that Microsoft cannot establish a TLS connection to our server because of the cipher:
TLS accept:error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher (sni: sbc.example.com - domain is obfuscated).
Certificate is valid, the configuration is below:
[server:default]
method = TLSv1.2+
verify_certificate = no
require_certificate = no
private_key = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.key
certificate = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.crt
server_name = sbc1-teams.example.net
ca_list = /usr/local/etc/kamailio/certs/sectigo_ca.pem
#ca_list=/etc/ssl/certs/ca-bundle.crt
[client:default]
method = TLSv1.2+
verify_certificate = no
require_certificate = no
private_key = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.key
certificate = /usr/local/etc/kamailio/certs/example.net/sbc1-teams_example_net.crt
ca_list = /usr/local/etc/kamailio/certs/sectigo_ca.pem
#ca_list=/etc/ssl/certs/ca-bundle.crt
We use a certificate from Sectigo, but I've tried with Let's Encrypt - and it's the same. Any idea what could be the reason?
Hello,
I am considering to release Kamailio v5.6.4 (out of branch 5.6) next
week (likely on Monday or Tuesday, Feb 27/28, 2023). If anyone is aware of
issues not yet on the bug tracker, report them there asap in order to
have a better chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com
Dear Kamailio community,
I am a newbie in Kamailio and I am currently working on a project that involves communicating with Kamailio using Python. I have been exploring the Kamailio documentation and I have come across RPC, JSONRPCS..., which I believe can help me achieve my goal.
However, I am not sure about the steps to follow in the Kamailio configuration file to create my own script to communicate with Kamailio using Python (the script is on an other machine on the same LAN). I would be grateful if someone could guide me through the process.
I have already set up Kamailio (builed it from the source code 5.5.5) and Python on my machines and I have basic knowledge of Kamailio configuration. I just need some guidance on how to set up the RPC module in Kamailio and how to create a Python script to communicate with it. I found that I can use RPyC library of python.
I would appreciate any help or suggestions from the Kamailio community. Thank you in advance for your time and assistance.
Best regards,
Wild Coder.
Hi
Sorry for the OT but I think here's the place where I an find a lot of Ms teams
integrations
I've been working on MS teams direct routing integration for PekePBX. It works.
I guess I've done it as everybody else, using Henning's guide as base and
extending it for multitenant setup (thanks Henning!)
What I've realized is that the source IP address of calls coming from MS are
not always matching dispatcher hosts. Sometimes they come from another source
IP and failover to the dispatcher hosts when they receive no response. That
makes some of the calls to have an additional latency
Searching in the MS doc I see that they document these nets as source of their
signaling:
52.112.0.0/14
52.120.0.0/14
But I've seen IP addresses outside of this range as source.
In this blog
https://erwinbierens.com/microsoft-teams-direct-routing-ip-addresses/
The ranges are listed as
52.112.0.0/16
52.113.0.0/16
52.114.0.0/16
52.115.0.0/16
52.120.0.0/16
52.121.0.0/16
52.122.0.0/16
52.123.0.0/16
which looks better but scares me out. Having no auth is it secure to bind so
many ranges to MS?
Do you use anything else than certificate verification for these calls?
cheers,
Jon
--
PekePBX, the multitenant PBX solution
https://pekepbx.com
Hi
Again, fighting with MS Teams but this time it's a kamailio question.
I have MSteams hosts in the dispatcher for OPTIONS and for destination.
Acording to MS you need to try sip.pstnhub.foo then sip2.pstnhub.foo
and sip3.pstnhub.foo
2 | sip:sip.pstnhub.microsoft.com;transport=tls | 0 | 1
2 | sip:sip2.pstnhub.microsoft.com;transport=tls | 0 | 2
2 | sip:sip3.pstnhub.microsoft.com;transport=tls | 0 | 3
I was going to implement dispatcher failover as usual ds_select_domain (alg 8)
with failure routes but checking the SRV of the first domain I see it already
includes 4 hosts:
host -t srv _sips._tcp.sip.pstnhub.microsoft.com_sips._tcp.sip.pstnhub.microsoft.com has SRV record 10 0 5061
sip.pstnhub.microsoft.com.
_sips._tcp.sip.pstnhub.microsoft.com has SRV record 20 0 5061
sip2.pstnhub.microsoft.com.
_sips._tcp.sip.pstnhub.microsoft.com has SRV record 30 0 5061
sip3.pstnhub.microsoft.com.
_sips._tcp.sip.pstnhub.microsoft.com has SRV record 40 0 5061
sip4.pstnhub.microsoft.com.
So... If I have dns srv failover enabled in kamailio... what would be the point
of the dispatcher failover? In case I only want failover in case 408 or 5XX
wouldn't the tm module do it for me?
cheers,
Jon
--
PekePBX, the multitenant PBX solution
https://pekepbx.com
Hello ,
i would like to know if there is a way to change the default 477 response code generated by kamailio in some cases.
for example if kamalio generates 477 because its not able to reach a peer i would like to change it to another code before to forward it.
Thanks.
Hello,
I'd like to start tracking a call history/log as soon as I receive a call.
I'd like the customer to be able to see that there's an incoming call to
one of their numbers in real time.
I'm thinking of using the RABBITMQ Module to manually emit an event from my
main route when I receive an INVITE. Is that a bad idea? What if the broker
isn't located on the same host (latency/availability)? I don't want to
negatively affect the call processing.
I was looking at the Dialog Module and it has three event routes:
* event_route[dialog:start]
* event_route[dialog:end]
* event_route[dialog:failed]
It's really close to what I want, but I'd like to capture the dialog before
it starts (Unconfirmed or Early). Maybe another option is to scan the
Dialog table with an external process and emit events from there.
Has anyone had success in creating a realtime call history? Is there a
better way to go about doing so?
Thanks!
--
Anthony Wittig
Mango Voice Developer
Hello,
a quick note to the community forums to announce that the registration
for the next Kamailio World Conference (June 5-7, 2022, in Berlin,
Germany) is now open! The event returns to an in-person conference
format, at the same wonderful location in the city center of Berlin!
More details are available at:
* https://www.kamailioworld.com/k2023/registration/
Call for presentations is also open, there is already a group of very
interesting submissions, we aim to publish details about them in the
near future.
Looking forward to meeting many of you in Berlin!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com
