i'm seeing this for some reason, anyone knows why?
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
On Wed, Jul 9, 2025 at 3:34 PM Mail Delivery Subsystem <
mailer-daemon(a)googlemail.com> wrote:
> [image: Error Icon]
> Delivery incomplete
> There was a temporary problem delivering your message to
> *users(a)lists.openser.org*. Gmail will retry for 21 more hours. You'll be
> notified if the delivery fails permanently.
> The response from the remote …
[View More]server was:
>
> 454 4.7.1 : Relay access denied
>
>
>
> ---------- Forwarded message ----------
> From: David Villasmil <david.villasmil.work(a)gmail.com>
> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>,
> openser users <users(a)lists.openser.org>
> Cc:
> Bcc:
> Date: Mon, 7 Jul 2025 12:44:38 +0200
> Subject: Stir/Shaken
> Hello,
>
> I've seen people wondering how to implement Stir/shaken on Kamailio and
> OpenSIPS. It occurred to me that making a docker image would help a lot of
> people so I did. You can find it in
> https://hub.docker.com/repository/docker/davidcsi/kamailio-stirshaken/gener…
> and in the description you can read how it works and how to use it.
>
> Hope it helps!
>
> David Villasmil
> email: david.villasmil.work(a)gmail.com
>
>
[View Less]
To whom may concert:
Thank you very much for your time reading this e-mail.
I have a config issue when I use kamailio as pcscf. It report the following message when I type ./kamailio -c:
0(1121575) ERROR: <core> [core/pvapi.c:924]: pv_parse_spec2(): error searching pvar "uac_req"
0(1121575) ERROR: <core> [core/pvapi.c:1127]: pv_parse_spec2(): wrong char [m/109] in [$uac_req(method)] at [9 (5)]
I notice that Miconda post at https://github.com/kamailio/kamailio/issues/1123:
[cid:…
[View More]image001.png@01DBEFFE.5BC17BA0]
So I add -DWITH_NATPING to C_DEFS in config.mak,and recompile kamailio, but I still get the same error message showing above.
Here are more information:
kamailio version: 5.5 I download source code from https://github.com/kamailio/kamailio/tree/5.5.0
Comile step:
make cfg include_modules="cdp cdp_avp db_unixodbc ims_dialog ims_ipsec_pcscf ims_qos ims_registrar_pcscf ims_usrloc_pcscf xmlrpc"
make all
config files: from the source code packet: kamailio-5.5.0/misc/examples/ims/pcscf
So I am writing this e-mail for help, thank you very much.
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
[View Less]
Hi, very new to this and trying to add some security for inbound invites. We only want to allow invites from users that are in the registration table, but everything gets a 403, not just an Invite from an unregistered user.
if (KSR.is_INVITE()) {
if (KSR.registrar.lookup("location", KSR.pv.get("$fu") < 0 )) {
KSR.info("Check user registation before passing invite: " + username + KSR.pv.get("$f"));
KSR.sl.send_reply(…
[View More]403, "Forbidden");
KSR.x.exit();
}
}
Any help is appreciated.
[View Less]
Hello,
I've seen people wondering how to implement Stir/shaken on Kamailio and
OpenSIPS. It occurred to me that making a docker image would help a lot of
people so I did. You can find it in
https://hub.docker.com/repository/docker/davidcsi/kamailio-stirshaken/gener…
and in the description you can read how it works and how to use it.
Hope it helps!
David Villasmil
email: david.villasmil.work(a)gmail.com
Over the years I have been slowly writing a node module to help me
write SIP functional/integration tests:
https://github.com/MayamaTakeshi/sip-lab
I have been adding new features as I needed for new kinds of test but
didn't have time to document it.
But now I need to mentor some newcomers to the company I work for
and had to do it.
I asked gemini to do it for me and got:
https://github.com/MayamaTakeshi/sip-lab/blob/master/DOC.md
It might be of help for other people so I am sharing it.
Hi everyone.
I want to start development of an kamailio module. and I am wondering is
the any tutorial about that and also what ide or other setup the other
people use for this. sorry for begginer question and thanks for attention.
Hi,
I'm in the process of updating Kamailio from 5.8.x to 6.0.x, and in my last tests I noticed these error messages in rtpengine log:
WARNING: [3B4A4512-7DA7-439F-97B7-78021488407B]: [core] Unknown dictionary key encountered: 'sip-message-type'
We run rtpengine still with version 10.5.x.x (currently 10.5.6.3), and the update of rtpengine is a bit blocked (mainly because of the removal of iptables support requiring more changes for nftables in the background). I tracked down the changes …
[View More]both in rtpengine and kamailio repository, and with rtpengine 12.x it probably would work, but I'm not there yet.
In this combination, does rtpengine still do what it should do? I did not notice any problems, but before our customers do, I thought I'd rather ask.
Thanks for any advice,
Sebastian
[View Less]
version: kamailio 6.1.0-dev1 (x86_64/linux) 75b73d
loadmodule "microhttpd.so"
modparam("microhttpd", "listen_addr", "0.0.0.0")
modparam("microhttpd", "listen_port", 8364)
event_route[microhttpd:request] {
mhttpd_reply("200", "OK", "","");
}
When using "curl -X POST http://127.0.0.1:8364", a response can be obtained. When using "curl -d '{"test":"2", "test2":"1"}' -H "Content-Type: application/json" -X POST http://127.0.0.1:8364" to pass json data, the kamailio process will be blocked.
Hello everyone,
I have Kamailio set up as a proxy between external clients and an Asterisk server. When traffic comes in over WSS, should Kamailio handle the TLS handshake, or should it be passed through to Asterisk?
Thank you.
My dmq configuration:
loadmodule "dmq_usrloc.so"
modparam("dmq_usrloc", "enable", 1)
modparam("dmq_usrloc", "sync", 1)
modparam("dmq_usrloc", "usrloc_domain", "location_shuidi_online_agent")
modparam("dmq_usrloc", "batch_size", 1000)
modparam("dialog", "enable_dmq", 1)
loadmodule "dmq.so"
# ----- dmq params -----
modparam("dmq", "server_address", DMQ_SIP_URL)
modparam("dmq", "server_socket", DMQ_UDP_URL)
#!ifexp POD_NAME == "kamailio-cti-xyy-0"
modparam("dmq", "notification_address", "sip:…
[View More]kamailio-cti-xyy-1.kamailio-cti-xyy-headless.devops.svc.bedin.bj3:5062")
#!endif
#!ifexp POD_NAME == "kamailio-cti-xyy-1"
modparam("dmq", "notification_address", "sip:kamailio-cti-xyy-0.kamailio-cti-xyy-headless.devops.svc.bedin.bj3:5062")
#!endif
modparam("dmq", "multi_notify", 1)
modparam("dmq", "num_workers", 4)
modparam("dmq", "ping_interval", 15)
Report an error:
NATMANAGE cline: c=IN IP4 10.21.24.151
1(11) WARNING: <core> [core/msg_translator.c:2904]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found
1(11) ERROR: <core> [core/msg_translator.c:2044]: build_req_buf_from_sip_req(): could not create Via header
1(11) ERROR: tm [t_fwd.c:482]: prepare_new_uac(): could not build request
1(11) ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches
1(11) ERROR: sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Message processing error (2/SL)
I think the reason is that the socket field in the location database is copied to another kamailio node and then updated to the database, causing it to be overwritten and empty.
A part of location database table:
user_agent socket methods
SIP.js/0.21.2 5023
SIP.js/0.21.1 5023
SIP.js/0.21.2 5023
SIP.js/0.21.1 5023
SIP.js/0.21.2 5023
please help !!!
I really don't know how to prevent the socket field from being overwritten.
[View Less]
We are fixing the FreeSwitch issue with Contact headers containing ";"
character in the user param.
https://github.com/signalwire/freeswitch/issues/2824
Now required to test other use cases where the user part contains
"&" / "$" / "," / "?" / "/"
Could you provide some examples of SIP messages with these characters in
the user part?
Sergey
Hi there,
I'm new to Kamailio, and maybe this is a silly question.
I’ve set up Kamailio as a SIP proxy with two Asterisk servers acting as
media services.
This is my configuration for the dispatcher module:
loadmodule "dispatcher.so"
modparam("dispatcher", "db_url", DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "ds_ping_interval", 20)
modparam("dispatcher", "ds_ping_method", "OPTIONS")
modparam("dispatcher", "…
[View More]ds_probing_threshold", 5)
modparam("dispatcher", "ds_inactive_threshold", 5)
modparam("dispatcher", "ds_ping_latency_stats", 1)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=488;class=3")
modparam("dispatcher", "ds_ping_from", SIPCALL)
I can see the SIP OPTIONS requests going from Kamailio to Asterisk and
receiving 200 OK responses.
However, the dispatcher is still setting the IP (Inactive Probing) flag on
the servers:
kamcmd dispatcher.list
{
NRSETS: 1
RECORDS: {
SET: {
ID: 1
TARGETS: {
DEST: {
URI: sip:172.16.254.21:5060
FLAGS: IP
PRIORITY: 0
LATENCY: {
AVG: 0
STD: 0
EST: 0
MAX: 0
TIMEOUT: 183
}
}
DEST: {
URI: sip:172.16.254.20:5060
FLAGS: IP
PRIORITY: 0
LATENCY: {
AVG: 0
STD: 0
EST: 0
MAX: 0
TIMEOUT: 183
}
}
}
}
}
}
So when I try to use ds_select_dst("1", "4"), it always fails.
Did I miss something in my configuration?
Thanks!
Regards,
Pablo.
[View Less]
Hi,
we are using kamailio 5.8 with t_suspend to suspend calls until a push notification wakes up the phone.
The phone will then send an NOTIFY with information, so that t_continue can be called.
This works well, but currently we are facing issues with rtpengine, and looking at the logs, there is something suspicious:
we are calling:
t_continue("$sht(vtp=>id_index::$hdr(X-Resume))", "$sht(vtp=>id_label::$hdr(X-Resume))", "RESUME");
...
route[RESUME] {
xdbgl("[RESUME] rm=$rm ru=$ru du=…
[View More]$du \n");
...
after the call to t_continue i can see the log mentioned above:
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} <script>: 486:[RESUME] rm=INVITE ru=sip:<URI_REDACTED>
I wondered why the log call still logs the context as the NOTIFY context and not the INVITE context, and if that might lead to issues?
currently we get problems with rtpengine_manage when we try to call it in the route[RESUME]
Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke
We are currently checking, if we can work around this issue, but i am hoping to getting a bit of insight from you.
Best Regards
JWes
[View Less]
Hello,
Kamailio SIP Server v6.0.2 stable release is out.
This is a maintenance release of the latest stable branch, 6.0, that
includes fixes since the release of v6.0.2. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v6.0.x. Deployments running previous v6.0.x
versions are strongly recommended to be upgraded to v6.0.2.
For more details about version 6.0.2 (including links and guidelines to
download the tarball or …
[View More]from GIT repository), visit:
* https://www.kamailio.org/w/2025/06/kamailio-v6-0-2-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
[View Less]
All,
I've tried searching and have found similar posts before, but I have yet to find a real 'solution'.
I'm running Kamailio 6.0.1 & RTPEngine 13.3.1.7 (on a Linux VM) as a "SBC" (at home) using the config from:
https://github.com/voiceboys/sbcOS/blob/version_2.0/var/www/html/alpine/con…
Except that I've added the following:
mhomed=1
modparam("rr", "force_send_socket", 1)
The SBC is dual-homed: one interface on the local LAN and another interface directly on the Internet/…
[View More]WAN (real public IP).
Everything works fine, EXCEPT if the remote end (the side on the WAN/Internet) hangs up first. If they do, the BYE never makes it past Kamailio to the local PBX and/or phone.
https://users.openser.narkive.com/1aK7n8Il/sr-multihomed-kamailio-and-enabl… suggests to use $sht to save the information needed, but I have no clue where in the config to put that.
Any help would be greatly appreciated.
Thanks!
-Dustin
[View Less]
Hi Timothy,
Have you checked to see there is no firewall blocking traffic?
Regards,
Jonathan
From: Timothy Delin <timothy.delin(a)singtel.com>
Sent: 25 June 2025 05:53
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: Who AmI <myfriendjohn1(a)gmail.com>; Jonathan Aquilina <jaquilina(a)eagleeyet.net>
Subject: RE: [SR-Users] Re: kamailio tls module not loading
Hey Jonathan,
I can confirm that this IP address is only used for the Kamailio TLS …
[View More]listener based on the netstat command.
/usr/src/kamailio # netstat -tuln | grep 5063
tcp 0 0 192.168.254.19:5063 0.0.0.0:* LISTEN
I am not sure if I should have a separate listener and outgoing port for listener.
Best regards,
Timothy
From: Jonathan Aquilina <jaquilina(a)eagleeyet.net<mailto:jaquilina@eagleeyet.net>>
Sent: Wednesday, June 25, 2025 11:41 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>>; Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>>
Subject: RE: [SR-Users] Re: kamailio tls module not loading
[CAUTION: External email] Do not click links or open attachments unless you recognize the sender and know the content is safe.
___
Hi Timothy,
This line is the give all tell all here:
0(1) DEBUG: <core> [core/tcp_main.c:1305]: find_listening_sock_info(): binding to source address 192.168.254.19:5061 failed: [Address in ue] [98]
Address in use im guessing that should say. Can you confirm there are no ip conflicts with another container using the same ip address?
Regards,
Jonathan
From: Timothy Delin via sr-users <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Sent: 25 June 2025 03:40
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>>; Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>>
Subject: [SR-Users] Re: kamailio tls module not loading
Hey John,
Apologies on the late reply, was away for the whole week.
All your questions have been checked and ruled out.
However, I still not able to resolve it. Hence, I decided to approach it differently with manual loadparam
loadmodule "tls.so"
#modparam("tls", "config", "/etc/kamailio/tls/tls.cfg")
modparam("tls", "tls_method", "TLSv1.2+") # Force TLS 1.2+ for all connections
modparam("tls","require_certificate",1)
modparam("tls","verify_certificate",1)
modparam("tls","verify_depth",9)
modparam("tls","certificate","/etc/kamailio/tls/certificate.pem")
modparam("tls","private_key","/etc/kamailio/tls/private_key.pem")
modparam("tls","ca_list","/etc/kamailio/tls/server_cas.pem")
Now it is showing that the TLS connectivity exist, but I know can't let the Kamailio docker run properly and I keep receiving this log message
0(1) DEBUG: <core> [core/tcp_main.c:1305]: find_listening_sock_info(): binding to source address 192.168.254.19:5061 failed: [Address in ue] [98]
0(1) DEBUG: tls [tls_server.c:242]: tls_complete_init(): completing tls connection initialization
0(1) DEBUG: tls [tls_server.c:204]: tls_get_connect_server_name(): xavp with outbound server name not found
0(1) DEBUG: tls [tls_server.c:178]: tls_get_connect_server_id(): xavp with outbound server id not found
0(1) DEBUG: tls [tls_server.c:185]: tls_get_connect_server_id(): outbound server id not set
Just to confirm, does it mean that I cant be using the TLS listen port and output port the same?
Best regards,
Timothy
From: Who AmI <myfriendjohn1(a)gmail.com<mailto:myfriendjohn1@gmail.com>>
Sent: Monday, June 16, 2025 6:31 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: Timothy Delin <timothy.delin(a)singtel.com<mailto:timothy.delin@singtel.com>>
Subject: Re: [SR-Users] kamailio tls module not loading
[CAUTION: External email] Do not click links or open attachments unless you recognize the sender and know the content is safe.
___
Hi there,
A few quick questions just to rule out the simple stuff.
- I don't see it, but I assume you have added "loadmodule "tls.so"" to the cfg?
- In the file: /etc/kamailio/modules/tls.cfg - this points to the path where the certs are - is that path accessible by the kamailio process for read access? (0600 with owner kamailio or 644 with owner root etc)
- Correctly named path and cert name as well in the above file?
Hope this helps.
John.
On Mon, 16 Jun 2025 at 10:30, Timothy Delin via sr-users <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> wrote:
Hi everyone,
I am facing an issue where I cannot load the TLS module in my Kamailio server. I keep receiving this error message
"0(1) ERROR: <core> [core/sr_module.c:529]: ksr_locate_module(): could not find module <tls> in </usr/local/lib64/kamailio/modules>
0(1) CRITICAL: <core> [core/cfg.y:4015]: yyerror_at(): parse error in config file /etc/kamailio/modules/tls.cfg, line 1, column 12-19: failed to load module"
The Kamailio that I run has this configuration
version: kamailio 5.8.6 (x86_64/linux) 6c71d5
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 6c71d5
compiled on 04:12:34 Jun 6 2025 with gcc 12.2.1
-------------------------------------------------------------------
#global.cfg
debug=2
log_stderror=no
memdbg=5
memlog=5
log_facility=LOG_LOCAL0
log_prefix="{$mt $hdr(CSeq) $ci} "
/* number of SIP routing processes */
children=2
/* Defining interfaces */
#!substdef "!PUBLICIP!$env(PUBLICIP)!"
#!substdef "!UDPPORT!$env(UDPPORT)!"
#!substdef "!PUBLIC_UDP_SOCKET!udp:PUBLICIP:UDPPORT!"
/* Need for TLS Support */
#!substdef "!PUBLIC_TLS_SOCKET!TLS:PUBLICIP:5061!"
#!substdef "!COREIP!$env(COREIP)!"
#!substdef "!UDPPORT!$env(UDPPORT)!"
#!substdef "!CORE_UDP_SOCKET!udp:COREIP:UDPPORT!"
#!substdefs "!CORESUBNET!$env(CORESUBNET)!"
/* listen addresses */
listen=PUBLIC_UDP_SOCKET
listen=CORE_UDP_SOCKET
/* Need for TLS Support */
listen=tls:0.0.0.0:5061<https://link.edgepilot.com/s/79616226/8h-IjRzlmUan51PlxuZR2Q?u=http://0.0.0…>
#!substdef "!DBUSERNAME!$env(DBUSERNAME)!"
#!substdef "!DBPASSWORD!$env(DBPASSWORD)!"
#!substdef "!DBHOST!$env(DBHOST)!"
#!substdef "!DBNAME!$env(DBNAME)!"
#!define DBURL "mysql://DBUSERNAME:DBPASSWORD@DBHOST/DBNAME"
#!define HTTP_API_ROUTING_ENDPOINT "https://link.edgepilot.com/s/47dca7bc/8tV4cYQp4UOpnHFQ2B1E6A?u=http://172.1…"
----------------------------------------------------------------
#kamailio.cfg
####### Enable TLS ########
enable_tls=yes
####### Core Modules Section ########
include_file "/etc/kamailio/modules-core.cfg"
####### Global Parameters #########
include_file "/etc/kamailio/globals.cfg"
####### Other Modules Section ########
include_file "/etc/kamailio/modules.cfg"
####### Custom Parameters #########
/* These parameters can be modified runtime via RPC interface
* - see the documentation of 'cfg_rpc' module.
*
* Format: group.id<https://link.edgepilot.com/s/46e1218e/fSZaVF1GX0mM6LO8mQoqWA?u=http://group…> = value 'desc' description
* Access: $sel(cfg_get.group.id<https://link.edgepilot.com/s/c2c005e4/uslHdtRDQE6btKKfMLeGzQ?u=http://cfg_g…>) or @cfg_get.group.id<https://link.edgepilot.com/s/c2c005e4/uslHdtRDQE6btKKfMLeGzQ?u=http://cfg_g…> */
####### Routing Logic ########
include_file "/etc/kamailio/routes.cfg"
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.
[View Less]
Hello,
I am considering to release Kamailio v6.0.2 (out of branch 6.0) on
Wednesday, June 25, 2025. 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 (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Hello all,
Just wondering your opinions on this....
The project I'm in uses a REST API to get the routes to relay the call to,
and one of the main requirements is whenever an egress gateway is down,
inform the REST API about its status, and the same once the gateway is up
again.
So I was reading the modules docs and was stuck with a question: what would
be the best solution to keep track of egress gateways availability?
1 - using Keepalive with DRouting to ping each endpoint's address:port ,
…
[View More]even though the solution is going to use RTJson with the JSON route list
returned from a REST API which makes DRouting virtually useless, unless for
using the list of gateways to send OPTIONS too. There is no event:routes to
execute every time a gateway is down or up....
2 - using Dispatcher module to "watch" for each endpoint's availability,
and make use of the event:route of the Dispatcher module to inform REST API
that the endpoint is down or back up once again. Again, RTJson with the
JSON route list returned from the REST API would be used to manage routing.
I've done a few tests with Dispatcher, and it was really easy to setup the
endpoint "watching" mode as well as the event:routes, but I might give a
try on Keepalive if it is the better bet.
Would greatly appreciate your opinions and expertise on this.
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
[View Less]
Could you look at the attached PCAP with OPTIONS message. When OPTIONS
message is received, then Kamailio generates error logs like
dropping insane message from 10.140.6.38:60083
After checking the PCAP, I see extra %x00 characters after the OPTIONS
message in the same UDP frame.
Example
[image: image.png]
I have checked RFC3261 and do not see a definition of "x00" chars.
Also in the same RFC, present a reference to the RFC2234
<https://datatracker.ietf.org/doc/html/rfc2234> where is …
[View More]described "space
chars", "white space". According to RFC2223, char %x00 cannot be treated as
"space" and should be treated as control (CTL) char.
Also, RFC3261 does not use "CTL" chars.
Using these two RFC, I can conclude, OPTIONS in the attached PCAP breaks
RFC requirements, and we can request partner fix this issue on their
equipment.
Is anything else in the RFC can be used to justify that the given examples
of OPTIONS messages violate RFCs?
Sergey
[View Less]