sr-users January 2024

sr-users@lists.kamailio.org

49 participants
66 discussions

How to set a branch specific variable?
by Benoit Panizzon 25 Jan '24

25 Jan '24

Hi Gang I would like to set a variable specific to the branch. Is there a way? append_branch($var(aor1)); $(branch(dst_uri)[-1]) = $var($dst1) $(branch(want_plus)[-1]) = 1; append_branch($var(aor2)); $(branch(dst_uri)[-1]) = $var($dst2) $(branch(want_plus)[-1]) = 0; t_on_branch("BR_T"); branch_route[BR_T] { if ($branch(want_plus)) { $rU = "+" + $rU; } } Or would there be a way to query the index of the added branch so I could stack an avp with that index to access in the branch route? 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 ______________________________________________________

1 0

Re: STIR/SHAKEN
by Anthony Wittig 25 Jan '24

25 Jan '24

Hey everyone, I've set it up so that when the invite comes into Kamailio I suspend the transaction (save the transaction info in sht) and use dispatcher to send a request to our NSS server. On the reply from NSS I throw the identity header into a sht and continue the original transaction. Does that seem like the right way to do it? The next things I need to look at are: * if first NSS server doesn't respond quickly, try the second (change some timeouts and use dispatcher to try the backup) * if both NSS servers aren't working, I still want to resume the original call and let it through. Maybe I can keep track of the failures in a sht and if I have two failures, resume the original invite without the identity header. Sound like an ok plan? -- Anthony Wittig Mango Voice Developer > > ---------- Forwarded message ---------- > From: Anthony Wittig <awittig(a)mangovoice.com> > To: sr-users(a)lists.kamailio.org, david.villasmil.work(a)gmail.com > Cc: > Bcc: > Date: Tue, 23 Jan 2024 20:39:09 -0700 > Subject: [SR-Users] STIR/SHAKEN > Thanks! > > This is what I've got so far: > > 1. Kamailio invite -> NSS > 2. NSS 302 -> Kamailio > 3. Kamailio ack -> NSS > > I can see the identity header on the 302 response in my onreply_route. How > can I replay the same invite from step #1 with the identity header I get > back in step #2? Should I be doing something with a transaction on step #1, > maybe start a branch that goes out to NSS and when it comes back resume the > transaction (these are all words I've heard smart people say, but I don't > fully understand them...). > > Any pointers would be greatly appreciated, thanks! > -- > Anthony Wittig > Mango Voice Developer > > ---------- Forwarded message ---------- > From: David Villasmil <david.villasmil.work(a)gmail.com> > To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> > Cc: > Bcc: > Date: Tue, 23 Jan 2024 14:56:52 +0100 > Subject: [SR-Users] Re: STIR/SHAKEN > Ditto, i do first approach. > > Regards, > > David Villasmil > email: david.villasmil.work(a)gmail.com > phone: +34669448337 > > > On Tue, Jan 23, 2024 at 2:38 PM Alex Balashov via sr-users < > sr-users(a)lists.kamailio.org> wrote: > >> These are all valid approaches, depending on preference. Catching 302s >> and extracting exactly the desired info might be easier with Kamailio, so I >> suppose, ceteris paribus, I'd recommend the first one. >> >> Dispatcher is a great approach! >> >> > On 23 Jan 2024, at 00:01, Anthony Wittig via sr-users < >> sr-users(a)lists.kamailio.org> wrote: >> > >> > Hello, >> > >> > We're attempting to add identities to our invites. I believe we want to >> send our invites to the NSS, and it'll reply with a 302'd invite with an >> identity header. We currently use FreeSWITCH for dialplans and media and >> Kamailio as our SBC. >> > >> > Should we be trying for something like: FreeSWITCH -> Kamailio -> NSS >> (302) -> Kamailio -> PSTN >> > >> > or would it make more sense to do: FreeSWITCH -> NSS (302) -> >> FreeSWITCH -> Kamailio -> PSTN >> > >> > Assuming we wanted Kamailio -> NSS, is using dispatcher the right >> approach? We currently use it for our two Kamailios and our FreeSWITCHs. >> We're going to have two NSS servers, one for failover. >> > >> > Any thoughts would be greatly appreciated, thanks! >> > >> > -- >> > Anthony Wittig >> > Mango Voice Developer >> > __________________________________________________________ >> > 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: >> >> -- >> Alex Balashov >> Principal Consultant >> Evariste Systems LLC >> Web: https://evaristesys.com >> Tel: +1-706-510-6800 >> >

