Thanks Daniel, that's what I'm thinking (dmq).

I'll let you know how I get on!

Cheers,

Charles

On Mar 26, 2013 4:40 PM, "Daniel-Constantin Mierla" <miconda@gmail.com> wrote:
Hello,

On 3/26/13 5:30 PM, Charles Chance wrote:
Hi Daniel,

Yes, dmq is the clear way forward once it's working. Is it a lot of work to get going again? For it to be really useful, I would imagine other modules will need to make use of it from within their code, rather than the user trying to do stuff in the config. I may take a look and see how far along it is.

The others all seem to hinge around dialog:start and dialog:end event routes, but we really need to replicate info about early dialogs too. So I think we'll have to send some notifications from the other routes as well.

Initial dialog event_route was not added because that is practically the moment when dlg_manage() is executed for initial INVITE -- if there is no error executing dlg_manage(), do the actions for initialing the state on the other nodes as well.

Could be easier to add event_routes for add to/remove from profiles -- the information is really small there, replicating it should be easy. Or even skip event routes and replicate directly from inside dialog module using dmq.

Cheers,
Daniel

--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
 - http://conference.kamailio.com -


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.