Hello,
Kamailio SIP Server project is organizing another meeting of its
developers and community members during November 19-20, 2024 (Tue-Wed),
hosted again by sipgate.de in Dusseldorf, Germany.
The event is intended to facilitate the interaction between Kamailio
developers and contributors in order to offer a convenient environment
for working together on several topics of high interest for the project,
including writing code for Kamailio and its tools, improving
documentation, or discuss about future development.
Everyone from the community is welcome to join, developer or user
interested in helping the project. Please note we have a limited
capacity of seats in the meeting room, the main policy for accepting
participants being first come first server. Also, very important to be
aware that this is not an event to learn how to use Kamailio.
More details about the event, the venue, how to register, are available at:
 * https://www.kamailio.org/w/developers-meeting/
Looking forward to those two intensive hacking Kamailio days in Dusseldorf!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Hello,
After upgraded from kamailio 5.7.5 to 5.7.6, when did start kamailio
process, got the following error:
WARNING: db_mysql [km_my_con.c:179]: db_mysql_new_connection(): opt_ssl_ca
option not supported by mysql version (value (null)) - ignoring
After downgrade to 5.7.5 dind't happened.
(we don't use mysql ssl connection).
I am currently using Kamailio version 5.7.5, which I installed from the source code. I would like to upgrade to version 5.7.6 but have been unable to find documentation specifically addressing minor upgrades between these minor releases.
I have found only wikis detailing the process for upgrading for major releases (like 5.7.x to 5.8.0).
Could you please point me to the documentation for my current need or share with me steps on how to perform this minor upgrade?
Thank you.
Cheers.
modparam("rtpengine", "rtpengine_sock","udp:192.168.1.3:12221=2
udp:192.168.1.1:12222=1 udp:192.168.1.5:12221=7")
When rtpengine_sock is set to multiple rtproxies mode, how to get the id or ip of the
rtpengine used in the current call? There is no information returned which rtpengine
modparam("rtpengine", "rtpengine_sock","udp:192.168.1.3:12221=2 udp:192.168.1.1:12222=1 udp:192.168.1.5:12221=7")
When rtpengine_sock is set to multiple rtproxies mode, how to get the id or ip of the rtpengine used in the current call? There is no information returned which rtpengine kamailio selected for the call.
Hello,
I need help with modifying the "To" header in the "failure_route[ID]{...}". Specifically, I want to add the "to tag" parameter from the previous SIP messages of the current dialog(e.g., 180 Ringing, PRACK or final responses).
Here's the scenario:
1. Kamailio receives and relays the SIP messages: INVITE, 180 Ringing, PRACK, 200 OK, 486 Busy Here.
2. In my case, the 180 Ringing includes the "to tag" parameter.
3. When Kamailio receives the 486 response, it triggers "failure_route[ID]" using "t_on_failure(ID)" method.
4. I extract the SIP response code and reason from the final response of the INVITE transcation in this failure_route.
5. After processing and applying some instructions, I send a reply using "t_send_reply" with the code and reason extracted.
The problem:
- The failure_route[ID] holds the initial INVITE, which has no "to tag" parameter.
- When I send a reply using "t_send_reply()", Kamailio generates a random "to tag" different from the previous SIP messages, which confuses my UAC.
I think adding the "to tag" parameter manually might be a solution, but I'm not sure if I'm doing it correctly or if there is a better approach. I also tried using uac_replace_to() method, but it doesn't work in the failure_route[ID].
How can I make sure the reply in failure_route[ID] uses the correct "to tag" from the previous SIP messages? Are there any other possibilities to achieve this?
Any assistance would be appreciated.
Thank you!
Hello,
Please help. I am using Kemi with the python3 module. I get random
TypeError exceptions thrown within the Kamailio code.
For example I have the following code:
event = str(KSR.pv.get("$hdr(Event)"))
log.logInfo(
"KamailioStateful.ksr_request_route_loopback(): " +
"Passing the request to the presence " +
"publish handler for event: " + event
)
rc = KSR.presence.handle_publish()
if rc != 1:
log.logError(
"KamailioStateful.ksr_request_route_loopback(): " +
"The presence publish handler returned " +
"an error code: " + str(rc)
)
This is what I see in the logs:
21(120) ERROR: PY3 {PUBLISH}: app_python3 [python_support.c:167]:
python_handle_exception(): apy_exec: ksr_request_route((null)): Unhandled
exception in the Python code:
TypeError: expected bytes, str found
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/etc/kamailio/kamailio.py", line 91, in ksr_request_route
return ksf.ksr_request_route(msg, "Loopback")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/etc/kamailio/kamailio_stateful.py", line 100, in ksr_request_route
return self.ksr_request_route_loopback(msg)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/etc/kamailio/kamailio_stateful.py", line 240, in
ksr_request_route_loopback
rc = KSR.presence.handle_publish()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SystemError: <built-in function handle_publish> returned a result with an
exception set
If I put the offending line within a Try/Except it hides it but I would
rather not see it not happen at all. Any Kemi Python3 users experiencing
something similar? What could be causing this?
Regards,
Michel Pelletier