--- Roy Sigurd Karlsbakk <roy(a)karlsbakk.net>
wrote:
Asterisk does indeed support INVITE auth. I want
all REGISTERs to go to
the asterisk box(es) but I want to allow one of them to die. All data
about the register is stored in a common database between the asterisk
boxes, so it's no problem sharing that.
In the system we use here, all clients register with SER and the invites are forwarded to
Asterisk
only when we need any PBX feature. Normal calls are forwarded by SER alone, which we
found
scalable, as it doesn't handle RTP streams. When the clients register with Asterisk,
all invites
go through Asterisk, which handles media. Of course, we can have Dial statements which
dont
request for pbx features, but designing such a complex dialplan was difficult. Also, we
wanted to
avoid frequent reloads of Asterisk due to the change of dial preferences by users.
Yes. This
is possible. You can have failure routing in your script and
check for the status of
replies and then decide on what to do. Maybe like forwarding calls to
another Asterisk or send to
a voicemail server etc.
probably something like that, or just 'try forward to server A, didn't
work, try server B, etc'
btw, is it possible to schedule this via random or round robin somehow?
AFAIK, there is no such built-in mechanisms to acheive scheduling in a random manner. The
failure
routes follow a sequential order. However, you can implement this feature by adding a
custom-built
module to SER.
Actualy there is a dispatcher module which take a list of servers and
can forward requests to a random server even based on callid so all
incall messages get to the correct server.
=====
Girish Gopinath <gr_sh2003(a)yahoo.com>
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers