New subject: [Users] Dispatcher module - Does it actually work?

25 Nov 2005

Correct me if I am wrong here, but the sketchy docs at openser.org seem to imply that I am
going to need to have multiple rows in my mysql table 'gw' for every single user
who places calls? Is that correct? Is there some way to trim this down? 

-----Original Message----- 
From: Andreas Granig [mailto:andreas.granig@inode.info] 
Sent: Thu 11/24/2005 5:24 PM 
To: Douglas Garstang 
Cc: users(a)openser.org 
Subject: Re: [Users] Dispatcher module - Does it actually work?

	Douglas Garstang wrote:
...
  Andy, no. No one has suggested using the lcr module,
and I wasn't even aware of it until you mentioned it just now. I took a look at the
module docs, they're way beyond my current understanding. it. I'll have to do some
reading. Does it allow you to try another route when one is not responding?

	Yes. You have to define a set of destinations which you can load in the
	script using load_gws(), and every call to next_gw() sets the ip/port of
	another destination as ruri, until no more destinations are available.

	You can find an example here:

	        http://linguin.org/ser/lcr_cap/lcr_config_example.txt

	It's for a lcr-version which I have extended a little to be able to
	group destinations according to their capabilities
	(http://linguin.org/ser.php#lcr-cap), but you should at least get the
	idea on how to do it with the vanilla lcr module (just leave out the
	argument in load_gws()).

	Andy

RE: [Users] Dispatcher module - Does it actually work?