| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
I don't know of anyway offhand, other than to implement at application layer or use a properly configured RFC3263 DNS setup for failover.Scott
On Tue, Sep 3, 2013 at 1:11 PM, Jorge Bustamante <jorge@xxxxxxxxxxxxxxxxxx> wrote:
_______________________________________________Jorge BustamanteRegards,Is there a way to handle this case with resiprocate so that the failover process is done internally? If so, what would it be?Now, the problem with this approach is we want to add more than one static route for the messages so that if one of them fails, it goes and try the next one in the list and so on. One way to do it was to send some ping message (OPTIONS message perhaps) to the host and wait for the answer, but since this happens asynchronously, this would add some complexity to our program that I believe might be handled internally on lower layers.Hi,Another question for you guys...So, right now we are using SipMessage.forceTarget(...) to set static routes for SIP messages on our program, and it is working fine so far.
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/