1 0

STIR/SHAKEN
by Anthony Wittig 24 Jan '24

24 Jan '24

Thanks! This is what I've got so far: 1. Kamailio invite -> NSS 2. NSS 302 -> Kamailio 3. Kamailio ack -> NSS I can see the identity header on the 302 response in my onreply_route. How can I replay the same invite from step #1 with the identity header I get back in step #2? Should I be doing something with a transaction on step #1, maybe start a branch that goes out to NSS and when it comes back resume the transaction (these are all words I've heard smart people say, but I don't fully understand them...). Any pointers would be greatly appreciated, thanks! -- Anthony Wittig Mango Voice Developer ---------- Forwarded message ---------- From: David Villasmil <david.villasmil.work(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Cc: Bcc: Date: Tue, 23 Jan 2024 14:56:52 +0100 Subject: [SR-Users] Re: STIR/SHAKEN Ditto, i do first approach. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 On Tue, Jan 23, 2024 at 2:38 PM Alex Balashov via sr-users < sr-users(a)lists.kamailio.org> wrote: > These are all valid approaches, depending on preference. Catching 302s and > extracting exactly the desired info might be easier with Kamailio, so I > suppose, ceteris paribus, I'd recommend the first one. > > Dispatcher is a great approach! > > > On 23 Jan 2024, at 00:01, Anthony Wittig via sr-users < > sr-users(a)lists.kamailio.org> wrote: > > > > Hello, > > > > We're attempting to add identities to our invites. I believe we want to > send our invites to the NSS, and it'll reply with a 302'd invite with an > identity header. We currently use FreeSWITCH for dialplans and media and > Kamailio as our SBC. > > > > Should we be trying for something like: FreeSWITCH -> Kamailio -> NSS > (302) -> Kamailio -> PSTN > > > > or would it make more sense to do: FreeSWITCH -> NSS (302) -> FreeSWITCH > -> Kamailio -> PSTN > > > > Assuming we wanted Kamailio -> NSS, is using dispatcher the right > approach? We currently use it for our two Kamailios and our FreeSWITCHs. > We're going to have two NSS servers, one for failover. > > > > Any thoughts would be greatly appreciated, thanks! > > > > -- > > Anthony Wittig > > Mango Voice Developer > > __________________________________________________________ > > 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: > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com > Tel: +1-706-510-6800 > > __________________________________________________________ > 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: >

1 0

STIR/SHAKEN
by Anthony Wittig 23 Jan '24

23 Jan '24

Hello, We're attempting to add identities to our invites. I believe we want to send our invites to the NSS, and it'll reply with a 302'd invite with an identity header. We currently use FreeSWITCH for dialplans and media and Kamailio as our SBC. Should we be trying for something like: FreeSWITCH -> Kamailio -> NSS (302) -> Kamailio -> PSTN or would it make more sense to do: FreeSWITCH -> NSS (302) -> FreeSWITCH -> Kamailio -> PSTN Assuming we wanted Kamailio -> NSS, is using dispatcher the right approach? We currently use it for our two Kamailios and our FreeSWITCHs. We're going to have two NSS servers, one for failover. Any thoughts would be greatly appreciated, thanks! -- Anthony Wittig Mango Voice Developer

3 3

How to check for branches with a pending reply in MANAGE_REPLY to correctly handle rtpengine?
by Benoit Panizzon 23 Jan '24

23 Jan '24

