Using 5.6.x, a scenario designed for a public IP now needs to support life
in the cloud behind NAT. I'd like to avoid having two listeners to separate
on-net from off-net traffic. In a HA scenario, it would be nice to have
only one floating IP.
Is it possible to use the same local address and port for external/public
and internal/private traffic?
Should set_advertised_address() override the listen advertise address?
Initial testing did not produce the expected result. I want to make sure
I'm following a sane pattern before going down a rabbit hole. The idea is
to toggle the advertised address by checking if the sender or recipient
is rfc1918().
For the dispatcher module, is it possible to use socket names like
below? In testing it appeared that only one of the two names was valid.
listen=udp:10.0.0.10:5060 name "onnet"
listen=udp:10.0.0.10:5060 advertise 11.11.11.11:5060 name "offnet"
Hi gang
In 2024, Switzerland will start using NG112 (NG911) procedures to
transmit the caller location via Geolocation URL via LIS Server to a
PSAP.
So time to start testing this on my devel plattform. Kamailio ships
with the lost module which looks promising.
In short, the Procedure is as follows:
Customer calls emergency number.
Kamailio performs a http request to our inhouse HELD server with the
identification of the calling customer.
HELD server looks up the location of the caller and pushes a HELD XML
object to the Swiss LIS Server, which then is queried by the emergency
PSAP receiving the call. LIS server return and URL.
HELD server returns the URL to Kamailio.
Kamailio adds Geolocation Header with that URL and relays the call.
This takes some time and as the call is not yet being relayed while
waiting for the held request to complete, there is no 100 trying being
sent and the emergency call is bound to time out.
So, shall I call t_reply("100","Performing HELD lkup") before
calling the lost module? Or is there a better way?
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
______________________________________________________
I have Kamailio 5.6 on Debian 11.
I need to use the function forward within a routing block in my configuration file:
forward("udp:192.168.28.51:5060");
But when I start the kamailio service I got:
CRITICAL: [core/proxy.c:264]: mk_proxy(): could not resolve hostname: "udp:192.168.28.51:5060"
The same occurs when I use the dns nane :
forward("udp:raspberry3.emtelco.co:5060");
Any ideas ?
Regards
Hi Experts,
I am planning to use *dns_query*() API from the ipops module, which I
understand from some documentation that it internally uses *getaddrinfo*().
I wanted to check if someone can comment on the DNS Cache mechanism in this
case.
* Does Kamailio retain any *dns cache* while using this API, or would it be
actually doing the resolution for each call.
* In light of the above, does Kamailio honour the *TTL value i*n response
to the DNS Query?
Regards,
Harneet Singh
--
"Once you eliminate the impossible, whatever remains, no matter how
improbable, must be the truth" - Sir Arthur Conan Doyle
Hi list
Since updating 5.5 to 5.6 i often see this message in the logs:
ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Duplicate entry 'uloc-645ca178-f29e-1' for key 'location.ruid_idx' (1062)
ERROR: <core> [db_query.c:244]: db_do_insert_cmd(): error while submitting query
ERROR: usrloc [ucontact.c:687]: db_insert_ucontact(): inserting contact in db failed ****** (uloc-645ca178-f29e-1)
ERROR: usrloc [urecord.c:420]: wb_timer(): inserting contact into database failed (aor: *******)
usrloc is dmq synced between two nodes. Were there some changes which
could have caused this issue?
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
______________________________________________________
Kamailio v5.7.0 is out – it comes with 4 new modules and a large
set of improvements touching again more than 60 existing modules.
You can read a bit more detailed release notes at:
* https://www.kamailio.org/w/kamailio-v5-7-0-release-notes/
Many thanks to all developers and community members that made possible
this release.
v5.7.0 brings more flexibility and optimizations across many components,
new variables and transformations, expression-based preprocessor values
and conditions,
alternative TLS module using WolfSSL project, improvements to
STIR/SHAKEN, IMS/VoLTE,
more functions exported to KEMI interface, including a new KEMI Python3
interpreter.
... just to list only a few here. Enjoy Kamailio v5.7.0!
Thank you for flying Kamailio!
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
Hi,
I've encountered a problem using db_redis for location, we recently migrated to redis from mysql and just found out this yesterday.
We are using the usrloc module with db_mode = 2, so the location info is written to redis every 60 seconds. When restarting, Kamailio reads all the contacts and loads them into memory, but for some contacts it loads the “methods” key with an incorrect value.
If in the REGISTER there are no methods kamailio saves it with methods= -1:
{
"jsonrpc": "2.0",
"result": {
"AoR": “zzzzzzz",
"Contacts": [{
"Contact": {
"Address": "sip:1540305477794@W.X.Y.Z:5060",
"Expires": 2752,
"Q": -1,
"Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z",
"CSeq": 11,
"User-Agent": “xxxxxxx",
"Received": "sip:W.X.Y.Z:5060",
"Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>",
"State": "CS_SYNC",
"Flags": 0,
"CFlags": 64,
"Socket": “udp:A.B.C.D:5060",
"Methods": -1,
"Ruid": "uloc-644a176b-6472-4641",
"Instance": "[not set]",
"Reg-Id": 0,
"Server-Id": 0,
"Tcpconn-Id": -1,
"Keepalive": 1,
"Last-Keepalive": 1684246829,
"Last-Modified": 1684246829
}
}]
},
"id": 19286
}
But when restarting kamailio, the same contacts has a methods= 0
{
"jsonrpc": "2.0",
"result": {
"AoR": “zzzzzzz",
"Contacts": [{
"Contact": {
"Address": "sip:1540305477794@W.X.Y.Z:5060",
"Expires": 2697,
"Q": -1,
"Call-ID": "7d3965a85bfd0e88-32357(a)W.X.Y.Z",
"CSeq": 11,
"User-Agent": “xxxxxxx",
"Received": "sip:W.X.Y.Z:5060",
"Path": "<sip:A.B.C.D;lr;received=sip:W.X.Y.Z:5060>",
"State": "CS_SYNC",
"Flags": 0,
"CFlags": 64,
"Socket": “udp:A.B.C.D:5060",
"Methods”: 0,
"Ruid": "uloc-644a176b-6472-4641",
"Instance": "[not set]",
"Reg-Id": 0,
"Server-Id": 0,
"Tcpconn-Id": -1,
"Keepalive": 1,
"Last-Keepalive": 1684246829,
"Last-Modified": 1684246829
}
}]
},
"id": 19286
}
In the schema file for redis the key is correctly set as int and in redis I can see it saved as -1.
So when a call comes in, the lookup() function returns a -2 as it doesn’t support the INVITE method and the call fails.
This is happening in kamailio 5.2.8 and kamailio 5.2.1 (old versions, I know, we are working on updating it); with mysql as a backend it works perfectly after a restart.
We do have the param method_filtering=1 , changing to 0 makes it works. We seem to have this since forever and for what I can see, is not unusual as is in the default kamailio.cfg provided (even the default value for it is 0).
Has anyone else encountered this?
Thanks!
========================================
Koldo Aingeru Marcos Fdez.
Ingeniería de Sistemas
Sarenet S.A.U.
944209470
Parque Tecnológico, Edificio 103
48170 Zamudio, Bizkaia
www.sarenet.es
========================================
Hi,
When I modify INVITEs with set_contact_alias() / add_contact_alias(), this is not preserved in dialog data, and therefore not honoured in BYEs locally generated due to dialog timeout.
For example, if the initial INVITE contained:
Contact: sip:line1@192.168.1.100
and, after transit, became:
Contact: <sip:line1@192.168.1.100>;alias=1.1.1.1~25844~1
There is no ;alias value stored in the caller dialog data, just the original URI + parameters.
A related problem:
I tried to work around this by storing an alias in dialog user variables, e.g.
$dlg_var(alternate_ct) = $_s($si~$sp~$prid)
and in fact, I am able to recover this value later:
event_route[tm:local-request] {
if($dlg_var(alternate_ct) ne $null) {
$ru = $ru + ";alias=" + $dlg_var(alternate_ct);
handle_ruri_alias();
}
}
And in fact, if I print the value of $du after calling handle_ruri_alias(), I can see that it is modified. However, this seems to have no effect on where the request actually goes at the network and transport level. I assume this is because the event_route does not actually allow one to overwrite elements of the spoofed request, and that its essential attributes have been pre-populated elsewhere.
Nevertheless, the effect is that these BYEs do not reach NAT'd endpoints. Any suggestions are appreciated!
Thanks in advance,
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
The header style was wrong for ctl, fixed, thanks.
Daniel
On 15.05.23 18:55, Дилян Палаузов wrote:
> Off-list
>
> Hello,
>
> at
> https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.… there
> is a horizonal line after ctl, which shall not be there.
>
> Greetings
> Дилян
>
>
> На 15 май 2023 г. 7:20:55 UTC, Daniel-Constantin Mierla
> <miconda(a)gmail.com> написа:
>
> Hello, with a few public holidays coming soon around here, I am
> considering to release 5.7.0 this week on Wednesday, May 17, 2023.
> Rather short notice, but there were no major bug reports that need
> to be tracked. The list of new features is being built in the
> wiki: -
> https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.…
> The other tutorials related to this major release should be ready
> by then as well. Should anyone think more time is needed, then it
> can be postponed, not a problem at all. 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