Charles hi,

 

That’s what I was trying to get at.

 

I have now set db_mode to 1 however I only get calls in state 4 (active) go into the db not calls in state 2 (ringing).

 

Case is to collect calls in to a specific group of destinations (pick-up  group) into a profile and on receiving a call to a vsc (eg. *98) to get the callid of the first ringing call (state 2) in that group and add a Replaces header and pass it to a B2BUA that would connect the 2 calls. This would allow a user to pick-up a ringing call in the same group on their handset by dialling *98. This would then work for non SIP UA handsets and doesn’t need BLF support etc.

 

All the data is there. When a call is ringing in that group ‘sercmd dlg.dlg_list’ gives all the needed data. I just need access to is from the config script to put it in a header.

 

With db_mode 1 if state 2 calls (ringing) went into the database that would solve the problem although it seems a bit heavyweight. It would be great if I could get all this from memory given that it is there.

 

Any suggestions ?

 

Thanks

 

John

 

From: Charles Chance [mailto:charles.chance@sipcentric.com]
Sent: 03 February 2014 18:13
To: John Murray
Cc: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] dialog list query

 

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.