Hi gang location database contains multiple contacts for an AOR The invite therefore is parallel branched to those multiple contacts. Each reply from each branch is handled by MANAGE_REPLY. rtpengine_manage() is called in MANAGE_REPLY to stop rtpengine processing a failed call. Unfortunately, if any of the contacts replies with an error rtpengine_manage() will stop RTP processing. Is there a way I could check if there are branches with a pending reply from within MANAGE_REPLY so I could call rtpengine_manage() only when the last reply (no pending replies) are present? Hmm, realizing, if I process the last pending error reply and a prior one got a positive reply, this would still kill media. => How do I solve this? 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 ______________________________________________________

1 0

Info: Kamailio World 2024 - Call for presentations
by Daniel-Constantin Mierla 22 Jan '24

22 Jan '24

Hello, a short note to inform that the Call For Presentations is now open for Kamailio World 2024. Everyone is welcome to submit proposal for presentations to share the knowledge about Kamailio or Real Time Communication services, security, high availability, scalability, etc. Submission form and more details are available at: - https://www.kamailioworld.com/k2024/call-for-speakers/ Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

2 2

IMS registration failure
by srinidhikrs＠yahoo.com 21 Jan '24

21 Jan '24

I am trying to get imsdroid register to pcscf . But failing with 504 server timeout . Please help to figure out the reason for register failure . <is_registered_fallback2ip> in module ims_registrar_pcscf [/usr/local/lib64/kamailio/modules/ims_registrar_pcscf.so] [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <is_registered_fallback2ip> in module ims_registrar_pcscf [/usr/local/lib64/kamailio/modules/ims_registrar_pcscf.so] [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/sr_module.c:632]: find_mod_export_record(): found export of <pcscf_unregister> in module ims_registrar_pcscf [/usr/local/lib64/kamailio/modules/ims_registrar_pcscf.so] [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg.lex:1643]: sr_push_yy_state(): including file: route/register.cfg (/etc/kamailio_pcscf/route/register.cfg) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/sr_module.c:632]: find_mod_export_record(): found export of <pcscf_is_registered> in module ims_registrar_pcscf [/usr/local/lib64/kamailio/modules/ims_registrar_pcscf.so] [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'core' (num=56, size=224) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'tcp' (num=27, size=108) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 0 (old) + 1 (new) = 1 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'tm' (num=36, size=168) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'maxfwd' (num=1, size=4) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'siputils' (num=1, size=4) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 1 (old) + 1 (new) = 2 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'xlog' (num=1, size=4) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'dispatcher' (num=3, size=24) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'sctp' (num=19, size=76) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 2 (old) + 1 (new) = 3 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'dbg' (num=3, size=12) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'registrar' (num=11, size=56) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/cfg/cfg.c:173]: cfg_declare(): new config group has been registered: 'rtpengine' (num=5, size=20) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 3 (old) + 1 (new) = 4 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 4 (old) + 1 (new) = 5 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:138]: register_procs(): registering new processes: 5 (old) + 1 (new) = 6 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/pt.c:99]: init_pt(): registering new processes: 6 (old) + 96 (new) = 102 (total) [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/route.c:885]: fix_actions(): fixing pcscf_is_registered() [0;39;49m[0;39;49m 0(310120) DEBUG: <core> [core/route.c:885]: fix_actions(): fixing pcscf_unregister() [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=9 a=16 n=if [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=7 a=63 n=assign [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=9 a=25 n=xnotice [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=10 a=25 n=xnotice [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=11 a=25 n=xnotice [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=12 a=25 n=xnotice [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=15 a=63 n=assign [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=22 a=16 n=if [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=17 a=25 n=is_present_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=18 a=25 n=pcscf_save_pending [0;39;49m[0;39;49m 4(310124) DEBUG: ims_registrar_pcscf [save.c:378]: save_pending(): registering for UL callback [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=25 a=63 n=assign [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=32 a=16 n=if [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=35 a=16 n=if [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=33 a=63 n=assign [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=81 a=25 n=append_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=83 a=25 n=remove_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=84 a=25 n=append_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=85 a=25 n=remove_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=86 a=25 n=append_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=94 a=16 n=if [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=89 a=25 n=is_present_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=93 a=25 n=append_hf [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=107 a=25 n=t_on_failure [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=109 a=25 n=t_on_reply [0;39;49m[0;31;49m 4(310124) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=111 a=5 n=route [0;39;49m[0;31;49m85(310272) ERROR: *** cfgtrace:failure_route=[REGISTER_failure] c=[/etc/kamailio_pcscf/route/register.cfg] l=316 a=16 n=if [0;39;49m[0;31;49m85(310272) ERROR: *** cfgtrace:failure_route=[REGISTER_failure] c=[/etc/kamailio_pcscf/route/register.cfg] l=311 a=25 n=t_check_status [0;39;49m[0;31;49m85(310272) ERROR: *** cfgtrace:failure_route=[REGISTER_failure] c=[/etc/kamailio_pcscf/route/register.cfg] l=312 a=26 n=send_reply [0;39;49m[0;31;49m85(310272) ERROR: *** cfgtrace:failure_route=[REGISTER_failure] c=[/etc/kamailio_pcscf/route/register.cfg] l=313 a=26 n=update_stat [0;39;49m[0;31;49m85(310272) ERROR: *** cfgtrace:failure_route=[REGISTER_failure] c=[/etc/kamailio_pcscf/route/register.cfg] l=314 a=2 n=exit

1 2

failed to open database connection
by mtohidi67＠gmail.com 20 Jan '24

20 Jan '24

Hello. I have installed Kamailio version devel on Ubuntu 22.04 and use the mysql database on the same machine. when i run systemctl status kamailio.service ● kamailio.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio; generated) Active: active (exited) since Sat 2024-01-20 11:35:09 +0330; 21min ago Docs: man:systemd-sysv-generator(8) CPU: 48ms /usr/local/sbin/kamailio[173481]: ERROR: usrloc [dlist.c:846]: register_udomain(): failed to open database connection /usr/local/sbin/kamailio[173481]: ERROR: registrar [registrar.c:767]: domain_fixup(): failed to register domain /usr/local/sbin/kamailio[173481]: ERROR: [core/route.c:1193]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio/kamailio.cfg:717 /usr/local/sbin/kamailio[173481]: ERROR: [core/rvalue.c:3818]: fix_rval_expr(): failure in cfg at line: 717 col: 22 /usr/local/sbin/kamailio[173481]: ERROR: [core/rvalue.c:3818]: fix_rval_expr(): failure in cfg at line: 717 col: 22 /usr/local/sbin/kamailio[173481]: ERROR: [core/route.c:1193]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio/kamailio.cfg:720 /usr/local/sbin/kamailio[173481]: INFO: [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized kamailio[173463]: * already running kamailio[173463]: ...done. systemd[1]: Started LSB: Start the Kamailio SIP proxy server. In /usr/local/etc/kamailio/kamctlrc, I uncomment these lines: SIP_DOMAIN=ims.mnc55.mcc999.farazNET.org DBENGINE=MYSQL DBHOST=localhost in /usr/local/etc/kamailio/kamailio.cfg i apply this changes: auto_aliases=no alias="ims.mnc55.mcc999.farazNET.org" listen=udp:192.168.75.185:5060 listen=tcp:192.168.75.185:5060 how can i solved it?

1 1

rr, loose_route and corex alias_subdomains
by Jon Bonilla (Manwe) 19 Jan '24

19 Jan '24

Hi I'm having an issue with the double rr for mst direct routing. I'm using subdomains like 23234.mydomain.com with a wildcard certificate and I set corex modparam alias_subdomains to mydomain.com But loose_route doesn't seem to detect the rr as myself I get the message: rr [loose.c:804]: rr_do_force_send_socket(): no socket found to match second RR (sip:20141.mydomain.com:5063;transport=tls;ftag=as7107d0fe;lr;r2=on;vsf=AAAAAAAAAAADCQMaABhMS1NYRh0cRllbR0RRQG91cC5lcw--;nat=yes;pet=mst) Regarding my setup is more or less like this: kamailio.local.cfg: #!substdef "!MSTDOMAIN!mydomain.com!g" kamailio.cfg: modparam("corex", "alias_subdomains", "MSTDOMAIN") But in the cli: kamctl rpc corex.list_aliases { "jsonrpc": "2.0", "result": [ ], "id": 1319303 } I don't remember to have this issue when I was developing the mst integration. Either I missed it or can it be a regression? kamailio version is 5.6.4 at the moment. Any ideas? cheers Jon -- PekePBX, the multitenant PBX solution https://pekepbx.com

2 3

Just need some basic help
by Jere Cassidy 18 Jan '24

18 Jan '24

Hello! Thanks in advance for any help you can provide. I have a simple setup here and am struggling a bit with getting a final working solution. This is just a single direction flow from a SIP provider inbound to servers running HMPelements with CTI integration (sip endpoint). Essentially a different DN / dial number would go to a different backend server. There is no registration involved. The kamailio server therefore needs to sit between the SIP provider and the backend servers, it will be a NAT situation where private RFC1918 addresses will be used on the backend after the server receives it with public IP information. So that's it. What is the simplest way to accomplish this? If it would help - here's what ive done so far: For the Kamailio server, I have an AWS EC2 instance with a public IP bound/assigned to the main private IP. During troubleshooting, I've added another private IP to the NIC so that I could throw up another listener. I was thinking I'd need to accept the SIP on the first listener with the "advertise" directive. The second listener would not have an advertise directive so perhaps could be used to talk to the backends. I defined the WITH NAT and rtp proxy settings (pointing to the first listener below). The RTP Proxy daemon also knows about the y.y.y.y public address below. In the kamailio.cfg, I have a listener setup : listen=udp:172.24.40.28:5060 advertise y.y.y.y:5060 listen=udp:172.24.40.26:5060 then threw in a route(CMS) in the request route and created the following route block: route[CMS] { #check URI matches phone xxxxxxxxxx if (uri=~"^sip:\+1xxxxxxxxxx@") { rewritehostport("10.12.18.193:5060"); forward(uri:host, uri:port); exit; }; } I get the SIP delivered to the backend host! but the INVITE headers are stil pointing to public IPs and the SDP info is not adjusted to be a private IP as well - as follows: z.z.z.z = sip provider , y.y.y.y = public ip (aws ec2 ip). xxxxxxxxx = calling phone, ######## = called phone (matches routeCMS above) INVITE sip:+1##########@10.12.18.193:5060 SIP/2.0 Record-Route: <sip:y.y.y.y;lr> Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK28b7.56b42fdeec9f10cd13030b3711b16f4d.0 Via: SIP/2.0/UDP z.z.z.z:11000;received=z.z.z.z;rport=11000;branch=z9hG4bKQ2yQKgv7NtKQF Max-Forwards: 48 From: "" <sip:+1xxxxxxxxxx@z.z.z.z;isup-oli=0>;tag=tUF15gaNg6N6j To: <sip:+1##########@y.y.y.y> Call-ID: 9ee7e073-c7fc-46ac-a839-f3c77eaed903 CSeq: 78244364 INVITE Contact: <sip:mod_sofia@z.z.z.z:11000> User-Agent: 2600Hz Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY Supported: path, replaces Allow-Events: talk, hold, conference, refer Privacy: none Content-Type: application/sdp Content-Disposition: session Content-Length: 278 X-FS-Core-UUID: 4e0b2928-d913-42c4-9809-f77a36d281be X-FS-Support: update_display,send_info P-Asserted-Identity: "" <sip:+1xxxxxxxxx@z.z.z.z> v=0 o=FreeSWITCH 1705572686 1705572687 IN IP4 z.z.z.z Thanks much!

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2024