Hi Henning
not sure about your motivation in using this method on
a busy
production system. Usually this is not necessary.
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
______________________________________________________