Hello
I have an issue with Rx in my VolTE call Flow. Please refer to picture
and pcap in annex.
I am using same rtp engine at origination and termination.
I am sending rtpmanage for invite and 183 session progress at both
origination and termination.
My issue is that Rx is not sending for the proper media flow component to PCRF.
At origination it is considering a media flow between A 50034 and
RTPEngine 49186 (instead of considering RTP Engine Port 49152)
At Termination it is considering a media flow between B 50054 and
RTPEngine 49132 (instead of considering RTP EnginePort 49170)
Any idea why?
Hi,
I had the intention to route calls to some SRV destinations via
dispatcher and to other SRV destinations via DNS lookup and
'use_dns_failover=on'.
Currently in a route block using dispatcher two out of three targets
within the SRV destination are unavailable (by intention).
During my tests to the dispatcher destination I have found that:
A) If I have 'use_dns_failover=on' this setting "overrules" the
dispatcher routing and the unavailable targets are also tried before DNS
failover finds the available target.
B) If I have 'use_dns_failover=off' the dispatcher routing logic works
as expected and the call is always routed to the only available target
directly, making use of the result of the dispatcher OPTIONS pinging.
--
So my conclusion is now that you have to choose: Either use dispatcher
routing, or use DNS failover based routing.
- I'm fine with this, but I just would like to know if my conclusion is
correct, or if there is actually a way to use dispacther for some SRV
destinations and DNS failover for other SRV destinations.
Regards,
Lars
Hi
CPE registering with TCP (or TLS).
2nd leg is UDP.
Within one transaction (INVITE to OK including all ACK and PRACK)
transport is kept as desired for both legs.
But when the B side disconnects (sending BYE, new reverse transaction),
this is sent via UDP to the A CPE which initially talked TCP and thus
ignored.
record_route() is called on each leg.
What could I be missing?
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Hi,
I’m using kamailio’s silo module to store offline messages in it. I set extra_hdrs modparam to e.g. : ‘Resent-from-silo’ so the clients get information that the message has arrived directly (immediatelly) from the sender or it was stored offline and comes from silo.
So the problem is the following:
* if receiver’s socket is broken (e.g. airplane mode on mobile) and kamailio ‘thinks’ it is registered, server tries to send the message
* message will be timed out and based on config it will be stored in silo.
* the next step is to check if receiver is registered or not (since the client can re-register during 30sec until the message has timed out)
* If client is registered, kamailio tries to send the message immediately with m_dump().
* If the receiver’s connection is still broken, the message will be timed out and store in silo.
* In every store, a new ‘resent’ extra_hdrs value is appended.
When extra_hdrs length reaches 1024 bytes, the m_dump will fail and it blocks the dumping of messages to the given receiver.
Question: can extra_hdrs value be removed before store? Or what can be the solution not to duplicate the extra_hdrs value in some bad network situation?
Peter
(adding sr-users)
Hello,
maybe because you're spelling it wrong? Compare e.g., to here:
https://kamailio.org/docs/tutorials/5.6.x/kamailio-kemi-framework/modules/#…
Cheers,
Henning
-----Original Message-----
From: agural5(a)gmail.com <agural5(a)gmail.com>
Sent: Freitag, 10. März 2023 08:32
To: sr-dev(a)lists.kamailio.org
Subject: [sr-dev] KEMI python 'KSR' has no attribute 'sanity'
Hello,
I am trying to use KEMI KSR.sanity in python but got error: AttributeError: module 'KSR' has no attribute 'sanity'
appreciate your help for solve this.
Thanks!
_______________________________________________
Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-leave(a)lists.kamailio.org
Hello,
please keep the list in the mail flow.
Have you tried to set the acc_function modparam to an empty string, as commented in the linked issue?
modparam("uac_redirect","acc_function","")
If you don't need the acc function from the uac_redirect.
Regarding the other warnings, they should be fixed - but different compilers can report different warnings, so it's sometimes happening. If they are just warnings, they should not create an issue.
If you are using Debian/Ubuntu you can just use the prebuild packages from deb.kamailio.org - you don't need to build by yourself.
Cheers,
Henning
-----Original Message-----
From: Muhammad Danish Moosa <danishmoosa(a)gmail.com>
Sent: Donnerstag, 2. März 2023 14:25
To: Henning Westerholt <hw(a)gilawa.com>
Subject: Re: [SR-Users] Kamailio stops processing the calls - restart fixes it.
Hi,
I tried to install 5.6.4
(https://www.kamailio.org/pub/kamailio/5.6.4/src/) and get this error.
Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: INFO: rr
[rr_mod.c:188]: mod_init(): outbound module not available Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR:
uac_redirect [../../modules/acc/acc_api.h:191]: acc_load_api(): cannot find bind_acc Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR:
uac_redirect [uac_redirect.c:259]: redirect_init(): cannot bind to ACC API Mar 3 00:05:39 lab-danish /usr/local/sbin/kamailio[24642]: ERROR:
<core> [core/sr_module.c:975]: init_mod(): Error while initializing module uac_redirect
(/usr/local/lib64/kamailio/modules/uac_redirect.so)
It seems this issue was reported earlier and supposed to be fixed but apparently it's not.
https://github.com/kamailio/kamailio/issues/3188
Besides that , I had seen warnings during compilation. What should be the most tested and supported version ?
Example Warnings:
dmq_funcs.c: In function ‘ki_dmq_send_message’:
dmq_funcs.c:303:3: warning: missing braces around initializer [-Wmissing-braces]
dmq_peer_t new_peer = {0};
^
dmq_funcs.c:303:3: warning: (near initialization for
‘new_peer.peer_id’) [-Wmissing-braces]
dmq_funcs.c: In function ‘ki_dmq_bcast_message’:
dmq_funcs.c:373:3: warning: missing braces around initializer [-Wmissing-braces]
dmq_peer_t new_peer = {0};
^
dmq_funcs.c:373:3: warning: (near initialization for
‘new_peer.peer_id’) [-Wmissing-braces]
CC (gcc) [M dmq.so] notification_peer.o
CC (gcc) [M dmq.so] dmq.o
dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces] sip_uri_t dmq_server_uri = {0};
On Wed, Mar 1, 2023 at 7:26 PM Henning Westerholt <hw(a)gilawa.com> wrote:
>
> Hello,
>
> better take the latest one, e.g. 5.6.4 released yesterday. Minor releases only contains bugfixes, documentation enhancements and similar. Only rarely regressions happen. But you should of course test it.
>
> Cheers,
>
> Henning
>
> -----Original Message-----
> From: Muhammad Danish Moosa <danishmoosa(a)gmail.com>
> Sent: Mittwoch, 1. März 2023 09:22
> To: Henning Westerholt <hw(a)gilawa.com>
> Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
> Subject: Re: [SR-Users] Kamailio stops processing the calls - restart fixes it.
>
> Thank you for your email.
>
> Is v5.6.1 (July 6, 2022) stable?
>
> obtained from
>
> https://www.kamailio.org/pub/kamailio/latest-stable-version-number
>
>
> On Wed, Mar 1, 2023 at 5:50 PM Henning Westerholt <hw(a)gilawa.com> wrote:
> >
> > Hello,
> >
> > hard to say without more information, a backtrace etc... As I first step, I would suggest you to update the system to one of the supported releases, e.g. the latest 5.6.x or 5.5.x.
> >
> > Cheers,
> >
> > Henning
> >
> > -----Original Message-----
> > From: Muhammad Danish Moosa <danishmoosa(a)gmail.com>
> > Sent: Mittwoch, 1. März 2023 01:39
> > To: sr-users(a)lists.kamailio.org
> > Subject: [SR-Users] Kamailio stops processing the calls - restart fixes it.
> >
> > Hi,
> >
> > I have a very simple proxy (stateful) where kamailio acts as a proxy between 2 endpoints. Everything works fine for weeks and suddenly I see kamailio stops responding. From pcap I can see kamailio is not proxying the session progress and bombarding invites to one endpoint without any reason. Even that invite was stripped on the Body part.
> >
> > Restarting kamailio fixes it immediately. Unfortunately I could not take bt full yet.
> >
> > Version is
> >
> > kamailio 5.5.3 (x86_64/linux) 473cef
> >
> > configuration is very simple , routing is based on tm.t_relay ( based on KEMI).
> >
> > Any help will be welcome.
> >
> > Danish
> >
> >
> >
> > --
> > Muhammad Danish Moosa
> > __________________________________________________________
> > Kamailio - Users Mailing List - Non Commercial Discussions To
> > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
> > Important: keep the mailing list in the recipients, do not reply only to the sender!
> > Edit mailing list options or unsubscribe:
>
>
>
> --
> Muhammad Danish Moosa
>
> " The core of mans' spirit comes from new experiences. "___
> Christopher McCandless
--
Muhammad Danish Moosa
" The core of mans' spirit comes from new experiences. "___ Christopher McCandless
Hello,
I have this error when trying to register this softphone:
https://github.com/InnovateAsterisk/Browser-Phone
61096#015#012Host: sip1.kamailio.xyz:8443#015#012Connection:
Upgrade#015#012Pragma: no-cache#015#012Cache-Control:
no-cache#015#012Upgrade: websocket#015#012Origin:
https://campus.voztovoice.org#015#012Sec-WebSocket-Version:
13#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0
Safari/537.36#015#012Accept-Encoding: gzip, deflate,
br#015#012Accept-Language: es-419,es;q=0.6#015#012sec-gpc:
1#015#012Sec-WebSocket-Key:
uj5cXle8zzBFUzv4kWB2pg==#015#012Sec-WebSocket-Extensions:
permessage-deflate;
client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012>
Mar 9 08:10:55 sip1 /sbin/kamailio[194807]: WARNING: <script>: HTTP
request received on 8443
Mar 9 08:10:55 sip1 /sbin/kamailio[194807]: DEBUG: xhttp
[xhttp_mod.c:426]: xhttp_send_reply(): sending out response: 403 Forbidden
Any help is really apreciated
--
---
I'm SoCIaL, MayBe
Hi List
CPE behind Firewall, registering to Kamailio via TCP (or TLS).
When a call is sent to the CPE, kamailio attemts to open a new TCP
connection and is blocked by Firewall.
Is there an option to tell kamailio to use the existing registered TCP
connection?
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________