Hi Benoit, checkout this command, you can filter here for more information, which probably is available from a customer service tool: https://kamailio.org/docs/modules/5.6.x/modules/dialog.html#dlg.r.list_match Another idea is to use that comment, which can be tuned to return only needed information: https://kamailio.org/docs/modules/5.6.x/modules/dialog.html#dlg.r.briefing Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com -----Original Message----- From: Benoît Panizzon <benoit.panizzon(a)imp.ch> Sent: Friday, January 20, 2023 11:13 AM To: Henning Westerholt <hw(a)gilawa.com> Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] [core/tcp_main.c:617]: _wbufq_add(): (1244714 bytes): write queue full or timeout Hi Henning The motivation is to provide a diagnosis tool to our customer helpdesk. (And also for me as a tech, to for example find long running calls and other stuff I might be interested in). Simplified: Customer Service enters a phone number of a customer and get an output of all settings like call forwarding (obtained from DB by our own API). But also information about registered AOR and their contacts (obtained by ul.dump) and as bonus: Information about active calls of the customer to which this phone number belongs. So I was looking for a way to gather the dialogues involving the phone number or better, AOR in question. dlg.dlg_list needs the call-id, which is not known. dlg.list_match is limited regarding what key can be used. It probably would work with trying to somehow partially matching ruri or furi, but we translate numbers, so that is a bit fuzzy and might return wrong matches or not match if clip-no-screening is used. The most promising would be to use dlg.list and then loop through the variables to find the dialogues associated with the authentication username (equal to the AOR in our case) of the customer to which the dialogue belongs to. As I kept running into DMQ sync issues with storing dialogue information in database, I switched off database support for dialogue. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

Hi Alex We have two 'core' nodes handling everything that is not related to registrar and location tasks. Therefore the dialog module is used to gather cdrs, but to ensure translated numbers are translated the other way on replies and many more. I noticed, when I restart kamailio after doing config changes, that entries kept accumulating with each restart in the 'dialog' and 'dialog_vars' tables, never expiring even the next day, when the dialog timeout we set to 12 hours should have made sure they got expired. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

Hi Alex That is not a module. We use the dlg_vars to store a lot of information. I would love if there was a module taking care of symmetric number translations in all messages. I think this is a common task. Consider this situation (intentionally using invalid prefixes) Interconnection uses e164 Numbers. eg: +41661234567 for Switzerland and we use NPRN (number portability routing prefixes) numbers to route ported numbers. Customer uses 'national' notation of same number: 0661234567 Call from Customer: RURI: 0661234567 (this is ported to NPRN 99052) From: 0667776655 Call towards IC therefore has to be: RURI: +4199052661234567 From: +4166776655 So I store the original FROM and RURI in dlg_variables so I can put them back in the appropriate header when passing a RINGING or 200 OK back to the customer. Even more important. When there is a Privacy: ID Header present: I (by OFCOM regulations MUST) replace $fu and $fn with 'Anonymous' towards the customer. And of course also the Contact: Username and possibly remove PAI, PPI or whatever the customer does not need to get. But I might want to send him the Diversion Header to indicate who diverted the call, it it's privacy flag allows it of course. On any subsequent messages, re-invites, whatever else is getting sent to the customer. I have to make sure I don't disclose the calling number by mistake (customer could be logging those on his CPE). So, yes, plenty of header usernames to track and replace for all kind of messages and transactions within a dialogue. I will give it another try :-) -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

Hi Benoit, I might not fully understand the logic, but at least for From and To header this can be easily done in a transparent way with the uac module. No need to use dialog variables for that. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com -----Original Message----- From: Benoît Panizzon <benoit.panizzon(a)imp.ch> Sent: Friday, January 20, 2023 4:07 PM To: Alex Balashov <abalashov(a)evaristesys.com> Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Re: [core/tcp_main.c:617]: _wbufq_add(): (1244714 bytes): write queue full or timeout Hi Alex That is not a module. We use the dlg_vars to store a lot of information. I would love if there was a module taking care of symmetric number translations in all messages. I think this is a common task. Consider this situation (intentionally using invalid prefixes) Interconnection uses e164 Numbers. eg: +41661234567 for Switzerland and we use NPRN (number portability routing prefixes) numbers to route ported numbers. Customer uses 'national' notation of same number: 0661234567 Call from Customer: RURI: 0661234567 (this is ported to NPRN 99052) From: 0667776655 Call towards IC therefore has to be: RURI: +4199052661234567 From: +4166776655 So I store the original FROM and RURI in dlg_variables so I can put them back in the appropriate header when passing a RINGING or 200 OK back to the customer. Even more important. When there is a Privacy: ID Header present: I (by OFCOM regulations MUST) replace $fu and $fn with 'Anonymous' towards the customer. And of course also the Contact: Username and possibly remove PAI, PPI or whatever the customer does not need to get. But I might want to send him the Diversion Header to indicate who diverted the call, it it's privacy flag allows it of course. On any subsequent messages, re-invites, whatever else is getting sent to the customer. I have to make sure I don't disclose the calling number by mistake (customer could be logging those on his CPE). So, yes, plenty of header usernames to track and replace for all kind of messages and transactions within a dialogue. I will give it another try :-) -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: