Hi John,

For the current call, you can access dialog attributes via the "$dlg(...)" pseudo-variable. But I don't believe there is a way to access other dialogs from within the config script without querying the database (and setting db_mode to 1).

If you can explain your use case slightly, someone may be able to suggest another way to achieve it.

Regards,

Charles



On 2 February 2014 15:40, John Murray <john.murray@skyracktelecom.com> wrote:

Charles,

Thanks For that.

How do I get the callid from a call in a specific profile if it is stored in memory?

Regards.

John

On 2 Feb 2014 15:05, "Charles Chance" <charles.chance@sipcentric.com> wrote:

Hi John,

>
> >What db_mode are you using for dialog module?
>
> Mode 5. I Don't need to persist the dialog state so means table maintained in memory and not flushed to disk until shutdown but I can access it through normal avp_db_query right?

Do you mean mode 3? Anyway, avp_db_query is for reading from the database - if you're not persisting dialogs to db in realtime then there'll be nothing to read.

> >Are the entries in the db if you check manually?
>
> If I do sercmd dlg.dlg_list I see the call fine including callid etc.

dlg.list shows all dialogs in memory, not in db.

Regards,

Charles


www.sipcentric.com

Follow us on twitter @sipcentric

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham B7 4EJ.




www.sipcentric.com

Follow us on twitter @sipcentric

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham B7 4EJ.