Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Resilient TWorker set ??

Status
Not open for further replies.

danramirez

Programmer
Oct 25, 2009
1,136
ES
Guys,

Is there a way to make a TWorker set resilient?

Imagine there are two 3300 controllers and all sets in the office are resilient, i.e if current controller fails sets can register on secondary controller.

In above scenario there is also an MBG and TWorker sets register on one controller. In case that controller fails, is there any way to make TWorker sets to register on sencondary controller??

Thanks in advance, regards,

Daniel

 
I have deployed and it works. The Teleworker is aware of both controllers and the controllers have resiliency to each other. It does fail over, and I you have the option to set the TW endpoint to either controller manually which is nice for troubleshooting issues in one or both controllers.
 
619Tech, I don't get it...

Do you have to set anything in the MBG?

I have already made the MBG aware of the existance of the two controllers.

Extension is already set to be resilient (MCD primary controller)

In MBG, Configured ICP, is pointing to primary controller.

I just dont get how the Tweorker set will be aware that it's got a secondary controller to fail over.

Is this somewhere in the resiliency guide?

Thanks a lot, regards,

Daniel

 
I think you will find that when the primary MCD fails the TW handset will lose its MCD connection and due to the MCD resiliency programmed it will then home to the secondary controller

If I never did anything I'd never done before , I'd never do anything.....
 
Not sure the settings but a teleworker can fail to another controller. Also a teleworker set can fail to another MBG. It might be dependant on the load of the MBG becuase it is a feature ( sets failing ) that was introduced in a particular load. Just don't know which.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top