22 Jul
2010
22 Jul
'10
8:37 p.m.
Hey,
Iñaki Baz Castillo wrote:
2010/7/21 Timo Reimann <timo.reimann(a)1und1.de>de>:
Ops, really sorry, in fact I *alreay* use it! and it's a good
solution. Sorry, not sure what I was thinking about when asked the
question XD
However I still think that having custom variables associated to
dialogs could be useful for some other cases.
Hmm, not sure if I get you. According to the docs, you can pass
pseudo-variables to profiles already now. How would the current dialog
interface need to differ in your opinion?
Could be elaborate a bit please?
Thanks,
--Timo
In my
case when my kamailio handles a call it sets it a "client_name"
profile which is enough to list/terminate all the calls belonging to
such client.
But sometimes I need to terminate those calls with a specific CLI, and
the CLI is not the From username but a custon PAI inserted by
Kamailio. This info is not stored with the dialog.
A workaround could be settting the dialog in two profiles: client_name
and PAI, but I think it's not very elegant.
Also I think that storing custom variables within each dialog could be
very useful for other subjects.
Opinions? Thanks.
Have you considered using profiles that are associated to
specific
values? I haven't tried them myself but it looks pretty much like what
you seek. Consider exported functions *profile(profile, value), and the
MI function "profile_list_dlgs":