The logs indicated that the sip request type is not advertised as
supported by the contact.
You should upgrade to latest 5.3.x version, iirc there was a commit
fixing the read of methods fields from the rpc command, or just set:
modparam("registrar", "method_filtering", 0)
in kamailio.cfg
Cheers,
Daniel
On 30.07.20 19:01, Igor Potjevlesh wrote:
>
> The most relevant logs are:
>
> ERROR: *** cfgtrace:request_route=[INVITE]
> c=[/usr/local/etc/kamailio/kamailio.cfg] l=988 a=25 n=lookup -> which
> is the line where I do lookup("aliases")
>
> DEBUG: registrar [lookup.c:313]: lookup_helper(): contact for
> [0123456789] cannot handle the SIP method
>
> DEBUG: registrar [lookup.c:321]: lookup_helper(): '0123456789' has no
> valid contact in usrloc
>
>
>
> So a record is found.
>
>
>
> And if I restart Kamailio, alias is retrieve from db at startup and
> it's working.
>
>
>
> Regards,
>
>
>
> Igor.
>
>
>
> *De :*Daniel-Constantin Mierla <[email protected]>
> *Envoyé :* jeudi 30 juillet 2020 18:11
> *À :* Igor Potjevlesh <[email protected]>; 'Kamailio (SER) -
> Users Mailing List' <[email protected]>
> *Objet :* Re: [SR-Users] Issue with kamctl after upgrading to 5.3.4
>
>
>
> From 4.3 to 5.3 is quite some jump, hard to remember what could be the
> relevant changes for alias lookup.
>
> But if you see the record present in the rpc command, then lookup
> should work. Run with debug=3 in kamailio.cfg and see the debug
> messages when lookup("aliases") is executed.
>
> Cheers,
> Daniel
>
> On 30.07.20 15:07, Igor Potjevlesh wrote:
>
> From the kamcmd ul.lookup tool aliaa seems to be present:
>
>
>
> kamcmd> ul.lookup aliases [email protected]
> <mailto:[email protected]>
>
> {
>
> AoR: 0762350002
>
> Contacts: {
>
> Contact: {
>
> Address: sip:012345678@host_1.local
>
> Expires: permanent
>
> Q: 0.000000
>
> Call-ID: [email protected]
> <mailto:[email protected]>
>
> CSeq: 1
>
> User-Agent: kamailio SIP Router - RPC Server
>
> Received: [not set]
>
> Path: [not set]
>
> State: CS_SYNC
>
> Flags: 0
>
> CFlags: 0
>
> Socket: [not set]
>
> Methods: -2147483648
>
> Ruid: ulcx-5f22a37b-654b-1
>
> Instance: [not set]
>
> Reg-Id: 0
>
> Server-Id: 0
>
> Tcpconn-Id: 0
>
> Keepalive: 0
>
> Last-Keepalive: 0
>
> Last-Modified: 0
>
> }
>
> }
>
> }
>
> kamcmd>
>
>
>
> *De :* Igor Potjevlesh <[email protected]>
> <mailto:[email protected]>
> *Envoyé :* jeudi 30 juillet 2020 14:56
> *À :* [email protected] <mailto:[email protected]>; 'Kamailio
> (SER) - Users Mailing List' <[email protected]>
> <mailto:[email protected]>
> *Objet :* RE: [SR-Users] Issue with kamctl after upgrading to 5.3.4
>
>
>
> Hello,
>
>
>
> I upgraded from 4.4.3.
>
>
>
> Regards,
>
>
>
> Igor.
>
>
>
> *De :* Daniel-Constantin Mierla <[email protected]
> <mailto:[email protected]>>
> *Envoyé :* jeudi 30 juillet 2020 14:55
> *À :* Kamailio (SER) - Users Mailing List
> <[email protected]
> <mailto:[email protected]>>; Igor Potjevlesh
> <[email protected] <mailto:[email protected]>>
> *Objet :* Re: [SR-Users] Issue with kamctl after upgrading to 5.3.4
>
>
>
> Hello,
>
> if you upgraded in the 5.3 series, then it should be no updates in
> the usrloc module that should change functionality. Or did you
> upgraded from an older series like 5.2 or even older?
>
> Cheers,
> Daniel
>
> On 30.07.20 14:43, Igor Potjevlesh wrote:
>
> With the right permissions now it's okay.
>
> The new aliases are created and then sync with the DB but the
> lookup(aliases) function doesn't find any record. Is there
> something new with this module? The one loaded at the startup
> looks to be good and run as usual.
>
>
>
> Regards,
>
>
>
> Igor.
>
>
>
> *De :* sr-users <[email protected]>
> <mailto:[email protected]> *De la part de*
> Sergey Safarov
> *Envoyé :* jeudi 30 juillet 2020 12:46
> *À :* Kamailio (SER) - Users Mailing List
> <[email protected]> <mailto:[email protected]>
> *Objet :* Re: [SR-Users] Issue with kamctl after upgrading to
> 5.3.4
>
>
>
> Think this will fork if command executed:
>
> 1) root user;
>
> 2) kamailio user;
>
> 3) member of kamailio group user;
>
>
>
> According to description command executed not under these users.
>
>
>
>
>
> On Thu, Jul 30, 2020 at 1:35 PM Igor Potjevlesh
> <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hello Daniel,
>
>
>
> I installed from the sources.
>
> But you're right. I missed the "fifo_mode" param with the
> right permission. It works better, thank you.
>
> Regards,
>
>
>
> Igor.
>
>
>
> *De :* Daniel-Constantin Mierla <[email protected]
> <mailto:[email protected]>>
> *Envoyé :* jeudi 30 juillet 2020 11:16
> *À :* Kamailio (SER) - Users Mailing List
> <[email protected]
> <mailto:[email protected]>>; Igor Potjevlesh
> <[email protected]
> <mailto:[email protected]>>;
> [email protected]
> <mailto:[email protected]>
> *Objet :* Re: [SR-Users] Issue with kamctl after upgrading
> to 5.3.4
>
>
>
> Hello,
>
> did you install from packages on an OS with systemd? I
> think I saw some discussion here on mailing list related
> to restriction/permissions enforced by systemd, but I am
> not sure it was about the same case.
>
> Anyhow, jsonrpcs also uses a fifo file to receive commands
> from kamctl and kamailio_rpc.fifo is the one create in
> such case. The mi_fifo is no longer available, which was
> for MI commands, not for RPC commands.
>
> The jsonrpcs module should have modparams to set access
> rights as well as user/group for the rpc fifo file. That
> should give enough flexibility to allow different users to
> access the fifo file.
>
> Otherwise, I am not sure why it worked for you before,
> because it was supposed to be restricted access and as
> long as I can remember I used sudo to run kamctl...
>
> Cheers,
> Daniel
>
> On 30.07.20 10:47, Igor Potjevlesh wrote:
>
> Hello there!
>
>
>
> I'm having trouble with kamctl since I upgraded to 5.3.4.
>
> The command is working fine with root user but not
> with another user. The problem seems to be that the
> command try to access to
> /var/run/kamailio/kamailio_rpc.fifo even if the file
> exists.
>
> I guess it's a permission problem. But I was thinking
> that FIFO is no more used. Only jsonrpcs.
>
>
>
> How can I fix that?
>
>
>
> Regards,
>
>
>
> Igor.
>
>
>
>
> ------------------------------------------------------------------------
>
> Avast logo <https://www.avast.com/antivirus>
>
>
>
> L'absence de virus dans ce courrier électronique a été
> vérifiée par le logiciel antivirus Avast.
> www.avast.com <https://www.avast.com/antivirus>
>
>
>
>
>
> _______________________________________________
>
> Kamailio (SER) - Users Mailing List
>
> [email protected]
> <mailto:[email protected]>
>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
>
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
>
> www.twitter.com/miconda <http://www.twitter.com/miconda> --
> www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
>
> Funding: https://www.paypal.me/dcmierla
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> [email protected]
> <mailto:[email protected]>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> _______________________________________________
>
> Kamailio (SER) - Users Mailing List
>
> [email protected] <mailto:[email protected]>
>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
>
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
>
> www.twitter.com/miconda <http://www.twitter.com/miconda> --
> www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
>
> Funding: https://www.paypal.me/dcmierla
>
> --
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
> www.twitter.com/miconda <http://www.twitter.com/miconda> --
> www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
> Funding: https://www.paypal.me/dcmierla
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
_______________________________________________
Kamailio (SER) - Users Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
