[SR-Users] Intercepting OPTIONS from nathelper
Hello! I need advice on how to intercept local SIP OPTIONS requests from the nathelper module for some adjustments? As far as I tested, it does not fall into the *event_route[tm:local-request]* Thanks in advance! # kamailio -v version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: [Presence] Updating route information for SIP NOTIFY when re-SUBSCRIBE
Hi there!
I conducted some tests on the new Kamailio 5.7.3 and unfortunately, the
problem still exists.
Specifically, the problem lies in the fact that the data in the
*active_watchers* table and the *record_route* field are only updated with
initial Record-Route sets, and ignores any routing set changes for
in-dialog re-subscribtions.
However, there is a commit on GitHub that should fix this issue, but looks
did not:
https://github.com/kamailio/kamailio/commit/e52547956462ad53032be95ff5f2701785dfdd2a.
I can share sipp scripts for reproducing the problem, along with a set of
pcap traces (sip and mysql).
Thanks in advance!
чт, 29 февр. 2024 г. в 12:10, Denys Pozniak :
> Thanks for the information Fred!
> I tried to find some information in the module description...
>
> > Out of curiosity, since 5.1.2 is quite old…
> The version is really old, but it works damn stably under high load and I
> can’t even raise my hand to touch the server.
>
> ср, 28 февр. 2024 г. в 15:44, Fred Posner via sr-users <
> sr-users@lists.kamailio.org>:
>
>> Out of curiosity, since 5.1.2 is quite old…
>>
>> Have you considered a supported branch (5.6, 5.7) or tried the most
>> recent 5.1.10?
>>
>> The change log for 5.1.x includes:
>>
>> "presence: update record_route in database"
>>
>> Regards,
>>
>> Fred Posner
>> p: +1 (352) 664-3733
>> contact: https://fred.tel
>>
>>
>>
>>
>> > On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users <
>> sr-users@lists.kamailio.org> wrote:
>> >
>> > Hello!
>> >
>> > In my architecture, SIP SUBSCRIBE messages can reach the Kamailio
>> Presence server in several ways.
>> > And I noticed that re-SUBSCRIBEs messages do not update the
>> record_route field in the active_watchers table (MySQL), so subsequent SIP
>> NOTIFY messages do not inherit it and have the routes set of the initial
>> SIP SUBSCRIBE message.
>> >
>> > Is there any way to change this behavior?
>> >
>> > modparam("presence", "db_url", DBURL)
>> > modparam("presence", "subs_db_mode", 3)
>> > modparam("presence", "timeout_rm_subs", 0)
>> > modparam("presence", "expires_offset", 0)
>> > modparam("presence", "max_expires", 1800)
>> > modparam("presence", "db_update_period", 30)
>> > modparam("presence", "clean_period", 180)
>> > modparam("presence", "send_fast_notify", 1)
>> > modparam("presence", "pres_htable_size", 32)
>> > modparam("presence", "subs_htable_size", 32)
>> > modparam("presence", "publ_cache", 0)
>> > modparam("presence", "notifier_processes", 0)
>> >
>> > # kamailio -v
>> > version: kamailio 5.1.2 (x86_64/linux)
>> > --
>> >
>> > BR,
>> > Denys Pozniak
>>
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to
>> the sender!
>> Edit mailing list options or unsubscribe:
>>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: [Presence] Updating route information for SIP NOTIFY when re-SUBSCRIBE
Thanks for the information Fred!
I tried to find some information in the module description...
> Out of curiosity, since 5.1.2 is quite old…
The version is really old, but it works damn stably under high load and I
can’t even raise my hand to touch the server.
ср, 28 февр. 2024 г. в 15:44, Fred Posner via sr-users <
sr-users@lists.kamailio.org>:
> Out of curiosity, since 5.1.2 is quite old…
>
> Have you considered a supported branch (5.6, 5.7) or tried the most recent
> 5.1.10?
>
> The change log for 5.1.x includes:
>
> "presence: update record_route in database"
>
> Regards,
>
> Fred Posner
> p: +1 (352) 664-3733
> contact: https://fred.tel
>
>
>
>
> > On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users <
> sr-users@lists.kamailio.org> wrote:
> >
> > Hello!
> >
> > In my architecture, SIP SUBSCRIBE messages can reach the Kamailio
> Presence server in several ways.
> > And I noticed that re-SUBSCRIBEs messages do not update the record_route
> field in the active_watchers table (MySQL), so subsequent SIP NOTIFY
> messages do not inherit it and have the routes set of the initial SIP
> SUBSCRIBE message.
> >
> > Is there any way to change this behavior?
> >
> > modparam("presence", "db_url", DBURL)
> > modparam("presence", "subs_db_mode", 3)
> > modparam("presence", "timeout_rm_subs", 0)
> > modparam("presence", "expires_offset", 0)
> > modparam("presence", "max_expires", 1800)
> > modparam("presence", "db_update_period", 30)
> > modparam("presence", "clean_period", 180)
> > modparam("presence", "send_fast_notify", 1)
> > modparam("presence", "pres_htable_size", 32)
> > modparam("presence", "subs_htable_size", 32)
> > modparam("presence", "publ_cache", 0)
> > modparam("presence", "notifier_processes", 0)
> >
> > # kamailio -v
> > version: kamailio 5.1.2 (x86_64/linux)
> > --
> >
> > BR,
> > Denys Pozniak
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] [Presence] Updating route information for SIP NOTIFY when re-SUBSCRIBE
Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio
Presence server in several ways.
And I noticed that re-SUBSCRIBEs messages do not update the record_route
field in the active_watchers table (MySQL), so subsequent SIP NOTIFY
messages do not inherit it and have the routes set of the initial SIP
SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL)
modparam("presence", "subs_db_mode", 3)
modparam("presence", "timeout_rm_subs", 0)
modparam("presence", "expires_offset", 0)
modparam("presence", "max_expires", 1800)
modparam("presence", "db_update_period", 30)
modparam("presence", "clean_period", 180)
modparam("presence", "send_fast_notify", 1)
modparam("presence", "pres_htable_size", 32)
modparam("presence", "subs_htable_size", 32)
modparam("presence", "publ_cache", 0)
modparam("presence", "notifier_processes", 0)
# kamailio -v
version: kamailio 5.1.2 (x86_64/linux)
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Incompatibility of the DMQ htable protocol with older Kamailio versions
>dmq is designed to work only between kamailio nodes that have the same
major version (e.g., only between kamailio 5.7.x nodes).
Yes, looks like I missed this point about compatibility.
Thanks again for your help!
ср, 29 нояб. 2023 г. в 13:39, Daniel-Constantin Mierla :
> Hello,
>
> dmq is designed to work only between kamailio nodes that have the same
> major version (e.g., only between kamailio 5.7.x nodes).
>
> That's because even on the network the data may look the same, the
> internal structures, types of fields, sizes and meaning of values can be
> different. This is similar to how the major storage systems require nodes
> in the same replication group.
>
> A note about it is in the docs:
> - https://www.kamailio.org/docs/modules/stable/modules/dmq.html#idm39
>
> To detect different versions in the same cluster, you can eventually look
> at the User-Agent header (or Server for replies).
>
> Cheers,
> Daniel
>
> On 29.11.23 12:51, Denys Pozniak via sr-users wrote:
>
> Hello!
>
> I noticed that there are differences in the DMQ htable replication
> protocol for the old version of Kamailio 5.2 and the new 5.7.
> For example, the new version uses action 2 when updating values and action
> 4 to remove.
> The old Kamailio version uses the values 1 and 3 respectively.
>
> Well, as a result, the htable data is not shared between such nodes, plus
> there are errors in the syslog of the old version:
> ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action
>
> It would probably be worth introducing some kind of DMQ htable protocol
> versioning to maintain compatibility?
> And is there any option to make them work together (I wouldn’t really want
> to change the action number in sip/sdp/json on the fly)?
>
> Kamialio 5.2
>
> {"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
> {"action":3,"htname":"shared","cname":"user","mode":0}
>
> Kamailio 5.7
>
> {"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
> {"action":4,"htname":"shared","cname":"user","mode":0}
> --
>
> BR,
> Denys Pozniak
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
> Edit mailing list options or unsubscribe:
>
>
> --
> Daniel-Constantin Mierla (@ asipto.com)twitter.com/miconda --
> linkedin.com/in/miconda
> Kamailio Consultancy and Development Services
> Kamailio Advanced Training -- asipto.com
>
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Incompatibility of the DMQ htable protocol with older Kamailio versions
Hello!
I noticed that there are differences in the DMQ htable replication protocol
for the old version of Kamailio 5.2 and the new 5.7.
For example, the new version uses action 2 when updating values and action
4 to remove.
The old Kamailio version uses the values 1 and 3 respectively.
Well, as a result, the htable data is not shared between such nodes, plus
there are errors in the syslog of the old version:
ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action
It would probably be worth introducing some kind of DMQ htable protocol
versioning to maintain compatibility?
And is there any option to make them work together (I wouldn’t really want
to change the action number in sip/sdp/json on the fly)?
Kamialio 5.2
{"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
{"action":3,"htname":"shared","cname":"user","mode":0}
Kamailio 5.7
{"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
{"action":4,"htname":"shared","cname":"user","mode":0}
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: tps_storage_fill_contact(): no r-uri user
Mode 2 works fine if there is no user part in the Contact URI.
Thanks again for your help!
modparam("topos", "contact_mode", 2)
modparam("topos", "xavu_cfg", "tps")
modparam("topos", "xavu_field_a_contact", "a_contact")
modparam("topos", "xavu_field_b_contact", "b_contact")
modparam("topos", "xavu_field_contact_host", "contact_host")
request_route {
$xavu(tps=>a_contact) = "a_contact";
$xavu(tps=>b_contact) = "b_contact";
}
вт, 28 нояб. 2023 г. в 15:42, Denys Pozniak :
> Thanks!
>
> Yes exactly, I set the parameter contact_mode to 1 not to mask Contact.
> Сan I somehow bypass the restrictions of mode 1 through mode 2?
>
>
> вт, 28 нояб. 2023 г. в 13:25, Daniel-Constantin Mierla via sr-users <
> sr-users@lists.kamailio.org>:
>
>> I guess you face such case because of the contact mode parameter:
>>
>> -
>> https://www.kamailio.org/docs/modules/stable/modules/topos.html#topos.p.contact_mode
>>
>> Likely you set that modparam to 1, which needs to take user part from
>> r-uri and contact. I haven't implemented that functionality, but apparently
>> is for cases when UAs require user part to match corresponding user ids.
>>
>> The default mode is 0, which should not care about lack of user parts in
>> contact header.
>>
>> Cheers,
>> Daniel
>> On 28.11.23 12:22, Denys Pozniak via sr-users wrote:
>>
>> Thanks!
>> Yes, I experimented a little with the sipp and determined that the topos
>> "requires" a user part of Contact URI.
>> If this is so, then it would probably be necessary to indicate this
>> somewhere in the module description.
>>
>> вт, 28 нояб. 2023 г. в 11:42, Yuriy G :
>>
>>> Hi Denis. I think this is topos specific.
>>> When topos does topology striping it also affects contact field, so it
>>> adds some data/id username. So if you wish topos to be involved - the same
>>> form of the URI should be used. There is also API from topos module to
>>> handle contact on your own if needed.
>>>
>>> On Tue, Nov 28, 2023, 11:25 Denys Pozniak via sr-users <
>>> sr-users@lists.kamailio.org> wrote:
>>>
>>>> Hello!
>>>>
>>>> My topology is like this:
>>>> PBX -> Kamailio Topos -> User
>>>>
>>>> When calling the user, PBX does not add the user part in the Contact
>>>> URI, something like:
>>>> Contact:
>>>>
>>>> When the customer sends a reinvite, the topos turns off for this
>>>> transaction and the sip partially breaks down with error:
>>>>
>>>> topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user
>>>> topos [tps_storage.c:615]: tps_storage_record(): failed to store
>>>>
>>>> As far as I understand, the RFC allows the absence of the user part in
>>>> the URI and this occurs quite often.
>>>> I can provide the pcap file and debug log in a private message if this
>>>> helps identify the essence of the problem.
>>>>
>>>> # kamailio -v
>>>> version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty
>>>>
>>>> --
>>>>
>>>> BR,
>>>> Denys Pozniak
>>>>
>>>>
>>>> __
>>>> Kamailio - Users Mailing List - Non Commercial Discussions
>>>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>>>> Important: keep the mailing list in the recipients, do not reply only
>>>> to the sender!
>>>> Edit mailing list options or unsubscribe:
>>>>
>>>
>>
>> --
>>
>> BR,
>> Denys Pozniak
>>
>>
>>
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the
>> sender!
>> Edit mailing list options or unsubscribe:
>>
>> --
>> Daniel-Constantin Mierla (@ asipto.com)twitter.com/miconda --
>> linkedin.com/in/miconda
>> Kamailio Consultancy and Development Services
>> Kamailio Advanced Training -- asipto.com
>>
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to
>> the sender!
>> Edit mailing list options or unsubscribe:
>>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: tps_storage_fill_contact(): no r-uri user
Thanks! Yes exactly, I set the parameter contact_mode to 1 not to mask Contact. Сan I somehow bypass the restrictions of mode 1 through mode 2? вт, 28 нояб. 2023 г. в 13:25, Daniel-Constantin Mierla via sr-users < sr-users@lists.kamailio.org>: > I guess you face such case because of the contact mode parameter: > > - > https://www.kamailio.org/docs/modules/stable/modules/topos.html#topos.p.contact_mode > > Likely you set that modparam to 1, which needs to take user part from > r-uri and contact. I haven't implemented that functionality, but apparently > is for cases when UAs require user part to match corresponding user ids. > > The default mode is 0, which should not care about lack of user parts in > contact header. > > Cheers, > Daniel > On 28.11.23 12:22, Denys Pozniak via sr-users wrote: > > Thanks! > Yes, I experimented a little with the sipp and determined that the topos > "requires" a user part of Contact URI. > If this is so, then it would probably be necessary to indicate this > somewhere in the module description. > > вт, 28 нояб. 2023 г. в 11:42, Yuriy G : > >> Hi Denis. I think this is topos specific. >> When topos does topology striping it also affects contact field, so it >> adds some data/id username. So if you wish topos to be involved - the same >> form of the URI should be used. There is also API from topos module to >> handle contact on your own if needed. >> >> On Tue, Nov 28, 2023, 11:25 Denys Pozniak via sr-users < >> sr-users@lists.kamailio.org> wrote: >> >>> Hello! >>> >>> My topology is like this: >>> PBX -> Kamailio Topos -> User >>> >>> When calling the user, PBX does not add the user part in the Contact >>> URI, something like: >>> Contact: >>> >>> When the customer sends a reinvite, the topos turns off for this >>> transaction and the sip partially breaks down with error: >>> >>> topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user >>> topos [tps_storage.c:615]: tps_storage_record(): failed to store >>> >>> As far as I understand, the RFC allows the absence of the user part in >>> the URI and this occurs quite often. >>> I can provide the pcap file and debug log in a private message if this >>> helps identify the essence of the problem. >>> >>> # kamailio -v >>> version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty >>> >>> -- >>> >>> BR, >>> Denys Pozniak >>> >>> >>> __ >>> Kamailio - Users Mailing List - Non Commercial Discussions >>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org >>> Important: keep the mailing list in the recipients, do not reply only to >>> the sender! >>> Edit mailing list options or unsubscribe: >>> >> > > -- > > BR, > Denys Pozniak > > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the > sender! > Edit mailing list options or unsubscribe: > > -- > Daniel-Constantin Mierla (@ asipto.com)twitter.com/miconda -- > linkedin.com/in/miconda > Kamailio Consultancy and Development Services > Kamailio Advanced Training -- asipto.com > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: tps_storage_fill_contact(): no r-uri user
Thanks! Yes, I experimented a little with the sipp and determined that the topos "requires" a user part of Contact URI. If this is so, then it would probably be necessary to indicate this somewhere in the module description. вт, 28 нояб. 2023 г. в 11:42, Yuriy G : > Hi Denis. I think this is topos specific. > When topos does topology striping it also affects contact field, so it > adds some data/id username. So if you wish topos to be involved - the same > form of the URI should be used. There is also API from topos module to > handle contact on your own if needed. > > On Tue, Nov 28, 2023, 11:25 Denys Pozniak via sr-users < > sr-users@lists.kamailio.org> wrote: > >> Hello! >> >> My topology is like this: >> PBX -> Kamailio Topos -> User >> >> When calling the user, PBX does not add the user part in the Contact URI, >> something like: >> Contact: >> >> When the customer sends a reinvite, the topos turns off for this >> transaction and the sip partially breaks down with error: >> >> topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user >> topos [tps_storage.c:615]: tps_storage_record(): failed to store >> >> As far as I understand, the RFC allows the absence of the user part in >> the URI and this occurs quite often. >> I can provide the pcap file and debug log in a private message if this >> helps identify the essence of the problem. >> >> # kamailio -v >> version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty >> >> -- >> >> BR, >> Denys Pozniak >> >> >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email to sr-users-le...@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] tps_storage_fill_contact(): no r-uri user
Hello! My topology is like this: PBX -> Kamailio Topos -> User When calling the user, PBX does not add the user part in the Contact URI, something like: Contact: When the customer sends a reinvite, the topos turns off for this transaction and the sip partially breaks down with error: topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user topos [tps_storage.c:615]: tps_storage_record(): failed to store As far as I understand, the RFC allows the absence of the user part in the URI and this occurs quite often. I can provide the pcap file and debug log in a private message if this helps identify the essence of the problem. # kamailio -v version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Discrepancy between RPC stats and real data from the UAC module
Hello! We use the UAC module for outbound registrations and when we try to get RPC statistics we see that the data does not match, what could be the reason? # kamcmd stats.get_statistics uac: uac:regactive = 14 uac:regdisabled = 0 uac:regtotal = 0 # kamctl rpc uac.reg_dump | grep flag | grep 20 -c 745 # kamailio -v version: kamailio 5.6.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] [Proposal] To add tlsa module to the package builder
Hello! Are there any technical difficulties in adding tlsa module with the statically linked OpenSSL v1.1.1 to the package builder (deb)? -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: how to get value of next hop
Hello! Did you try $(hfl(name)[N]) ? чт, 10 авг. 2023 г. в 04:13, Sergey Safarov : > I receiving INVITE with two Route header (no to tag). > First Route header is my Kamailio host. > Second Route header is next hop after Kamailio. > > I need to get value of next hop. > I tried to use "$route_uri" after "loose_route" but his deos works. > "$route_uri" always use top Route header. > But in the INVITE first Route header is Kamailio host. > > Is any change to get top Route header after "loose_route"? > __ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: How to handle 302 redirects
Hello!
We use a similar mechanism and everything works fine. A new branch is
formed with RURI from 302 Contact:
failure_route[N_DISPATCH] {
if ( t_check_status("302") ) {
get_redirects("*:1");
route(RELAY);
exit;
}
...
}
ср, 21 июн. 2023 г. в 00:51, Trey Ormsbee <
trey.orms...@interoptechnologies.com>:
> Actually, I sent this way too soon. I think I tried a bunch of different
> things and got confused. This is config is working correctly and sending
> correctly.
>
>
>
> *From: *Trey Ormsbee
> *Date: *Tuesday, June 20, 2023 at 2:54 PM
> *To: *sr-users@lists.kamailio.org
> *Subject: *How to handle 302 redirects
>
> Hello,
>
>
>
> Im having a hard time figuring out how to handle a 302 reidrect, the
> uac_redirect modules shows a simple configuration. However for me, what it
> is not doing is changing the 302 back to invite. It is sending the 302 as
> is on.
>
>
>
>if(!t_check_status("3[0-9][0-9]")) {
>
> exit;
>
>}
>
>get_redirects("3:1");
>
>t_relay();
>
>
>
> This code just relays the 302 for me. I should add I am using this with
> the DISPATCHER module so perhaps that has something to do with my issue.
>
>
>
> Setup is this, kamailio is sitting between to sip servers, so the flow
> goes like this, sip_server_a -> kamailio -> sip_server_b.sip_server_b
> only responds with 302 redirects, sip_server_a does not handle 302’s at
> all. Kamailio will only get invites from sip_server_a, and the redirects
> from sip_server_b will only have one contact. How can I get kamailio to
> reply to sip_server_a’s invite with the updated INVITE?
>
>
>
> My config is a mesh of the dispatcher example and uac_redirect example
> with this specific section handling the redirect:
>
>
>
> # Sample failure route
>
> failure_route[RTF_DISPATCH] {
>
> xlog("L_NOTICE", "RTF_DISPATCH: ");
>
> if (t_is_canceled()) {
>
> exit;
>
> }
>
> # next DST - only for 500 or local timeout
>
> if (t_check_status("500")
>
> or (t_branch_timeout() and !t_branch_replied()))
>
> {
>
> if(ds_next_dst())
>
> {
>
> t_on_failure("RTF_DISPATCH");
>
> route(RELAY);
>
> exit;
>
> }
>
> }
>
> if (t_check_status("302")) {
>
> xlog("L_NOTICE", "RTF_DISPATCH: 302 ");
>
> if (!get_redirects("1:1")) {
>
> xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects ");
>
> t_reply("480", "Temporarily Unavailable");
>
> exit;
>
> }
>
> xlog("L_NOTICE", "RTF_DISPATCH: got redirects ");
>
> t_relay(“sip_server_a”,”5060”);
>
> }
>
> }
>
>
>
> Any ideas what I am doing wrong is this supported? Im expecting once I
> relay this message that it should be an INVITE not a 302 redirect. I cant
> find any examples of anyone else really doing this.
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: [auth_radius.c:123]: mod_init(): failed to open configuration file
Hello!
Figured out the source of the problem.
The radiusclient-ng library didn't like the radius_deadtime option (which
has been migrated from the freeradius-client library), commented it out and
everything works.
Maybe it makes sense to add additional logging to the configuration file to
avoid such problems?
/etc/radiusclient-ng/radiusclient.conf
...
#radius_deadtime 30
...
чт, 11 мая 2023 г. в 12:41, Denys Pozniak :
> In this commit, the radius library was changed specifically for the
> version of Centos 7:
>
> https://github.com/kamailio/kamailio/commit/a3ce062fdec2d3a5d5e46f49c9d0ea9d449a1bec
>
>
>
>
>
>
>
>
>
> *%if 0%{?fedora} || 0%{?suse_version} || 0%{?rhel} == 8Requires:
> freeradius-clientBuildRequires: freeradius-client-devel%elseRequires:
> radiusclient-ngBuildRequires: radiusclient-ng-devel%endif*
>
>
>
> чт, 11 мая 2023 г. в 11:56, Denys Pozniak :
>
>> As far as I can see, the new version of Kamailio requires
>> radiusclient-ng, although the current one old worked with freeradius-client.
>> Maybe there is a reason?
>>
>>
>> чт, 11 мая 2023 г. в 11:35, Denys Pozniak :
>>
>>> Hello!
>>>
>>> >Is it the same radius client library used for the two test cases?
>>> >It is the same operating system?
>>> >In other words, have you tried with the two version on exactly the same
>>> system?
>>>
>>> That's exactly what it is, in two cases the operating system and the
>>> radius library are the same, only the difference is in the version of
>>> Kamailio.
>>>
>>> CentOS Linux release 7.9.2009 (Core)
>>> freeradius-utils-3.0.13-15.el7.x86_64
>>> freeradius-3.0.13-15.el7.x86_64
>>> freeradius-client-1.1.7-16.el7.centos.x86_64
>>>
>>> I connected via strace to kamailio 5.6.4, maybe this output will somehow
>>> clarify the situation:
>>>
>>> ...
>>> write(2, " 0(20677) INFO: auth [auth_mod.c"..., 107 0(20677) INFO: auth
>>> [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count)
>>> support disabled
>>> ) = 107
>>> write(2, " 0(20677) DEBUG: [core/sr"..., 72 0(20677) DEBUG:
>>> [core/sr_module.c:969]: init_mod(): auth_radius
>>> ) = 72
>>> open("/etc/radiusclient/radiusclient.conf", O_RDONLY) = 4
>>> fstat(4, {st_mode=S_IFREG|0644, st_size=487, ...}) = 0
>>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>>> = 0x7f2df0119000
>>> read(4, "auth_order radius,local\nlog"..., 4096) = 487
>>> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
>>> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
>>> -1 ENOENT (No such file or directory)
>>> close(5)= 0
>>> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
>>> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
>>> -1 ENOENT (No such file or directory)
>>> close(5)= 0
>>> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
>>> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
>>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>>> = 0x7f2df0118000
>>> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
>>> read(5, " 74/udp "..., 4096) = 4096
>>> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
>>> read(5, "636/udp "..., 4096) = 4096
>>> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
>>> close(5)= 0
>>> munmap(0x7f2df0118000, 4096)= 0
>>> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
>>> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
>>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>>> = 0x7f2df0118000
>>> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
>>> read(5, " 74/udp "..., 4096) = 4096
>>> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
>>> read(5, "636/udp "..., 4096) = 4096
>>> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
>>> close(5)= 0
>>> munmap(0x7f2df0118000, 4096)= 0
>>> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0
[SR-Users] Re: [auth_radius.c:123]: mod_init(): failed to open configuration file
In this commit, the radius library was changed specifically for the version
of Centos 7:
https://github.com/kamailio/kamailio/commit/a3ce062fdec2d3a5d5e46f49c9d0ea9d449a1bec
*%if 0%{?fedora} || 0%{?suse_version} || 0%{?rhel} == 8Requires:
freeradius-clientBuildRequires: freeradius-client-devel%elseRequires:
radiusclient-ngBuildRequires: radiusclient-ng-devel%endif*
чт, 11 мая 2023 г. в 11:56, Denys Pozniak :
> As far as I can see, the new version of Kamailio requires radiusclient-ng,
> although the current one old worked with freeradius-client.
> Maybe there is a reason?
>
>
> чт, 11 мая 2023 г. в 11:35, Denys Pozniak :
>
>> Hello!
>>
>> >Is it the same radius client library used for the two test cases?
>> >It is the same operating system?
>> >In other words, have you tried with the two version on exactly the same
>> system?
>>
>> That's exactly what it is, in two cases the operating system and the
>> radius library are the same, only the difference is in the version of
>> Kamailio.
>>
>> CentOS Linux release 7.9.2009 (Core)
>> freeradius-utils-3.0.13-15.el7.x86_64
>> freeradius-3.0.13-15.el7.x86_64
>> freeradius-client-1.1.7-16.el7.centos.x86_64
>>
>> I connected via strace to kamailio 5.6.4, maybe this output will somehow
>> clarify the situation:
>>
>> ...
>> write(2, " 0(20677) INFO: auth [auth_mod.c"..., 107 0(20677) INFO: auth
>> [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count)
>> support disabled
>> ) = 107
>> write(2, " 0(20677) DEBUG: [core/sr"..., 72 0(20677) DEBUG:
>> [core/sr_module.c:969]: init_mod(): auth_radius
>> ) = 72
>> open("/etc/radiusclient/radiusclient.conf", O_RDONLY) = 4
>> fstat(4, {st_mode=S_IFREG|0644, st_size=487, ...}) = 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>> = 0x7f2df0119000
>> read(4, "auth_order radius,local\nlog"..., 4096) = 487
>> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
>> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
>> -1 ENOENT (No such file or directory)
>> close(5)= 0
>> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
>> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) =
>> -1 ENOENT (No such file or directory)
>> close(5)= 0
>> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
>> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>> = 0x7f2df0118000
>> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
>> read(5, " 74/udp "..., 4096) = 4096
>> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
>> read(5, "636/udp "..., 4096) = 4096
>> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
>> close(5)= 0
>> munmap(0x7f2df0118000, 4096)= 0
>> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
>> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
>> = 0x7f2df0118000
>> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
>> read(5, " 74/udp "..., 4096) = 4096
>> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
>> read(5, "636/udp "..., 4096) = 4096
>> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
>> close(5)= 0
>> munmap(0x7f2df0118000, 4096)= 0
>> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 5
>> connect(5, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
>> sendto(5, "<11>May 11 10:20:50 kamailio: /e"..., 113, MSG_NOSIGNAL, NULL,
>> 0) = 113
>> close(4)= 0
>> munmap(0x7f2df0119000, 4096)= 0
>> write(2, " 0(20677) ERROR: auth_radius [au"..., 97 0(20677) ERROR:
>> auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration
>> file
>> ) = 97
>> write(2, " 0(20677) ERROR: [core/sr"..., 149 0(20677) ERROR:
>> [core/sr_module.c:975]: init_mod(): Error while initializing module
>> auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)
>> ) = 149
>> write(2, "ERROR:
[SR-Users] Re: [auth_radius.c:123]: mod_init(): failed to open configuration file
As far as I can see, the new version of Kamailio requires radiusclient-ng,
although the current one old worked with freeradius-client.
Maybe there is a reason?
чт, 11 мая 2023 г. в 11:35, Denys Pozniak :
> Hello!
>
> >Is it the same radius client library used for the two test cases?
> >It is the same operating system?
> >In other words, have you tried with the two version on exactly the same
> system?
>
> That's exactly what it is, in two cases the operating system and the
> radius library are the same, only the difference is in the version of
> Kamailio.
>
> CentOS Linux release 7.9.2009 (Core)
> freeradius-utils-3.0.13-15.el7.x86_64
> freeradius-3.0.13-15.el7.x86_64
> freeradius-client-1.1.7-16.el7.centos.x86_64
>
> I connected via strace to kamailio 5.6.4, maybe this output will somehow
> clarify the situation:
>
> ...
> write(2, " 0(20677) INFO: auth [auth_mod.c"..., 107 0(20677) INFO: auth
> [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count)
> support disabled
> ) = 107
> write(2, " 0(20677) DEBUG: [core/sr"..., 72 0(20677) DEBUG:
> [core/sr_module.c:969]: init_mod(): auth_radius
> ) = 72
> open("/etc/radiusclient/radiusclient.conf", O_RDONLY) = 4
> fstat(4, {st_mode=S_IFREG|0644, st_size=487, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0119000
> read(4, "auth_order radius,local\nlog"..., 4096) = 487
> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> close(5)= 0
> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> close(5)= 0
> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0118000
> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
> read(5, " 74/udp "..., 4096) = 4096
> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
> read(5, "636/udp "..., 4096) = 4096
> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
> close(5)= 0
> munmap(0x7f2df0118000, 4096)= 0
> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0118000
> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
> read(5, " 74/udp "..., 4096) = 4096
> read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
> read(5, "636/udp "..., 4096) = 4096
> read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
> close(5)= 0
> munmap(0x7f2df0118000, 4096)= 0
> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
> sendto(5, "<11>May 11 10:20:50 kamailio: /e"..., 113, MSG_NOSIGNAL, NULL,
> 0) = 113
> close(4)= 0
> munmap(0x7f2df0119000, 4096)= 0
> write(2, " 0(20677) ERROR: auth_radius [au"..., 97 0(20677) ERROR:
> auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration
> file
> ) = 97
> write(2, " 0(20677) ERROR: [core/sr"..., 149 0(20677) ERROR:
> [core/sr_module.c:975]: init_mod(): Error while initializing module
> auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)
> ) = 149
> write(2, "ERROR: error while initializing "..., 40ERROR: error while
> initializing modules
> ) = 40
> rt_sigaction(SIGALRM, {sa_handler=0x41f3af, sa_mask=[ALRM],
> sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
> {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
> alarm(60) = 0
> wait4(-1, NULL, 0, NULL)= -1 ECHILD (No child processes)
> rt_sigaction(SIGALRM, {sa_handler=0x41f3c6, sa_mask=[ALRM],
> sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
> {sa_handler=0x41f3af, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART,
> sa_restorer=0x7f2def23b400}, 8) = 0
> write(2, " 0(20677) DEBUG: [core/sr"..., 98 0(20677) DEBUG:
> [core/sr_module.c:835]: destroy_
[SR-Users] Re: [auth_radius.c:123]: mod_init(): failed to open configuration file
Hello!
>Is it the same radius client library used for the two test cases?
>It is the same operating system?
>In other words, have you tried with the two version on exactly the same
system?
That's exactly what it is, in two cases the operating system and the radius
library are the same, only the difference is in the version of Kamailio.
CentOS Linux release 7.9.2009 (Core)
freeradius-utils-3.0.13-15.el7.x86_64
freeradius-3.0.13-15.el7.x86_64
freeradius-client-1.1.7-16.el7.centos.x86_64
I connected via strace to kamailio 5.6.4, maybe this output will somehow
clarify the situation:
...
write(2, " 0(20677) INFO: auth [auth_mod.c"..., 107 0(20677) INFO: auth
[auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count)
support disabled
) = 107
write(2, " 0(20677) DEBUG: [core/sr"..., 72 0(20677) DEBUG:
[core/sr_module.c:969]: init_mod(): auth_radius
) = 72
open("/etc/radiusclient/radiusclient.conf", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=487, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2df0119000
read(4, "auth_order radius,local\nlog"..., 4096) = 487
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
close(5)= 0
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
close(5)= 0
open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2df0118000
read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
read(5, " 74/udp "..., 4096) = 4096
read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
read(5, "636/udp "..., 4096) = 4096
read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
close(5)= 0
munmap(0x7f2df0118000, 4096)= 0
open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2df0118000
read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
read(5, " 74/udp "..., 4096) = 4096
read(5, " # Quick Mail Transfer Proto"..., 4096) = 4096
read(5, "636/udp "..., 4096) = 4096
read(5, " # Microsoft-SQL-Monito"..., 4096) = 4096
close(5)= 0
munmap(0x7f2df0118000, 4096)= 0
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
sendto(5, "<11>May 11 10:20:50 kamailio: /e"..., 113, MSG_NOSIGNAL, NULL,
0) = 113
close(4)= 0
munmap(0x7f2df0119000, 4096)= 0
write(2, " 0(20677) ERROR: auth_radius [au"..., 97 0(20677) ERROR:
auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration
file
) = 97
write(2, " 0(20677) ERROR: [core/sr"..., 149 0(20677) ERROR:
[core/sr_module.c:975]: init_mod(): Error while initializing module
auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)
) = 149
write(2, "ERROR: error while initializing "..., 40ERROR: error while
initializing modules
) = 40
rt_sigaction(SIGALRM, {sa_handler=0x41f3af, sa_mask=[ALRM],
sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
{sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
alarm(60) = 0
wait4(-1, NULL, 0, NULL)= -1 ECHILD (No child processes)
rt_sigaction(SIGALRM, {sa_handler=0x41f3c6, sa_mask=[ALRM],
sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
{sa_handler=0x41f3af, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART,
sa_restorer=0x7f2def23b400}, 8) = 0
write(2, " 0(20677) DEBUG: [core/sr"..., 98 0(20677) DEBUG:
[core/sr_module.c:835]: destroy_modules(): starting modules destroy phase
чт, 11 мая 2023 г. в 09:50, Daniel-Constantin Mierla :
> Hello,
>
> On 10.05.23 22:40, Victor Seva wrote:
> > Hi,
> >
> > On 10/5/23 16:36, Denys Pozniak wrote:
> >> Hello!
> >>
> >> After a major upgrade of Kamailio (5.1 -> 5.6), an error appears that
> >> it is not possible to open configuration file (I think this is about
> >> /etc/radiusclient/radiusclient.conf), although it exists with the
> >> necessary access rights:
> >> /0(27075) DEBUG: [core/sr_module.c:969]: init_mod(): auth_radius
> >> 0
[SR-Users] [auth_radius.c:123]: mod_init(): failed to open configuration file
Hello!
After a major upgrade of Kamailio (5.1 -> 5.6), an error appears that it is
not possible to open configuration file (I think this is about
/etc/radiusclient/radiusclient.conf), although it exists with the necessary
access rights:
*0(27075) DEBUG: [core/sr_module.c:969]: init_mod():
auth_radius0(27075) ERROR: auth_radius [auth_radius.c:123]: mod_init():
failed to open configuration file0(27075) ERROR:
[core/sr_module.c:975]: init_mod(): Error while initializing module
auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)ERROR: error while
initializing modules*
For the test, I made Kamailio downgrade back to 5.1 and the problem went
away.
Shortened the Kamailio config to the minimum for reproducing the problem:
*#!KAMAILIOmemdbg=5memlog=5children=1log_stderror=nolisten=udp:127.0.0.1:5060
<http://127.0.0.1:5060>loadmodule "kex.so"loadmodule "corex.so"loadmodule
"tm.so"loadmodule "sl.so"loadmodule "rr.so"loadmodule "pv.so"loadmodule
"maxfwd.so"loadmodule "auth.so"loadmodule
"auth_radius.so"modparam("auth_radius", "radius_config",
"/etc/radiusclient/radiusclient.conf")request_route {return;}*
Could the commit below somehow affect the acceptance of the radius_config
module parameter?
https://github.com/kamailio/kamailio/commit/f33ba318b20cbd2b34d278a7e2c4e64129b9e68d
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
Re: [SR-Users] Outgoing SIP/TLS connection error (msg_send_buffer(): tcp_send failed)
Thanks!!!
Yeah, *set_forward_no_connect()* was in the script ...
чт, 8 дек. 2022 г. в 12:23, Daniel-Constantin Mierla :
> Hello,
>
> check to see if the set_forward_no_connect() is used.
>
> Cheers,
> Daniel
> On 08.12.22 10:28, Denys Pozniak wrote:
>
> Hello!
>
> We use trunk with Twilio through a SIP/TLS.
> They establish incoming calls from random ports, like:
> (Twilio)3.3.3.3:54321 --> (Kamailio)2.2.2.2:5061
>
> In case of sending in-dialog requests to them, Kamailio should establish
> an outgoing connection to the dst port 5061 (as per Route), like:
> (Kamailio)2.2.2.2 --> (Twilio)3.3.3.3:5061
>
> But as per tcpdump traces and logs, Kamailio does not even try to
> establish an outgoing connection to Twilio.
> There should be no problems with routes and the network on that server, as
> regular telnet to Twilio shows that 5061 is open.
>
> What could be the reason and how to debug?
>
> *Script:*
> onsend_route {
> xlog("L_ERR","[$cfg(route)]*RELAY ONSEND* $rm / $du / $fs / $fsn /
> [$ci]\n");
> }
>
> *Syslog:*
> DEBUG [core/resolve.c:1259]: srv_sip_resolvehost(): 3.3.3.3:5061
> proto=3
> DEBUG [core/resolve.c:1371]: srv_sip_resolvehost(): returning
> 0x55acd63a63c0 (3.3.3.3:5061 proto=3)
> ERROR
[SR-Users] Outgoing SIP/TLS connection error (msg_send_buffer(): tcp_send failed)
Hello!
We use trunk with Twilio through a SIP/TLS.
They establish incoming calls from random ports, like:
(Twilio)3.3.3.3:54321 --> (Kamailio)2.2.2.2:5061
In case of sending in-dialog requests to them, Kamailio should establish an
outgoing connection to the dst port 5061 (as per Route), like:
(Kamailio)2.2.2.2 --> (Twilio)3.3.3.3:5061
But as per tcpdump traces and logs, Kamailio does not even try to establish
an outgoing connection to Twilio.
There should be no problems with routes and the network on that server, as
regular telnet to Twilio shows that 5061 is open.
What could be the reason and how to debug?
*Script:*
onsend_route {
xlog("L_ERR","[$cfg(route)]*RELAY ONSEND* $rm / $du / $fs / $fsn /
[$ci]\n");
}
*Syslog:*
DEBUG [core/resolve.c:1259]: srv_sip_resolvehost(): 3.3.3.3:5061
proto=3
DEBUG [core/resolve.c:1371]: srv_sip_resolvehost(): returning
0x55acd63a63c0 (3.3.3.3:5061 proto=3)
ERROR
Re: [SR-Users] Getting the name of an already set onreply_route
Here the question is more whether there is a variable ($T or any) into
which the name of the onreply_route is exported.
ср, 7 дек. 2022 г. в 13:21, Patrick Karton :
> Or transaction variable (xavp) is best for that.
>
> Le 7 déc. 2022 12:00, Patrick Karton a écrit :
>
> Hello i dont think so.
>
> But probably you can use shared or private variable depending on your
> needs
>
> Le 7 déc. 2022 11:28, Denys Pozniak a écrit :
>
> Hello!
>
> Is it possible to find out the name of the onreply_route that was set
> before?
> Something like this:
>
> t_on_reply("MANAGE_REPLY");
> ...
> if ( t_is_set("onreply_route") ) {
> get_onreply_route_name();
> ...
> }
>
> --
>
> BR,
> Denys Pozniak
>
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Getting the name of an already set onreply_route
Hello!
Is it possible to find out the name of the onreply_route that was set
before?
Something like this:
t_on_reply("MANAGE_REPLY");
...
if ( t_is_set("onreply_route") ) {
get_onreply_route_name();
...
}
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Starting with Kamailio
Hello! In my experience and opinion, it will be easier for you to start by reading the book "SIP routing with Kamailio". But you need to understand that Kamailio is a Proxy and it will be difficult to build a full-fledged RTC platform only on it. Usually, it is used in conjunction with Asterisk/Freeswitch. вт, 29 нояб. 2022 г. в 09:10, Clint Crabtree : > Hello, > > > > I’m a DIY entrepreneurial developer beginning to build a system and I > stumbled upon Kamailio. I’ve installed asterisk and kamailio in hopes of > setting up an IVR to collect voice to speech information from incoming > calls. I’m skilled with PHP to Javascript application development. In my > research of PBX and discovery of Asterisk I have found enough information > online to begin developing with Asterisk ARI; however, somewhere in my > discovery process was the suggestion that Kamailio can offer close to real > time voice recognition streaming whereas Asterisk is more of a record, > pause, translate, respond process. > > > > In an AstriCon presentation by Fred Posner I saw recommendations for new > applications the suggestion to develop with Kamailio: > https://www.youtube.com/watch?v=IaYOboZQEw0?t=23m10s > > > > I’m a newbie to SIP, but it seems really promising, can you help point me > in the right direction for aforementioned use-case for Kamailio? or am I > misunderstanding some if its capability? > > > > Regards, > > Clint Crabtree > __ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] db_mysql_new_connection(): driver error: Can't connect to MySQL server
Hello! It also seems to me that there are differences in the implementation of the protocol, but so far I have not been able to find a significant difference in the traces. Tried some tests with an intermediate ProxySQL and it looks encouraging. пн, 28 нояб. 2022 г. в 11:57, Henning Westerholt : > Hello, > > > > Interesting issue. Probably worth a try to look closer to the mysql > protocol traces (e.g., with wireshark) and try to spot differences in the > exchange at Kamailio startup for the working and non-working setup. > > > > Might be a slight incompatibility with the azure database implementation, > observed something like this in the past with one project. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of *Denys > Pozniak > *Sent:* Friday, November 25, 2022 5:09 PM > *To:* Kamailio (SER) - Users Mailing List > *Subject:* [SR-Users] db_mysql_new_connection(): driver error: Can't > connect to MySQL server > > > > Hello! > > > > We use Kamailio in conjunction with the cloud Azure Database for MySQL > 5.7. It has been noticed that Kamailio does not always start after > restarting. > > It happens to restart a couple of times and everything starts normally. > > From the pickup trace I collect on our side, it can be seen that Kamailio > connects to MySQL, requests and gets data, and then sends a Request Quit. > > On another server with a different configuration (slightly different set > of modules) and connected to the same database, this issue is not > reproduced. > > > > How to determine the source of the problem? > > > > Below, the logs are filtered by PID of processes in which an error > occurred: > > ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver > error: Can't connect to MySQL server on '10.1.128.4' (110) > > > > > > 11(588460) DEBUG: [core/pt.c:308]: fork_process(): seeding PRNG > with 893384711 > > 11(588460) DEBUG: [core/rand/cryptorand.c:36]: cryptorand_seed(): > seeding cryptorand generator with 893384711 > > 11(588460) DEBUG: [core/rand/fortuna/random.c:175]: > sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG > > 11(588460) DEBUG: [core/pt.c:313]: fork_process(): test random > numbers 289569343 1482836098 4036842274 2495827489 > > 11(588460) DEBUG: [core/sr_module.c:926]: init_child(): > initializing PROC_RPC with rank -2 > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: jsonrpcs [DMQ WORKER] > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: kex [DMQ WORKER] > > 11(588460) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-2) > > 11(588460) DEBUG: [core/utils/sruid.c:121]: sruid_init(): root for > sruid is [srid-6380d27f-8faac-] (0 / 20) > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: corex [DMQ WORKER] > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: tm [DMQ WORKER] > > 11(588460) DEBUG: tm [callid.c:136]: child_init_callid(): callid: ' > 558fadb265b2cc20-588460@10.1.15.12' > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: tmx [DMQ WORKER] > > 11(588460) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-2) > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: sl [DMQ WORKER] > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: usrloc [DMQ WORKER] > > 11(588460) DEBUG: [core/utils/sruid.c:121]: sruid_init(): root for > sruid is [ulcx-6380d27f-8faac-] (0 / 20) > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: registrar [DMQ WORKER] > > 11(588460) DEBUG: [core/utils/sruid.c:121]: sruid_init(): root for > sruid is [uloc-6380d27f-8faac-] (0 / 20) > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: ctl [DMQ WORKER] > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: dmq [DMQ WORKER] > > 11(588460) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 11 > rank -2: auth_db [DMQ WORKER] > > 11(588460) DEBUG: [db.c:315]: db_do_init2(): connection 0x > 7f96e7d58880 not found in pool > > 11(588460) DEBUG: db_mysql [km_my_con.c:110]: db_mysql_new_connection(): > opening connection: mysql://:@10.1.128.4/kamailio > > 11(588460) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): > driver error: Can't connect to MySQL server on '10.1.128.4' (110) > > 11
[SR-Users] db_mysql_new_connection(): driver error: Can't connect to MySQL server
srid-6380d27f-8fab2-] (0 / 20) 17(588466) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 17 rank -1: corex [Dialog Clean Timer] 17(588466) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 17 rank -1: tm [Dialog Clean Timer] 17(588466) DEBUG: tm [callid.c:136]: child_init_callid(): callid: ' 558fadb265b2cc20-588466@10.1.15.12' 17(588466) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 17 rank -1: tmx [Dialog Clean Timer] 17(588466) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-1) 17(588466) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 17 rank -1: sl [Dialog Clean Timer] 17(588466) DEBUG: [core/sr_module.c:878]: init_mod_child(): idx 17 rank -1: usrloc [Dialog Clean Timer] 17(588466) DEBUG: [core/utils/sruid.c:121]: sruid_init(): root for sruid is [ulcx-6380d27f-8fab2-] (0 / 20) 17(588466) DEBUG: [db.c:315]: db_do_init2(): connection 0x 7f96e7d58880 not found in pool 17(588466) DEBUG: db_mysql [km_my_con.c:110]: db_mysql_new_connection(): opening connection: mysql://:@10.1.128.4/kamailio 17(588466) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '10.1.128.4' (110) 17(588466) ERROR: [db.c:319]: db_do_init2(): could not add connection to the pool 17(588466) ERROR: usrloc [usrloc_mod.c:485]: child_init(): child(-1): failed to connect to database 17(588466) ERROR: [core/sr_module.c:882]: init_mod_child(): error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so) (idx: 17 rank: -1 desc: [Dialog Clean Timer]) 17(588466) ERROR: [core/pt.c:338]: fork_process(): init_child failed for process 17, pid 588466, "Dialog Clean Timer" 17(588466) ERROR: dialog [dialog.c:782]: child_init(): failed to start clean timer routine as process 17(588466) ERROR: [core/sr_module.c:882]: init_mod_child(): error while initializing module dialog (/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so) (idx: 17 rank: 0 desc: [Dialog Clean Timer]) 17(588466) ERROR: [main.c:1842]: main_loop(): error in init_child 17(588466) CRITICAL: [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f96e2f84650), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_free(323) - ignoring 17(588466) CRITICAL: [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f96e2f84900), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_malloc(293) - ignoring 17(588466) CRITICAL: [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f96e2fd50b0), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_free(323) - ignoring 17(588466) CRITICAL: [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f96e2f820e0), called from tls: tls_init.c: ser_free(323), first free tls: tls_init.c: ser_free(323) - ignoring - Debian 11.5 - libmariadb version 3.1.16 -modules: auth_db, permissions, domain, rtpengine, dispatcher, dialog, uac, carrierroute, topos, acc - kamailio 5.6.2 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Error in RTP engine setup
Hello! It is likely that the kernel module is not loaded. вт, 4 окт. 2022 г. в 15:25, palany : > I have installed RTPENGINE on debian 11 and on starting it I am getting > the > following errors. > > Oct 04 12:14:39 ip-172-31-26-106 systemd[1]: Starting NGCP RTP/media Proxy > Daemon... > Oct 04 12:14:39 ip-172-31-26-106 ngcp-rtpengine-iptables-setup[4655]: > /usr/sbin/ngcp-rtpengine-iptables-setup: 15: > /usr/libexec/rtpengine/rtpengine-get-table: not found > Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [crypto] Generating > new DTLS certificate > Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: ERR: [core] FAILED TO > CREATE KERNEL TABLE 0 (No such file or directory), KERNEL FORWARDING > DISABLED > Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [core] Startup > complete, version 11.1.0.0+0~mr11.1.0.0 git-master-c53f213f > Oct 04 12:14:39 ip-172-31-26-106 systemd[1]: Started NGCP RTP/media Proxy > Daemon. > Oct 04 12:14:39 ip-172-31-26-106 rtpengine[4659]: INFO: [http] Websocket > listener thread running > > How do I solve this. > > Best Regards, > > Palany Chakadya > > > > > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Keepalive dialog with SIP/TLS OPTIONS
Hello!
In order to keep the SIP/TCP connection alive for some specific clients
(more precisely, specific firewalls) in long calls, I use periodic SIP
OPTIONS probes through the dialog module.
I noticed that when subscribers are using the SIP/TLS protocol, such
keepalives are not sent (with SIP/UDP and SIP/TCP working well).
I did not detect any obvious errors in the debug mode.
Are there any ideas why the messages are not being sent for SIP/TLS leg?
loadmodule "dialog.so"
modparam("dialog", "db_url", "DBURL")
modparam("dialog", "db_mode", 1)
modparam("dialog", "ka_timer", 5)
modparam("dialog", "ka_interval", 30)
modparam("dialog", "ka_failed_limit", 2)
modparam("dialog", "send_bye", 1)
modparam("dialog", "track_cseq_updates", 1)
modparam("dialog", "default_timeout", 7205)
-
dlg_manage();
dlg_set_property("ka-src");
dlg_set_property("ka-dst");
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Core variable with from userinfo value of sip uri
Hello! It was accidentally noticed that the variable $fU gets the user part of userinfo SIP URI (although it is logical and described in the document RFC2543). I got message below and my spam filter based on $fU passed it inside the network, as $fU was test From: ;tag=123456 Sure I can filter it through a regular expression, but maybe it's worth adding another core variable with the userinfo value? SIP-URL = "sip:" [ userinfo "@" ] hostport url-parameters [ headers ] userinfo= user [ ":" password ] -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] slow timer too slow: overflow
Hello!
After some time, Kamailio stops processing incoming messages.
slow timer too slow: overflow messages appear in the log (I suspect that
the problem is related to the rtimer module)
Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS
2b45547f33f5203f-4091@10.10.10.10} [core/mem/q_malloc.c:430]:
qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core:
core/rvalue.c: rval_new_empty(246), module: core; Free fragment>
Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS
2b45547f33f5203f-4091@10.10.10.10} [core/rvalue.c:253]:
rval_new_empty(): could not allocate private memory from pkg pool
Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: [core/timer.c:936]:
timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023)
Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS
34618af41c3866bc-16408@10.10.10.20} [core/mem/q_malloc.c:297]:
qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found!
Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS
34618af41c3866bc-16408@10.10.10.20} [core/mem/q_malloc.c:430]:
qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core:
core/rvalue.c: rval_new_empty(246), module: core; Free fragment no>
Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS
34618af41c3866bc-16408@10.10.10.20} [core/rvalue.c:253]:
rval_new_empty(): could not allocate private memory from pkg pool
Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: [core/timer.c:936]:
timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023)
Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ
1c18959d07113951-203309@10.10.10.30} [core/mem/q_malloc.c:297]:
qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found!
Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ
1c18959d07113951-203309@10.10.10.30} [core/mem/q_malloc.c:430]:
qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core:
core/rvalue.c: rval_new_empty(246), module: core; Free fragment no>
Please point me out where the source of the problem could be.
version: kamailio 5.6.1 (x86_64/linux)
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [UAC] How to get the outbound registration status of uac.reg_active?
This is a bit not what I would like, the function above (uac.r.uac.reg_info) gives information on a specific l_uuid and it does not directly correlate with the activation/deactivation of the uac module (you need to wait for the registration to expire to understand). ср, 27 июл. 2022 г. в 14:03, Henning Westerholt : > Hello, > > > > this do not work for you? > > > > > https://kamailio.org/docs/modules/stable/modules/uac.html#uac.r.uac.reg_info > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of *Denys > Pozniak > *Sent:* Wednesday, July 27, 2022 10:16 AM > *To:* Kamailio (SER) - Users Mailing List > *Subject:* [SR-Users] [UAC] How to get the outbound registration status > of uac.reg_active? > > > > Hello! > > > > I have several Kamailio sharing a common uacreg table and use the RPC > interface to enable and disable outgoing registration on nodes depending on > the cluster status: > > *kamcmd uac.reg_active 0 kamcmd uac.reg_active 1* > > > https://kamailio.org/docs/modules/stable/modules/uac.html#uac.r.uac.reg_active > > > > How can I get the current status of uac outbound registration (to get 0 or > 1)? > > > > -- > > > > BR, > > Denys Pozniak > > > > > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] [UAC] How to get the outbound registration status of uac.reg_active?
Hello! I have several Kamailio sharing a common uacreg table and use the RPC interface to enable and disable outgoing registration on nodes depending on the cluster status: *kamcmd uac.reg_active 0kamcmd uac.reg_active 1* https://kamailio.org/docs/modules/stable/modules/uac.html#uac.r.uac.reg_active How can I get the current status of uac outbound registration (to get 0 or 1)? -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] iterate trough all Record-Route values via @hf_value.Record_Route
Hey! Try this one: *$(hdr(name)[N])* - represents the body of the N-th header identified by 'name'. вт, 19 июл. 2022 г. в 15:49, Patrick Karton : > Hello All, > > i would to iterate through all ips in Record-Route > through @hf_value.Record_Route. > > if i put static index like @hf_value.Record_Route[0] it works. > > but $var(i) = 0; @hf_value.Record_Route[$var(i)] does not work. > > is there a way to get the count of all headers values > through @hf_value.Record_Route > > For example i would like to iterate through all Record-Route Values if i > receive it like this > > Record-Route: > Record-Route: , > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Effect of GRUU on the behavior of loose_route()
Content-Length: 0 DEBUG: 1(11753) DEBUG: rr [loose.c:85]: is_preloaded(): is_preloaded: No 1(11753) DEBUG: [core/socket_info.c:646]: grep_sock_info(): checking if host==us: 13==13 && [2.2.2.2] == [2.2.2.2] 1(11753) DEBUG: [core/socket_info.c:649]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 1(11753) DEBUG: [core/forward.c:429]: check_self(): host (0: 2.2.2.2:5060) == me 1(11753) DEBUG: rr [loose.c:676]: after_strict(): Next hop: 'sip:2.2.2.2;lr=on;nat=yes;did=3f8.6a83' is loose router 1(11753) DEBUG: rr [loose.c:726]: after_strict(): The last route URI: 'sip:2.2.2.2;lr=on;nat=yes;did=3f8.6a83' 1(11753) DEBUG: rr [rr_cb.c:95]: run_rr_callbacks(): callback id 1 entered with 1(11753) DEBUG: path [path.c:397]: path_rr_callback(): no received parameter in route header 1(11753) DEBUG: rr [rr_cb.c:95]: run_rr_callbacks(): callback id 0 entered with 1(11753) DEBUG: rr [record.c:977]: add_rr_param(): rr_param_buf=<;did=3f8.6a83> 1(11753) DEBUG: siputils [checks.c:123]: has_totag(): totag found 1(11753) DEBUG: siputils [checks.c:123]: has_totag(): totag found 1(11753) DEBUG: tm [t_lookup.c:1329]: t_newtran(): msg (0x7efe343f4998) id=11/11753 global id=10/11753 T start=0x 1(11753) DEBUG: tm [t_lookup.c:498]: t_lookup_request(): start searching: hash=57361, isACK=1 1(11753) DEBUG: tm [t_lookup.c:456]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK110e.a47bb0e8f6d6d99a10ae36eb25d2f665.0] 1(11753) DEBUG: tm [t_lookup.c:675]: t_lookup_request(): no transaction found 1(11753) DEBUG: tm [t_funcs.c:286]: t_relay_to(): forwarding ACK statelessly -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Massive uploading of aliases through a dbtext
Do I understand correctly that if db_text is in caching mode ( db_mode=0 ),
then changes in the dbtext/domain file are not updated by the *kamcmd
domain.reload* command?
чт, 13 янв. 2022 г. в 12:17, Denys Pozniak :
> Thanks! Now it works!
>
> чт, 13 янв. 2022 г. в 11:55, Daniel-Constantin Mierla :
>
>> Hello,
>>
>> alias_db is for user aliases, not for host aliases. For multi-domain
>> support with database storage, use domain module and set register myself
>> mod param.
>>
>> Anyhow, the domains won't show up in core.aliases_list rpc response,
>> that's only for host aliases set in config file, but domain module has also
>> rpc command for listing its records.
>>
>> Cheers,
>> Daniel
>> On 13.01.22 10:49, Denys Pozniak wrote:
>>
>> Hello!
>>
>> I need help uploading a list of aliases through a dbtext to use them via
>> myself.
>> It is likely that there is some configuration problem:
>>
>> *loadmodule "db_text.so"*
>>
>>
>> *modparam("db_text", "db_mode", 1) modparam("db_text", "emptystring", 1) *
>>
>>
>>
>> *loadmodule "alias_db.so" modparam("alias_db", "db_url",
>> "text:///etc/kamailio/dbtext") *
>>
>>
>>
>>
>>
>> *[root@kamailio]$ cat dbtext/dbaliases id(int,auto)
>> alias_username(string) alias_domain(string) username(string) domain(string)
>> 1::sip.test.local:: *
>>
>>
>>
>>
>>
>>
>> *[root@kamailio]$ kamcmd core.aliases_list { myself_callbacks:
>> yes aliases: { } } *
>>
>> If done through a script (alias=sip.test.local), then everything works
>> fine:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *[root@kamailio]$ kamcmd core.aliases_list { myself_callbacks:
>> yes aliases: { alias: {
>> proto: * address: sip.test.local
>> port: * } } } *
>>
>>
>> --
>>
>> BR,
>> Denys Pozniak
>>
>>
>>
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> * sr-users@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the
>> sender!
>> Edit mailing list options or unsubscribe:
>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
>> www.linkedin.com/in/miconda
>> Kamailio Advanced Training - Online
>> Feb 21-24, 2022 (America Timezone)
>> * https://www.asipto.com/sw/kamailio-advanced-training-online/
>>
>>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Massive uploading of aliases through a dbtext
Thanks! Now it works!
чт, 13 янв. 2022 г. в 11:55, Daniel-Constantin Mierla :
> Hello,
>
> alias_db is for user aliases, not for host aliases. For multi-domain
> support with database storage, use domain module and set register myself
> mod param.
>
> Anyhow, the domains won't show up in core.aliases_list rpc response,
> that's only for host aliases set in config file, but domain module has also
> rpc command for listing its records.
>
> Cheers,
> Daniel
> On 13.01.22 10:49, Denys Pozniak wrote:
>
> Hello!
>
> I need help uploading a list of aliases through a dbtext to use them via
> myself.
> It is likely that there is some configuration problem:
>
> *loadmodule "db_text.so"*
>
>
> *modparam("db_text", "db_mode", 1) modparam("db_text", "emptystring", 1) *
>
>
>
> *loadmodule "alias_db.so" modparam("alias_db", "db_url",
> "text:///etc/kamailio/dbtext") *
>
>
>
>
>
> *[root@kamailio]$ cat dbtext/dbaliases id(int,auto) alias_username(string)
> alias_domain(string) username(string) domain(string) 1::sip.test.local:: *
>
>
>
>
>
>
> *[root@kamailio]$ kamcmd core.aliases_list { myself_callbacks: yes
> aliases: { } } *
>
> If done through a script (alias=sip.test.local), then everything works
> fine:
>
>
>
>
>
>
>
>
>
>
>
>
> *[root@kamailio]$ kamcmd core.aliases_list { myself_callbacks: yes
> aliases: { alias: { proto:
> * address: sip.test.local
> port: * } } } *
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> * sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
> Edit mailing list options or unsubscribe:
> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
> www.linkedin.com/in/miconda
> Kamailio Advanced Training - Online
> Feb 21-24, 2022 (America Timezone)
> * https://www.asipto.com/sw/kamailio-advanced-training-online/
>
>
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Massive uploading of aliases through a dbtext
Hello!
I need help uploading a list of aliases through a dbtext to use them via
myself.
It is likely that there is some configuration problem:
*loadmodule "db_text.so"*
*modparam("db_text", "db_mode", 1)modparam("db_text", "emptystring", 1)*
*loadmodule "alias_db.so"modparam("alias_db", "db_url",
"text:///etc/kamailio/dbtext")*
*[root@kamailio]$ cat dbtext/dbaliasesid(int,auto) alias_username(string)
alias_domain(string) username(string) domain(string)1::sip.test.local::*
*[root@kamailio]$ kamcmd core.aliases_list{myself_callbacks: yes
aliases: {}}*
If done through a script (alias=sip.test.local), then everything works fine:
*[root@kamailio]$ kamcmd core.aliases_list{myself_callbacks: yes
aliases: {alias: {proto: *
address: sip.test.localport: *
}}}*
--
BR,
Denys Pozniak
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Features of Kamailio as SBC
Hello! We also have a similar experience with the sems, in the end, we came to the conclusion that under heavy load and passing the RTP, it behaves unstable. Now we use sems only for SIP signaling processing and in conjunction with Kamailio and Rtpengine, and in this mode it is excellent! If someone needs packages for Centos 7, then you can use the repository (the building is triggered for each commit into sems-server master): https://copr.fedorainfracloud.org/coprs/denysp/sems/ вс, 26 дек. 2021 г. в 11:28, Mojtaba : > I also have written some applications which use some of its SBC > capabilities. > I feel so happy that the SEMS works powerfully in signaling mode. For some > reason, I don't anchor RTP sessions to SEMS and use a media server in > Kamailio (LRKProxy). > Because of the elasticity of each item, you might find some unusual manner > in Sems, they are quite a topic that has no effect on Sems's overall > behavior. For these cases, you can have contributions in solving them or > using Kamailio. > > On Sun, Dec 26, 2021 at 11:17 AM Juha Heinanen wrote: > >> Alex Balashov writes: >> >> > I use SEMS myself and like it very much. It’s sad to see it fall away >> > and I regret that I personally lack the resources to prop it >> > up. Nevertheless, I think it’s a fact that it’s not a dependable input >> > in a future-proof way for lack of active public development and (much) >> > maintenance. I think in the most optimistic view it is merely “very >> > unpolished”. >> >> I too feel sad that SEMS development has stalled to minimal maintenance >> level. I have written numerous applications from scratch using SEMS's >> DSM scripts (call center, conference, voicemail, ivr apps, charging, >> ...) plus I'm using some of its SBC capabilities. As long as there is >> no alternative, for me it is the only way to go. >> >> -- Juha >> >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> * sr-users@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > > > -- > --Mojtaba Esfandiari.S > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Issue Bug in SEMS (transparent SBC profile)
Did you check the documentation (core information is relevant)? https://frafosdocs.s3-eu-west-1.amazonaws.com/frafos_abc_sbc_handbook.pdf пт, 17 дек. 2021 г. в 12:28, Mojtaba : > Any update on this? > > > On Sat, Dec 11, 2021, 13:56 Mojtaba wrote: > >> Hello, >> Why in SEMS, some changes (in transparent SBC profile) in sip headers do >> not apply. For example i want to change CSeq or Contact header like this: >> # transparent SBC profile >> # defaults: transparent >> RURI=$r >> From=$f >> To=$t >> Call-ID=$ci_leg2 >> CSeq=$H(CSeq) >> Contact=$H(Contact) >> >> When I run SEMS, CSeq and Contact do not change, while other headers >> change. >> >> [#7fc688d7b1c0/9379] [onLoad, SBC.cpp:189] INFO: loading SBC call >> profiles from '/usr/local/etc/sems/etc/' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:418] >> INFO: SBC: loaded SBC profile 'mo' - MD5: d6a2c29084043edde1357231f6866737 >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:423] >> INFO: SBC: RURI = '$r' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:424] >> INFO: SBC: RURI-host = '' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:425] >> INFO: SBC: From = '$f' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:426] >> INFO: SBC: To = '$t' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:431] >> INFO: SBC: Call-ID = '$ci_leg' >> [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:434] >> INFO: SBC: force outbound proxy: yes >> This issue caused the Asterisk could not pass the Authentication process >> in "match_req_to_dialog" function because the CSeq is the same as the >> dialogs. So the Asterisk thought this message was a LOOP message. >> Has anybody encountered this issue in SEMS? How did you solve this? I >> know there are some ways for doing this with Kamailio, But i focused on >> issues in SEMS >> >> With Best Regards >> >> *-- Mojtaba Esfandiari.S* >> >> *-- PhD student and Research Affiliate, * >> >> *-- Technical Manager at IP-PBX Laboratory, Ferdowsi University of >> Mashhad, Iran.* >> >> -- Address: IP-PBX Lab., Engineering Faculty, Ferdowsi University Main >> Campus, Mashhad, Iran. >> >> -- Tel: +98-51-38763635 >> >> -- Mobile: +98-915-117-6713 >> >> ______ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [uac] How to force outbound registration?
As far as I tested, after unregistering the account, new registration no longer occurs regardless of the reg_timer_interval. What command should be used to enable it again? ср, 24 нояб. 2021 г. в 15:40, Sergiu Pojoga : > You can't immediately register back. Registration scheduler runs at > certain intervals, defined by reg_timer_interval modparam. > > > https://kamailio.org/docs/modules/stable/modules/uac.html#uac.p.reg_timer_interval > > Regards, > --Sergiu > > On Wed, Nov 24, 2021 at 7:11 AM Denys Pozniak > wrote: > >> Hello! >> >> In some cases, I need to forcibly unregister a remote SIP account through >> uac module, and then immediately register. >> To unregister I can use the command: >> *kamcmd uac.reg_unregister l_uuid * >> >> But it's not clear how to immediately register back. For example, these >> commands do not give the desired effect: >> *kamcmd uac.reg_enable l_uuid * >> *kamcmd uac.reg_reload* >> >> [root@kamailio]# kamailio -V >> version: kamailio 5.5.2 (x86_64/linux) 55e232 >> >> -- >> BR, >> Denys Pozniak >> >> >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> * sr-users@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] install latest sems-server on debian 10 buster
@Mojtaba if not difficult, could you add a description of the installation process to the wiki? https://github.com/sems-server/sems/wiki вс, 15 авг. 2021 г. в 11:06, Mojtaba : > After several attempts to install SEMS in Debian10, it was done > successfully. > The issue was strang but I had to install "python3.7-dev > python3-distutils", and update PATH in Linux. > Thanks > > On Thu, Aug 12, 2021 at 12:32 PM Mojtaba wrote: > >> I installed the master branch of SEMS(1.7.0~dev) as you suggested. I used >> these commands: >> $ git clone https://github.com/sems-server/sems.git >> $ cd sems/ >> $ ln -s pkg/deb/buster ./debian >> $ dch -v 1.7.0~dev "SEMS 1.7.0~dev release" >> $ dpkg-buildpackage -rfakeroot -us -uc >> >> Does it need to run "make & make install" commands after above commands >> or not? because i got these error as i told >> >> usr/bin/ld: AmDtmfDetector.o: in function >> `AmSpanDSPInbandDtmfDetector::streamPut(unsigned char const*, unsigned int, >> unsigned long long)': >> ./core/AmDtmfDetector.cpp:768: undefined reference to `dtmf_rx' >> /usr/bin/ld: AmDtmfDetector.o: in function >> `AmSpanDSPInbandDtmfDetector::AmSpanDSPInbandDtmfDetector(AmKeyPressSink*, >> int)': >> ./core/AmDtmfDetector.cpp:749: undefined reference to `dtmf_rx_init' >> /usr/bin/ld: AmDtmfDetector.o: in function >> `AmSpanDSPInbandDtmfDetector::~AmSpanDSPInbandDtmfDetector()': >> ./core/AmDtmfDetector.cpp:763: undefined reference to `dtmf_rx_free' >> /usr/bin/ld: AmDtmfDetector.o: in function >> `AmSpanDSPInbandDtmfDetector::AmSpanDSPInbandDtmfDetector(AmKeyPressSink*, >> int)': >> ./core/AmDtmfDetector.cpp:754: undefined reference to >> `dtmf_rx_set_realtime_callback' >> collect2: error: ld returned 1 exit status >> make[1]: *** [Makefile:115: sems] Error 1 >> make[1]: Leaving directory '/usr/src/sems-master/core' >> make: *** [Makefile:38: install] Error 2 >> >> >> >> >> >> >> >> >> On Tue, Aug 10, 2021 at 4:24 PM Juha Heinanen wrote: >> >>> Mojtaba writes: >>> >>> > Would you please let me know about what version of sems you use? >>> > Please tell me more about it. >>> >>> Master branch of https://github.com/sems-server/sems. >>> >>> -- Juha >>> >>> __ >>> Kamailio - Users Mailing List - Non Commercial Discussions >>> * sr-users@lists.kamailio.org >>> Important: keep the mailing list in the recipients, do not reply only to >>> the sender! >>> Edit mailing list options or unsubscribe: >>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >> >> -- >> --Mojtaba Esfandiari.S >> > > > -- > --Mojtaba Esfandiari.S > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] which is better for B2BUA
@Mojtaba > Just a question, Let me know which scenario is like that you use? --- --- - this server has 2 interfaces: local and public - controls RTPengine and rewrites SDP пн, 2 авг. 2021 г. в 20:36, Carsten Bock : > Hi, > > We don't do RTP on this setup, as we only use it for connecting different > Consumer-Voice-Platforms with various upstream carriers. > > We did trigger RTPEngine once from Kamailio for connecting IPv6 to IPv4 > carriers, but we've removed that meanwhile. > > Thanks, > Carsten > > Carsten Bock I CTO & Founder > > > > > ng-voice GmbH > > Trostbrücke 1 I 20457 Hamburg I Germany > T +49 40 524 75 93-40 | M +49 179 2021244 I www.ng-voice.com > > Registry Office at Local Court Hamburg, HRB 120189 > Managing Directors: Dr. David Bachmann, Carsten Bock > > Mojtaba schrieb am Mo., 2. Aug. 2021, 13:04: > >> Hi Carsten, >> Yes, Using SEMS as B2BUA would be good plan, But just a question, Do you >> skip RTP flow to SEMS, too? >> Thanks >> >> On Mon, Aug 2, 2021 at 1:46 PM Carsten Bock wrote: >> >>> Hi, >>> >>> we even take it one step further: >>> Incoming <-> Kamailio <-> SEMS (B2BUA) <-> Kamailio <-> Interconnect >>> >>> We do this, to limit the required functionality of SEMS to be a B2BUA >>> and we do all further stuff (Number Portability Lookup, Least-Cost-Routing, >>> Message Manipulation, ..) on Kamailio. >>> >>> I almost hate to say this as Kamailian, but one more alternative to SEMS >>> worth checking is OpenSIPS and its b2b modules. >>> >>> Thanks, >>> Carsten >>> -- >>> Carsten Bock I CTO & Founder >>> >>> ng-voice GmbH >>> >>> Trostbrücke 1 I 20457 Hamburg I Germany >>> T +49 40 524 75 93-40 | M +49 179 2021244 I www.ng-voice.com >>> >>> Registry Office at Local Court Hamburg, HRB 120189 >>> Managing Directors: Dr. David Bachmann, Carsten Bock >>> >>> >>> Am Sa., 31. Juli 2021 um 23:24 Uhr schrieb Mojtaba : >>> >>>> Thanks Guys for your comments. >>>> @Gerry, I agree with you, I have a few experiences working with Yate, >>>> It could work great in enterprise solutions. Thanks >>>> @Denys, Thanks for sharing your experience, Although its configurations >>>> look complicated, But in signaling, It would work great. >>>> Just a question, Let me know which scenario is like that you use? >>>> >>>> --- >>>> or >>>> --- >>>> >>>> >>>> >>>> On Fri, Jul 30, 2021 at 9:15 AM Denys Pozniak >>>> wrote: >>>> >>>>> Hello! >>>>> We used sems to interconnect with external operators. But with a heavy >>>>> call load and with the processing of the media stream, it often crashed. >>>>> Now we use Kamailio / Rtpengine for media stream processing and sems >>>>> for signaling processing. We install all this on one server. It probably >>>>> looks complicated, but it works great. >>>>> >>>>> вт, 27 июл. 2021 г. в 16:10, Gerry | Rigatta : >>>>> >>>>>> Hi, >>>>>> >>>>>> Some comments on Yate. >>>>>> >>>>>> Yate works well as a B2BUA. It is very performant and stable. It can >>>>>> bypass media dynamically. >>>>>> >>>>>> The main beauty of Yate is how it processes calls internally. Yate >>>>>> represents calls internally as messages with parameters (caller, callee, >>>>>> codecs …) . While the call passes from the incoming to the outgoing call >>>>>> leg the message parameters can be manipulated by different yate modules. >>>>>> In >>>>>> turn, message parameters can trigger yate modules for some actions, e.g. >>>>>> start a sip call. >>>>>> >>>>>> The Yate internal messaging allows to build with little code complex >>>>>> call logic. E.g a mysql query result can be used directly for routing. >>>>>> E,g, >>>>>> you can build a switch just with a couple of mysql procedures. >>>>>> >>>>>> Cheers >>>>>> >>>>>> Gerry >>>>>> >>>>>> >
Re: [SR-Users] which is better for B2BUA
Hello! We used sems to interconnect with external operators. But with a heavy call load and with the processing of the media stream, it often crashed. Now we use Kamailio / Rtpengine for media stream processing and sems for signaling processing. We install all this on one server. It probably looks complicated, but it works great. вт, 27 июл. 2021 г. в 16:10, Gerry | Rigatta : > Hi, > > Some comments on Yate. > > Yate works well as a B2BUA. It is very performant and stable. It can > bypass media dynamically. > > The main beauty of Yate is how it processes calls internally. Yate > represents calls internally as messages with parameters (caller, callee, > codecs …) . While the call passes from the incoming to the outgoing call > leg the message parameters can be manipulated by different yate modules. In > turn, message parameters can trigger yate modules for some actions, e.g. > start a sip call. > > The Yate internal messaging allows to build with little code complex call > logic. E.g a mysql query result can be used directly for routing. E,g, you > can build a switch just with a couple of mysql procedures. > > Cheers > > Gerry > > > > On 27 Jul 2021, at 11:35, Karsten Horsmann wrote: > > Hello, > > just for the records: > > You can also bypass media with FreeSWITCH if you want. The overall > handling of many parallel calls is still not so high like in SEMS. > > https://freeswitch.org/confluence/display/FREESWITCH/Proxy+Media > This is also possible on a per Call base. > > And you can use different profiles as well in FreeSWITCH. > > Asterisk Experts will have more knowledge what is possible there, and > maybe someone told us whats going on with Yate. > > Kind regards > Karsten > > Am Di., 13. Juli 2021 um 10:11 Uhr schrieb Mojtaba : > >> >> Hello there, >> According to , >> https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html, >> which talked about B2BUA (just signalling) in Kamailio. >> As i have experienced working with SEMS, freeswitch and Kamailio while >> using B2BUA feature, Each of them have pros and cons: >> 1- The sems is a light sip engine server with several applications (like >> as sbc) for using b2bua. All incoming and outgoing calls could go to sems >> server for doing b2bua like this: >> >> Incoming<===>Kamailio<>Sems<>Kamailio<===>outgoing >> >> 2- In sems, you could disable rtp realying. It forces sems to work just >> as b2bua without anchoring RTP >> 3- Easy to use different active profiles in routing. >> >> __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] handle_ruri_alias() and multiple aliases
Thank you! I will report on the results of the testing. вт, 1 июн. 2021 г. в 10:39, Daniel-Constantin Mierla : > Hello, > > I also agree that it should be fixed in signalling processing rules, the > proxy that is not next hop after NAT route should not add alias parameter. > > However, I also faced similar multi-alias issues a few times in the > past, when the proxy I controlled was the one that had to add the alias > and had to do some tricks in the config to get it working until the > issue was mitigated between companies. Iirc, in my case the issue was > more complex as the other proxy didn't consume it properly always. > > Anyhow, from that moment I had it in my to-do list to check what takes > to add a mode to consume either first or last alias parameter, and since > same issue surfaced again in another corner of the world, I just looked > and updating the code was not complex. Therefore I just added in master > branch an optional mode parameter to handle_ruri_alias() to be able to > specify which one (first or last) should be consumed. > > Testing and feedback is very appreciated! > > Cheers, > Daniel > > On 01.06.21 00:32, Alex Balashov wrote: > > On 5/31/21 6:27 PM, Ovidiu Sas wrote: > > > >> You can adjust your script to use aliases only when needed. We want > >> clean and simple signalling. > > > > I strongly agree with Ovidiu. This is really the solution. > > > > -- > > Alex Balashov | Principal | Evariste Systems LLC > > > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) > * https://www.asipto.com/sw/kamailio-advanced-training-online/ > > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] handle_ruri_alias() and multiple aliases
Thanks, Alex and Ovidiu, Yes, I agree that *set_contact_alias ()* should only be used once. The essence of the problem is that all external connections are processed as for NAT by default in my script. Is there any reason for improving the *handle_ruri_alias ()* function so that we can specify the ordinal number of the alias parameter? пн, 31 мая 2021 г. в 21:10, Ovidiu Sas : > If there are two proxies involved, only one should handle aliases (the > one that is communicating directly with the endpoint). > If a Contact has a private IP, but the request is coming from a proxy > that is in charge of NAT, then the Contact should not be altered. When > you route back in dialog requests, it is ok to have a private IP in > RURI and proper Route headers, The next SIP hop (the other proxy) will > take care of properly routing the request. > > Regards, > Ovidiu Sas > > On Mon, May 31, 2021 at 1:53 PM Denys Pozniak > wrote: > > > > Hello! > > > > I need help understanding how the handle_ruri_alias() function works. > > Call-flow: Upstream operator -> Kamailio Proxy -> Edpoint. > > > > The upstream operator in the initial SIP INVITE in the Contact field > sends us an alias parameter, in turn, our Kamailio Proxy adds its own too. > > The Contact after the Proxy looks something like this: > > > > Contact: ;alias=10.0.0.115~5060~1;alias=3.3.3.3~5060~1> > > > > When the Endpoint sends us a SIP BYE, then the handle_ruri_alias() > absorbs not the last alias, but the first one, and this leads to the > incorrect formation of a $du. > > The RURI after the Proxy looks something like this: > > > > Request-Line: BYE sip:10.0.0.115:5060;alias=3.3.3.3~5060~1 SIP/2.0 > > > > The first thing that comes to mind is a modification of the original > Contact field with storing it's within a dialogue ... > > > > Is it possible to elegantly solve this problem? > > > > -- > > > > BR, > > Denys Pozniak > > > > > > __ > > Kamailio - Users Mailing List - Non Commercial Discussions > > * sr-users@lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to > the sender! > > Edit mailing list options or unsubscribe: > > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > VoIP Embedded, Inc. > http://www.voipembedded.com > > __ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] handle_ruri_alias() and multiple aliases
Hello! I need help understanding how the *handle_ruri_alias()* function works. *Call-flow:* Upstream operator -> Kamailio Proxy -> Edpoint. The upstream operator in the initial SIP INVITE in the Contact field sends us an alias parameter, in turn, our Kamailio Proxy adds its own too. The Contact after the Proxy looks something like this: *Contact: * When the Endpoint sends us a SIP BYE, then the *handle_ruri_alias()* absorbs not the last alias, but the first one, and this leads to the incorrect formation of a $du. The RURI after the Proxy looks something like this: *Request-Line: BYE sip:10.0.0.115:5060;alias=3.3.3.3~5060~1 SIP/2.0* The first thing that comes to mind is a modification of the original Contact field with storing it's within a dialogue ... Is it possible to elegantly solve this problem? -- BR, Denys Pozniak __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Need help in transforming an SDP string through a re.subst
Hello!
Thanks for the answer.
But if we abstract, it’s an SDP. How to transform a string containing #
character?
пн, 1 мар. 2021 г. в 13:05, Daniel-Constantin Mierla :
> Hello,
>
> there should be a function to remove a line from sdp by matching on its
> prefix (in sdpops?!?), might be easier to use that one.
>
> Cheers,
> Daniel
> On 23.02.21 19:51, Denys Pozniak wrote:
>
> Hello!
>
> There is a task to remove a fragment (*a=rtpmap:8 PCMA/8000#015#012*)
> from the SDP string generated by the rtpengine.
>
>
> *v=0#015#012o=kw 1614043485 1614043486 IN IP4
> 185.19.237.77#015#012s=kw#015#012c=IN IP4 1.1.1.1#015#012t=0
> 0#015#012m=audio 31828 RTP/AVP 0 8 101#015#012a=silenceSupp:off - - -
> -#015#012a=direction:both#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
> PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
> 0-16#015#012a=sendrecv#015#012a=rtcp:31829#015#012a=ptime:20#015#012 *
>
> The most logical option seems to be using the re.subst transformation, but
> so far no success.
> $avp(write_sdp_pv) = $(avp(write_sdp_pv){re.subst,/a=rtpmap:8
> PCMA\/8000%23015%23012//s});
>
> Сan there be an alternative or am I doing something wrong with the
> re.subst?
>
> --
>
> BR,
> Denys Pozniak
>
>
>
> ___
> Kamailio (SER) - Users Mailing
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
> www.linkedin.com/in/miconda
> Funding: https://www.paypal.me/dcmierla
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Need help in transforming an SDP string through a re.subst
Hello!
There is a task to remove a fragment (*a=rtpmap:8 PCMA/8000#015#012*) from
the SDP string generated by the rtpengine.
*v=0#015#012o=kw 1614043485 1614043486 IN IP4
185.19.237.77#015#012s=kw#015#012c=IN IP4 1.1.1.1#015#012t=0
0#015#012m=audio 31828 RTP/AVP 0 8 101#015#012a=silenceSupp:off - - -
-#015#012a=direction:both#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8
PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
0-16#015#012a=sendrecv#015#012a=rtcp:31829#015#012a=ptime:20#015#012*
The most logical option seems to be using the re.subst transformation, but
so far no success.
$avp(write_sdp_pv) = $(avp(write_sdp_pv){re.subst,/a=rtpmap:8
PCMA\/8000%23015%23012//s});
Сan there be an alternative or am I doing something wrong with the re.subst?
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to drop 200 OK in onreply_route ?
> I do not understand what is difficult, to configure the next hop
application to send 100 trying? Or maybe you can provide a diagram of how
sip traffic is routed on your case.
1) Diagram below is the case I described in the initial email. Here you can
see incoming SIP PUBLISH and 3 forked legs towards Presence Servers.
As soon as Kamailio Proxy receives SIP PUBLISH it sends 200 Ok back.
The Presence Server that has active subscription answers with 200 OK
otherwise 404 Not Found.
So the question was how to drop sending 200 OK (and any other replies) from
Proxy to the left side.
[image: image.png]
2) When I drop 200 OK in *reply_route*, Kamailio Proxy retransmits SIP
PUBLISH to Presence Server.
[image: image.png]
чт, 4 февр. 2021 г. в 14:55, David Villasmil :
> I think he’s trying to reply to the client immediately with a 200 and
> consume and not forward the 200 coming from the presence servers.
>
> On Thu, 4 Feb 2021 at 12:43, Daniel-Constantin Mierla
> wrote:
>
>>
>> On 04.02.21 12:59, Denys Pozniak wrote:
>>
>> > If you need to stop the retransmission, a 100 trying should be sent
>> instead of 200ok. Can you reconfigure the next hop to do that? Or is it out
>> of your control?
>> Looks it is difficult to do this as Kamailio Proxy forks via
>> append_branch() incoming SIP PUBLISH to all Presence Servers.
>>
>>
>> I do not understand what is difficult, to configure the next hop
>> application to send 100 trying? Or maybe you can provide a diagram of how
>> sip traffic is routed on your case.
>>
>>
>> And even if Presence Server answers 200 OK, the Kamailio Proxy still
>> sends a repeated SIP PUBLISH there within the fr timer.
>>
>>
>> This remark is also not clear, is the 200ok handled by Kamailio, sent
>> upstream, but then Kamailio still resends the PUBLISH?
>>
>> Cheers,
>> Daniel
>>
>>
>>
>> чт, 4 февр. 2021 г. в 13:04, Daniel-Constantin Mierla > >:
>>
>>> Hello,
>>>
>>> if the 200ok is consumed by tm, it will destroy the transaction very
>>> soon. I am not sure this is a good path to go.
>>>
>>> If you need to stop the retransmission, a 100 trying should be sent
>>> instead of 200ok. Can you reconfigure the next hop to do that? Or is it out
>>> of your control?
>>>
>>> Cheers,
>>> Daniel
>>> On 04.02.21 11:47, Denys Pozniak wrote:
>>>
>>> Hello!
>>>
>>> In the configuration below Kamailio Proxy creates a transaction for the
>>> SIP PUBLISH to get info from the HTTP server in async mode.
>>> But before creating a transaction, a synthetic 200 OK is sent, so that I
>>> need somehow to drop the real 200 OK from the upstream Presence Server.
>>> If drop 200 OK in *reply_route*, tm module starts to retransmit.
>>> Those it is necessary that the 200 OK be consumed by the tm module, but
>>> does not go further.
>>>
>>>
>>> *if ( !is_method("PUBLISH") ) { *
>>>
>>>
>>> *sl_send_reply("200", "Ok"); t_newtran(); *
>>>
>>>
>>> *$http_req(suspend) = 1; http_async_query("$var(url)",
>>> "CALLBACK"); *
>>> *}*
>>>
>>>
>>> *route[CALLBACK] { *
>>> **
>>>
>>>
>>>
>>> *t_on_reply("PUBLISH_REPLY"); route(RELAY);
>>> exit; *
>>> *}*
>>>
>>>
>>>
>>>
>>>
>>>
>>> *onreply_route[PUBLISH_REPLY] { if ( t_check_status("200") ) {
>>> drop; # Does not work!!! } } *
>>>
>>> Any advice is appreciated
>>>
>>> --
>>>
>>> BR,
>>> Denys Pozniak
>>>
>>>
>>>
>>> _______
>>> Kamailio (SER) - Users Mailing
>>> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>> --
>>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
>>> www.linkedin.com/in/miconda
>>> Funding: https://www.paypal.me/dcmierla
>>>
>>>
>>
>> --
>>
>> BR,
>> Denys Pozniak
>>
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
>> www.linkedin.com/in/miconda
>> Funding: https://www.paypal.me/dcmierla
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> --
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to drop 200 OK in onreply_route ?
> If you need to stop the retransmission, a 100 trying should be sent
instead of 200ok. Can you reconfigure the next hop to do that? Or is it out
of your control?
Looks it is difficult to do this as Kamailio Proxy forks via
append_branch() incoming SIP PUBLISH to all Presence Servers.
And even if Presence Server answers 200 OK, the Kamailio Proxy still sends
a repeated SIP PUBLISH there within the fr timer.
чт, 4 февр. 2021 г. в 13:04, Daniel-Constantin Mierla :
> Hello,
>
> if the 200ok is consumed by tm, it will destroy the transaction very soon.
> I am not sure this is a good path to go.
>
> If you need to stop the retransmission, a 100 trying should be sent
> instead of 200ok. Can you reconfigure the next hop to do that? Or is it out
> of your control?
>
> Cheers,
> Daniel
> On 04.02.21 11:47, Denys Pozniak wrote:
>
> Hello!
>
> In the configuration below Kamailio Proxy creates a transaction for the
> SIP PUBLISH to get info from the HTTP server in async mode.
> But before creating a transaction, a synthetic 200 OK is sent, so that I
> need somehow to drop the real 200 OK from the upstream Presence Server.
> If drop 200 OK in *reply_route*, tm module starts to retransmit.
> Those it is necessary that the 200 OK be consumed by the tm module, but
> does not go further.
>
>
> *if ( !is_method("PUBLISH") ) { *
>
>
> *sl_send_reply("200", "Ok"); t_newtran(); *
>
>
> *$http_req(suspend) = 1; http_async_query("$var(url)",
> "CALLBACK"); *
> *}*
>
>
> *route[CALLBACK] { *
> **
>
>
>
> *t_on_reply("PUBLISH_REPLY"); route(RELAY); exit; *
> *}*
>
>
>
>
>
>
> *onreply_route[PUBLISH_REPLY] { if ( t_check_status("200") ) {
> drop; # Does not work!!! } } *
>
> Any advice is appreciated
>
> --
>
> BR,
> Denys Pozniak
>
>
>
> ___
> Kamailio (SER) - Users Mailing
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
> www.linkedin.com/in/miconda
> Funding: https://www.paypal.me/dcmierla
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] How to drop 200 OK in onreply_route ?
Hello!
In the configuration below Kamailio Proxy creates a transaction for the SIP
PUBLISH to get info from the HTTP server in async mode.
But before creating a transaction, a synthetic 200 OK is sent, so that I
need somehow to drop the real 200 OK from the upstream Presence Server.
If drop 200 OK in *reply_route*, tm module starts to retransmit.
Those it is necessary that the 200 OK be consumed by the tm module, but
does not go further.
*if ( !is_method("PUBLISH") ) {*
*sl_send_reply("200", "Ok");t_newtran();*
*$http_req(suspend) = 1; http_async_query("$var(url)",
"CALLBACK");*
*}*
*route[CALLBACK] {*
**
*t_on_reply("PUBLISH_REPLY");route(RELAY);exit;*
*}*
*onreply_route[PUBLISH_REPLY] {if ( t_check_status("200") ) {
drop; # Does not work!!!}}*
Any advice is appreciated
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] [Presence] publ_cache=2 usage
Hello! Could somebody explain how the parameters *publ_cache=2* and *subs_db_mode* depend on each other? Do I understand correctly that only the following modes of *subs_db_mode* are allowed 0,1,2? *subs_db_mode:0 - This disables database completely. Only memory will be used. Subscriptions will not survive restart. Use this value if you need a really fast presence module and subscription persistence is not necessary or is provided by other means.1 - Write-Through scheme. Subscriptions are updated synchronously in database and in memory(used for read operations). Use this scheme if speed is not top priority, but it's important that no subscriptions will be lost during crash or reboot or if you have an external application that reads the state of the subscriptions from database and they need to be updated synchronously.2 - Write-Back scheme. This is a combination of previous two schemes. All changes are made to memory and database synchronization is done in the timer. The timer deletes all expired contacts and flushes all modified or new subscriptions to database. Use this scheme if you encounter high-load peaks and want them to process as fast as possible. Latency of this mode is much lower than latency of mode 1, but slightly higher than latency of mode 0. To control the interval at which data is flushed to database, set the db_update_period parameter.3 - DB-Only scheme. No memory cache is kept, all operations being directly performed with the database. The timer deletes all expired subscriptions from database. The mode is useful if you configure more servers sharing the same DB without any replication at SIP level. The mode may be slower due the high number of DB operation.* -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
Hello!
Thanks!
*msg_apply_changes()* works for me!
PS. Maybe it is worth adding this to the documentation, as it is not
entirely trivial?
ср, 18 нояб. 2020 г. в 12:46, David Villasmil <
david.villasmil.w...@gmail.com>:
> Isn’t “message_apply_changes” applied automatically?
>
> But I think Alfonso is talking specifically about CANCELs generated by
> Kamailio on timeouts.
>
> On Wed, 18 Nov 2020 at 09:58, Daniel-Constantin Mierla
> wrote:
>
>> Hello,
>> On 18.11.20 10:39, Denys Pozniak wrote:
>>
>> Hello!
>>
>> Call flow: FreeSWITCH --> SBC --> Edge Proxy
>>
>> In my case, the problem is related to the fact that the SBC deletes the
>> Reason header from FreeSWITCH and I am trying to recover it on the Kamailio
>> side (Edge Proxy).
>> It is especially important to recover the message: "Call completed
>> elsewhere" because this disables the missed call notification on the
>> destination phone in case of hunt-groups.
>> The option to forward the call through the stateless loop works well but
>> it complicates the logic unnecessarily.
>>
>> So would be great to have a tm function to setup custom Reason, like
>> below:
>> *...*
>>
>> *t_cancel_reason("Reason: SIP ;cause=200 ;text=\"Call completed
>> elsewhere\"\r\n"); t_relay();*
>> **
>>
>> iirc, the Reason header should be propagated if it is in incoming CANCEL,
>> so for this particular case, it should work if you do:
>>
>>
>> if(is_method("CANCEL")) {
>>
>> append_hf("Reason: ...\r\n");
>>
>> msg_apply_changes();
>>
>> t_realy();
>>
>> exit;
>>
>> }
>>
>> Cheers,
>> Daniel
>>
>>
>> ср, 18 нояб. 2020 г. в 11:16, Daniel-Constantin Mierla > >:
>>
>>> Same question here like in my other reply:
>>>
>>> *
>>> https://lists.kamailio.org/pipermail/sr-users/2020-November/23.html
>>>
>>> How do you expect to fill the value of the header?
>>>
>>> Cheers,
>>> Daniel
>>> On 17.11.20 19:20, David Villasmil wrote:
>>>
>>> And on internally generated CANCELs
>>>
>>> On Tue, 17 Nov 2020 at 14:20, Denys Pozniak
>>> wrote:
>>>
>>>> Hello!
>>>>
>>>> We need to append our own Reason header for the "relayed" CANCEL
>>>> message, if it is not on the input.
>>>> Like below:
>>>>
>>>>
>>>> *if ( is_method("CANCEL") && !is_present_hf("Reason") ) { *
>>>> * append_hf("Reason: );*
>>>> * t_relay();*
>>>> *...*
>>>>
>>>>
>>>>
>>>>
>>>> вт, 17 нояб. 2020 г. в 13:00, Daniel-Constantin Mierla <
>>>> mico...@gmail.com>:
>>>>
>>>>> Hello,
>>>>>
>>>>> what is exactly the problem? The header is not added if you enable:
>>>>>
>>>>> *
>>>>> http://kamailio.org/docs/modules/stable/modules/tm.html#local_cancel_reason
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>> On 16.11.20 20:43, Denys Pozniak wrote:
>>>>>
>>>>> Hello guys,
>>>>>
>>>>> We have faced almost the same problem adding *Reason:
>>>>> SIP;cause=200;text="Call completed elsewhere"* to the t_relayed
>>>>> CANCEL request.
>>>>> Is there an elegant solution to add this header?
>>>>>
>>>>> PS. Switching to the stateless mode does not look pretty for us...
>>>>>
>>>>>
>>>>> сб, 1 февр. 2020 г. в 06:04, Alfonso Pinto :
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> Thanks for your answers.
>>>>>> I did try local_cancel_reason and it’s not doing anything for the
>>>>>> CANCELs generated by kamailio. Isn’t that parameter intended for the
>>>>>> CANCELs received and then relayed?
>>>>>>
>>>>>> As Alex and David mentioned, what I need is to add my own reason
>>>>>> header. There are some cases that requires to set the Reason header to
>>>>>> something specific. IE: terminal supported call waiting in IMS.
>>>>>>
>>>>>> Thanks for the piece of code, I will check what can be done here.
>>>>>>
>>&
Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
Hello!
Call flow: FreeSWITCH --> SBC --> Edge Proxy
In my case, the problem is related to the fact that the SBC deletes the
Reason header from FreeSWITCH and I am trying to recover it on the Kamailio
side (Edge Proxy).
It is especially important to recover the message: "Call completed
elsewhere" because this disables the missed call notification on the
destination phone in case of hunt-groups.
The option to forward the call through the stateless loop works well but it
complicates the logic unnecessarily.
So would be great to have a tm function to setup custom Reason, like below:
*...*
*t_cancel_reason("Reason: SIP ;cause=200 ;text=\"Call completed
elsewhere\"\r\n");t_relay();*
**
ср, 18 нояб. 2020 г. в 11:16, Daniel-Constantin Mierla :
> Same question here like in my other reply:
>
> *
> https://lists.kamailio.org/pipermail/sr-users/2020-November/23.html
>
> How do you expect to fill the value of the header?
>
> Cheers,
> Daniel
> On 17.11.20 19:20, David Villasmil wrote:
>
> And on internally generated CANCELs
>
> On Tue, 17 Nov 2020 at 14:20, Denys Pozniak
> wrote:
>
>> Hello!
>>
>> We need to append our own Reason header for the "relayed" CANCEL message,
>> if it is not on the input.
>> Like below:
>>
>>
>> *if ( is_method("CANCEL") && !is_present_hf("Reason") ) { *
>> * append_hf("Reason: );*
>> * t_relay();*
>> *...*
>>
>>
>>
>>
>> вт, 17 нояб. 2020 г. в 13:00, Daniel-Constantin Mierla > >:
>>
>>> Hello,
>>>
>>> what is exactly the problem? The header is not added if you enable:
>>>
>>> *
>>> http://kamailio.org/docs/modules/stable/modules/tm.html#local_cancel_reason
>>>
>>> Cheers,
>>> Daniel
>>> On 16.11.20 20:43, Denys Pozniak wrote:
>>>
>>> Hello guys,
>>>
>>> We have faced almost the same problem adding *Reason:
>>> SIP;cause=200;text="Call completed elsewhere"* to the t_relayed CANCEL
>>> request.
>>> Is there an elegant solution to add this header?
>>>
>>> PS. Switching to the stateless mode does not look pretty for us...
>>>
>>>
>>> сб, 1 февр. 2020 г. в 06:04, Alfonso Pinto :
>>>
>>>> Hi guys,
>>>>
>>>> Thanks for your answers.
>>>> I did try local_cancel_reason and it’s not doing anything for the
>>>> CANCELs generated by kamailio. Isn’t that parameter intended for the
>>>> CANCELs received and then relayed?
>>>>
>>>> As Alex and David mentioned, what I need is to add my own reason
>>>> header. There are some cases that requires to set the Reason header to
>>>> something specific. IE: terminal supported call waiting in IMS.
>>>>
>>>> Thanks for the piece of code, I will check what can be done here.
>>>>
>>>> Regards,
>>>> Alfonso
>>>>
>>>> El El vie, 31 ene 2020 a las 22:10, Henning Westerholt
>>>> escribió:
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> ok, I was reading that he wants to get just one reason header, not one
>>>>> dynamic generated.
>>>>>
>>>>> Just looked briefly, this seems to be the code:
>>>>>
>>>>> t_msgbuilder.c
>>>>> /* Build a local request based on a previous request; main
>>>>> * customers of this function are local ACK and local CANCEL
>>>>> */
>>>>> char *build_local(struct cell *Trans,unsigned int branch,
>>>>> unsigned int *len, char *method, int method_len, str *to
>>>>> , struct cancel_reason* reason
>>>>> )
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Henning
>>>>>
>>>>> --
>>>>> Henning Westerholt – https://skalatan.de/blog/
>>>>> Kamailio services – https://gilawa.com
>>>>>
>>>>> -Original Message-
>>>>> From: sr-users On Behalf Of
>>>>> Alex Balashov
>>>>> Sent: Friday, January 31, 2020 9:45 PM
>>>>> To: sr-users@lists.kamailio.org
>>>>> Subject: Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
>>>>>
>>>>> I understood Alfonso's question to implicitly be: how can I add a
>>>>> dynamic and variable Reason header to outgoing CANCELs?
>>>>>
Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
Hello!
We need to append our own Reason header for the "relayed" CANCEL message,
if it is not on the input.
Like below:
*if ( is_method("CANCEL") && !is_present_hf("Reason") ) {*
* append_hf("Reason: );*
* t_relay();*
*...*
вт, 17 нояб. 2020 г. в 13:00, Daniel-Constantin Mierla :
> Hello,
>
> what is exactly the problem? The header is not added if you enable:
>
> *
> http://kamailio.org/docs/modules/stable/modules/tm.html#local_cancel_reason
>
> Cheers,
> Daniel
> On 16.11.20 20:43, Denys Pozniak wrote:
>
> Hello guys,
>
> We have faced almost the same problem adding *Reason:
> SIP;cause=200;text="Call completed elsewhere"* to the t_relayed CANCEL
> request.
> Is there an elegant solution to add this header?
>
> PS. Switching to the stateless mode does not look pretty for us...
>
>
> сб, 1 февр. 2020 г. в 06:04, Alfonso Pinto :
>
>> Hi guys,
>>
>> Thanks for your answers.
>> I did try local_cancel_reason and it’s not doing anything for the CANCELs
>> generated by kamailio. Isn’t that parameter intended for the CANCELs
>> received and then relayed?
>>
>> As Alex and David mentioned, what I need is to add my own reason header.
>> There are some cases that requires to set the Reason header to something
>> specific. IE: terminal supported call waiting in IMS.
>>
>> Thanks for the piece of code, I will check what can be done here.
>>
>> Regards,
>> Alfonso
>>
>> El El vie, 31 ene 2020 a las 22:10, Henning Westerholt
>> escribió:
>>
>>> Hi Alex,
>>>
>>> ok, I was reading that he wants to get just one reason header, not one
>>> dynamic generated.
>>>
>>> Just looked briefly, this seems to be the code:
>>>
>>> t_msgbuilder.c
>>> /* Build a local request based on a previous request; main
>>> * customers of this function are local ACK and local CANCEL
>>> */
>>> char *build_local(struct cell *Trans,unsigned int branch,
>>> unsigned int *len, char *method, int method_len, str *to
>>> , struct cancel_reason* reason
>>> )
>>>
>>> Cheers,
>>>
>>> Henning
>>>
>>> --
>>> Henning Westerholt – https://skalatan.de/blog/
>>> Kamailio services – https://gilawa.com
>>>
>>> -Original Message-
>>> From: sr-users On Behalf Of Alex
>>> Balashov
>>> Sent: Friday, January 31, 2020 9:45 PM
>>> To: sr-users@lists.kamailio.org
>>> Subject: Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
>>>
>>> I understood Alfonso's question to implicitly be: how can I add a
>>> dynamic and variable Reason header to outgoing CANCELs?
>>>
>>> Perhaps I was mistaken. But if I'm not, as far as I know there is no
>>> means of doing that. Right?
>>>
>>> On Fri, Jan 31, 2020 at 08:37:48PM +, Henning Westerholt wrote:
>>>
>>> > Hello,
>>> >
>>> > have you tried to use this parameter:
>>> >
>>> > http://kamailio.org/docs/modules/stable/modules/tm.html#local_cancel_r
>>> > eason
>>> >
>>> > Cheers,
>>> >
>>> > Henning
>>> >
>>> > --
>>> > Henning Westerholt – https://skalatan.de/blog/ Kamailio services –
>>> > https://gilawa.com<https://gilawa.com/>
>>> >
>>> > From: sr-users On Behalf Of
>>> > Alfonso Pinto
>>> > Sent: Wednesday, January 29, 2020 8:04 PM
>>> > To: Kamailio (SER) - Users Mailing List
>>> > Subject: [SR-Users] Add Reason Header to kamailio generated CANCEL
>>> >
>>> > Hi everyone,
>>> >
>>> > I've got a specific case: when the inv_fr times out, I need to add a
>>> Reason header to the CANCEL generated by kamailio. I've tried to see if I
>>> could do it in the onsend_route, but that one is not triggered for the
>>> generated CANCEL. I also checked event_route[tm:local-request], but that
>>> one isn't triggered either for the generated CANCEL.
>>> >
>>> > Is there any way to do it? Or maybe to have any pointer about where to
>>> look in the code so I may try to trigger event_route[tm:local-request] for
>>> these generated CANCELs?
>>> >
>>> > Regards,
>>> > Alfonso
>>>
>>> > ___
>>> > Kamailio (SER) - Users Maili
Re: [SR-Users] Add Reason Header to kamailio generated CANCEL
Hello guys, We have faced almost the same problem adding *Reason: SIP;cause=200;text="Call completed elsewhere"* to the t_relayed CANCEL request. Is there an elegant solution to add this header? PS. Switching to the stateless mode does not look pretty for us... сб, 1 февр. 2020 г. в 06:04, Alfonso Pinto : > Hi guys, > > Thanks for your answers. > I did try local_cancel_reason and it’s not doing anything for the CANCELs > generated by kamailio. Isn’t that parameter intended for the CANCELs > received and then relayed? > > As Alex and David mentioned, what I need is to add my own reason header. > There are some cases that requires to set the Reason header to something > specific. IE: terminal supported call waiting in IMS. > > Thanks for the piece of code, I will check what can be done here. > > Regards, > Alfonso > > El El vie, 31 ene 2020 a las 22:10, Henning Westerholt > escribió: > >> Hi Alex, >> >> ok, I was reading that he wants to get just one reason header, not one >> dynamic generated. >> >> Just looked briefly, this seems to be the code: >> >> t_msgbuilder.c >> /* Build a local request based on a previous request; main >> * customers of this function are local ACK and local CANCEL >> */ >> char *build_local(struct cell *Trans,unsigned int branch, >> unsigned int *len, char *method, int method_len, str *to >> , struct cancel_reason* reason >> ) >> >> Cheers, >> >> Henning >> >> -- >> Henning Westerholt – https://skalatan.de/blog/ >> Kamailio services – https://gilawa.com >> >> -Original Message- >> From: sr-users On Behalf Of Alex >> Balashov >> Sent: Friday, January 31, 2020 9:45 PM >> To: sr-users@lists.kamailio.org >> Subject: Re: [SR-Users] Add Reason Header to kamailio generated CANCEL >> >> I understood Alfonso's question to implicitly be: how can I add a dynamic >> and variable Reason header to outgoing CANCELs? >> >> Perhaps I was mistaken. But if I'm not, as far as I know there is no >> means of doing that. Right? >> >> On Fri, Jan 31, 2020 at 08:37:48PM +, Henning Westerholt wrote: >> >> > Hello, >> > >> > have you tried to use this parameter: >> > >> > http://kamailio.org/docs/modules/stable/modules/tm.html#local_cancel_r >> > eason >> > >> > Cheers, >> > >> > Henning >> > >> > -- >> > Henning Westerholt – https://skalatan.de/blog/ Kamailio services – >> > https://gilawa.com<https://gilawa.com/> >> > >> > From: sr-users On Behalf Of >> > Alfonso Pinto >> > Sent: Wednesday, January 29, 2020 8:04 PM >> > To: Kamailio (SER) - Users Mailing List >> > Subject: [SR-Users] Add Reason Header to kamailio generated CANCEL >> > >> > Hi everyone, >> > >> > I've got a specific case: when the inv_fr times out, I need to add a >> Reason header to the CANCEL generated by kamailio. I've tried to see if I >> could do it in the onsend_route, but that one is not triggered for the >> generated CANCEL. I also checked event_route[tm:local-request], but that >> one isn't triggered either for the generated CANCEL. >> > >> > Is there any way to do it? Or maybe to have any pointer about where to >> look in the code so I may try to trigger event_route[tm:local-request] for >> these generated CANCELs? >> > >> > Regards, >> > Alfonso >> >> > ___ >> > Kamailio (SER) - Users Mailing List >> > sr-users@lists.kamailio.org >> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> >> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] webrtc sound problem in version 85.0 google chrome version
Hello Hamed, I think you need to update OpenSSL. https://developers.google.com/web/updates/2020/05/chrome-84-deps-rems чт, 17 сент. 2020 г. в 13:34, Sergey Safarov : > Please check rtcp-mux enabled on FreeSwitch side. > > On Thu, Sep 17, 2020 at 9:49 AM Henning Westerholt wrote: > >> Hello Hamed, >> >> >> >> i’d suggest looking at the media transport level (like SDP, RTP) in this >> question and compare to the previous browser version. Also have check the >> browser debug console out. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> -- >> >> Henning Westerholt – https://skalatan.de/blog/ >> >> Kamailio services – https://gilawa.com >> >> >> >> *From:* sr-users *On Behalf Of *Hamed >> Rastegar >> *Sent:* Wednesday, September 16, 2020 10:34 AM >> *To:* sr-users@lists.kamailio.org >> *Subject:* [SR-Users] webrtc sound problem in version 85.0 google chrome >> version >> >> >> >> Hello >> I am using kamailio 5.1 for WebRTC (websocket) >> But in the latest version of Google Chrome (85.0) I have a problem, No >> sound is transmitted between the source and the destination. >> This problem does not exist in Firefox browser >> If you have experience in this field, please comment >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Call forking and pua_dialog problem
Hello! To simplify the question, how to force the dialog module to separate incoming calls that have the same callid and from_tag (forked by an upstream proxy)? пт, 21 авг. 2020 г. в 19:12, Denys Pozniak : > Hello! > > We have a next call-flow topology: User A -> FreeSWITCH -> Kamailio Fork > -> Kamailio Edge => User(s) B, C, D, ... > - FreeSWITCH adds X- header with a list of users to fork call (B, C, D > legs). > - Kamailio Fork generates branches via append_branch function towards > Kamailio Edge. > - Kamailio Edge keeps customer registration and sends BLF statuses > (pua_dialoginfo). > > The problem (or normal behavior by RFC) is that the dialog module on > Kamailio Edge does not split these incoming legs into separated dialogs > (incoming SIP Call-ID and from tag are the same). > And as per my checking *kamcmd dlg.list_ctx* shows only the structure > from the first leg and finally, it leads to a problem with BLF (as > pua_diloginfo loses some SIP PUBLISHes). > > Any advice on how to fix this is appreciated! > > -- > > BR, > Denys Pozniak > > > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Call forking and pua_dialog problem
Hello! We have a next call-flow topology: User A -> FreeSWITCH -> Kamailio Fork -> Kamailio Edge => User(s) B, C, D, ... - FreeSWITCH adds X- header with a list of users to fork call (B, C, D legs). - Kamailio Fork generates branches via append_branch function towards Kamailio Edge. - Kamailio Edge keeps customer registration and sends BLF statuses (pua_dialoginfo). The problem (or normal behavior by RFC) is that the dialog module on Kamailio Edge does not split these incoming legs into separated dialogs (incoming SIP Call-ID and from tag are the same). And as per my checking *kamcmd dlg.list_ctx* shows only the structure from the first leg and finally, it leads to a problem with BLF (as pua_diloginfo loses some SIP PUBLISHes). Any advice on how to fix this is appreciated! -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] ERROR: kazoo [kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Hello!
Sometimes presence server stops sending SIP NOTIFY events with syslog
output below (after Kamailio restarting everything is restored):
Jul 27 17:07:28 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:28 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Jul 27 17:07:29 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:29 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Jul 27 17:07:37 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:37 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Jul 27 17:07:37 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:37 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Jul 27 17:07:41 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:41 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Jul 27 17:07:41 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR:
db_mysql [km_dbase.c:602]: db_mysql_start_transaction(): transaction
already started
Jul 27 17:07:41 prd-sip-presence-2 /usr/sbin/kamailio[4838]: ERROR: kazoo
[kz_pua.c:131]: kz_pua_update_presentity(): in start_transaction
Where is a possible source of the problem?
Kamailio 5.1.2 with MySQL
modparam("presence", "db_url", DBURL)
modparam("presence", "subs_db_mode", 3)
modparam("presence", "timeout_rm_subs", 0)
modparam("presence", "expires_offset", 0)
modparam("presence", "max_expires", 1800)
modparam("presence", "db_update_period", 30)
modparam("presence", "clean_period", 180)
modparam("presence", "send_fast_notify", 1)
modparam("presence", "pres_htable_size", 32)
modparam("presence", "subs_htable_size", 32)
modparam("presence", "publ_cache", 0)
modparam("presence", "notifier_processes", 0)
modparam("presence_xml", "db_url", DBURL)
modparam("presence_xml", "force_active", 1)
modparam("presence_xml", "integrated_xcap_server", 0)
modparam("presence_xml", "disable_presence", 1)
modparam("presence_xml", "disable_winfo", 1)
modparam("presence_dialoginfo", "force_single_dialog", 1)
modparam("presence_dialoginfo", "force_dummy_dialog", 1)
modparam("dialog", "dlg_flag", 4)
modparam("dialog", "db_mode", 0)
modparam("dialog", "dlg_match_mode", 1)
modparam("kazoo", "node_hostname", NODE_HOSTNAME)
modparam("kazoo", "amqp_connection", "AMQP_URL")
modparam("kazoo", "pua_mode", 1)
modparam("kazoo", "db_url", DBURL)
modparam("kazoo", "amqp_consumer_processes", 10)
modparam("kazoo", "amqp_max_channels", 50)
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found
Hello!
Thanks!!!
And yes, 200 OK on PUBLISH does not have Expires header (we are sending
synthetic reply).
вт, 23 июн. 2020 г. в 08:59, Daniel-Constantin Mierla :
> Hello,
>
> I looked at the code and actually the log message from the c code is
> printed on SIP reply handler. So look at the reply of the PUBLISH and see
> if it has expires header.
>
> Cheers,
> Daniel
> On 22.06.20 21:41, Denys Pozniak wrote:
>
> Hello!
>
> I added logging to onsend_route (as I understand this is only one place to
> catch publishes):
>
> if ( is_method("PUBLISH") ) {
> xlog("L_WARN", "[PUBLISH] $rm/$ru expires=$hdr(Expires) [$ci]\n");
> }
>
>
> Got output:
>
> 64(13374) WARNING:
Re: [SR-Users] ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found
Hello!
I added logging to onsend_route (as I understand this is only one place to
catch publishes):
if ( is_method("PUBLISH") ) {
xlog("L_WARN", "[PUBLISH] $rm/$ru expires=$hdr(Expires) [$ci]\n");
}
Got output:
64(13374) WARNING:
Re: [SR-Users] ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found
Hello!
Any help is appreciated.
вт, 16 июн. 2020 г. в 15:04, Denys Pozniak :
> Hello!
>
> Could someone point me to the possible source of the problem?
>
> Jun 16 09:51:06 proxy-edge /usr/sbin/kamailio[9645]: ERROR: pua
> [send_publish.c:304]: publ_cback_func(): No Expires header found
> Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9640]: ERROR: pua
> [send_publish.c:304]: publ_cback_func(): No Expires header found
> Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9600]: ERROR: pua
> [send_publish.c:304]: publ_cback_func(): No Expires header found
> Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9660]: ERROR: pua
> [send_publish.c:304]: publ_cback_func(): No Expires header found
>
> Modules settings:
>
> *loadmodule "pua.so"*
> *loadmodule "pua_dialoginfo"*
> *loadmodule "dialog.so" *
>
>
> *modparam("pua", "default_expires", 1200)*
> *modparam("pua", "outbound_proxy", LOCAL_IP_ADDR)*
> *modparam("pua_dialoginfo", "include_callid", 1)*
>
> *modparam("pua_dialoginfo", "include_localremote", 1)*
> *modparam("pua_dialoginfo", "include_tags", 1)*
> *modparam("pua_dialoginfo", "send_publish_flag", 8)*
>
>
>
>
>
>
>
> *modparam("dialog", "dlg_flag", 4)modparam("dialog", "db_mode",
> 0)modparam("dialog", "enable_stats", 1)modparam("dialog", "dlg_match_mode",
> 1)modparam("dialog", "default_timeout", 7200) modparam("dialog",
> "hash_size", 8192)*
>
> *request_route{*
> *...*
>
> *setflag(8);*
> *...*
> *}*
>
>
> Generated SIP PUBLISH:
>
> *PUBLISH sip:extens...@sip.company.com
> SIP/2.0*
> *Via: SIP/2.0/UDP
> 8.8.8.8;branch=z9hG4bK3e55.afdce977.0*
> *To: >*
> *From: >;tag=e98d9fc94bada9746d67946ab287a76f-ba77*
> *CSeq: 10 PUBLISH*
> *Call-ID: 72ef85f374c8e703-9659@10.10.10.10
> <72ef85f374c8e703-9659@10.10.10.10>*
> *Content-Length: 578*
> *User-Agent: proxy*
> *Max-Forwards: 70*
> *Event: dialog*
> *Expires: 7201*
> *Content-Type: application/dialog-info+xml*
>
> **
> * state="full" entity="sip:extens...@sip.company.com
> ">*
> * call-id="162092997-5060-...@bjc.bgi.ca.bbi" direction="initiator">*
> *Trying*
> **
> * sip:1234567...@sip.company.com
> *
> * *
> **
> **
> * sip:extens...@sip.company.com
> *
> * *
> **
> * *
> **
>
>
>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] ERROR: pua [send_publish.c:304]: publ_cback_func(): No Expires header found
Hello!
Could someone point me to the possible source of the problem?
Jun 16 09:51:06 proxy-edge /usr/sbin/kamailio[9645]: ERROR: pua
[send_publish.c:304]: publ_cback_func(): No Expires header found
Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9640]: ERROR: pua
[send_publish.c:304]: publ_cback_func(): No Expires header found
Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9600]: ERROR: pua
[send_publish.c:304]: publ_cback_func(): No Expires header found
Jun 16 09:51:07 proxy-edge /usr/sbin/kamailio[9660]: ERROR: pua
[send_publish.c:304]: publ_cback_func(): No Expires header found
Modules settings:
*loadmodule "pua.so"*
*loadmodule "pua_dialoginfo"*
*loadmodule "dialog.so" *
*modparam("pua", "default_expires", 1200)*
*modparam("pua", "outbound_proxy", LOCAL_IP_ADDR)*
*modparam("pua_dialoginfo", "include_callid", 1)*
*modparam("pua_dialoginfo", "include_localremote", 1)*
*modparam("pua_dialoginfo", "include_tags", 1)*
*modparam("pua_dialoginfo", "send_publish_flag", 8)*
*modparam("dialog", "dlg_flag", 4)modparam("dialog", "db_mode",
0)modparam("dialog", "enable_stats", 1)modparam("dialog", "dlg_match_mode",
1)modparam("dialog", "default_timeout", 7200) modparam("dialog",
"hash_size", 8192)*
*request_route{*
*...*
*setflag(8);*
*...*
*}*
Generated SIP PUBLISH:
*PUBLISH sip:extens...@sip.company.com
SIP/2.0*
*Via: SIP/2.0/UDP
8.8.8.8;branch=z9hG4bK3e55.afdce977.0*
*To: >*
*From: >;tag=e98d9fc94bada9746d67946ab287a76f-ba77*
*CSeq: 10 PUBLISH*
*Call-ID: 72ef85f374c8e703-9659@10.10.10.10
<72ef85f374c8e703-9659@10.10.10.10>*
*Content-Length: 578*
*User-Agent: proxy*
*Max-Forwards: 70*
*Event: dialog*
*Expires: 7201*
*Content-Type: application/dialog-info+xml*
**
**
* *
*Trying*
**
* sip:1234567...@sip.company.com
*
* *
**
**
* sip:extens...@sip.company.com
*
* *
**
* *
**
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] CRITICAL: [core/data_lump.c:292]: del_lump(): offset exceeds message size (1436 > 1432) aborting...
Hello! Could you please check the reason of crash below? syslog: kamailio[31738]: CRITICAL: |RGFLAFL63U| [core/data_lump.c:292]: del_lump(): offset exceeds message size (1436 > 1432) aborting... gdb ( uri and IP were modified ): Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.'. Program terminated with signal 6, Aborted. #0 0x7f5d8556d4f5 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-15.el6_6.2.x86_64 glibc-2.12-1.212.el6.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-65.el6.x86_64 libcom_err-1.41.12-24.el6.x86_64 libcurl-7.19.7-53.el6_9.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 libssh2-1.4.2-2.el6_7.1.x86_64 mysql-libs-5.1.73-8.el6_8.x86_64 nspr-4.19.0-1.el6.x86_64 nss-3.36.0-9.el6_10.x86_64 nss-softokn-freebl-3.14.3-23.3.el6_8.x86_64 nss-util-3.36.0-1.el6.x86_64 openldap-2.4.40-16.el6.x86_64 openssl-1.0.1e-58.el6_10.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt #0 0x7f5d8556d4f5 in raise () from /lib64/libc.so.6 #1 0x7f5d8556ecd5 in abort () from /lib64/libc.so.6 #2 0x0046a4a6 in del_lump (msg=0x7f5d846cd798, offset=1436, len=29, type=HDR_OTHER_T) at core/data_lump.c:293 #3 0x7f5d7e6fd7f5 in alter_rtcp (msg=0x7f5d846cd798, body=0x7fffc60c8600, oldport=0x7f5d84715500, newport=0x7fffc60c8550) at rtpproxy.c:1229 #4 0x7f5d7e70ec5d in force_rtp_proxy (msg=0x7f5d846cd798, str1=0x7f5d846af190 "co", str2=0x7fffc60c87f0 "162.221.21.250", offer=1, forcedIP=0) at rtpproxy.c:2669 #5 0x7f5d7e705f64 in rtpproxy_manage (msg=0x7f5d846cd798, flags=0x7f5d846af190 "co", ip=0x0) at rtpproxy.c:1862 #6 0x7f5d7e7064c6 in rtpproxy_manage1 (msg=0x7f5d846cd798, flags=0x7f5d846907f0 "\220\361j\204]\177", ip=0x0) at rtpproxy.c:1904 #7 0x00434f19 in do_action (h=0x7fffc60cae70, a=0x7f5d846b16d8, msg=0x7f5d846cd798) at core/action.c:1073 #8 0x00441a94 in run_actions (h=0x7fffc60cae70, a=0x7f5d846b16d8, msg=0x7f5d846cd798) at core/action.c:1564 #9 0x00431663 in do_action (h=0x7fffc60cae70, a=0x7f5d8468ae40, msg=0x7f5d846cd798) at core/action.c:691 #10 0x00441a94 in run_actions (h=0x7fffc60cae70, a=0x7f5d846848a0, msg=0x7f5d846cd798) at core/action.c:1564 #11 0x00431663 in do_action (h=0x7fffc60cae70, a=0x7f5d846abca0, msg=0x7f5d846cd798) at core/action.c:691 #12 0x00441a94 in run_actions (h=0x7fffc60cae70, a=0x7f5d846abca0, msg=0x7f5d846cd798) at core/action.c:1564 #13 0x00434df4 in do_action (h=0x7fffc60cae70, a=0x7f5d846abdf0, msg=0x7f5d846cd798) at core/action.c:1058 #14 0x00441a94 in run_actions (h=0x7fffc60cae70, a=0x7f5d846a45f8, msg=0x7f5d846cd798) at core/action.c:1564 #15 0x00442190 in run_top_route (a=0x7f5d846a45f8, msg=0x7f5d846cd798, c=0x0) at core/action.c:1646 #16 0x00546d87 in receive_msg ( buf=0x29463b0 "INVITE sip:999@18.12.188.108 SIP/2.0\r\nVia: SIP/2.0/TCP 10.0.0.33:49631;branch=z9hG4bK.9XHFYH0zF;rport\r\nFrom: < sip:rgflafl...@proxy.company.com>;tag=DcTh-~6~M\r\nTo: \"Liz - Home Office\" ;tag=DcTh-~6~M\r\nTo: \"Liz - Home Office\" ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to get cause from reason header?
Try this one:
$(hdr(Reason){param.value,cause})
пт, 8 мая 2020 г. в 21:57, Luis Rojas G. :
> Hello,
>
> That is one of the parts I read, but to transform something first I would
> need something to transform.
>
> I don't know how to get the cause from the header. I was reading this :
>
>
> https://kamailio.org/docs/modules/5.3.x/modules/textopsx.html#textopsx.sel.hf_value
>
> It gives some nice examples, like :
>
> $b = @hf_value.p_associated_uri;
> $rr = @hf_value.route.uri;
> $prt = @hf_value2.authorization.integrity_protected;
>
> What about @hf_value.reason.cause or @hf_value2.reason.cause ? They don't
> even compile.
>
> 0(3848) ERROR: [core/select.c:299]: resolve_select(): Unable to
> resolve select 'cause' at level 2
> 0(3848) ERROR: [core/rvalue.c:2893]: fix_rval(): Unable to resolve
> select in cfg at line: 209 col: 42
> 0(3848) ERROR: [core/select.c:434]: log_select(): select( 0(3848)
> ERROR: [core/select.c:439]: log_select(): hf_value2, 0(3848) ERROR:
> [core/select.c:439]: log_select():
> , 0(3848) ERROR: [core/select.c:439]:
> log_select(): cause, 0(3848) ERROR: [core/select.c:442]:
> log_select(): )
>
> Luis
>
>
> On 5/8/20 2:42 PM, Denys Pozniak wrote:
>
> Hello!
>
> Did you try Parameters List Transformations?
>
> https://www.kamailio.org/wiki/cookbooks/devel/transformations#parameters_list_transformations
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.kamailio.org%2Fwiki%2Fcookbooks%2Fdevel%2Ftransformations%23parameters_list_transformations=02%7C01%7C%7Ca702e4ab30164604fec508d7f37f9be0%7Cab4a33c2b5614f798601bc921698ad08%7C0%7C0%7C637245601731466978=ub57diRdKH%2Bv7AmwCXz82DqhyiCriw1bu5U%2FEn9OZyQ%3D=0>
>
>
> пт, 8 мая 2020 г. в 19:32, Luis Rojas G. :
>
>> Hello,
>>
>> I am sure that this is very easy to do, but I have been googling and I
>> can't find a way.
>>
>> Having a Reason header, for instance :
>>
>> Reason: SIP;cause=Some_Cause;text="Some_text"
>>
>> How can I get the value of "Some_Cause"? I need to compare it to some
>> specific numeric values...
>>
>> Thanks in advance,
>>
>> Luis
>>
>> --
>> Luis Rojas
>> Software Architect
>> Sixbell
>> Los Leones 1200
>> Providencia
>> Santiago, Chile
>> Phone: (+56-2) 22001288
>> mailto:luis.ro...@sixbell.com
>> http://www.sixbell.com
>> <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sixbell.com%2F=02%7C01%7C%7Ca702e4ab30164604fec508d7f37f9be0%7Cab4a33c2b5614f798601bc921698ad08%7C0%7C0%7C637245601731466978=6PUKqMIEB%2FK%2BkcgxsYJ7pMxifhVh5y96ymcHjYF%2F5rM%3D=0>
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.kamailio.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsr-users=02%7C01%7C%7Ca702e4ab30164604fec508d7f37f9be0%7Cab4a33c2b5614f798601bc921698ad08%7C0%7C0%7C637245601731476971=1c6ILaqdc1paDW6Bon83APNAwq1eJ7TatMfPPyMbDQk%3D=0>
>>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>
> --
> Luis Rojas
> Software Architect
> Sixbell
> Los Leones 1200
> Providencia
> Santiago, Chile
> Phone: (+56-2) 22001288mailto:luis.ro...@sixbell.com
> http://www.sixbell.com
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to get cause from reason header?
Hello! Did you try Parameters List Transformations? https://www.kamailio.org/wiki/cookbooks/devel/transformations#parameters_list_transformations пт, 8 мая 2020 г. в 19:32, Luis Rojas G. : > Hello, > > I am sure that this is very easy to do, but I have been googling and I > can't find a way. > > Having a Reason header, for instance : > > Reason: SIP;cause=Some_Cause;text="Some_text" > > How can I get the value of "Some_Cause"? I need to compare it to some > specific numeric values... > > Thanks in advance, > > Luis > > -- > Luis Rojas > Software Architect > Sixbell > Los Leones 1200 > Providencia > Santiago, Chile > Phone: (+56-2) 22001288 > mailto:luis.ro...@sixbell.com > http://www.sixbell.com > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] How Kamailio processes SIP ACK on local 4XX reply?
Hello!
I have some misunderstanding regarding the processing of SIP ACK on local
Kamailio 4xx reply (eg 407 Proxy Authentication Required).
In the picture below you can see that such a message just goes through the
proxy and moreover gets into the *request_route* section.
I expect this SIP ACK to be consumed by the sl module without hitting
script logic.
[image: image.png]
I put the part below to the very top of the *request_route* section:
*request_route* {
if ( is_method("ACK") ) {
t_check_trans();
$var(error) = $rc;
xlog("L_ERR", "[CATCH_ACK] m=$rm cseq=$cs ru=$ru err=$var(error)
[$ci]");
}
And as a result, I detected in syslog:
May 7 16:15:34 test-edge /usr/sbin/kamailio[11642]: ERROR:
Re: [SR-Users] Kamailio connection issue
(-i) 31393 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 65535 > pipe size(512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 31393 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > In the kamailio log file I don't see anything wrong, I don't see messages > like "[tcp_main.c:3913]: handle_new_connect(): maximum number of tls > connections exceeded". > > Here is the output of kamctl ps command > Process:: ID=0 PID=11725 Type=main process - attendant > Process:: ID=1 PID=11727 Type=udp receiver child=0 sock= > 10.208.194.26:5061 > Process:: ID=2 PID=11728 Type=udp receiver child=1 sock= > 10.208.194.26:5061 > Process:: ID=3 PID=11729 Type=udp receiver child=2 sock= > 10.208.194.26:5061 > Process:: ID=4 PID=11730 Type=udp receiver child=3 sock= > 10.208.194.26:5061 > Process:: ID=5 PID=11731 Type=udp receiver child=4 sock= > 10.208.194.26:5061 > Process:: ID=6 PID=11732 Type=udp receiver child=5 sock= > 10.208.194.26:5061 > Process:: ID=7 PID=11733 Type=udp receiver child=6 sock= > 10.208.194.26:5061 > Process:: ID=8 PID=11734 Type=udp receiver child=7 sock= > 10.208.194.26:5061 > Process:: ID=9 PID=11735 Type=udp receiver child=8 sock= > 10.208.194.26:5061 > Process:: ID=10 PID=11736 Type=udp receiver child=9 sock= > 10.208.194.26:5061 > Process:: ID=11 PID=11737 Type=udp receiver child=10 sock= > 10.208.194.26:5061 > Process:: ID=12 PID=11738 Type=udp receiver child=11 sock= > 10.208.194.26:5061 > Process:: ID=13 PID=11739 Type=udp receiver child=12 sock= > 10.208.194.26:5061 > Process:: ID=14 PID=11740 Type=udp receiver child=13 sock= > 10.208.194.26:5061 > Process:: ID=15 PID=11741 Type=udp receiver child=14 sock= > 10.208.194.26:5061 > Process:: ID=16 PID=11742 Type=udp receiver child=15 sock= > 10.208.194.26:5061 > Process:: ID=17 PID=11743 Type=slow timer > Process:: ID=18 PID=11744 Type=timer > Process:: ID=19 PID=11745 Type=secondary timer > Process:: ID=20 PID=11746 Type=MI FIFO > Process:: ID=21 PID=11747 Type=USRLOC Timer > Process:: ID=22 PID=11748 Type=USRLOC Timer > Process:: ID=23 PID=11749 Type=USRLOC Timer > Process:: ID=24 PID=11750 Type=USRLOC Timer > Process:: ID=25 PID=11751 Type=ctl handler > Process:: ID=26 PID=11752 Type=RTIMER SEC EXEC > Process:: ID=27 PID=11753 Type=TIMER NH > Process:: ID=28 PID=11754 Type=tcp receiver (generic) child=0 > Process:: ID=29 PID=11755 Type=tcp receiver (generic) child=1 > Process:: ID=30 PID=11756 Type=tcp receiver (generic) child=2 > Process:: ID=31 PID=11757 Type=tcp receiver (generic) child=3 > Process:: ID=32 PID=11758 Type=tcp receiver (generic) child=4 > Process:: ID=33 PID=11759 Type=tcp receiver (generic) child=5 > Process:: ID=34 PID=11760 Type=tcp receiver (generic) child=6 > Process:: ID=35 PID=11761 Type=tcp receiver (generic) child=7 > Process:: ID=36 PID=11762 Type=tcp receiver (generic) child=8 > Process:: ID=37 PID=11763 Type=tcp receiver (generic) child=9 > Process:: ID=38 PID=11764 Type=tcp receiver (generic) child=10 > Process:: ID=39 PID=11765 Type=tcp receiver (generic) child=11 > Process:: ID=40 PID=11766 Type=tcp receiver (generic) child=12 > Process:: ID=41 PID=11767 Type=tcp receiver (generic) child=13 > Process:: ID=42 PID=11768 Type=tcp receiver (generic) child=14 > Process:: ID=43 PID=11769 Type=tcp receiver (generic) child=15 > Process:: ID=44 PID=11770 Type=tcp main process > > > Can anyone address me to find out this happens, please? > Please let me know if you need further information... > > Thanks in advance, > Best Regards > Tomas > > > > Tomas Zanet > R Software Designer > tza...@came.com > CAME S.p.A. > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] I need to configure apns push notification in kamailio
Hello Master1024 :),
>I read from the site
https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eeca2f8e08d
but
I don't understand properly because here is missing push.php
The goal of this article was to show the SIP call-flow logic only.
In my project scenario, the app sends token and device type to Kamailio in
a custom SIP header, and Kamailio calls API ("push.php") with that
arguments.
ср, 4 мар. 2020 г. в 09:09, max :
> I think you need to enable below module and try again
>
> loadmodule "cfgutils.so"
>
>
>
>
>
> --
> Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] pv_parse_spec2(): wrong char [)/41] in [$T(reply_reason)] at [15 (5)]
Hello!
Looks like $T(reply_reason) does not work well (although $T_reply_reason is
ok).
Kamailio script:
failure_route[TRUNK_FAILURE] {
...
xlog("L_WARN","rm=$rm / $T(reply_reason) \n");
...
}
0(8894) ERROR: tmx [t_var.c:696]: pv_parse_t_name(): unknown PV name
reply_reason
0(8894) ERROR: [core/pvapi.c:952]: pv_parse_spec2(): pvar "T" has
an invalid name param [reply_reason]
0(8894) ERROR: [core/pvapi.c:1107]: pv_parse_spec2(): wrong char
[)/41] in [$T(reply_reason)] at [15 (5)]
0(8894) ERROR: xlog [xlog.c:511]: xdbg_fixup_helper(): wrong format[rm=$rm
/ $T(reply_reason)
https://www.kamailio.org/wiki/cookbooks/5.2.x/pseudovariables
$T(name)
- pseudo-variable class to access TM attributes
The *name* can be:
- reply_reason - reply reason
[kamailio]$ kamailio -v
version: kamailio 5.2.2 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
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_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_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: unknown
compiled on 18:04:26 Apr 3 2019 with gcc 4.8.5
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [dispatcher] freeing already freed pointer, called from core: core/xavp.c: xavp_free
I have fixed this issue moving AUTORUN from [htable:mod-init] to
[core:worker-one-init].
event_route[core:worker-one-init] {
route(AUTORUN);
}
вт, 17 дек. 2019 г. в 11:56, Denys Pozniak :
> Hello!
>
> The configuration below leads to a CRITICAL message in the console.
> Please let me know how to avoid this issue.
>
> event_route[htable:mod-init] {
> route(AUTORUN);
> ...
> }
>
> route[AUTORUN] {
> if ( ds_select("9", "4") ) {
> xlog("L_WARN", "[$cfg(route)] *ds_select* $xavp(_dsdst_[0]=>uri)
> $xavp(_dsdst_[1]=>uri) $xavp(_dsdst_[2]=>uri)\n");
> }
> ...
> }
>
> dispatcher.list
> # group 9
> 9 sip:192.168.20.125:5070
> 9 sip:192.168.20.160:5070
> 9 sip:192.168.20.7:5070
> 9 sip:192.168.20.107:5070
> 9 sip:192.168.20.190:5070
>
> 0(6088) DEBUG: dispatcher [dispatch.c:2054]: ds_manage_routes(): set [9]
> 0(6088) DEBUG: dispatcher [dispatch.c:2158]: ds_manage_routes(): using
> alg [4] hash [0]
> 0(6088) DEBUG: dispatcher [dispatch.c:2199]: ds_manage_routes(): selected
> [4-9-2/0]
> 0(6088) DEBUG: dispatcher [dispatch.c:2218]: ds_manage_routes(): using
> first entry [9/0]
> 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
> entry [9/1]
> 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
> entry [9/2]
> 0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
> entry [9/3]
> 0(6088) DEBUG: dispatcher [dispatch.c:2272]: ds_manage_routes(): using
> default entry [9/4]
> 0(6088) DEBUG: dispatcher [dispatch.c:2016]: ds_select_dst_limit():
> selected target destinations: 5
> 0(6088) WARNING:
[SR-Users] [dispatcher] freeing already freed pointer, called from core: core/xavp.c: xavp_free
Hello!
The configuration below leads to a CRITICAL message in the console.
Please let me know how to avoid this issue.
event_route[htable:mod-init] {
route(AUTORUN);
...
}
route[AUTORUN] {
if ( ds_select("9", "4") ) {
xlog("L_WARN", "[$cfg(route)] *ds_select* $xavp(_dsdst_[0]=>uri)
$xavp(_dsdst_[1]=>uri) $xavp(_dsdst_[2]=>uri)\n");
}
...
}
dispatcher.list
# group 9
9 sip:192.168.20.125:5070
9 sip:192.168.20.160:5070
9 sip:192.168.20.7:5070
9 sip:192.168.20.107:5070
9 sip:192.168.20.190:5070
0(6088) DEBUG: dispatcher [dispatch.c:2054]: ds_manage_routes(): set [9]
0(6088) DEBUG: dispatcher [dispatch.c:2158]: ds_manage_routes(): using alg
[4] hash [0]
0(6088) DEBUG: dispatcher [dispatch.c:2199]: ds_manage_routes(): selected
[4-9-2/0]
0(6088) DEBUG: dispatcher [dispatch.c:2218]: ds_manage_routes(): using
first entry [9/0]
0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/1]
0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/2]
0(6088) DEBUG: dispatcher [dispatch.c:2238]: ds_manage_routes(): using
entry [9/3]
0(6088) DEBUG: dispatcher [dispatch.c:2272]: ds_manage_routes(): using
default entry [9/4]
0(6088) DEBUG: dispatcher [dispatch.c:2016]: ds_select_dst_limit():
selected target destinations: 5
0(6088) WARNING:
Re: [SR-Users] Not working : Using $cfg(line) to print line number
Hello!
I think you missed corex module.
пт, 29 нояб. 2019 г. в 13:35, mahesh b :
> Hi All,
> Below is the syntax am using to print the line number in kamailio
> configuration file.
>
> xlog("L_WARN","Hi Mahesh at line $cfg(line)\n");
>
> Unfortunately , when i do this looks like kamailio is not starting, Any
> help please regarding what am i missing here. I tried Xlogl as well, which
> doesnt print the line number by default in my setup.
>
>
> This is the details i had read to understand config file attributes :
>
> $cfg(key) - Config File Attributes
>
> Attributes related to configuration file.
>
> The key can be:
>
>- line - return the current line in config
>- name - return the name of current config file
>- file - return the name of current config file
>- route - return the name of routing block
>
> Example:
>
> send_reply("404", "Not found at line $cfg(line)")
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to use sdp_remove_media() ?
Hey Karsten,
I am not sure RTPengine allows us to delete a specific stream from SDP (as
it is the main task I am solving).
Anyway, I put route(SDP_VIDEO_REMOVER) above calling record_route and it
works well.
So that the main question is about the source of an issue: my configuration
or something wrong with sdp_remove_media()?
пт, 1 нояб. 2019 г. в 19:03, Karsten Horsmann :
> Hi Denys,
>
> AFAIK read and writes rtpengine the complete sdp. So manipulating with the
> "classic" textops tools is more for RtpProxy. You can search for things but
> writing will done by rtpengine.
> I remove for example an codec with codec-mask. Or you can manipulate the
> avp you read from rtpengine (via modparam) in the request.
>
> Did you try to *codec-mask= in the rtpengine calls (answer / manage)? *
> *So rtpengine takes care for the removal. *
> *It needs to know what to remove. *
>
> https://www.kamailio.org/docs/modules/5.3.x/modules/rtpengine.html#idm1459
>
>
> Cheers
> Karsten
>
> Denys Pozniak schrieb am Fr., 1. Nov. 2019,
> 15:10:
>
>> If I put route(SDP_VIDEO_REMOVER) into the section route[NATMANAGE] (
>> https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L820
>> ), Kamailio shows the error I posted below.
>>
>> route[SDP_VIDEO_REMOVER] {
>> if ( is_request() && has_body("application/sdp") &&
>> sdp_with_media("video") ) {
>> sdp_remove_media("video");
>> msg_apply_changes();
>> xlog("L_WARN","[$cfg(route)] *m=video detected* |
>> $rm/$rs/$avp(sdp_mvideo_line)/ \n");
>> }
>> }
>>
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:883]: sdp_with_media(): attempting
>> to search for media type: [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 0 of
>> 0 - media [audio]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 1 of
>> 0 - media [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1038]: sdp_remove_media():
>> attempting to search for media type: [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 0
>> of 0 - media [audio]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 1
>> of 0 - media [video]
>> 16(15993) DEBUG: sdpops [sdpops_mod.c:1061]: sdp_remove_media(): removing
>> media stream: video16(15993) *ERROR: textopsx [textopsx.c:181]:
>> ki_msg_apply_changes(): invalid usage - not in request route or a reply*
>> 16(15993) WARNING:
Re: [SR-Users] How to use sdp_remove_media() ?
If I put route(SDP_VIDEO_REMOVER) into the section route[NATMANAGE] (
https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L820 ),
Kamailio shows the error I posted below.
route[SDP_VIDEO_REMOVER] {
if ( is_request() && has_body("application/sdp") &&
sdp_with_media("video") ) {
sdp_remove_media("video");
msg_apply_changes();
xlog("L_WARN","[$cfg(route)] *m=video detected* |
$rm/$rs/$avp(sdp_mvideo_line)/ \n");
}
}
16(15993) DEBUG: sdpops [sdpops_mod.c:883]: sdp_with_media(): attempting to
search for media type: [video]
16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 0 of 0
- media [audio]
16(15993) DEBUG: sdpops [sdpops_mod.c:898]: sdp_with_media(): stream 1 of 0
- media [video]
16(15993) DEBUG: sdpops [sdpops_mod.c:1038]: sdp_remove_media(): attempting
to search for media type: [video]
16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 0
of 0 - media [audio]
16(15993) DEBUG: sdpops [sdpops_mod.c:1055]: sdp_remove_media(): stream 1
of 0 - media [video]
16(15993) DEBUG: sdpops [sdpops_mod.c:1061]: sdp_remove_media(): removing
media stream: video16(15993) *ERROR: textopsx [textopsx.c:181]:
ki_msg_apply_changes(): invalid usage - not in request route or a reply*
16(15993) WARNING:
Re: [SR-Users] How to use sdp_remove_media() ?
Got message in debug=3:
*13(2141) ERROR: textopsx [textopsx.c:181]: ki_msg_apply_changes(): invalid
usage - not in request route or a reply*
But definitely msg_apply_changes() is placed in request_route section.
I have just moved code part before calling record_route() function and it
helped.
Interesting, but as I remember Kamailio should display in such cases
something like below:
"...cannot apply msg changes after adding record-route header..."
Thanks for the hint.
пт, 1 нояб. 2019 г. в 11:35, Daniel-Constantin Mierla :
> Hello,
>
> run with debug=3 and what the logs to see if there are error/warning
> messages.
>
> Cheers,
> Daniel
> On 01.11.19 10:26, Denys Pozniak wrote:
>
> Hello!
>
> I'm trying to remove m=video stream from incoming SIP/SDP request in th
> way below:
>
> modparam("rtpengine", "read_sdp_pv", "$avp(read_sdp_pv)")
> modparam("rtpengine", "write_sdp_pv", "$avp(write_sdp_pv)")
> ...
> sdp_remove_media("video");
> msg_apply_changes();
> sdp_get("$avp(read_sdp_pv)");
> xlog("L_WARN","[$cfg(route)] *m=video removed* ci| rb=/$rb/ \n");
> xlog("L_WARN","[$cfg(route)] *m=video removed* ci|
> avp(read_sdp_pv)=/$avp(read_sdp_pv)/ \n");
> rtpengine_manage("$avp(rtpengine_offer)");
> set_body("$avp(write_sdp_pv)", "application/sdp");
>
> But no luck, xlog shows m=video in $rb and $avp(rtp_sdp_read) as well.
>
> --
>
> BR,
> Denys Pozniak
>
>
>
> ___
> Kamailio (SER) - Users Mailing
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
> www.linkedin.com/in/miconda
> Kamailio World Conference - April 27-29, 2020, in Berlin --
> www.kamailioworld.com
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] How to use sdp_remove_media() ?
Hello!
I'm trying to remove m=video stream from incoming SIP/SDP request in th way
below:
modparam("rtpengine", "read_sdp_pv", "$avp(read_sdp_pv)")
modparam("rtpengine", "write_sdp_pv", "$avp(write_sdp_pv)")
...
sdp_remove_media("video");
msg_apply_changes();
sdp_get("$avp(read_sdp_pv)");
xlog("L_WARN","[$cfg(route)] *m=video removed* ci| rb=/$rb/ \n");
xlog("L_WARN","[$cfg(route)] *m=video removed* ci|
avp(read_sdp_pv)=/$avp(read_sdp_pv)/ \n");
rtpengine_manage("$avp(rtpengine_offer)");
set_body("$avp(write_sdp_pv)", "application/sdp");
But no luck, xlog shows m=video in $rb and $avp(rtp_sdp_read) as well.
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] KW 2019 presentation files
Hi, Thanks for the link, but I am looking for pdf docs. пн, 8 июл. 2019 г. в 16:13, Markus Monka : > Hi, > > you can find the presentation as videos on youtube: > > https://www.youtube.com/channel/UCElq4JNTPd7bs2vbfAAYVJA > > Best Regards > Markus > > On Mon, Jul 8, 2019 at 2:48 PM Denys Pozniak > wrote: > >> Hello! >> >> Where can I find fresh presentation files from the KW 2019? >> >> PS. Nothing here: https://www.kamailio.org/events/ >> >> -- >> >> BR, >> Denys Pozniak >> >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > > > -- > Dipl. Ing. > Markus Monka - mmo...@sipgate.de > Telefon: +49 (0)211-63 55 55-23 > Telefax: +49 (0)211-63 55 55-22 > > sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf > HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois > Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 > _______ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] KW 2019 presentation files
Hello! Where can I find fresh presentation files from the KW 2019? PS. Nothing here: https://www.kamailio.org/events/ -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Rabbitmq module blocks sip request
Hello!
I use rabbitmq module to get destination IP for the next call routing, but
this module blocks sip request in case of RabbitMQ server is unreachable
(timeout_sec/usec does not run out here).
- Is there any solution to avoid such behavior and force function
rabbitmq_publish_consume() to return an error code and continue script
execution?
- Is this connected with the nature of rabbitmq-c client? ("Currently
librabbitmq offers no async API, but sync API, with a timeout.")
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Centos 7 opensuse repo issues for 5.2
>> = >> Install 1 Package >> >> Total download size: 5.6 M >> Installed size: 25 M >> Downloading packages: >> Delta RPMs disabled because /usr/bin/applydeltarpm not installed. >> kamailio-5.2.2-3.el7.centos.x8 >> FAILED >> >> http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.2.x-rpms/CentOS_7/x86_64/kamailio-5.2.2-3.el7.centos.x86_64.rpm: >> [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable >> Trying other mirror. >> >> >> Error downloading packages: >> kamailio-5.2.2-3.el7.centos.x86_64: [Errno 256] No more mirrors to try. >> >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Use Kamailio as forward proxy between two networks
Hello! Maybe it will help you: https://kamailio.org/docs/modules/devel/modules/rtpproxy.html#rtpproxy.f.rtpproxy_ofrer *i, e - these flags specify the direction of the SIP message. These flags only make sense when rtpproxy is running in bridge mode. 'i' means internal network (LAN), 'e' means external network (WAN). 'i' corresponds to rtpproxy's first interface, 'e' corresponds to rtpproxy's second interface. You always have to specify two flags to define the incoming network and the outgoing network. For example, 'ie' should be used for SIP message received from the local interface and sent out on the external interface, and 'ei' vice versa. Other options are 'ii' and 'ee'. So, for example if a SIP requests is processed with 'ie' flags, the corresponding response must be processed with 'ie' flags.* пн, 1 апр. 2019 г. в 16:59, Lauritz : > Hello, > > I am trying to implement the following network setup using Kamailio and > RTPProxy, but was not able to find any recent documentation or blog posts > with hints: > > local_net1 : local_net2 > 10.250.10.* : 10.250.11.* > : > (1)(2) : > +-+ +--+ > +--+ > ! !.11.12 ! Proxy!.21 ! Debian > Host !.22 > ! Starface!---! + Kamailio !<<--! + > Linphone !.23 > ! ! ! + RTPProxy ! > ! ! > +-+ +--+ > +--+ > eth0 : eth1 > : > : > > > As you can see, the proxy has two interfaces and its purpose is to forward > traffic from the client's network to the Starface's network. > > Has anyone experience to share or got any other hints where to start? > Thank you very much for your help :) > > Kind regards, > Lauritz > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] presence_dialoginfo module not sending publish on dialogue change
Hello!
I am using construction below to send PUBLISH to the SERVER on call state
events and it works well.
Table watchers is emty on suscriber side too.
...
modparam("pua", "db_url", DB_URL)
modparam("pua", "outbound_proxy", SERVER)
modparam("pua_dialoginfo", "send_publish_flag", 8)
...
request_route {
...
setflag(8);
...
}
пт, 29 мар. 2019 г. в 23:28, Richard Nunley :
> To whom can be of assistance,
>
>
>
> I’m am working towards enabling presence on my Kamailio proxy but have hit
> a bit of a brick wall. I’m seeing dialogues being created and persisted to
> the database, subscriptions are being handled and rows are being written to
> the active_watchers table but no PUBLISH is ever being received by the
> server to kickoff the sending of NOTIFY to the active watchers. Further,
> I’m never seeing a row in the watchers table though I don’t know that this
> isn’t expect behavior. I’ve attached my current config for review. Any help
> will be greatly appreciated!
>
>
>
> Thank in advance!
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Presence module. How to update contact DB record after re-SUBSCRIBE ?
Hello!
We are using Presence module with MySQL with parameters below. And looks
like module does not update contact DB record in case of re-SUBSCRIBE.
So we have a case when NAT router periodically changes the outgoing port,
but NOTIFY from Kamailio goes to port from initial SUBSCRIBE.
Is this normal module behavior or we missed something?
modparam("presence", "db_url", DBURL)
modparam("presence", "subs_db_mode", 3)
modparam("presence", "timeout_rm_subs", 0)
modparam("presence", "expires_offset", 0)
modparam("presence", "max_expires", 1800)
modparam("presence", "db_update_period", 30)
modparam("presence", "clean_period", 180)
modparam("presence", "send_fast_notify", 1)
modparam("presence", "pres_htable_size", 32)
modparam("presence", "subs_htable_size", 32)
modparam("presence", "publ_cache", 0)
modparam("presence", "notifier_processes", 0)
# kamailio -v
version: kamailio 4.4.2 (x86_64/linux) 892ad6
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
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_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 892ad6
compiled on 14:45:42 Sep 26 2017 with gcc 4.8.5
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] radius_www_authorize error code -1
Hello!
We are using radius_www_authorize() function to authorize incoming SIP
REGISTERs, but sometimes happens case -1: for valid credentials (as I could
see this in sngrep).
And this time I did not detect corresponding Access-Request to RADIUS
server side.
Setting Kamailio debug level does not help to catch the real reason for
this case in syslog.
How to investigate this issue?
Simple script example:
if (!radius_www_authorize("$td")) {
switch ($rc) {
case -1:
send_reply("400", "Bad Request");
exit;
default:
};
};
# -1 (error) - some error occurred during authorization (see syslog);
[root@kamaili]# kamailio -v
version: kamailio 4.4.2 (x86_64/linux) 892ad6
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
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_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 892ad6
compiled on 14:33:45 Apr 18 2018 with gcc 4.8.5
[root@kamailio]# rpm -qa | grep freeradius-client
freeradius-client-1.1.7-16.el7.centos.x86_64
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Sanity check with default_checks=0
It shows error and sometimes it brakes REGISTER:
ERROR: sanity [sanity_mod.c:228]: w_sanity_check(): input parameter (0)
outside of valid range <1-16384)
чт, 7 мар. 2019 г. в 15:10, Daniel-Constantin Mierla :
> Hello,
>
> On 07.03.19 12:04, Denys Pozniak wrote:
> > Hello!
> >
> > I have Kamailio v4.4 and use (historical) the next param setting to
> > disable sanity check:
> > modparam("sanity", "default_checks", 0)
> >
> > I see that this value 0 is not described in module documentation, but
> > looks like this modparam behaves in another way on Kamailio v5.
> >
> > So my question is how to disable sanity checking in modparam?
>
> How it behaves in v5?
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla -- www.asipto.com
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
> Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA --
> www.asipto.com
>
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Sanity check with default_checks=0
Hello!
I have Kamailio v4.4 and use (historical) the next param setting to disable
sanity check:
modparam("sanity", "default_checks", 0)
I see that this value 0 is not described in module documentation, but looks
like this modparam behaves in another way on Kamailio v5.
So my question is how to disable sanity checking in modparam?
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Dispatcher problem $avp(dsattrs) is null
Hello!
Do you have as follows parameter?
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")
чт, 28 февр. 2019 г. в 05:21, jaflong jaflong :
>
> I am doing a ds_select_dst call. I think dispatcher did run because $du
> gets updated
>
>
> The problem is $(avp(dsattrs)) value is null.
>
> Any ideas why?
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Dispatcher with parameter use_default=1
Thanks!
I set in the way below, looks working. Maybe wiki needs to be updated?
4 sip:10.6.3.122:5060 0 5
4 sip:10.6.3.1:5060 0 5
4 sip:10.6.3.2:5060 0 5
4 sip:10.6.3.3:5060 0 5
4 sip:10.6.3.4:5060 0 5
4 sip:10.6.3.5:5060 0 1
вт, 26 февр. 2019 г. в 17:48, Daniel-Constantin Mierla :
> Hello,
>
> you have to set the priority field for each destination to ensure a
> particular order there. While with text file one can consider the order of
> appearance, this is no longer valid for database -- the order in a table
> can be different that what is returned by "select * ...", therefore the
> priority field is the one that matter here.
>
> Cheers,
> Daniel
> On 26.02.19 16:40, Denys Pozniak wrote:
>
>
> kamcmd dispatcher.list shows gateways in reverse order (comparing to the
> file) and "last hope" gw is the last one here (URI: sip:10.6.3.122:5060).
>
> SET: {
> ID: 4
> TARGETS: {
> DEST: {
> URI: sip:10.6.3.5:5060
> FLAGS: AX
> PRIORITY: 0
> }
> DEST: {
> URI: sip:10.6.3.4:5060
> FLAGS: AX
> PRIORITY: 0
> }
> DEST: {
> URI: sip:10.6.3.3:5060
> FLAGS: AX
> PRIORITY: 0
> }
> DEST: {
> URI: sip:10.6.3.2:5060
> FLAGS: AX
> PRIORITY: 0
> }
> DEST: {
> URI: sip:10.6.3.1:5060
> FLAGS: AX
> PRIORITY: 0
> }
> DEST: {
> URI: sip:10.6.3.122:5060
> FLAGS: AX
> PRIORITY: 0
> }
> }
> }
>
>
>
> вт, 26 февр. 2019 г. в 17:24, Denys Pozniak :
>
>> Hello!
>>
>> I use dispatcher with algorithm=1 (hashing over from URI) with module
>> parameter use_default=1.
>> So I am expecting that last string in dispatcher.list for specific set
>> will be the "last hope" for call routing.
>>
>> dispatcher.list
>> ..
>> 4 sip:10.6.3.122:5060
>> 4 sip:10.6.3.1:5060
>> 4 sip:10.6.3.2:5060
>> 4 sip:10.6.3.3:5060
>> 4 sip:10.6.3.4:5060
>> 4 sip:10.6.3.5:5060
>>
>> But as I see from logs dispatcher module takes first string as the "last
>> hope":
>>
>> xlog("L_WARN", "TEST-- $(avp(AVP_DST)[0]) $(avp(AVP_DST)[1])
>> $(avp(AVP_DST)[2]) $(avp(AVP_DST)[3]) $(avp(AVP_DST)[4])
>> $(avp(AVP_DST)[5]) $(avp(AVP_DST)[6]) \n");
>>
>> Feb 26 16:11:39 kamailio-2 /usr/sbin/kamailio[28156]: WARNING:
Re: [SR-Users] Dispatcher with parameter use_default=1
kamcmd dispatcher.list shows gateways in reverse order (comparing to the
file) and "last hope" gw is the last one here (URI: sip:10.6.3.122:5060).
SET: {
ID: 4
TARGETS: {
DEST: {
URI: sip:10.6.3.5:5060
FLAGS: AX
PRIORITY: 0
}
DEST: {
URI: sip:10.6.3.4:5060
FLAGS: AX
PRIORITY: 0
}
DEST: {
URI: sip:10.6.3.3:5060
FLAGS: AX
PRIORITY: 0
}
DEST: {
URI: sip:10.6.3.2:5060
FLAGS: AX
PRIORITY: 0
}
DEST: {
URI: sip:10.6.3.1:5060
FLAGS: AX
PRIORITY: 0
}
DEST: {
URI: sip:10.6.3.122:5060
FLAGS: AX
PRIORITY: 0
}
}
}
вт, 26 февр. 2019 г. в 17:24, Denys Pozniak :
> Hello!
>
> I use dispatcher with algorithm=1 (hashing over from URI) with module
> parameter use_default=1.
> So I am expecting that last string in dispatcher.list for specific set
> will be the "last hope" for call routing.
>
> dispatcher.list
> ..
> 4 sip:10.6.3.122:5060
> 4 sip:10.6.3.1:5060
> 4 sip:10.6.3.2:5060
> 4 sip:10.6.3.3:5060
> 4 sip:10.6.3.4:5060
> 4 sip:10.6.3.5:5060
>
> But as I see from logs dispatcher module takes first string as the "last
> hope":
>
> xlog("L_WARN", "TEST-- $(avp(AVP_DST)[0]) $(avp(AVP_DST)[1])
> $(avp(AVP_DST)[2]) $(avp(AVP_DST)[3]) $(avp(AVP_DST)[4])
> $(avp(AVP_DST)[5]) $(avp(AVP_DST)[6]) \n");
>
> Feb 26 16:11:39 kamailio-2 /usr/sbin/kamailio[28156]: WARNING:
[SR-Users] Dispatcher with parameter use_default=1
Hello!
I use dispatcher with algorithm=1 (hashing over from URI) with module
parameter use_default=1.
So I am expecting that last string in dispatcher.list for specific set will
be the "last hope" for call routing.
dispatcher.list
..
4 sip:10.6.3.122:5060
4 sip:10.6.3.1:5060
4 sip:10.6.3.2:5060
4 sip:10.6.3.3:5060
4 sip:10.6.3.4:5060
4 sip:10.6.3.5:5060
But as I see from logs dispatcher module takes first string as the "last
hope":
xlog("L_WARN", "TEST-- $(avp(AVP_DST)[0]) $(avp(AVP_DST)[1])
$(avp(AVP_DST)[2]) $(avp(AVP_DST)[3]) $(avp(AVP_DST)[4])
$(avp(AVP_DST)[5]) $(avp(AVP_DST)[6]) \n");
Feb 26 16:11:39 kamailio-2 /usr/sbin/kamailio[28156]: WARNING:
Re: [SR-Users] Memory allocator was called from cdp: diameter_avp.c:365
Hello! Issue was created: https://github.com/kamailio/kamailio/issues/1851 пт, 15 февр. 2019 г. в 09:33, Daniel-Constantin Mierla : > Hello, > > it looks like a buffer overflow there. I am not familiar with the cdp > module, however, if nobody takes over it, I will try to troubleshoot as I > get some spare time. So it is better to open an bug on issue tracker on > github project not to forget about this one. Also, keep the core file > because it may be needed to get some more info from it with gdb. > > Cheers, > Daniel > On 14.02.19 16:46, Denys Pozniak wrote: > > Hello! > > I have faced with Kamailio (5.1.7) crashes, probably it is connected to > cdp module, please check the source of issue: > > 14(5649) INFO: cdp [receiver.c:455]: receiver_process(): > receiver_process(): [diameter1.dev] Receiver process doing init on new > process... > 14(5649) INFO: cdp [receiver.c:188]: add_serviced_peer(): > add_serviced_peer(): Adding serviced_peer_t to receiver for peer > [diameter1.dev] > 14(5649) INFO: cdp [receiver.c:460]: receiver_process(): > receiver_process(): [diameter1.dev] Receiver process starting up... > 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver > cdp_receiver_peer=diameter1.dev Serviced Peers: --- > 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: > diameter1.dev TCP Socket: -1 Recv.State: 0 > 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): > > 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver > cdp_receiver_peer=diameter1.dev Serviced Peers: --- > 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: > diameter1.dev TCP Socket: -1 Recv.State: 0 > 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): > > 16(5651) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 16 > rank 1001: cdp [cdp_timer] > 16(5651) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 16 > rank 1001: cdp_avp [cdp_timer] > 16(5651) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): > Initializing child in module cdp_avp for rank [1001] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: acc [cdp_acceptor] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: uac [cdp_acceptor] > 16(5651) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 16 > rank 1001: ims_charging [cdp_timer] > 16(5651) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 16 > rank 1001: ims_dialog [cdp_timer] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: htable [cdp_acceptor] > 15(5650) DEBUG: htable [htable.c:236]: child_init(): rank is (1000) > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: carrierroute [cdp_acceptor] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: dispatcher [cdp_acceptor] > 16(5651) INFO: cdp [timer.c:205]: timer_process(): Timer process starting > up... > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: cdp [cdp_acceptor] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: cdp_avp [cdp_acceptor] > 15(5650) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): > Initializing child in module cdp_avp for rank [1000] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: ims_charging [cdp_acceptor] > 15(5650) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 15 > rank 1000: ims_dialog [cdp_acceptor] > 15(5650) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process > starting up... > 15(5650) DEBUG: cdp [tcp_accept.c:114]: create_socket(): create_sockets: > create socket and bind for IPv4... > 15(5650) WARNING: cdp [tcp_accept.c:121]: create_socket(): > create_socket(): Trying to open/bind/listen on 10.10.10.10 port 38680 > 15(5650) WARNING: cdp [tcp_accept.c:146]: create_socket(): > create_socket(): Successful socket open/bind/listen on 10.10.10.10 port > 38680 > 15(5650) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened > sockets. Entering accept loop ... > [root@10-10-10-10 kamailio]# 17(5652) DEBUG: > [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: kex [tcp main > process] > 17(5652) DEBUG: kex [kex_mod.c:157]: child_init(): rank is (-4) > 17(5652) DEBUG: [sruid.c:106]: sruid_init(): root for sruid is > [srid-5c658bbb-1614-] (0 / 19) > 17(5652) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 17 > rank -4: corex [tcp main process] > 17(5652) DEBUG: [core/sr_module.c:942]: init_mod_child(): idx 17 > rank -4: tm [tcp main process] > 17(5652) DE
[SR-Users] Memory allocator was called from cdp: diameter_avp.c:365
943
__FUNCTION__ = "init_mod_child"
#17 0x0053b353 in init_mod_child (m=0x7fbde5885dc8, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#18 0x0053b353 in init_mod_child (m=0x7fbde5886190, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#19 0x0053b353 in init_mod_child (m=0x7fbde58865d0, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#20 0x0053ba85 in init_child (rank=0) at core/sr_module.c:970
No locals.
#21 0x00424fe5 in main_loop () at main.c:1701
i = 4
pid = 5641
si = 0x0
si_desc = "udp receiver child=3
sock=10.10.10.10:5060\000\275\177\000\000\300\023\na\376\177\000\000\022\000\000\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\200\000\000\000\000\000\263\215z",
'\000' ,
"\220\026\na\376\177\000\000\207\"\003\346\275\177\000\000\260yw\000\000\000\000\000\060;\223\345\275\177\000"
nrprocs = 4
woneinit = 1
__FUNCTION__ = "main_loop"
#22 0x0042b994 in main (argc=4, argv=0x7ffe610a1778) at main.c:2642
cfg_stream = 0x103a020
c = -1
r = 0
tmp = 0x0
tmp_len = 0
port = 0
proto = 0
options = 0x758c10
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"
ret = -1
seed = 1364069336
rfd = 4
debug_save = 0
debug_flag = 0
dont_fork_cnt = 0
n_lst = 0x0
p = 0x0
st = {st_dev = 19, st_ino = 68292, st_nlink = 2, st_mode = 16832,
st_uid = 995, st_gid = 994, __pad0 = 0, st_rdev = 0, st_size = 40,
st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1550156643,
tv_nsec = 63000}, st_mtim = {tv_sec = 1550158563, tv_nsec =
502470819}, st_ctim = {tv_sec = 1550158563, tv_nsec = 502470819}, __unused
= {0, 0, 0}}
__FUNCTION__ = "main"
(gdb)
version: kamailio 5.1.7 (x86_64/linux) 567df3
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
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_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_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: 567df3
compiled on 02:06:09 Feb 2 2019 with gcc 4.8.5
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] reg_fetch_contacts and t_relay usage
Hello! Try to use indexes: http://kamailio.org/docs/modules/stable/modules/registrar.html#idm1026882308 пн, 11 февр. 2019 г. в 17:44, Володимир Іванець : > Hello! > > I'm using *reg_fetch_contacts* function to get information about all > contacts. This allows to define which contacts should receive the call. My > question is if it's possible to choose only one contact before *t_relay* is > called? Or *reg_fetch_contacts* call and verification should be done > after *t_relay* in all branches and those which are not needed should be > stopped? > > Thanks a lot! > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Diameter (CDP) crashes on startup. ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
357) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer:
dev-diameter-1.ams.proxy.dev TCP Socket: 10 Recv.State: 2
24(17357) DEBUG: cdp [receiver.c:114]: log_serviced_peers():
24(17357) DEBUG: cdp [receiver.c:1107]: receive_message():
receive_message(): [dev-diameter-1.ams.proxy.dev] Recv msg 257
24(17357) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process():
Peer dev-diameter-1.ams.proxy.dev State Wait_I_CEA Event I_Rcv_CEA
24(17357) DEBUG: cdp [peerstatemachine.c:698]:
count_Supported_Vendor_Id_AVPS(): Found 0 Supported_Vendor AVPS24(17357)
DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 0
of maximum 0
24(17357) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage():
AAAFreeMessage: Freeing message (0x7fc375e01da0) 257
24(17357) CRITICAL: [core/mem/q_malloc.c:149]:
qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0,
abcdefed)[0x7fc375e023c8:0x7fc375e02400]! Memory allocator was called from
cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec
from core/mem/q_malloc.c:504.
25(17358) DEBUG: cdp [tcp_accept.c:221]: accept_loop(): accept_loop(): No
connection attempts
23(17356) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver
cdp receiver peer unknown Serviced Peers: ---
23(17356) DEBUG: cdp [receiver.c:114]: log_serviced_peers():
23(17356) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver
cdp receiver peer unknown Serviced Peers: ---
23(17356) DEBUG: cdp [receiver.c:114]: log_serviced_peers():
26(17359) DEBUG: cdp [session.c:396]: cdp_sessions_log(): --- CDP
Sessions
26(17359) DEBUG: cdp [session.c:431]: cdp_sessions_log():
-
32(17365) CRITICAL: [core/pass_fd.c:277]: receive_fd(): EOF on 39
32(17365) DEBUG: [core/tcp_main.c:3513]: handle_ser_child(): dead
child 24, pid 17357 (shutting down?)
32(17365) DEBUG: [core/io_wait.h:602]: io_watch_del(): DBG:
io_watch_del (0xa838a0, 39, -1, 0x0) fd_no=39 called
0(17333) ALERT: [main.c:756]: handle_sigs(): child process 17357
exited by a signal 6
0(17333) ALERT: [main.c:759]: handle_sigs(): core was generated
0(17333) INFO: [main.c:781]: handle_sigs(): terminating due to
SIGCHLD
0(17333) DEBUG: [main.c:783]: handle_sigs(): terminating due to
SIGCHLD
31(17364) INFO: [main.c:836]: sig_usr(): signal 15 received
...
0(17333) DEBUG: cdp_avp [cdp_avp_mod.c:225]: cdp_avp_destroy(): Destroying
module cdp_avp
0(17333) INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child
stopping ...
0(17333) INFO: cdp [diameter_peer.c:364]: diameter_peer_destroy():
destroy_diameter_peer(): Terminating all children...
0(17333) INFO: cdp [diameter_peer.c:371]: diameter_peer_destroy():
destroy_diameter_peer(): Waiting for child [17359] to terminate...
...
0(17333) INFO: cdp [diameter_peer.c:383]: diameter_peer_destroy():
destroy_diameter_peer(): All processes terminated. Cleaning up.
0(17333) INFO: cdp [worker.c:139]: worker_destroy(): Unlocking workers
waiting on empty queue...
0(17333) INFO: cdp [worker.c:142]: worker_destroy(): Unlocking workers
waiting on full queue...
0(17333) DEBUG: cdp [peermanager.c:129]: peer_manager_destroy():
peer_manager_init(): ...Peer Manager destroyed
0(17333) CRITICAL: cdp [diameter_peer.c:423]: diameter_peer_destroy():
destroy_diameter_peer(): Bye Bye from C Diameter Peer test
0(17333) INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child
stopped
0(17333) DEBUG: tm [t_funcs.c:85]: tm_shutdown(): start
0(17333) DEBUG: tm [t_funcs.c:88]: tm_shutdown(): emptying hash table
0(17333) DEBUG: tm [t_funcs.c:90]: tm_shutdown(): removing semaphores
0(17333) DEBUG: tm [t_funcs.c:92]: tm_shutdown(): destroying tmcb lists
0(17333) DEBUG: tm [t_funcs.c:95]: tm_shutdown(): done
0(17333) INFO: [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API
not initialized
0(17333) DEBUG: [core/mem/shm.c:283]: shm_destroy_manager():
destroying memory manager: q_malloc
0(17333) DEBUG: [core/mem/q_malloc.c:1178]: qm_shm_lock_destroy():
destroying the shared memory lock
0(17333) DEBUG: [core/mem/pkg.c:91]: pkg_destroy_manager():
destroying memory manager: q_malloc
Configs:
[root@test]# cat diameter.xml
[root@test]# cat kamailio.cfg
#!KAMAILIO
children=5
memdbg=5
memlog=5
debug=3
log_stderror=no
log_facility=LOG_LOCAL0
fork=yes
disable_tcp=no
auto_aliases=no
mpath="/usr/lib64/kamailio/modules/"
loadmodule "kex.so"
loadmodule "tm.so"
loadmodule "sl.so"
loadmodule "rr.so"
loadmodule "xlog.so"
loadmodule "cfg_rpc.so"
loadmodule "cdp.so"
loadmodule "cdp_avp.so"
modparam("cdp","config_file","/etc/kamailio_test/diameter.xml")
modparam("
[SR-Users] Diameter (CDP) crashes on startup. ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
__FUNCTION__ = "receiver_process"
#14 0x7f3ed05fd7de in diameter_peer_start (blocking=0) at
diameter_peer.c:289
pid = 0
k = -1
p = 0x7f3ecb7a00d8
__FUNCTION__ = "diameter_peer_start"
#15 0x7f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243
__FUNCTION__ = "cdp_child_init"
#16 0x00544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at
core/sr_module.c:943
__FUNCTION__ = "init_mod_child"
#17 0x00544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#18 0x00544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#19 0x00544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#20 0x00545205 in init_child (rank=0) at core/sr_module.c:970
No locals.
#21 0x00424f85 in main_loop () at main.c:1701
i = 32
pid = 7821
si = 0x0
si_desc = "udp receiver child=31
sock=10.10.10.10:5060\000\177\000\000`\336\275\206\375\177\000\000A\307g\000\000\000\000\000`\202A\000\000\000\000\000ȖP\313>\177",
'\000' ,
"\001\000\000\000\260\336\275\206\375\177\000\000\234\240h\000\000\000\000\000
\243w\000\000\000\000\000H\361m\327>\177\000"
nrprocs = 32
woneinit = 1
__FUNCTION__ = "main_loop"
#22 0x0042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638
cfg_stream = 0x2b13020
c = -1
r = 0
tmp = 0x0
tmp_len = 0
port = 0
proto = 0
options = 0x758490
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"
ret = -1
seed = 4201223303
rfd = 4
debug_save = 0
debug_flag = 0
dont_fork_cnt = 4
n_lst = 0x0
p = 0x0
st = {st_dev = 19, st_ino = 82198, st_nlink = 2, st_mode = 16832,
st_uid = 995, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize
= 4096, st_blocks = 0, st_atim = {tv_sec = 1547739314,
tv_nsec = 58200}, st_mtim = {tv_sec = 1547743303, tv_nsec =
194148453}, st_ctim = {tv_sec = 1547743303, tv_nsec = 194148453}, __unused
= {0, 0, 0}}
__FUNCTION__ = "main"
(gdb)
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Updating default kamailio.cfg to use rtpengine
Karsten, if you use repo for rtpengine, please share the link. ср, 16 янв. 2019 г. в 19:16, Karsten Horsmann : > Hello Daniel, > > I use rtpengine on Centos 7. It's possible to create an DKMS package > (automatic rebuild for new Kernel version). > > Kind regards > Karsten > > Am Di., 15. Jan. 2019, 10:00 hat Daniel-Constantin Mierla < > mico...@gmail.com> geschrieben: > >> Hello, >> >> being discussed at events offline or during irc meetings couple of >> times, I want to open the discussion about updating the default >> configuration file to use rtpengine. So far I let rtpproxy because was >> packaged in many Linux distros, however, given the benefits of rtpengine >> in terms of performance as well as webrtc support, doubled by the fact >> that nowadays in the community it seems to be the primary choice of rtp >> relay, we should decide what to do. I see two options: >> >> 1) add a define to allow selection between rtpproxy and rtpengine >> >> 2) replace rtpproxy completely with rtpengine >> >> I would prefer 2) for simplicity of the configuration file, but the main >> question for the users community is how easy they find the deploying of >> rtpengine. Using Debian/Ubuntu should be trivial, there are packages for >> it, but I do not know about CentOS, Fedora, openSUSE or other Linux/BSD >> OSes people here are using it. >> >> Reply to sr-users if you have an opinion on this matter (I cc-ed sr-dev >> mainly to make aware the devs, but it is a matter of using kamailio). Of >> course, other suggestions are welcome as well. >> >> Cheers, >> Daniel >> >> -- >> Daniel-Constantin Mierla -- www.asipto.com >> www.twitter.com/miconda -- www.linkedin.com/in/miconda >> Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com >> Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in >> Washington, DC, USA -- www.asipto.com >> >> >> ___ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR, Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Logging from cfg file
Now it works!
Thanks!
пн, 14 янв. 2019 г. в 12:47, Daniel-Constantin Mierla :
> Hello,
>
> have you loaded corex module?
>
> Cheers,
> Daniel
> On 14.01.19 10:40, Denys Pozniak wrote:
>
> Hello!
> Tried to use $cfg(line), but got error.
> Please point me where the issue is.
>
> loadmodule "cfgutils.so"
> xlog("L_WARNING", "route block: $cfg(line) \n");
>
> Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/pvapi.c:903]:
> pv_parse_spec2(): error searching pvar "cfg"
> Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/pvapi.c:1107]:
> pv_parse_spec2(): wrong char [l/108] in [$cfg(line)] at [5 (5)]
> Jan 14 10:39:19 dev kamailio[10856]: ERROR: xlog [xlog.c:513]:
> xdbg_fixup_helper(): wrong format[pvar $cfg(line) #012]
> Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/route.c:1154]:
> fix_actions(): fixing failed (code=-1) at
> cfg:/etc/kamailio/routing.d/main.cfg:8
>
> # kamailio -v
> version: kamailio 5.1.6 (x86_64/linux)
>
>
>
> вс, 30 дек. 2018 г. в 05:19, Joel Serrano :
>
>> Adding it to my log_prefix !!!
>>
>> Sounds dum but this simplifies my logging so much
>>
>> Thanks guys, every day you learn something new!
>>
>>
>> On Sat, Dec 29, 2018 at 14:42 David Villasmil <
>> david.villasmil.w...@gmail.com> wrote:
>>
>>> yep: $cfg(route)
>>> added Jun 2017
>>> Regards,
>>>
>>> David Villasmil
>>> email: david.villasmil.w...@gmail.com
>>> phone: +34669448337
>>>
>>>
>>> On Sat, Dec 29, 2018 at 10:09 PM * Paolo Visintin - evosip.cloud
>>> wrote:
>>>
>>>> Joel , you could use $cfg(route) !
>>>>
>>>> I usually store my breadcrumbs in a define and use on top of every
>>>> interesting route !
>>>>
>>>>
>>>> Il giorno sab 29 dic 2018 alle 21:29 Joel Serrano
>>>> ha scritto:
>>>>
>>>>> I wonder if there is a $something that contains the route-block-name?
>>>>>
>>>>> Anyone know?
>>>>>
>>>>>
>>>>> On Sat, Dec 29, 2018 at 10:52 David Villasmil <
>>>>> david.villasmil.w...@gmail.com> wrote:
>>>>>
>>>>>> I prefer using
>>>>>>
>>>>>> log(“L_ERR”, “[REQUEST_ROUTE]: $ci Register Request\n”);
>>>>>>
>>>>>> That way you have the route block where you are logging from and the
>>>>>> Call-ID with your information string. (I mostly use L_ERR when debugging)
>>>>>>
>>>>>> Cheers
>>>>>> On Sat, 29 Dec 2018 at 11:02, Mojtaba wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> You could use xlog instead of log, like this:
>>>>>>> xlog("Register request...\n");
>>>>>>> With Regards.Mojtaba
>>>>>>>
>>>>>>> On Sat, Dec 29, 2018 at 11:14 AM Muhammad Allaudin
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Hi everyone,
>>>>>>> >
>>>>>>> > I have recently started working on Kamailio, I am trying to learn
>>>>>>> the basics. For "Register" route, I am trying to print the log but log
>>>>>>> is
>>>>>>> not appearing in log file. Other logs are there, only this one is
>>>>>>> missing.
>>>>>>> >
>>>>>>> > if(is_method("REGISTER")){
>>>>>>> > log(2, "Register request");
>>>>>>> > }
>>>>>>> >
>>>>>>> > I will be really helpful if you can help me with this.
>>>>>>> >
>>>>>>> > Thanks & Kind Regards
>>>>>>> >
>>>>>>> > Regards,
>>>>>>> > M.Allaudin
>>>>>>> > Software Engineer
>>>>>>> > Nowtel Group
>>>>>>> > Phone # +92-333-8291874
>>>>>>> > Blogger @ allaudin.github.io
>>>>>>> > ___
>>>>>>> > Kamailio (SER) - Users Mailing List
>>>>>>> > sr-users@lists.kamailio.org
>>>>>>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>
>>>>
Re: [SR-Users] Logging from cfg file
Hello!
Tried to use $cfg(line), but got error.
Please point me where the issue is.
loadmodule "cfgutils.so"
xlog("L_WARNING", "route block: $cfg(line) \n");
Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/pvapi.c:903]:
pv_parse_spec2(): error searching pvar "cfg"
Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/pvapi.c:1107]:
pv_parse_spec2(): wrong char [l/108] in [$cfg(line)] at [5 (5)]
Jan 14 10:39:19 dev kamailio[10856]: ERROR: xlog [xlog.c:513]:
xdbg_fixup_helper(): wrong format[pvar $cfg(line) #012]
Jan 14 10:39:19 dev kamailio[10856]: ERROR: [core/route.c:1154]:
fix_actions(): fixing failed (code=-1) at
cfg:/etc/kamailio/routing.d/main.cfg:8
# kamailio -v
version: kamailio 5.1.6 (x86_64/linux)
вс, 30 дек. 2018 г. в 05:19, Joel Serrano :
> Adding it to my log_prefix !!!
>
> Sounds dum but this simplifies my logging so much
>
> Thanks guys, every day you learn something new!
>
>
> On Sat, Dec 29, 2018 at 14:42 David Villasmil <
> david.villasmil.w...@gmail.com> wrote:
>
>> yep: $cfg(route)
>> added Jun 2017
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.w...@gmail.com
>> phone: +34669448337
>>
>>
>> On Sat, Dec 29, 2018 at 10:09 PM * Paolo Visintin - evosip.cloud
>> wrote:
>>
>>> Joel , you could use $cfg(route) !
>>>
>>> I usually store my breadcrumbs in a define and use on top of every
>>> interesting route !
>>>
>>>
>>> Il giorno sab 29 dic 2018 alle 21:29 Joel Serrano
>>> ha scritto:
>>>
>>>> I wonder if there is a $something that contains the route-block-name?
>>>>
>>>> Anyone know?
>>>>
>>>>
>>>> On Sat, Dec 29, 2018 at 10:52 David Villasmil <
>>>> david.villasmil.w...@gmail.com> wrote:
>>>>
>>>>> I prefer using
>>>>>
>>>>> log(“L_ERR”, “[REQUEST_ROUTE]: $ci Register Request\n”);
>>>>>
>>>>> That way you have the route block where you are logging from and the
>>>>> Call-ID with your information string. (I mostly use L_ERR when debugging)
>>>>>
>>>>> Cheers
>>>>> On Sat, 29 Dec 2018 at 11:02, Mojtaba wrote:
>>>>>
>>>>>> Hi,
>>>>>> You could use xlog instead of log, like this:
>>>>>> xlog("Register request...\n");
>>>>>> With Regards.Mojtaba
>>>>>>
>>>>>> On Sat, Dec 29, 2018 at 11:14 AM Muhammad Allaudin
>>>>>> wrote:
>>>>>> >
>>>>>> > Hi everyone,
>>>>>> >
>>>>>> > I have recently started working on Kamailio, I am trying to learn
>>>>>> the basics. For "Register" route, I am trying to print the log but log is
>>>>>> not appearing in log file. Other logs are there, only this one is
>>>>>> missing.
>>>>>> >
>>>>>> > if(is_method("REGISTER")){
>>>>>> > log(2, "Register request");
>>>>>> > }
>>>>>> >
>>>>>> > I will be really helpful if you can help me with this.
>>>>>> >
>>>>>> > Thanks & Kind Regards
>>>>>> >
>>>>>> > Regards,
>>>>>> > M.Allaudin
>>>>>> > Software Engineer
>>>>>> > Nowtel Group
>>>>>> > Phone # +92-333-8291874
>>>>>> > Blogger @ allaudin.github.io
>>>>>> > ___
>>>>>> > Kamailio (SER) - Users Mailing List
>>>>>> > sr-users@lists.kamailio.org
>>>>>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --Mojtaba Esfandiari.S
>>>>>>
>>>>>> ___
>>>>>> Kamailio (SER) - Users Mailing List
>>>>>> sr-users@lists.kamailio.org
>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>> ___
>>>>> Kamailio (SER) - Users Mailing List
>>>>> sr-users@lists.kamailio.org
>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>> ___
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users@lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>> --
>>> *Paolo Visintin*
>>> *CTO*
>>> evosip.cloud
>>> [image: Risultati immagini per evosip]
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
--
BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
